Getting the static model of PIM from the CIM

Abstract

In the last few years, Model Driven Architecture (MDA), introduced by the Object Management Group (OMG), has become an important approach that uses models throughout the life cycle of software design and development. It distinguishes four levels: Computation Independent Model (CIM), Platform Independent Model (PIM), Platform Specific Model (PSM) and the code level. Transformations between PIMs and PSMs and code generation from the PIMs are well studied by various researchers.This research focuses on an important part of the transformation from the high level CIM to a PIM level. In this paper we derive the PIM Static Model, which is represented by the Domain Class Model, from a BPMN which is a key artifact of the CIM, using a set of transformation rules. Finally, we will apply our proposal to a case study, to further illustrate how to use these rules.

Alignment of Software System Level with Business Process Level: Resolving Syntactic and Semantic Conflicts

“…Cruz et al [25] present rules to transform a set of business process models into a data model. Kriouile et al [26] describe an approach to transform a BPMN model into a domain class model. Bousetta et al [27] propose an approach for building a domain class diagram based on a BPMN model, using a set of business rules.…”

Aligning Software System Level with Business Process Level through Model-Driven Architecture

“…Cruz et al [23] present rules to transform a set of business process models into a data model. Kriouile et al [24] describe an approach to transform a BPMN model into a domain class model. Bousetta et al [25] propose an approach to building a domain class diagram, based on a BPMN model, using a set of business rules.…”

Processing Use Case Scenarios and Text in a Formal Style as Inputs for TFM-based Transformations

“…Transformation from BPMN models to use cases (Kriouile et al, 2015) to behavioural and domain classes models resulted in complete acquisition of control flows and message flows, however, the domain classes model contained only aggregation relationships obtained from the BPMN pools and lanes (Kriouile et al, 2014). Using structural business rules allows keeping knowledge about terms and facts, as well as relations among them (Bousetta et al, 2013), thus getting necessary static knowledge such as names of classes, compositions and aggregations among them, generalization/specialization relationships, navigations, and multiplicity in associations in semi-automatic way.…”