Integration of Communication Analysis and the OO-Method: Rules for the manual derivation of the Conceptual Model

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 [Espa\~na, Gonz\'alez et al. 2009]) and the OO-Method (a model-driven object-oriented software development method [Pastor and Molina 2007]). For this purpose, a systematic technique for deriving OO-Method Conceptual Models from business process and requirements models is proposed. The business process specifications (which include message structures) are processed in order to obtain static and dynamic views of the computerised information system. Then, using the OLIVANOVA framework, software source code can be generated automatically [CARE Technologies].

[1]  Nelly Condori-Fernández,et al.  An empirical comparative evaluation of requirements engineering methods , 2010, Journal of the Brazilian Computer Society.

[2]  Shahbaz Maqbool,et al.  Transformation of a core scenario model and activity diagrams into Petri nets , 2005 .

[3]  Alexander Raschke.  Translation of UML 2 Activity Diagrams into Finite State Machines for Model Checking , 2009, 2009 35th Euromicro Conference on Software Engineering and Advanced Applications.

[4]  Juan Sánchez,et al.  Conceptual Modeling Based on Transformation Linguistic Patterns , 2005, ER.

[5]  John C. Henderson,et al.  Strategic Alignment: Leveraging Information Technology for Transforming Organizations , 1993, IBM Syst. J..

[6]  Juan Sánchez,et al.  System Modeling from Extended Task Descriptions , 2010, SEKE.

[7]  Rik Eshuis,et al.  Symbolic model checking of UML activity diagrams , 2006, TSEM.

[8]  A. B. Kahn,et al.  Topological sorting of large networks , 1962, CACM.

[9]  Elvinia Riccobene,et al.  An ASM Semantics for UML Activity Diagrams , 2000, AMAST.

[10]  Oscar Pastor,et al.  Model-driven architecture in practice - a software production environment based on conceptual modeling , 2007 .

[11]  Georg Kösters,et al.  Coupling Use Cases and Class Models as a Means for Validation and Verification of Requirements Specifications , 2001, Requirements Engineering.

[12]  John C. Henderson,et al.  Strategic Alignment: Leveraging Information Technology for Transforming Organizations , 1999, IBM Syst. J..

[13]  Oscar Pastor,et al.  Systematic Derivation of Class Diagrams from Communication-Oriented Business Process Models , 2011, BMMDS/EMMSAD.

[14]  Oscar Pastor,et al.  Communication Analysis: A Requirements Engineering Method for Information Systems , 2009, CAiSE.

[15]  Oscar Pastor,et al.  Integration of Communication Analysis and the OO Method: Manual derivation of the Conceptual Model. The SuperStationery Co. lab demo , 2011, ArXiv.

[16]  Oscar Pastor,et al.  Systematic derivation of state machines from communication-oriented business process models , 2011, 2011 FIFTH INTERNATIONAL CONFERENCE ON RESEARCH CHALLENGES IN INFORMATION SCIENCE.