Agile or adaptive enterprise architecture driven software development approach requires a modelling standard to describe the existing and to-be developed artifacts both at the high enterprise level and low, detailed level. However, a single modelling standard may not be used off-the-shelf to fully support the modelling needs of an adaptive enterprise architecture driven software development needs. The modelling standards need to be systematically analyzed and integrated for a particular modelling context. This paper reviews two well-known modeling standards ArchiMate and BPMN by using the interoperability research framework. Based on the syntax, semantics and structural analysis of these two modelling standards' metamodels, it proposes a hybrid adaptive enterprise architecture modelling approach for describing and analysing the artifacts both at the high enterprise level and low, detailed level for a particular context. This paper has both theoretical and practical implications for researchers and practitioners pursuing to integrate various modelling standards.
Henderson-Sellers, B., Qureshi, M. & Gonzalez-Perez, C. 2012, 'Towards an interoperable metamodel suite: size assessment as one input', International Journal of Software and Informatics, vol. 6, no. 2, pp. 1-14.View/Download from: UTS OPUS
In recent years, many metamodels have been introduced in the software engi- neering literature and standards. These metamodels vary in their focus across, for example, process, product, organizational and measurement aspects of software development and have typically been developed independently of each other with shared concepts being only accidental. There is thus an increasing concern in the standards communities that possible conicts of structure and semantics between these various metamodels will hinder their widespread adoption. The complexity of these metamodels has also increased significantly and is another barrier in their appreciation. This complexity is compounded when more than one metamodel is used in the lifecycle of a software project. Therefore there is a need to have interoperable metamodels. As a first step towards engendering interoperability and/or possible mergers between metamodels, we examine the size and complexity of various meta- models. To do this, we have used the Rossi and Brinkkemper metrics-based approach to evaluate the size and complexity of several standard metamodels including UML 2.3, BPMN 2.0, ODM, SMM and OSM. The size and complexity of these metamodels is also compared with the previous version of UML, BPMN and Activity diagrams. The comparatively large sizes of BPMN 2.0 and UML 2.3 suggest that future integration with these metamodels might be more difficult than with the other metamodels under study (especially ODM, SSM and OSM).
Several metamodels have been proposed in the software engineering literature recently. For practical usage, it is important to ensure that these metamodels can be used in an interoperable fashion. In this paper we present an approach as a part of our PhD research in the same direction. Our methodology is based on the study of analogous characteristics among metamodels, ontologies and schemas. We have adopted ontology merging and schema matching techniques and apply them to the domain of metamodels to assist in creating interoperable metamodels. This methodology is applied and presented here with an illustrative example in which we show the results of merging two of the OMG metamodels: the Organization Structure Metamodel (OSM) and the Business Process Modelling Notation (BPMN).