Verónica Andrea Bollati

Applying MDE to the (semi-)automatic development of model transformations

ContextModel transformations play a key role in any software development project based on Model-Driven Engineering principles. However, despite the inherent complexity of developing model transformations, little attention has been paid to the application of MDE principles to the development of model transformations. ObjectiveIn order to: (a) address the inherent complexity of model transformation development and (b) alleviate the problem of the diversity of the languages that are available for model transformation, this paper proposes the application of MDE principles to the development of model transformations. In particular, we have adopted the idea of handling model transformations as transformation models in order to be able to model, transform and generate model transformations. MethodThe proposal follows an MDA-based approach that entails the modeling of model transformations at different abstraction levels and the connection of these models by means of model transformations. It has been empirically validated by conducting a set of case studies following a systematic research methodology. ResultsThe proposal was supported by the introduction of MeTAGeM, a methodological and technical framework for the model-driven development of model transformations that bundles a set of Domain-Specific Languages for modeling model transformations with a set of model transformations in order to bridge these languages and (semi-)automate model transformations development. ConclusionThis paper serves to show that a semi-automatic development process for model transformations is not only desirable but feasible. This process, based on MDE principles, helps to ease the task of developing model transformations and to alleviate interoperability issues between model transformation languages.

Model-Driven Engineering as a new landscape for traceability management: A systematic literature review

Context: Model-Driven Engineering provides a new landscape for dealing with traceability in software development. Objective: Our goal is to analyze the current state of the art in traceability management in the context of Model-Driven Engineering. Method: We use the systematic literature review based on the guidelines proposed by Kitchenham. We propose five research questions and six quality assessments. Results: Of the 157 relevant studies identified, 29 have been considered primary studies. These studies have resulted in 17 proposals. Conclusion: The evaluation shows that the most addressed operations are storage, CRUD and visualization, while the most immature operations are exchange and analysis traceability information.

Supporting Model---Driven Development of Object---Relational Database Schemas: A Case Study

This paper completes our proposal for automatic development of Object-Relational (OR) DataBase (DB) schemas. By means of a case study, this work focuses on presenting the tooling developed to support the whole process. As usual, the proposal starts from a conceptual data model (Platform Independent Model) depicted in a UML class diagram. Then, the conceptual data model is mapped into an OR DB model (Platform Specific Model) that represents the OR DB schema. To that end, we have implemented a set of formalized mapping rules using the ATL language. Finally, the SQL code that implements the modeled schema in Oracle 10g is automatically generated from the OR model by means of a MOFScript model to text transformation. Moreover, since the OR model could be refined along the design process, we have developed a graphical editor for OR DB models.

Dealing with Traceability in the MDDof Model Transformations

Traceability has always been acknowledged as a relevant topic in Software Engineering. However, keeping track of the relationships between the different assets involved in a development process is a complex and tedious task. The fact that the main assets handled in any model-driven engineering project are models and model transformations eases the task. In order to take advantage of this scenario, which has not been appropriately capitalized on by the most widely adopted model transformation languages before, this work presents MeTAGeM-Trace, a methodological and technical proposal with which to support the model-driven development of model transformations that include trace generation. The underlying idea is to start from a high-level specification of the transformation which is subsequently refined into lower-level transformation models in terms of a set of DSLs until the source code that implements the transformation can be generated. Running this transformation produces not only the corresponding target models, but also a trace model between the elements of the source and target models. As part of the proposal, an EMF-based toolkit has been developed to support the development of ATL and ETL model transformations. This toolkit has been empirically validated by conducting a set of case studies following a systematic research methodology.

Analysing the cognitive effectiveness of the WebML visual notation

WebML is a domain-specific language used to design complex data-intensive Web applications at a conceptual level. As WebML was devised to support design tasks, the need to define a visual notation for the language was identified from the very beginning. Each WebML element is consequently associated with a separate graphical symbol which was mainly defined with the idea of providing simple and expressive modelling artefacts rather than by adopting a rigorous scientific approach. As a result, the graphical models defined with WebML may sometimes prevent proper communication from taking place between the various stakeholders. In fact, this is a common issue for most of the existing model-based proposals that have emerged during the last few years under the umbrella of model-driven engineering. In order to illustrate this issue and foster in using a scientific basis to design, evaluate, improve and compare visual notations, this paper analyses WebML according to a set of solid principles, based on the theoretical and empirical evidence concerning the cognitive effectiveness of visual notations. As a result, we have identified a set of possible improvements, some of which have been verified by an empirical study. Furthermore, a number of findings, experiences and lessons learnt on the assessment of visual notations are presented.

MeTAGeM-Trace

In the context of Model-Driven Engineering (MDE), generation of traces can be automated using the implicit traceability relationships contained in any model transformation. Besides, if transformations are developed adopting a Model-Driven Engineering (MDE) approach, i.e. promoting the role of models and the level of automation, model transformation will benefit from the promised advantages of MDE in terms of less costly software development while reducing the inherent complexity of coding model transformations. To put these ideas into practice, this work introduces MeTAGeM-Trace, the first prototype of an EMF-based toolkit for the MDD of model-to-model transformations which supports trace generation, i.e. it allows developing model transformations that produce not only the corresponding target models, but also a trace model between the elements of the source and target models involved in the transformation.

Model Management Systems vs. Model Driven Engineering: a case study

Research in the field of Model-Driven Development follows two main approaches: Model Management Systems and Model-Driven Engineering. The former comes from the field of Databases whereas the latter has its roots in the Software Engineering community. This paper presents a practical comparison of the two approaches in order to identify the strengths and weaknesses of each one. More specifically, we have compared MIDST and ATL, as representative technological solutions for a Model Management System and Model-Driven Engineering respectively. This has been achieved by carrying out a case study based on the transformation of Entity-Relationship schemas into Object-Relational schemas. The conclusion reached is that, although the use of MIDST is, in general, more complex, in data model domains the benefits of its use compensate for its complexity. However, in other domains, such as those which are Service-Oriented, ATL may be more intuitive.

Enabling the Development of Cognitive Effective Visual DSLs

The development of graphical editors for visual DSLs is far from being a trivial task. There are consequently several tools that provide technical support for this task. However, this paper shows that the analysis of the main characteristics of such tools leaves some space for improvement as regard the cognitive effectiveness of the visual notations produced with them. To deal with this issue, this work introduces CEViNEdit, a GMF-based framework for the development of visual DSLs which takes into account Moody’s principles for the development and evaluation of graphical notations. To that end, CEViNEdit eases the selection of values for the visual variables of which the notation is composed, computes a set of metrics to assess the appropriateness of these values and then automates the generation of the graphical editor.

On the Impact of Automation and Trace-Enabling over the Quality of Model Transformations

In the context of Model-Driven Engineering (MDE), the generation of traces can be automated using the implicit traceability relationships contained in any model transformation. Furthermore, if transformations were to be developed by adopting a model-based approach, they might benefit from the promised advantages of MDE in terms of a less costly software development while reducing the inherent complexity of coding them. Bearing these ideas in mind, in previous works we have introduced MeTAGeM-Trace, an EMF-based toolkit for the MDD of model transformations which supports trace generation. However, automation might have a negative impact on the quality of the products generated. To assess whether this is actually the case with MeTAGeM-Trace, this work presents the principal results of an experiment in which the quality of model transformations developed in different manners, including the use of MeTAGeM-Trace, are compared with the aim of evaluating the impact of automation and trace-enabling on the quality of model transformations.

Model-Driven Development of Model Transformations Supporting Traces Generation

This work introduces a framework for model-driven development of model transformations that support traces generation. The proposal starts from a high-level specification of the relationships that must hold between the elements of source and target metamodels. Such specification is subsequently refined into lower-level transformation models until they can be serialized into the source code that implements the transformation. Running such transformation produces not only the corresponding source models but also a trace model between the elements of source and target models.