International conference Advanced Information Technology, Services and Systems (AIT2S-15)

Establishing Business View and Transform it to Information System View Using DFD and UML Yassine Rhazali MISC Laboratory Faculty of science Kenitra Ibn Tofail University Kenitra – MOROCCO [email protected]

Youssef Hadi

Abdelaziz Mouloudi

MISC Laboratory Faculty of science Kenitra Ibn Tofail University Kenitra – MOROCCO [email protected]

MISC Laboratory Faculty of science Kenitra Ibn Tofail University Kenitra – MOROCCO [email protected]

which represent standards of business model to define the CIM level. Then the rich business models of well-concentrated information help us to achieve models of PIM level. The first model of the PIM level is the use case diagram model. Then, the class diagram model allows modeling the system classes and their relationships independently of a programming language. Finally, all classes are structured in packages into package diagram model.

Abstract—This paper proposes a model transformation method to master transformation of CIM to PIM in accordance with the MDA approach. Our approach is founded on building a good CIM level via well-defined rules, allowing us to win precious models that facilitate the task of the transformation from CIM level to PIM level. Next, we define a set of well- selected rules to shift from CIM to PIM so as to ensure a semi-automatic transformation. This method follows the recommendations of the MDA approach by take into consideration the business dimension in the CIM level through the use the business modeling standards of OMG, and by take into account the UML advocated by MDA into PIM level.

The rest of this paper is organized as follows. Section II analyzes the related works of the CIM transformation to PIM. Section III presents our approach and describes the rules for constructing models of CIM level and the rules for transformation from the CIM level to the PIM level. In Section IV we illustrate our proposal in a case study showing the construction of the CIM level and the transformation to the PIM level. Finally, in Section V, we conclude by determining the outcome of our work and describing future works.

Keywords—model transformation; MDA; CIM ; PIM; business processes

I.

INTRODUCTION

Transformations between the different levels of MDA (Model Driven Architecture) [1] begin with the transformations from CIM (Computation Independent Mode) to PIM (Platform Independent Model) that aim to partially build PIM models from CIM models. The goal is to rewrite the information contained in the CIM models into PIM models which would ensure that business information is conveyed and respected throughout the MDE process [4]. Then, the transformation of PIM models to PSM models adds PIM technical information related to a target platform.

II.

RELATED WORK

In this section, we are going to shed light on the related works concerning the passage of the CIM level to the PIM level in MDA. The oriented service transformation from CIM to PIM was proposed by Castro et al. [6]. The authors present the CIM level using BPMN [3] for modeling business process and the value model [5] so as to identify services from the beginning in the business perspective. Through the ATL (atlas transformation language) language, the authors move towards a PIM level presented by two extensions of use case model and two extensions of the activity diagram.

In practice, the automatic transformation starts from the second PIM level. The goal is that business models do not remain a simple documents of communication between business experts and software designers. However, our ultimate objective is to make the CIM level a productive one, and also a basis for building PIM level through an automatic processing.

A transformation approach from CIM to PIM based on security requirements from the beginning in the business perspective is presented by Rodríguez et al. [7]. The authors use the BPMN notation for modeling business processes secure of the CIM level; then, they determine the transformations in QVT (query view transformation) [12] in order to obtain class diagrams and use case.

In this paper, we propose a solution to induce the automation of the transformation of CIM level to the PIM level by studying how to use the current standards of business modeling effectively so as to achieve focused CIM models to simplify the transformation to PIM. Then, we define a set of rules to automate the transformation to a PIM level.

Hahn et al. [9] focus on engineering services driven by models. The authors present the CIM level with BPMN notation and establish the ATL language to achieve a

Our approach uses the DFD (data flow diagram) [19] and the UML 2 (Unified Modeling Language) [2] activity diagram

11

International conference Advanced Information Technology, Services and Systems (AIT2S-15) transformation to the PIM level represented in this approach by using SoaML models.

models to preserve the business knowledge during the transformation to the PIM level in order to achieve a quality information system.

Zhang et al. [10] describe an approach in which the CIM and PIM are respectively represented by functionalities and components. Responsibilities in this demarche are considered as connectors between functionalities and components to simplify the task of transforming CIM to PIM. Grammel and Kastenholz [11] rely on a DSL connection, which focuses on the management of traceability in general.

In this approach, we do not use DFD and UML 2 activity diagram just to present an approach that uses both standard modeling business processes, but we try to take advantage of each one to achieve a rich and concentrated level, which simplifies our transformation to the PIM level. MDA recommends the use of UML in the PIM level. The use case diagram model present the information system functionalities, however, class diagram shows the structure of the information system, then, we organize all classes in packages themselves transformed since the CIM level.

An approach respecting MDA which aims at transforming the diagram of use case to the activity diagram is proposed by Gutiérrez et al. [13]. The authors use QVT to transform existing use cases to the activity diagram. Mazon et al. [14] propose an objective-oriented approach by defining a UML profile to present the CIM level, based on the i* modeling framework . The authors use QVT to move towards the PIM that focuses on conceptual modeling of data warehouse.

All models of the PIM level are realized through an automatic transformation of CIM level, via well-defined and concentrated transformation rules. Below, we present the rules of construction of CIM level and the rules of transformation to the PIM level.

Kherraf et al. [8] propose a disciplined approach to transform the CIM to PIM using the business process model and use case diagram as an initial step in the modeling of business processes, then a detailed activity diagram which defines the system requirements which represents the last step in the CIM level. The elements of the requirements’ model are transformed as components of the system. These are presented in the component diagram as a first step in the PIM level. Finally, a set of business archetypes helps to transform the system components to obtain the class diagram.

A. Construction Rules of CIM Level The rules for constructing the model of DFD: • Define means and not complex processes, i.e., each process must not contain other processes. In fact, each process must be comprised of about 4 to 12 tasks.

Kardos et al. [15] present an analytical method for the transformation of CIM to PIM in MDA. The authors define the CIM level through the data flow diagram; then they use the use case diagram to initiate the information system view. This approach also defines a model of activity diagram as well as a model of sequence diagram and finally a model class diagram. An approach for transforming business process models to PIM is presented by Rhazali et al. [16, 17, 18]. The author based on BPMN to model business process in CIM-level. However, PIM-level is presented by UML 2 use case diagram model, state diagram model and class diagram model. III.

•

If a sub-process consists of less than 4 tasks, or represents a complementary operation to another process, we merge two processes into one.

•

Coloring manual processes with another color for example we used the gray.

•

The model presents a description of the most common business processes.

•

Identify the maximum possible of the actors who interact and who collaborate in the achievement of business processes since we talk about an enterprise process.

The rules of construction of activity diagram model: • Detail individually each process in a model as several

PROPOSED METHOD OF TRANSFORMATION FROM CIM TO PIM

Our proposal considers the business dimension in the CIM presentation level through the use of real high-level business

Fig. 1. Schema of passage from DFD model and activity diagram model to use case diagram model

12

International conference Advanced Information Technology, Services and Systems (AIT2S-15)

Fig. 2. Schema of passage from DFD model and class diagram model to package diagram model

• Each process of DFD model is transformed to a package which includes the use cases corresponding to the actions of this process.

actions (this latter constitute the fundamental unit in the activity diagram). • In activity diagram model do not represent the manual tasks of DFD model. •

The rules of passage from the model of activity diagram to the model of class diagram (cf. Fig. 2): • Transform object nodes of model activity diagram as classes.

Present connections in this model.

• Enrich this model with the most exceptional ways. • Add an object node containing object state at the output of each action.

• Each state of an object becomes a class method. The rules of passage from the model of Data Flow Diagram and the model of class diagram to the model of package diagram (cf. Fig. 4): • Each process transforms to a package

B. Transformation Rules from CIM to PIM The rules of passage from the CIM level models to model of use case diagram (cf. Figure 1): • Every action of the model activity diagram that corresponds to a functionality of the system is transformed to the use case.

• Classes resulting from the same process will be placed in the package that corresponds to the processes. IV. CASE STUDY

• The collaborator, who realizes the process of the model of DFD, becomes an actor of use cases that correspond to the actions of this process.

In this section, we present a case study for sales through ecommerce to illustrate our approach of transforming the CIM level to the PIM level.

• If there is a "decision node" between two actions, the corresponding use cases are connected by a relationship "extend".

A customer can browse the catalog of products available. He can also see detailed information about each item, then he decides either to put a quantity of product in the cart or not. Each time the customer has the right to change the amount or eliminate completely the article from the cart. Once products that satisfied the needs of the customer are clearly selected, the latter starts the command. Then, he presents the payment information, and precise details of delivery. assembly worker collects reserved items, manually, from stock. The assembly team leader checks quantity and quality of each product. Then the delivery agent carries the confirmed order, so that the customer gets his ordered products.

• If there is just a control flow between two actions, the corresponding use cases are connected by a relationship "include". • Do not transform the control flow returning back. An order agent begins treating the order, declaring the reservation of products specified by the customer. Then, the

A. Presentation of the CIM Level Fig. 4 shows the model of the business process represented by Data Flow Diagram. In this model we just specified processes and their sequence to present a business process in general. We have presented the maximum of business actors to define a true business process, in which there is collaboration between several business actors. For example, instead of putting a single external "delivery service", we Fig. 3. Schema of passage from activity diagram model to class diagram model

13

International conference Advanced Information Technology, Services and Systems (AIT2S-15) identified the externals: "assembly worker", "assembly team leader" and "delivery agent".

B. Presentation of the PIM level Fig. 6 presents a model of diagram use case, Fig. 7 shows the final objective of the PIM level which is the construction of a model of class diagram. Fig. 8 shows a model of the package diagram.

Fig. 6. Use case diagram model of “select products of order”.

Fig. 7. Class diagram model of “select products of order”. Fig. 4. Data flow diagram model of “sales through e-commerce”.

Fig. 8. Package diagram model of “sales through e-commerce”.

V. ANALYSIS AND DISCUSSION Concerning the works of passage from CIM level to PIM level, we can classify the works into five categories. We find researches use, early in CIM level, the requirements models which represent the system requirements (through use case diagram) to facilitate the transformation to PIM [13, 8]. Then, other studies [6, 9], even if they define the business processes in CIM level, do not represent the structural view usually (through the class diagram) that represents the goal of the PIM level. Then there are methods that target transformation in a particular field [7, 14], like in [14] the authors use QVT to move to the PIM that focuses on conceptual modeling of data warehouse, however, this approach only tackles the transformation in the field of data warehouse. There are also methods such as [15] which represent the structural view in the PIM level and are not intended for a particular area, but the authors show a case study of a transformation to the PIM level without mentioning the rules used in the transformation. Next,

Fig. 5. detailled model of activity diagram of “select products of order”.

Fig. 5 shows the second model in CIM level as a model of activity diagram. Through this model we individually detail each process of the previous model as several actions. However, in this model the process "select product for order" is analyzed. Also, we have identified all possible ways towards connections. Then we presented an object node with its state in the output of each action.

14

International conference Advanced Information Technology, Services and Systems (AIT2S-15) there are methods [10, 11] that define exactly the transformation rules and do not have the models used in the CIM and PIM level.

[10]

In [20, 21, 22, 23, 24, 25, 26] the authors propose interesting approach concerning transformation from CIM to PIM, but it is based on BPMN to create the CIM level for this the authors are limited when transforming the CIM level into the PIM level.

[11]

[12]

So we can say that the main contributions of our study in comparison with others as follow: the business process model is used in CIM level. Then, we define the structural view in PIM level (through using class and package models). Next, we propose an approach of generic transformation that is not related to a particular field. Finally, our approach has clear rules to achieve, the maximum possible, automatic transformation from CIM to PIM.

[13]

[14]

[15]

VI. CONCLUSIONS AND FUTURE WORK One of the major challenges in the software development process is the definition of an approach that allows moving from models that describe the operation of business to models which present the analysis and design of software.

[16]

Based on MDA, our approach provides a solution to the problem of transformation of business models represented in CIM level to analysis and design models, modeled in PIM level. This approach results in a set of well organized and useful classes in the process of software development.

[17]

[18]

The ongoing work is intended to improve the rules of construction of the CIM and the rules of transformation to the PIM in order to implement these transformations to a tool via the ATL language. In addition, in our future work, we plan to transform the models obtained in the PIM to models of PSM (Platform Specific Model) level, since our ultimate goal is to provide the source code from the business models through automatic transformations.

[19] L. Qing, and Y.L. Chen,”Modeling

and Analysis of Enterprise and Information Systems”. Beijing : Higher Education Press,2009

[20] Y. Rhazali, Y. Hadi, and A. Mouloudi, “Methodology for Transforming CIM to PIM through UML: From Business View to Information System View,” presented at the IEEE Third World Conference on Complex Systems, Marakech, Morocco, 2015. [21] Y. Rhazali, Y. Hadi, and A. Mouloudi, A Methodology of Model Transformation in MDA: from CIM to PIM, International Review on Computers and Software, Vol. 10, No. 12, pp. 1186-1201, 2015. [22] Y. Rhazali, Y. Hadi, and A. Mouloudi, A Based-Rule Method to Transform CIM to PIM into MDA, International Journal of Cloud Applications and Computing, Vol. 6, No. 2, 2016. [23] Y. Rhazali, Y. Hadi, A. Mouloudi, A New Methodology CIM to PIM Transformation Resulting from an Analytical Survey, in 4th International Conference on Model-Driven Engineering and Software Development, Rome, Italy, 2016, pp. 266 - 273. [24] Y. Rhazali, Y. Hadi, and A. Mouloudi, CIM to PIM Transformation in MDA: from Service-Oriented Business Models to Web-Based Design Models, International Journal of Software Engineering and Its Applications, Vol. 10, No.4, 2016, pp 125-142. [25] Y. Rhazali, Y. Hadi, A. Mouloudi, “Model Transformation with ATL into MDA from CIM to PIM Structured through MVC”, Procedia Computer Science - Journal - Elsevier Vol. 83, pp. 1096–1101, 2016. [26] Y. Rhazali, Y. Hadi, and A. Mouloudi, A Methodology for Transforming Models from Computing Independent Model to Platform Independent Model, Advances in Information Technology : Theory and Application, Vol. 1, No. 1 , 2016. [27] Y. Rhazali, Y. Hadi, A. Mouloudi, A Model Transformation According Model Driven Architecture, in 3rd International Conference on Computing Engineering & Enterprise Management (ICCEEM-2015), Tetouan, Morocco, 2015, pp. 6 - 14.

REFERENCES [1] [2] [3] [4] [5]

[6]

[7]

[8]

[9]

presented at Proceedings of the 4th Workshop on Agent-based Technologies and applications for enterprise interoperability, Toronto, Canada, 2010, pp. 13–24. W. Zhang, H. Mei, H. Zhao, and J. Yang, “Transformation from CIM to PIM: a feature-oriented component-based approach,” presented at MoDELS 2005, Montego Bay, Jamaica, 2005. B. Grammel, and S. Kastenholz, “A generic traceability framework for facet-based traceability data extraction in model-driven software development,” presented at the 6th ECMFA Traceability Workshop held in conjunction ECMFA 2010, Paris, France, 2010, pp. 7–14. OMG, “MOF 2.0 Query/View/Transformation (QVT)”, V1.0. OMG Document – formal/08-04-03, 2008. J. J. Gutiérrez, C. Nebut, M. J. Escalona, M. Mejías, and I. M. Ramos, “Visualization of use cases through automatically generated activity diagrams,” presented at 11th international conference on Model Driven Engineering Languages and Systems, France, 2008, pp. 83-96 . J. Mazón, J. Pardillo, and J. Trujillo, “A model-driven goal-oriented requirement engineering approach for data warehouses,” presented at the Conference on Advances in Conceptual Modeling: Foundations and Applications, Auckland, New Zealand, 2007, pp. 255–264. M. Kardoš, and M. Drozdová, “Analytical method of CIM to PIM transformation in model driven architecture (MDA),” : JIOS, VOL. 34, NO. 1, 2010, pp. 89-99. Y. Rhazali, Y. Hadi, A. Mouloudi, Transformation Method CIM to PIM: From Business Processes Models Defined in BPMN to Use Case and Class Models Defined in UML, International Journal of Computer, Electrical, Automation, Control and Information Engineering, Vol. 8, n. 8, pp. 1453–1457, 2014. Y. Rhazali, Y. Hadi, and A. Mouloudi, “Disciplined Approach for Transformation CIM to PIM in MDA,” presented at 3rd International Conference on Model-Driven Engineering and Software Development, Angers, France, 2015, pp. 312 - 320. Y. Rhazali, Y. Hadi, and A. Mouloudi, “ Transformation Approach CIM to PIM: From Business Processes Models to State Machine and Package Models,” presented at the 1st International Conference on Open Source Software Computing, Amman, Jordan,2015.

OMG-MDA, "MDA Guide Version 1.0.1," 1 juin 2003. OMG, UML Superstructure 2.0. OMG Adopted Specification ptc/03-0802, 2003. . OMG, “Business Process Modelling Notation”, Version 2.0, 2011. C. Schmidt, “COVER FEATURE Model Driven Engineering”, 2006. J. Gordijn, and J. M. Akkermans, “Value based requirements engineering: exploring innovative e-commerce idea,” Requirements Engineering Journal 8 (2), 2003, pp. 114–134. V. D. Castro, E. Marcos, and J. M. Vara, “Applying CIM-to-PIM model transformations for the service-oriented development of information systems,” presented at 2nd Information and Software Technology, 2011, pp. 87–105. A. Rodríguez, I. García-Rodríguez de Guzmán, E. Fernández Medina, and M. Piattini, “Semi-formal transformation of secure business processes into analysis class and use case models: an MDA approach,” presented at 9th Information and Software Technology 52, 2010, pp. 945–971. S. Kherraf, E. Lefebvre, and W. Suryn, “Transformation from CIM to PIM using patterns and archetypes,” presented at 19th Australian Conference on Software Engineering, 2008,pp. 338-346. C. Hahn, P. Dmytro, and K. Fischer, “A model-driven approach to close the gap between business requirements and agent-based execution,”

15