Marcela Ruiz

Systematic Derivation of Class Diagrams from Communication-Oriented Business Process Models

Enterprise information systems can be developed following a model-driven paradigm. This way, models that represent the organisational work practice are used to produce models that represent the information system. Current software development methods are starting to provide guidelines for the construction of conceptual models, taking as input requirements models. This paper proposes the integration of two methods: Communication Analysis (a communication-oriented requirements engineering method [1]) and the OO Method (a model-driven object-oriented software development method [2]). For this purpose, a systematic technique for deriving class diagrams from business process models is proposed. The business process specifications (which include message structures) are processed in order to obtain class diagram views, which are integrated to create the class diagram incrementally. Then, using the olivanova framework, software source code can be generated automatically. The paper also discusses the advantages and current limitations of the technique. Results show that, although there is room for improvement, the technique is feasible and it does facilitate the creation of the class diagram.

Integrating the goal and business process perspectives in information system analysis

There are several motivations to promote investment and scientific effort in the integration of intentional and operational perspectives: organisational reengineering, continuous improvement of business processes, alignment among complementary analysis perspectives, information traceability, etc. In this paper we propose the integration of two modelling languages that support the creation of goal and business process models: the i* goal-oriented modelling method and Communication Analysis, a communication-oriented business process modelling method. We describe the methodological integration of the two modelling methods with the aim of fulfilling several criteria: i) to rely on appropriate theories; ii) to provide abstract and concrete syntaxes; iii) to provide scenarios of application; and iv) to develop tool support. We provide guidelines for using the two modelling methods in a top-down analysis scenario. We also present an illustrative case that demonstrates the feasibility of the approach.

Systematic derivation of conceptual models from requirements models: A controlled experiment

There is an open challenge in the area of model-driven requirements engineering. Model transformations that allow deriving (platform-independent) conceptual models from (computation-independent) requirements models are being proposed. However, rigorous assessments of the quality of the resulting conceptual models are needed. This paper reports a controlled experiment that compares the performance of subjects applying two different techniques for deriving object-oriented, UML-compliant conceptual models. We compare the quality of the OO-Method conceptual models obtained by applying a text-based derivation technique (which mimics what OO-Method practitioners actually do in real projects) with the quality obtained by applying a novel communication-based derivation technique (which takes as input Communication Analysis requirements models). The results show that there is an interaction between the derivation technique and the OO-Method modelling competence of the subject: the derivation technique has a significant impact on model completeness within the high-competence group. No impact has been observed on model validity. We also discuss new challenges raised by the evaluation.

Systematic derivation of state machines from communication-oriented business process models

Model-driven development (MDD) is a promising paradigm for enterprise information systems. However, an open research challenge is to successfully integrate requirements practices into the MDD software lifecycle, and an open industrial challenge is to provide proper tool support for the complete software lifecycle. We propose to address these challenges by integrating Communication Analysis, (a communication-oriented requirements engineering method [1]) and the OO-Method (a model-driven object-oriented software development method with full-fledged tool support and successful industrial practice [2]). The OO-Method conceptual model offers four complementary views of the system under construction, which cover the structural, behavioural and presentation aspects. A requirements-based derivation of the Object Model (the structural view which consists of an extended UML Class Diagram) has been defined [3]. This paper builds upon previous work by proposing a systematic technique for deriving the Dynamic Model (the behavioural view which consists of a collection of UML State Machines), taking as input the business process models. Some derivation guidelines are described and its usage is illustrated. The technique has been used in several lab demos that prove its feasibility. Moreover, the conceptual model that results from the structural and behavioural derivation can be used to automatically generate a fully-functional software application. As an additional benefit of the approach, the derivation allows tracing back and forth the elements of the requirements model, the conceptual model, and the final code.

Aligning Communication Analysis with the Unifying Meta-model for Enterprise Modeling

Enterprise Modeling (EM) captures and represents organizational knowledge in models that cover different views of the enterprise. The models can be leveraged in the development of information systems. Investigating how to use them as input to model-driven development (MDD) is an open challenge. This paper explores how a holistic EM approach, represented by a unifying meta-model, can benefit from integrating with Communication Analysis, a communication-oriented business process modeling and requirements engineering method. As a first step towards an integrated EM-enabled MDD approach, the unifying meta-model and Communication Analysis meta-model are aligned. A set of guidelines for transforming models conforming to the unifying meta-model to Communication Analysis models are formulated. The approach is illustrated using a lab demo.

LightCDD: A Lightweight Capability-Driven Development Method for Start-Ups

Novice innovators and entrepreneurs face the risk of designing naive business models. In fact, lack of realism and failing to envision contextual constraints is one of the main threats to start-up success. Both the literature and the responses we gathered from experts in incubation confirm this problem. Capability Driven Development (CDD) is an integrated approach consisting of a method, tools, and best practices. It has proved to be successful when applied to mature enterprises that intend to become context-aware and adaptive. In this paper we report on the application of CDD to two start-up projects and how, despite being useful in making the entrepreneurs aware of dynamic business environments and constraints, a trade-off analysis showed that a simpler version of the method was necessary. Therefore, we present LightCDD, a context-aware enterprise modelling method that is tailored for business model generation. It reduces the set of modelling constructs and guidelines to facilitate its adoption by entrepreneurs, yet keeping it expressive enough for their purposes and, at the same time, compatible with CDD methodology. We also discuss what implications this simplification has with regard to the CDD tool environment.

Model-driven organisational reengineering A framework to support organisational improvement

Companies need to rethink business processes, infrastructures, technologies, staff, etc. according to new demands, strategic goals, and changes in their environment. Information System evolution has been supported by the reengineering process. Since the models are now part of an increasing number of engineering processes and model-driven software development is a well-established paradigm to support information systems, the reengineering process could be improved with the incorporation of the model-driven development paradigm. This paper presents a model-driven organisational reengineering framework to support organisational improvement. The main idea is to get the most out of the existing proposals in model-driven development for the reengineering process (reverse engineering, improvement processes, and forward processes). Methods, techniques, model-driven tools, and perspectives for analysing information systems at a high level of abstraction are presented as a part of this proposal. A reference framework for the reengineering process is established to provide a consistent set of concepts that support the proposed framework. An illustrative example is introduced to present the feasibility of the proposal. The example illustrates the SuperStationery Co. case in order to present a reengineering process to align an existing desk application with a web application that fulfils the strategic goals of the company. Finally, we conclude with an analysis and discussion about lessons learned and future works.

From Requirements to Code: A Full Model-Driven Development Perspective

Models play a paramount role in model-driven development (MDD): several modelling layers allow defining views of the system under construction at different abstraction levels, and model transformations facilitate the transition from one layer to the other. However, how to effectively integrate requirements engineering within model-driven development is still an open research challenge. This paper shows a full MDD approach that covers from requirements engineering to automatic software code generation. This has been achieved by the integration of two methods: Communication Analysis (a communication-oriented requirements engineering method [1]) and the OO Method (a model-driven object-oriented software development method [2]). For this purpose, we have proposed a systematic technique for deriving conceptual models from from business process and requirements models; it allows deriving class diagrams, state-transition diagrams and specifications of class service behaviour. The approach has been evaluated by means of an ontological evaluation, lab demos and controlled experiments; we are currently planning apply it under conditions of practice in an action research endeavour.

LightCDD: Application of a Capability-Driven Development Method for Start-ups Development

Novice innovators and entrepreneurs face the risk of designing naive business models. In fact, lack of viability in business models is perceived to be a major threat for the start-up success. Both the literature and the responses we gathered from experts in incubation present evidences of this problem. The LightCDD method helps entrepreneurs in the analysis, design and specification of start-ups that are context aware and adaptive to contextual changes and evolution. In this article we describe the LightCDD method, a context-aware enterprise modeling method that is tailored for business model generation. The LightCDD applies a lightweight Capability‑Driven Development (CDD) methodology. It reduces the set of modeling constructs and guidelines to facilitate its adoption by entrepreneurs, yet keeping it expressive enough for their purposes and, at the same time, compatible with the CDD methodology. We provide a booklet with the LightCDD method for start-ups development. The feasibility of the LightCDD method is validated by means of its application to one start-up development case. From a practitioner viewpoint (entrepreneurs and experts in incubation), it is important to provide integrative modeling perspectives to specify business ideas, but it is vital to keep it light. The LightCDD is giving a step forward in this direction. From a researcher point of view, the LightCDD booklet facilitates the application of LightCDD to different start-up development cases. The feasibility validation has produced important feedback for further empirical validation exercises in which is necessary to study the scalability and sensitivity of LightCDD.

Supporting organisational evolution by means of model-driven reengineering frameworks

Enterprise systems need to evolve to be adapted with changes in their context. Model-driven reengineering frameworks have been developed in order to support post-delivery life cycle activities and software system maintenance (for instance, architecture-driven modernisation is an object management group initiative). However, existing proposals are general purpose and full support for an organisational reengineering framework is still needed. This paper presents a research effort aiming at designing and developing guidelines and tools for supporting model-driven organisational improvement. We propose to support model evolution by means of two artefacts: a pattern definition metamodel and an evolution metamodel. As a proof of concept, this paper applies the proposal to support business process evolution. We illustrate an instance of these metamodels by means of a laboratory-demo. We also discuss benefits and limitations of our proposal.