A method to build information systems engineering process metamodels

Abstract

To cite this version:Charlotte Hug, Agnès Front, Dominique Rieu, Brian Henderson-Sellers. A method to build information systems engineering process metamodels. Journal of Systems and Software, Elsevier, 2009, 82 (10) Abstract: Several process metamodels exist. Each of them presents a different viewpoint of the same information systems engineering process. However, there are no existing correspondences between them. We propose a method to build unified, fitted and multi-viewpoint process metamodels for information systems engineering. Our method is based on a process domain metamodel that contains the main concepts of information systems engineering process field. This process domain metamodel helps selecting the needed metamodel concepts for a particular situational context. Our method is also based on patterns to refine the process metamodel. The process metamodel can then be instantiated according to the organisation's needs. The resulting method is represented as a pattern system.

ProMISE: A Process Metamodelling Method for Information Systems Engineering

“…The existing process metamodels are also fixed [10]. They do not allow method engineers to extend them or customize them.…”

“…It was built from a Process Domain Metamodel and a 3D Space [8], [9], [10]. A study [10], [11] of the different existing process metamodels (activity oriented [12]; [13]; [14]; [15]; [16]) such as SPEM, product oriented [17]; [18]; [19]; [1] such as Statechart and State Machines, decision oriented [20]; [21]; [22]; [23] like Ibis and Daida, context oriented [24] such as NATURE and strategy oriented [25] like MAP), allowed us to define a Process Domain Metamodel which only contains the main classes of existing process metamodels and the associations between the concepts. In order to facilitate the classes' selection from the Process Domain Metamodel, we propose the use of a conceptual graph that allows method engineers to easily navigate between the concepts.…”

“…However, existing process metamodels are hardly adaptable and are defined independently of one another [8], [9], [10]. Upon modelling the process models of their organizations, method engineers have to use those already predefined process models or to instantiate process metamodels without adaptation possibilities; the resulting models might be partially inadequate to the organizations specificities and constraints and to their business activities.…”

Towards a Methodological Tool Support for Modeling Security-Oriented Processes

“…Different process metamodels are proposed [8,12] for modeling software engineering processes. These process metamodels are divided into different categories according to [7]. The viewpoint of process metamodel concentrates different aspects of methodologies that are used by these metamodels.…”

A Governance Framework for Mitigating Risks and Uncertainty in Collaborative Business Processes

“…Recent years have seen the development of many Information System-based business process engineering methods, such as the activity-oriented, product-oriented, decision-oriented, context-oriented and strategy-oriented process meta-models that can be selected and combined [3]. To cope with interoperability constraints involved by collaborative / federated business development, standardized modeling languages can also be used [4].…”