Transformation from CIM to PIM Using Patterns and Archetypes (original) (raw)
Related papers
Applying a Model Driven Architecture Approach: Transforming CIM to PIM Using UML
International Journal of Online Engineering (iJOE), 2018
Over the last few years, as they evolve with business needs and technology, enterprises are faced with the need to adapt their business processes to work in open settings. In such settings, the automation and the interoperability of business process and applications become a key concern. The Model Driven Architecture (MDA) is introduced as an approach to cope with this challenge. MDA specifies four levels of abstraction, most of the existing studies focus on modeling and transforming the Platform-Independent Model (PIM) to Platform-Specific Model (PSM) levels, while the more conceptual level, the Computation-Independent Model (CIM) is often presumed as present and is not further studied. In this paper, we propose an approach for transforming a CIM into a PIM using the core modeling concepts of the Unified Modeling Language (UML). One important characteristic of this approach is that it provides a method to capture and describe the requirements of the business process using a use cas...
Transformation of a Process Business Model to Domain Model
2008
This paper presents a methodology to perform transformations from a business process model, specifying an UML activity diagram to an UML domain model. The transformation is based in the interaction between an action and an information object from an activity diagram. The transformation is combined with a process of refinement, supported by the specifications of the information objects of the activity diagram, having as final result, a more elab- orated domain model that can specify associations of the generalization. The transformation process it is made from an computation independent model (CIM) to an platform independent model (PIM), under the conceptual framework of the model driver architec- ture (MDA).
2016
This research represents a methodology that control model transformation from CIM level to PIM level in accordance with MDA approach. Our approach is founded on establishing a good CIM level, through well-selected rules, to facilitate transformation to PIM level. However, we create a rich PIM level through use case diagram model, state diagram model, class diagram model and package diagram models. Then, we establish transformation rules to ensure a semi-automatic transformation from CIM level to PIM level. Our Approach conform MDA approach by taking into consideration the business dimension in CIM level, since, we present this level through DFD and UML activity diagram. However, we model into PIM by UML diagrams, because UML is recommended by MDA in this level.
Deriving Integrated Software Design Models from BPMN Business Process Models
Business process management focuses its attention on designing, modelling and documenting business processes , to describe which activities are performed and the dependencies between them. These business process models have lots of useful information for starting to develop a supporting software system. This paper proposes a model-driven approach to support the construction of a use case model, an integrated domain model, and a user interface model, from a set of business process models, comprising all existing information in those models. The proposed approach obtains a system's complete use case model, including the identification of actors , use cases and the corresponding descriptions, and relations between use cases, and between these and the structural domain classes. The resulting integrated use case and domain models are then further transformed into the system's default abstract user interface model. A demonstration case is used throughout the paper as a running example. At the end, conclusions are presented, together with some future research directions.
Deriving Software Design Models from a Set of Business Processes
Requirements elicitation is a crucial activity and one of the first steps in software development process. A popular way to capture and describe requirements is through UML use case models. Transforming requirement specifications into software design models is a complex and error prone software development activity. Software design usually involves several models, each one representing a different perspective. One of those perspectives is the data perspective which can be modeled using a data model. Although of the importance of this model, few works has been done to derive a data model from use case model. The 4SRS (4-Step Rule Set) method generates a logical architecture of a software-based system, based on a use case model. This paper proposes an approach to adapt and extend the 4SRS method in order to generate a data model supporting the generated logical architecture and the elicited requirements based in a set of business process models.
Transforming the business process diagram into a class diagram by model-driven architecture
The Indonesian Journal of Electrical Engineering and Computer Science (IJEECS), 2023
The strength of the model-driven architecture (MDA) lies in its use of models and diagrams in the process of visualizing and developing information systems of companies, that is why we chose the business process model and notations (BPMN) due to the simplicity of the symbols of its diagrams and the clarity of its notations so that all simple users of information systems within the organization can understand their needs and goals quickly and smoothly. In our paper, we suggested that we connect all categories of the staff in the companies, whatever their specialty, and the IT developers, by making a transformation between the BPMN diagrams as independent computing model to the unified modeling language (UML) class diagram as platform independent model. We chose the latter as a destination due to its development and the possibility of transforming it into a powerful and integrated program, and also to complete other transformations later, we chose query views transformations (QVT) due to its consistency with the same family of programs and previous languages.
Transformations’ Study Between Requirements Models and Business Process Models in MDA Approach
Procedia Computer Science, 2020
Models transformation has become in the last decade, the primary key in the Model Driven Architecture (MDA) approach. Most of these models' transformation are made between one or many abstraction levels (higher level, average level, or lower level). For that, the Object Management Group (OMG) offers for the MDA approach three abstraction levels, which are "Computation Independent Model" (CIM: the higher abstraction level), "Platform Independent Model" (PIM: average abstraction level) and "Platform Specific Model" (PSM: lower abstraction level). Hitherto, most researchers focused on the transformation between average abstraction level and lower abstraction level because those levels have multiple common points. However, the transformation between higher abstraction level and average abstraction level is rarely discussed because they are two distinct levels that can contain higher abstraction model nature, such as Requirements models and Business Process models. Therefore, our contribution in this paper is to study different transformations approaches between Requirements and Business Process models in the higher and average MDA abstraction levels. To do so, we study the selected approaches, analyze the results descriptively, then discuss them, plus propose new taxonomies based on the deduced evaluation criteria.
Practitioners View on Domain Specific Business Process Modeling
Proceedings of the 2011 Conference on Databases and Information Systems Vi Selected Papers from the Ninth International Baltic Conference Db Is 2010, 2011
Practitioners view on modeling with Domain Specific Languages (DSLs) is presented in this paper. It is shown, that unlike general-purpose modeling languages (UML [1], BPMN [2]), DSLs provide means for concise representation of semantics of the particular business domain, enabling development of consistent and expressive business process models. Resulting models can be used not only as specifications for information systems, but also for generation of implementation artifacts, creating documentation, testing and for other purposes. Thus one of the most principal goals of Model Driven Architecture (MDA [3]) -the development of model-based information system -is achieved. specification (as specification language is not sufficient), they must be incorporated directly into the source-code of the system, and, in case of automatically generated source-code serious problems can arise. CASE tools are also quite conservative and slow to catch up the fast development of the programming technologies. As a result, only a fraction of applications can be generated from specifications.
Model Transformation with ATL into MDA from CIM to PIM Structured through MVC
Models transformation is the most important key in Model Driven Architecture (MDA). The first transformation in MDA is Computing Independent Model (CIM) to Platform Independent Model (PIM) transformation, the second is PIM to Platform Specific Model (PSM) transformation. This latter transformation deals the two less abstract levels, PIM and PSM, for that most researchers focused on this kind of transformation. Nevertheless, the top level of abstraction, CIM, and its transformation to PIM is rarely discussed in research topics. Our goal in this paper is to represent an approach that allows mastering transformation from CIM to PIM in accordance with MDA. Our method based on creating a good CIM level, using construction rules, to facilitate the transformation to PIM level. Next, our transformation rules, implemented with Atlas Transformation Language (ATL), ensure a semi-automatic transformation from CIM to PIM. Our approach conforms to MDA, because it allows considering the business dimension in the CIM level, and it allows modelling this latter level by using Business Process Model and Notation (BPMN), this latter is the OMG standard for modelling the business process. However, we founded on UML to model PIM level, because UML is advocated by MDA in PIM. Our proposal results a set of classes, organized according to the Model View Controller (MVC).