Model Migration with MOLA

We have modeled a UML1.4 to UML2.2 Activity Diagram model transformation for the TTC2010 Transformation Tool Contest with the Fujaba Tool Suite. The solution uses core fujaba feature: the whole application is modeled using Story Driven Modelling .

2020

The main scope is to introduce the transformation algorithm of UML Activity model generation from Enterprise model (EM). The transformation algorithm is described in details by showing full process through steps. Whole generation process steps illustrated by particular example of Paper submission for the publishing following the transformation algorithm step by step.

2015

Introduction In recent years many organizations have begun to consider MDA as an approach to design and implement enterprise applications. The central idea of MDA is to separate the platform independent design from the platform specific implementation of applications delaying as much as possible the dependence on specific technologies [1]. The MDA uses models as first class entities, enabling the definition and automatic execution of transformations between models and from models to code. The creation of meta-models for specifying modeling languages is a basic task in MDA. Models in MDA are the key artifacts in all phases of development and are mostly expressed with Unified Modeling Language (UML). Also the specification of transformations between models, are called model-to-model (M2M) transformations, and from model to code, are called model-to-text (M2T) transformations. The main advantage of this approach of software development is that MDA tools enable these transformations to ...

The 7th International Conference on Information Technology, 2015

The use of UML Activity Diagrams for modeling global dynamic behaviors of systems is very widespread. UML diagrams support developers by means of visual conceptual illustrations. However, the lack of firm semantics for the UML modeling notations makes the detection of behavioral inconsistencies difficult in the initial phases of development. The use of formal methods makes such error detection possible but the learning cost is high. Integrating UML with formal notation is a promising approach that makes UML more precise and allows rigorous analysis. In this paper, we present an approach that integrates UML Activity Diagrams with Rewriting Logic language Maude in order to benefit from the strengths of both approaches. The result is an automated approach and a tool environment that transforms global dynamic behaviors of systems expressed using UML models into their equivalent Maude specifications for analysis purposes. The approach is based on Graph Transformation and the Meta-Modeling tool AToM 3 is used. The approach is illustrated through an example.

Software Engineering and …, 2007

Model transformation tools often work at the metamodel level by manipulating instances of metamodel constructs. In our work on developing a tool for test case generation from UML diagrams, we built a model transformation tool that converts sequence diagrams to an new graphical notation. Our tool uses a sequence diagram editor, SeDi, which uses the UML2 Eclipse plugin, which in turn implements the superstructure of the UML 2.0 metamodel. We faced several challenges that can be attributed to either the UML superstructure itself or its implementation. We illustrate the problems with examples from the superstructure and its implementation. We describe how we addressed the problems.

2000

This paper provides a solution to the mandatory transformation example specified in MOLA -a graphical model transformation language developed at the University of Latvia. The solution is validated by executing it via the MOLA execution environment on several examples. In addition, a solution to one of the optional examples -determinization of a nondeterministic automaton is provided.

IEEE/ASME Journal of Microelectromechanical Systems - J MICROELECTROMECHANICAL SYST, 2003

In a Model Driven Architecture (MDA) software development process, models are repeatedly transformed to other models in order to finally achieve a set of models with enough details to implement a system. Generally, there are multiple ways to transform one model into another model. Alternative target models differ in their quality properties and the selection of a particular model is determined on the basis of specific requirements. Software engineers must be able to identify, compare and select the appropriate transformations within the given set of requirements. The current transformation languages used for describing and executing model transformations only provide means to specify the transformations but do not help to identify and select from the alternative transformations. In this paper we propose a process and a set of techniques for constructing a transformation space for a given transformation problem. The process uses a source model, its meta-model and the meta-model of th...

DATESO

International Journal of Computational Science and Engineering, 2019

This paper presents a specific tool, called MAV-UML-AD, allowing the specification and the verification of workflow models using UML activity diagrams (UML ADs) and Event-B and based on institutions. The developed tool translates an activity diagram model into an equivalent Event-B specification according to a mathematical semantics. The transformation approach of UML AD models is based on the theory of institutions. In fact, each of UML AD and Event-B specifications is defined by an instance of its corresponding institution. The transformation approach is represented by an institution co-morphism which is defined between the two institutions. Institution theory is adopted as the theoretical framework of the tool essentially for two reasons. First, it gives a locally mathematical semantics for UML AD and Event-B. Second, it defines a semantic preserving mapping between UML AD specification and Event-B machine. Thanks to the B theorem prover, functional proprieties like liveness and fairness can be formally checked. The core of the model transformation approach will be highlighted in this paper and how institution concepts such as category, co-morphism and signature are presented in the two used formalisms. This paper will also illustrate the use of the developed tool MAV-UML-AD through an example of specification and verification.

IEEE Transactions on Software Engineering, 2002

One of the most important features of modeling tools is generation of output. The output may be documentation, source code, net list, or any other presentation of the system being constructed. The process of output generation may be considered as automatic creation of a target model from a model in the source modeling domain. This translation does not need to be accomplished in a single step. Instead, a tool may generate multiple intermediate models as other views to the system. These models may be used either as better descriptions of the system, or as a descent down the abstraction levels of the user-defined model, gradually leading to the desired implementation. If the modeling domains have their metamodels defined in terms of object-oriented concepts, the models consist of instances of the abstractions from the metamodels and links between them. A new technique for specifying the mapping between different modeling domains is proposed in the paper. It uses UML object diagrams that show the instances and links of the target model that should be created during automatic translations. The diagrams are extended with the proposed concepts of conditional, repetitive, parameterized, and polymorphic model creation, implemented by the standard UML extensibility mechanisms. Several examples from different engineering domains are provided, illustrating the applicability and benefits of the approach. The first experimental results show that the specifications may lead to better reuse and shorter production time when developing customized output generators.