On Object-Orientation

Although object-orientation has been around for several decades, its key concept abstraction has not been exploited for proper application of object-orientation in other phases of software development than the implementation phase. We mention some issues that lead to a lot of confusion and obscurity with object-orientation and its application in software development. We describe object-orientation as abstract as possible such that it can be applied to all phases of software development

Initial specification of the evaluation tasks "Use cases to bridge validation and benchmarking" PROMISE Deliverable 2.1

Evaluation of multimedia and multilingual information access systems needs to be performed from a usage oriented perspective. This document outlines use cases from the three use case domains of the PROMISE project and gives some initial pointers to how their respective characteristics can be extrapolated to determine and guide evaluation activities, both with respect to benchmarking and to validation of the usage hypotheses. The use cases will be developed further during the course of the evaluation activities and workshops projected to occur in coming CLEF conferences

The Quest for a Practical Sophomore-Level Software Engineering Course

This paper describes our efforts starting since 2014 when we began developing a practical introductory sophomore-level software engineering course. The aim is to guide students into the fundamental theory and practice of building reliable software, with an emphasis on agile and object-oriented practices. Course topics revolve around three main themes: 1) managing complexity (how to model and scale software), 2) achieving quality (how to minimize defects) and 3) supporting usability (how to deliver user functionality). Students are exposed to theoretical and practical aspects of software production, such as software life-cycle models, strong-typing, testing, documentation, graphical user interfaces, UML, design patterns, version control systems and software deployment. The course is in constant evolution: near-future plans include adding build automation tools and DevOps concepts. We made the early decision to use reference materials available to our students at no cost; therefore, all reference materials are accessed online through resources afforded by our library

Formalizing relations between use cases in the unified modeling language

The Unified Modeling Language (UML) is a semi-formal graphical language that has been accepted as standard to model object-oriented software systems. This language defines various kinds of diagrams that are used to describe different aspects or views of a system. In particular, Use Cases diagrams are used to capture the requirements of the systems and to guide their development process. The different Use Cases defined throughout a development process are not independent but it is possible to set relations between them. The main relations considered by UML are the following: Generalization, Include and Extend. These relations as well as the remaining UML constructs are semi-formally defined, giving place to ambiguous interpretations and inconsistencies.\nThis paper presents a formalization that gives precision to the definition of the main relations between Use Cases. This formalization will allow us to check consistency when incrementing the Use Cases model during the software development process and when relating Use Cases model with others modelsÁrea: Informática Teórica - Inteligencia Artificial - Lenguajes - Compiladore

Mapping of oil and gas exploration business data entities for effective operational management

Spatio-temporal data of petroleum resources businesses are heterogeneous in nature with multiple relationships among various entities and attributes. Object oriented (OO) systems provide alternative solutions for handling the complex exploration business data entities, where traditional database systems pose serious limitations. Exploration, which is a key business object class in any petroleum business environment, is composed of several sub classes, such as navigation, seismic, vertical seismic profiling (VSP), well-log and reservoir. Authors classify these typical spatio-temporal data items as classes and sub class objects in the OO modelling. In the present paper, logical entity relationship (ER) models have been re-written in multidimensional and object-oriented models. Syntax of typical exploration data object classes, attributes, operations and their relationships has been described for implementation purposes. This work demonstrates how object class logical data models are flexible and interoperable for fast changing petroleum business situations. Models presented in this paper, guide exploration data managers for effectively managing their operations. An OLAP model discussed in this paper is a pursuit of cost saving detailed exploration for oil and gas prospect investigation in any basin

Methodology for object-oriented real-time systems analysis and design: Software engineering

Successful application of software engineering methodologies requires an integrated analysis and design life-cycle in which the various phases flow smoothly 'seamlessly' from analysis through design to implementation. Furthermore, different analysis methodologies often lead to different structuring of the system so that the transition from analysis to design may be awkward depending on the design methodology to be used. This is especially important when object-oriented programming is to be used for implementation when the original specification and perhaps high-level design is non-object oriented. Two approaches to real-time systems analysis which can lead to an object-oriented design are contrasted: (1) modeling the system using structured analysis with real-time extensions which emphasizes data and control flows followed by the abstraction of objects where the operations or methods of the objects correspond to processes in the data flow diagrams and then design in terms of these objects; and (2) modeling the system from the beginning as a set of naturally occurring concurrent entities (objects) each having its own time-behavior defined by a set of states and state-transition rules and seamlessly transforming the analysis models into high-level design models. A new concept of a 'real-time systems-analysis object' is introduced and becomes the basic building block of a series of seamlessly-connected models which progress from the object-oriented real-time systems analysis and design system analysis logical models through the physical architectural models and the high-level design stages. The methodology is appropriate to the overall specification including hardware and software modules. In software modules, the systems analysis objects are transformed into software objects

Warehousing of object oriented petroleum data for knowledge mapping

Australia produces a-third of world?s natural resources. Enormous amounts of energy and financial resources are expended in order to tap these natural reserves from the earth?s surface. Vast amounts of these resources, however, remain unexplored and under exploited. Data pertaining natural resources, such as mineral and petroleum, are, in general, heterogeneous and complex in nature. Volumes of these types of data are geographically distributed among many companies in Australia and abroad. The existing historical resources data are logically and physically organized using warehousing techniques. Entity relationship (ER) and object oriented (OO) data mapping techniques are used for analyzing the data entities, dimensions and objects. In this paper object oriented data and warehousing of object class data models have been described. Data mining techniques can be employed to explore many more resources hidden, under great depths of the earth?s crust, without additional efforts of exploration and development. Warehoused object oriented resources data can significantly reduce the complexity of the resources data structuring and enhance the data integration and information sharing among various operational units of the resources industry. Large amount of financial inputs can be saved if these technologies are successfully implemented in the resources industry

Criticality estimation of IT business functions with the Business Continuity Testing Points method for implementing effective recovery exercises of crisis scenarios

The primary goal of the present paper is the introduction of a new approach of defining IT unit business functions exact criticality levels and respectively categorize them to the appropriate recovery tests, prior to their thorough documentation which includes actual desired recovery time frames. The method is entitled as Business Continuity Testing Points and it is based on the concept of Use Case Points, a fundamental project estimation tool utilized for sizing of object-oriented system development. The aim of the contribution is to ameliorate the existing manual way of determining recovery time of IT business functions that is based exclusively on experience of IT personnel, by introducing a calculation method of multiple factors that can negatively affect the recovery process. The elimination of damage as a result of tested immediate response action in a crisis situation that disrupts core IT operations constitutes the aimed advantage of the proposed contributionComment: 9 pages. International Journal of Computer Science Issues, 201

Formalizing relations between use cases in the unified modeling language

The Unified Modeling Language (UML) is a semi-formal graphical language that has been accepted as standard to model object-oriented software systems. This language defines various kinds of diagrams that are used to describe different aspects or views of a system. In particular, Use Cases diagrams are used to capture the requirements of the systems and to guide their development process. The different Use Cases defined throughout a development process are not independent but it is possible to set relations between them. The main relations considered by UML are the following: Generalization, Include and Extend. These relations as well as the remaining UML constructs are semi-formally defined, giving place to ambiguous interpretations and inconsistencies. This paper presents a formalization that gives precision to the definition of the main relations between Use Cases. This formalization will allow us to check consistency when incrementing the Use Cases model during the software development process and when relating Use Cases model with others modelsÁrea: Informática Teórica - Inteligencia Artificial - Lenguajes - CompiladoresRed de Universidades con Carreras en Informática (RedUNCI

A coalgebraic semantic framework for component-based development in UML

This paper introduces a generic semantic framework for component-based development, expressed in the unified modelling language UML. The principles of a coalgebraic semantics for class, object and statechart diagrams as well as for use cases, are developed. It is also discussed how to formalize the refinement steps in the development process based upon a suitable notion of behavior refinement. In this way, a formal basis for component-based development in UML is studied, which allows the construction of more complex and specific systems from independent components.FCT -Fuel Cell Technologies Program(POSI/ICHS/44304/2002