On the Specification of Model Transformations through a Platform Independent Approach

@inproceedings{Magalhes2015OnTS,
  title={On the Specification of Model Transformations through a Platform Independent Approach},
  author={Ana Patr{\'i}cia Fontes Magalh{\~a}es and Aline Maria Santos Andrade and Rita Suzana Pitangueira Maciel},
  booktitle={SEKE},
  year={2015}
}
Transformations are key artifacts in the MDD (Model Driven Development) approach: a software development project can be defined through a transformation chain converting source models into target models until code, enabling development process automation. Transformations can be complex and demand software processes, languages and techniques to improve their development in order to increase reuse, portability, correctness, and so on. In this context we propose a framework to develop model… 

Figures and Tables from this paper

A Model Driven Transformation Development Process for Model to Model Transformation

TLDR
This paper presents a framework to support the development of model transformation chains using MDD, comprised of a Development Process, to guide on transformation development tasks; a Model Transformation Profile (MTP) as the transformation modeling language; a transformation chain, which helps the automation of the proposed transformation process; and an environment to support it.

XRTSDIC: model transformation from PIM to PSM

TLDR
An algorithm and defined model transformation and consistency rules are proposed and the empirical results revealed that the model transformation is consistent and accurate.

References

SHOWING 1-10 OF 12 REFERENCES

MTP: Model Transformation Profile

TLDR
This paper proposes amodel transformation profile (MTP) suitable for the transformation specification since requirements elicitation, which provides specifications independent of platform that can bereused to generate code in different transformation languages.

A Visual Specification Language for Model-to-Model Transformations

TLDR
This paper presents a visual, formal, declarative specification language to express model-to-model transformations and their correctness properties and provides a compilation of specifications into OCL as this has many practical applications, e.g. it allows injecting assertions and correctness properties for automated testing of transformation implementations based on OMG standards.

transML: a family of languages to model model transformations

TLDR
A unified family of languages to cover the life-cycle of transformation development is proposed and tools to partially automate the progressive refinement of models between the different phases and the generation of code for specific transformation implementation languages are provided.

Generic Model Transformations: Write Once, Reuse Everywhere

TLDR
This paper defines model transformation templates, which are defined over metamodel concepts which later can be bound to specific meta-models which can be applied to any model transformation language.

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

A Taxonomy of Model Transformation

Model Transformation Specification and Verification

  • K. LanoD. Clark
  • Computer Science
    2008 The Eighth International Conference on Quality Software
  • 2008
TLDR
This paper defines an approach for specifying transformations as constraints, and for verifying the correctness of these transformations.

Towards a general composition semantics for rule-based model transformation

TLDR
This paper aims to generalise two internal composition mechanisms for rule-based transformation languages, module import and rule inheritance, by providing executable semantics for the composition mechanisms within a virtual machine.

Goal Question Metric (GQM) Approach

TLDR
The most common and popular mechanism for goal-oriented software measurement is the Goal Question Metric approach which is presented in this article in combination with examples from GQM application in industry.

Towards a decision-making structure for selecting a research design in empirical software engineering

TLDR
A decision-making structure containing a number of decision points, each one of them representing a specific aspect on empirical software engineering research, is provided to ensure that researchers make well-founded and informed decisions about their research designs.