A Based-Rule Method to Transform CIM to PIM into MDA

A Based-Rule Method to Transform CIM to PIM into MDA

Yassine Rhazali (Ibn Tofail University, Kenitra, Morocco), Youssef Hadi (Ibn Tofail University, Kenitra, Morocco) and Abdelaziz Mouloudi (Ibn Tofail University, Kenitra, Morocco)
Copyright: © 2016 |Pages: 14
DOI: 10.4018/IJCAC.2016040102
OnDemand PDF Download:
List Price: $37.50


The model transformation is the most interesting part into MDA. Indeed, two transformations exist between three levels of MDA. Most searches cover the transformation from PIM to PSM. However, a little of approaches allow transforming CIM to PIM. This paper represents an approach allows mastering transformation from CIM to PIM into MDA. This approach is based on good CIM level through selected rules allowing provide rich models that facilitate the transformation to PIM level. Afterwards, the authors determine a concentrated PIM level with main design models established through use case diagram, state diagram, and package diagram. Next, to ensure a semi-automatic transformation from CIM to PIM the researchers specify a set of well-chosen transformation rules. For respecting MDA approach the authors consider the business dimension in CIM level by using business modeling standards of OMG (BPMN and activity diagram). However, the researchers focus on UML diagrams to establish PIM models because UML is recommended by MDA in PIM level.
Article Preview

1. Introduction

MDE (Model Driven Engineering) (Schmidt, 2006) is an alternative approach of software engineering. This approach allows the development of software systems by basing on the models. MDE founds on the construction of basic models and transforming them, in order to provide code source automatically. The objective of this approach is to automate the operation of software development that is realized manually by the software experts. MDE is a general methodology which can be supported by several approaches, indeed, MDA (Model Driven Architecture) (OMG-MDA, 2015) of OMG (Object Management Group) is considered as the most prevalent approach. MDA follows the same fundamentals of MDE; however, it identifies its own bases presented by three levels of abstraction, respect of various requirements, and the recommendation of some standards.

CIM (Computation Independent Model) is the highest level of abstraction and the first into MDA. Indeed, CIM level is independent of computation, for this, the researchers represent only the business process reality into this level. CIM models are made by business experts. The second level of abstraction in MDA is the PIM level that describes models useful to information system analysts and designers. PIM (Platform Independent Model) level contains the conceptual models, and sometimes the analysis models, of information system. The lowest level of abstraction in MDA is the PSM (Platform Specific Model) which is constituted by code models; these models are very useful by software developers. The models of PSM level formed of all information related to a specific platform. MDA is a model-based architecture, for this, the textual code does not interpret as a level in MDA, however, source code is the ultimate goal into MDA.

Model transformation presents the key of MDA. The transformations between different levels of MDA start with the transformations from CIM (Computation Independent Mode) to PIM (Platform Independent Model) that allow to partially obtain the PIM models from the CIM models. The objective is to rewrite technically the information contained in the CIM models into PIM models, which enables to ensure that business information is preserved throughout the MDA process. Then, the transformation from PIM level to PSM (Platform Specific Model) level requires adding into PIM models the technical information related to the target platform.

The unique transformation in practice is PIM to PSM transformation. However, our objective consists to make the CIM a productive level, and a basis for manufacturing PIM level through an automatic transformation. Nevertheless, the goal is that business models will not remain simple documents of communication between software designers and business experts.

The researchers propose, in this paper, a solution for automating transformation from CIM level to PIM level, by studying how to use the current standards of business modeling effectively, in order to achieve concentrated CIM models that allow simplifying the transformation to PIM. Next, the authors specify a set of well-selected rules to automate transformation to PIM level.

Our approach based, in CIM level, on UML (Unified Modeling Language) (Miles & Hamilton, 2006) activity diagram and BPMN (Business Process Model and Notation) (OMG-BPMN, 2011) collaboration diagram which represent standards of business process model. Next, through these latter standards the authors can build rich business models that contain well-concentrated information help us to get PIM models. The first model in the PIM level is the use case diagram model that interprets the functionalities of the system. Then, the state diagram model describes information system states. Next, the class diagram model allows presenting the system classes and their relationships. Finally, all classes are structured in packages into package diagram model.

The rest of this paper is organized as follows. In Section 2, the authors describe the related works of the transformation from CIM to PIM. Then, in Section 3, the researchers show the approach, specify the construction rules of CIM level, and describe the transformation rules that allow transforming CIM models to PIM models. Next, in Section 4, the authors illustrate the proposal in a case study showing the establishment of CIM level and transforming it to PIM level. However, in Section 5 the researchers analyze the contributions of the approach compared with related work. Finally, in Section 6, the authors conclude by specifying the current works and by presenting future works.

Complete Article List

Search this Journal:
Open Access Articles: Forthcoming
Volume 7: 4 Issues (2017)
Volume 6: 4 Issues (2016)
Volume 5: 4 Issues (2015)
Volume 4: 4 Issues (2014)
Volume 3: 4 Issues (2013)
Volume 2: 4 Issues (2012)
Volume 1: 4 Issues (2011)
View Complete Journal Contents Listing