Difference between revisions of "Model to Model Transformation - MMT"

From Eclipsepedia

Jump to: navigation, search
(improved page structure and updated a few facts)
(M2M Transformation Languages and Engines)
Line 9: Line 9:
 
The three languages currently supported by M2M are:
 
The three languages currently supported by M2M are:
 
* [[M2M/Atlas Transformation Language (ATL)|Atlas Transformation Language (ATL)]]
 
* [[M2M/Atlas Transformation Language (ATL)|Atlas Transformation Language (ATL)]]
* [[M2M/Operational QVT Language (QVTO)|Operational QVT Language (QVTO)]], aka Procedural QVT (''Operational Mappings'')
+
* [[M2M/Operational QVT Language (QVTO)|QVT Operational Mappings Language (QVTo)]]
* [[M2M/Relational QVT Language (QVTR)|Relational QVT Language (QVTR)]], aka Declarative QVT (''Core'' and ''Relations'')
+
* [[M2M/QVT_Declarative_(QVTd)|QVT Declarative Languages (QVTd)]], supporting QVT Core (QVTc) and QVT Relations (QVTr)
  
 
==Questions and Discussions About M2M Usage==
 
==Questions and Discussions About M2M Usage==

Revision as of 03:05, 22 November 2009

< To: Modeling

Model-to-model transformation is a key aspect of model-driven development (MDD). The M2M project provides a framework for model-to-model transformation languages. Transformations are executed by transformation engines. There are three transformation engines that are developed in the scope of this project: ATL, QVTO, QVTR. M2M is a subproject of the top-level Eclipse Modeling Project.

Contents


M2M Transformation Languages and Engines

The three languages currently supported by M2M are:

Questions and Discussions About M2M Usage

Questions and discussions about the M2M projects and/or about its components (i.e., ATL, QVTO, QVTR) should be directed to the eclipse.modeling.m2m Eclipse newsgroup. There are also archives, as well as a newsportal (i.e., news access from web browser) available for this newsgroup.

In order to keep the discussions understandable, the subject of every post should be prefixed with the name of the component it is targeting:

  • [ATL] for the ATL component.
  • [QVTO] for the Operational QVT component
  • [QVTR] for the Relational QVT component
  • or [M2M] if the overall project is targeted.

This last rule is to make sure that erroneously unprefixed messages are not misinterpreted as targeting the overall project.