Model-driven engineering (MDE) uses models during the application development process. Thus, the MDE is particularly based on model-driven architecture (MDA), which is one of the important variants of the Object Management Group (OMG).... more
Model-driven engineering (MDE) uses models during the application development process. Thus, the MDE is particularly based on model-driven architecture (MDA), which is one of the important variants of the Object Management Group (OMG). MDA aims to generate source code from abstract models through several model transformations between, and inside the different MDA levels: computation independent model (CIM), platform independent model (PIM), and platform specific model (PSM) before code. In this context, several methods and tools were proposed in the literature and in the industry that aim to automatically generate the source code from the MDA levels. However, researchers still meet many constraints—model specifications, transformation automation, and level traceability. In this paper, we present a tool support, the model-driven architecture for web application (MoDAr-WA), that implements our proposed approach, aiming to automate transformations from the highest MDA level (CIM) to th...
Model Driven Engineering (MDE) and Agile Methods (AM) are two principal domains that are in the way of improvement and evolution in order to facilitate the realisation of IT projects. However, these areas evolve separately despite the... more
Model Driven Engineering (MDE) and Agile Methods (AM) are two principal domains that are in the way of improvement and evolution in order to facilitate the realisation of IT projects. However, these areas evolve separately despite the great number of researches that focus on improving realisation project’ techniques. Thus, our approach aims to provide an approach that combines two variants of MDE, Model Driven Architecture approach and Model-Based Testing with the V development lifecycle used in every scrum Agile Methodology sprint to deal with system evolution. In order to well illustrate this approach, we apply it on Rental Car Agency System realisation using Scrum methodology with some requirements’ evolution.
Agile methods (AM) and model-driven engineering (MDE) are two principal domains of software development. AM proposes best practices in information programming, while MDE focuses on technical part of software development. Both of these... more
Agile methods (AM) and model-driven engineering (MDE) are two principal domains of software development. AM proposes best practices in information programming, while MDE focuses on technical part of software development. Both of these domains are in the way of improvement and evolution in order to facilitate the development of IT projects. However, these areas evolve separately despite the great number of researches that focus on improving development project' techniques. Thus, in this chapter the authors present an overview of their approach “Scrum with MoDAr-WA”, that aims to improve Scrum Agile methodology by combining two variants of MDE: model-driven architecture and mode-based testing with the V development lifecycle used to deal with sprint development in Scrum methodology. Then they present a comparison study between the standard Scrum process and Scrum with MoDAr-WA approach in order to highlight the authors' contribution to improve agile methodologies.
The Model Driven Architecture (MDA) approach introduces a clear separation of system requirements and their implementation. This approach uses models at the center of the development of software systems. The MDA approach is based on... more
The Model Driven Architecture (MDA) approach introduces a clear separation of system requirements and their implementation. This approach uses models at the center of the development of software systems. The MDA approach is based on models transformations; in the literature, several works have summarized the MDA approach to the passage from PIM to PSM then to code. But very little works have contributed on CIM to PIM transformations. Thus, our proposal aims to provide a method of transforming CIM to PIM using QVT transformation rules and respecting the two levels aspects as specified by the Object Management Group (OMG). Our approach proposes to represent a CIM level by Business Use Case Diagram and Activity Diagram while after applying transformation rules, the PIM level is represented by Class Diagram and Sequence Diagram.
Model Transformations is the core of Model Driven Architecture; several works have been focused on transformations between the different models that compose the MDA approach: the Computation Independent Model (CIM), the Platform... more
Model Transformations is the core of Model Driven Architecture; several works have been focused on transformations between the different models that compose the MDA approach: the Computation Independent Model (CIM), the Platform Independent Model (PIM) and the Platform Specific Model (PSM). In this paper, we propose a new method of transformations between CIM and PIM levels; this approach aims to automate transformations using rules which are described with QVT standard. In order to respect OMG specifications defined for each level, we choose to model CIM level by an extended version of UML UseCase Diagram to support DataObject element and to cover the functional and static aspects while dynamic one is represented by Activity Diagram. On the same level, we used SBVR standard to express system rules and requirements which are transformed to OCL constraints. PIM level is represented by Class Diagram and Sequence Diagram; this level is the result of a vertical transformation of CIM. This paper shows also an application of our approach on an e-library system.
