A Brief History of the Object-Oriented Approach

Unlike other fads, the object-oriented paradigm is here to stay. The road towards an object-oriented approach is described and several object-oriented programming languages are reviewed. Since the object-oriented paradigm promised to revolutionize software development, in the 1990s, demand for object-oriented software systems increased dramatically; consequently, several methodologies have been proposed to support software development based on thatparadigm. Also presented are a survey and a classification schemefor object-oriented methodologies

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

Iterative criteria-based approach to engineering the requirements of software development methodologies

Software engineering endeavours are typically based on and governed by the requirements of the target software; requirements identification is therefore an integral part of software development methodologies. Similarly, engineering a software development methodology (SDM) involves the identification of the requirements of the target methodology. Methodology engineering approaches pay special attention to this issue; however, they make little use of existing methodologies as sources of insight into methodology requirements. The authors propose an iterative method for eliciting and specifying the requirements of a SDM using existing methodologies as supplementary resources. The method is performed as the analysis phase of a methodology engineering process aimed at the ultimate design and implementation of a target methodology. An initial set of requirements is first identified through analysing the characteristics of the development situation at hand and/or via delineating the general features desirable in the target methodology. These initial requirements are used as evaluation criteria; refined through iterative application to a select set of relevant methodologies. The finalised criteria highlight the qualities that the target methodology is expected to possess, and are therefore used as a basis for de. ning the final set of requirements. In an example, the authors demonstrate how the proposed elicitation process can be used for identifying the requirements of a general object-oriented SDM. Owing to its basis in knowledge gained from existing methodologies and practices, the proposed method can help methodology engineers produce a set of requirements that is not only more complete in span, but also more concrete and rigorous

Industry 4.0 and Object-Oriented Development: Incremental and Architectural Change

Industry 4.0 in manufacturing is about combining cyber-physical systems with industrial automation systems. This integration of systems so different in nature aims to create context-aware factories in which people and machines are in real-time alignment. This paper examines the change processes triggered by Industry 4.0 from a conceptual perspective. We find that the observed patterns of change are not novel but have a lot in common with the paradigmatic shift in software development from structured to object-oriented development. The latter approach features to be incremental in the production phase and architectural in the product and process design phase. We argue that Industry 4.0 will be equally paradigmatic and mind-set changing for architects and engineers as to crafting production processes and creating products for the futur

Aspect-Oriented Business Process Modeling Approaches: An assessment of AOP4ST

Aspect-oriented business process modeling (AOBPM) is an emerging discipline which has recently attracted the attention of researchers and professionals. In 2014, Amin Jalali reviewed the state of the art of AOBPM and proposed a framework to assess the available approaches. We have developed AOP4ST, an aspect-oriented process for the software development life cycle, which includes the business process modeling as its first phase, and which follows the Jalali’s recommendations. In this paper, we present the assessment of the AOP4ST’s business modeling capability by comparing it with all of the original proposals assessed by Jalali’s framework. Finally, we present ongoing work for the improvement of our approach on its AOBPM capabilities and its ability to detect and separate concerns at early stages of the development.Sociedad Argentina de Informática e Investigación Operativ

Aspect-Oriented Business Process Modeling Approaches: An assessment of AOP4ST

Aspect-oriented business process modeling (AOBPM) is an emerging discipline which has recently attracted the attention of researchers and professionals. In 2014, Amin Jalali reviewed the state of the art of AOBPM and proposed a framework to assess the available approaches. We have developed AOP4ST, an aspect-oriented process for the software development life cycle, which includes the business process modeling as its first phase, and which follows the Jalali’s recommendations. In this paper, we present the assessment of the AOP4ST’s business modeling capability by comparing it with all of the original proposals assessed by Jalali’s framework. Finally, we present ongoing work for the improvement of our approach on its AOBPM capabilities and its ability to detect and separate concerns at early stages of the development.Sociedad Argentina de Informática e Investigación Operativ

Early aspects in “Aspect-Oriented Process for a Smooth Transition”

The aspect-oriented paradigm brought new expectations about building software in a modular way and improving many quality attributes, but it also came with new challenges. One of them is the lack of casuistry of its use in the industry. Software development project leaders are already facing enough risks and should not add more, such as incorporating an immature approach. Furthermore, there are no aspect-oriented proposals using standard notations and covering the full Software Development Life Cycle (SDLC). We have elaborated an alternative called Aspect-Oriented Process for a Smooth Transition (AOP4ST), that allows the smoothly incorporation of the aspectoriented paradigm in the current industrial projects and offers a complete homogenous proposal for the phases of the SDLC. In this paper, we present the first stages of AOP4ST, seeking the incorporation of the aspect-oriented paradigm in the industry with the least impact, but trying to take full advantage of the possibilities it offers.XIV Workshop de Ingeniería de Software (WIS).Red de Universidades con Carreras en Informática (RedUNCI

Aspect-Oriented Business Process Modeling Approaches: An assessment of AOP4ST

Aspect-oriented business process modeling (AOBPM) is an emerging discipline which has recently attracted the attention of researchers and professionals. In 2014, Amin Jalali reviewed the state of the art of AOBPM and proposed a framework to assess the available approaches. We have developed AOP4ST, an aspect-oriented process for the software development life cycle, which includes the business process modeling as its first phase, and which follows the Jalali’s recommendations. In this paper, we present the assessment of the AOP4ST’s business modeling capability by comparing it with all of the original proposals assessed by Jalali’s framework. Finally, we present ongoing work for the improvement of our approach on its AOBPM capabilities and its ability to detect and separate concerns at early stages of the development.Sociedad Argentina de Informática e Investigación Operativ