DOCSLIB.ORG

ATL Inventory

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text
ATL Inventory ATLAS group LINA & INRIA Nantes ATL Inventory Date of preparation: 31/08/06 Revision: 0.1 INRIA ATLAS – ATL Inventory - Revision 0.1 date: 31/08/06 Page 1 of 32 Date Rev. Author Checked by Description (dd/mm/yy) 0.1 Freddy Creation of the document Allilaire INRIA ATLAS – ATL Inventory - Revision 0.1 date: 31/08/06 Page 2 of 32 Table of contents Table of contents ...................................................................................................... 3 Tables list .................................................................................................................. 4 Figures list................................................................................................................. 5 1. Introduction .................................................................................................... 6 2. An Introduction to Model Transformation.................................................... 7 2.1. The Model-Driven Architecture ................................................................................. 7 2.2. Model Transformation................................................................................................ 8 3. Overview of the Atlas Transformation Language...................................... 10 3.1. ATL module............................................................................................................... 10 3.1.1. Structure of an ATL module...................................................................................................... 10 3.1.1.1. Header section .................................................................................................................. 10 3.1.1.2. Import section.................................................................................................................... 11 3.1.1.3. Helpers.............................................................................................................................. 11 3.1.1.4. Rules ................................................................................................................................. 12 3.1.2. Module execution modes.......................................................................................................... 14 3.1.2.1. Normal execution mode .................................................................................................... 14 3.1.2.2. Refining execution mode................................................................................................... 14 3.1.3. Module execution semantics .................................................................................................... 16 3.1.3.1. Default mode execution semantics ................................................................................... 16 3.1.3.2. Refining mode execution semantics ................................................................................. 16 3.2. ATL Query ................................................................................................................. 17 3.2.1. Structure of an ATL query......................................................................................................... 17 3.2.2. Query execution semantics ...................................................................................................... 17 3.3. ATL Library ............................................................................................................... 17 4. ATL Inventory ............................................................................................... 18 4.1. Documentation ......................................................................................................... 18 4.1.1. Reference manuals................................................................................................................... 18 4.1.1.1. User Manual...................................................................................................................... 18 4.1.1.2. Starter Guide..................................................................................................................... 18 4.1.1.3. Installation Guide .............................................................................................................. 19 4.1.1.4. Installation from source..................................................................................................... 19 4.1.1.5. Specification of the ATL Virtual Machine .......................................................................... 19 4.1.2. ATL References........................................................................................................................ 19 4.1.2.1. ATL Publications ............................................................................................................... 19 4.1.2.2. ATL External References.................................................................................................. 20 INRIA ATLAS – ATL Inventory - Revision 0.1 date: 31/08/06 Page 3 of 32 4.1.2.3. AMMA/ATL Workshop on Model Engineering .................................................................. 20 4.1.3. ATL Wiki.................................................................................................................................... 20 4.1.3.1. Standard Library................................................................................................................ 20 4.1.3.2. Troubleshooter .................................................................................................................. 20 4.1.3.3. FAQ................................................................................................................................... 20 4.1.3.4. How to ............................................................................................................................... 21 4.1.3.5. AM3 Ant Task.................................................................................................................... 21 4.1.3.6. Wish List............................................................................................................................ 21 4.2. ATL Examples........................................................................................................... 21 4.2.1. The ATL Transformation Zoo.................................................................................................... 21 4.2.2. A Classification of the ATL Transformations Zoo ..................................................................... 25 4.2.2.1. Semantic Bridges .............................................................................................................. 25 4.2.2.2. Bridges to Graphical Representations .............................................................................. 26 4.2.2.3. From Tool to Tool Transformations................................................................................... 26 4.2.2.4. Calculation Transformations ............................................................................................. 26 4.2.2.5. Miscellaneous Transformations ........................................................................................ 27 4.3. How to find some helps and to contribute to the ATL community...................... 27 4.3.1. ATL Mailing List ........................................................................................................................ 27 4.3.2. Bug reporting / Patch providing ................................................................................................ 27 4.3.3. Provide ATL examples.............................................................................................................. 27 4.4. Download .................................................................................................................. 28 4.4.1. GMT .......................................................................................................................................... 28 4.4.2. ATL Bundle ............................................................................................................................... 28 4.4.2.1. Getting Started .................................................................................................................. 28 4.4.2.2. Package Structure............................................................................................................. 28 4.5. AMMA Platform......................................................................................................... 28 4.5.1. AM3........................................................................................................................................... 29 4.5.2. AMW ......................................................................................................................................... 29 4.5.3. TCS........................................................................................................................................... 29 4.5.4. KM3........................................................................................................................................... 29 5. References.................................................................................................... 30 Appendix ................................................................................................................. 32 Tables list Figure 1. Conformance relation 7 Figure 2. Meta relations 7 Figure 3. The model-driven architecture 8 Figure 4. An overview of model transformation
Load more

Recommended publications
  • Towards Automated Model Driven Development with Model Transformation and Domain Specific Languages
    International Journal of Computer Science and Electronics Engineering (IJCSEE) Volume 1, Issue 1 (2013) ISSN 2320–4028 (Online) Towards automated model driven development with model transformation and domain specific languages Cuong V. Nguyen, Xhevi Qafmolla communication between individuals and teams working on the Abstract— Modeling plays a very important role in dealing system [4]. with the complexity of software systems during their Model Driven Architecture (MDA) aims to separate development and maintenance processes. As more complex application structure PIM (Platform Independent Model) from models need to be developed, the importance of its functionality, PSM (Platform specific Model). The transformations between models grows. Model mapping between these models is realized by model transformations allow the definition and implementation of transformation. The problem of model transformation based operations on models, also provide a chain that can enable the on Meta-Object Facility (MOF) can, then, be stated in the automated development of a system from its corresponding following way: “Given a source model ‘m1’ described by a models. In this context, approaches to model transformation meta-model ‘MM1’ we define an automatic process making it techniques promise to bring productivity and efficiency to the possible to obtain a model ‘m2’ conforming to a meta-model whole process. This paper outlines practices from current ‘MM2’; ‘MM1’ and ‘MM2’ being MOF compliant” [10]. model transformation approaches and the benefit of using Model transformations require specialized support in order to domain specific language (DSL) for modeling purposes. We also present the approach of using hybrid transformation with realize their full potential. Nowadays, there are still open to support automation of model driven development.
    [Show full text]
  • Application of Model-Driven Engineering and Metaprogramming to DEVS Modeling & Simulation
    Application of Model-Driven Engineering and Metaprogramming to DEVS Modeling & Simulation Luc Touraille To cite this version: Luc Touraille. Application of Model-Driven Engineering and Metaprogramming to DEVS Model- ing & Simulation. Other. Université Blaise Pascal - Clermont-Ferrand II, 2012. English. NNT : 2012CLF22308. tel-00914327 HAL Id: tel-00914327 https://tel.archives-ouvertes.fr/tel-00914327 Submitted on 5 Dec 2013 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. D.U.: 2308 E.D.S.P.I.C: 594 Ph.D. Thesis submitted to the École Doctorale des Sciences pour l’Ingénieur to obtain the title of Ph.D. in Computer Science Submitted by Luc Touraille Application of Model-Driven Engineering and Metaprogramming to DEVS Modeling & Simulation Thesis supervisors: Prof. David R.C. Hill Dr. Mamadou K. Traoré Publicly defended on December 7th, 2012 in front of an examination committee composed of: Reviewers: Prof. Jean-Pierre Müller, Cirad, Montpellier Prof. Gabriel A. Wainer, Carleton University, Ottawa Supervisors: Prof. David R.C. Hill, Université Blaise Pascal, Clermont-Ferrand Dr. Mamadou K. Traoré, Université Blaise Pascal, Clermont- Ferrand Examiners Dr. Alexandre Muzy, Università di Corsica Pasquale Paoli, Corte Prof.
    [Show full text]
  • Model Driven Software Engineering for Web Applications
    Model Driven Software Engineering for Web Applications Andreas Kraus Dissertation zur Erlangung des akademischen Grades des Doktors der Naturwissenschaften an der Fakultät für Mathematik, Informatik und Statistik der Ludwig-Maximilians-Universität München vorgelegt am 23.04.2007 Model Driven Software Engineering for Web Applications Tag der Einreichung: 23.04.2007 Tag des Rigorosums: 04.07.2007 Berichterstatter Prof. Dr. Rolf Hennicker (Ludwig-Maximilians-Universität, München) Prof. Dr. Antonio Vallecillo (Universidad de Malaga, Spanien) 2 Model Driven Software Engineering for Web Applications Summary Model driven software engineering (MDSE) is becoming a widely accepted approach for developing complex applications and it is on its way to be one of the most promising para- digms in software engineering. MDSE advocates the use of models as the key artifacts in all phases of the development process, from analysis to design, implementation and testing. The most promising approach to model driven engineering is the Model Driven Architec- ture (MDA) defined by the Object Management Group (OMG). Applications are modeled at a platform independent level and are transformed to (possibly several) platform specific implementations. Model driven Web engineering (MDWE) is the application of model driven engineering to the domain of Web application development where it might be par- ticularly helpful because of the continuous evolution of Web technologies and platforms. However, most current approaches for MDWE provide only a partial application of the MDA pattern. Further, metamodels and transformations are not always made explicit and metamodels are often too general or do not contain sufficient information for the automatic code generation. Thus, the main goal of this work is the complete application of the MDA pattern to the Web application domain from analysis to the generated implementation, with transformations playing an important role at every stage of the development process.
    [Show full text]
  • Model-Driven Interoperability to Enhance Product Data Quality
    Model-Driven Interoperability to enhance Product Data Quality Néjib Moalla 1, 2, Yacine Ouzrout 1, Gilles Neubert 1, Abdelaziz Bouras 1 1 University of Lyon 2 - CERRAL / IUT-Lumière Lyon 2. 160, Boulevard de l’université, 69500, Bron, France. {Nejib.Moalla, Yacine.Ouzrout, Gilles.Neubert, Abdelaziz.Bouras}@univ-lyon2.fr 2 Sanofi Pasteur France - Campus Mérieux. 1541, Avenue Marcel Mérieux 69280, Marcy-L’étoile, France. {Nejib.Moalla}@sanofipasteur.com Abstract. Data quality presents a major issue to reduce product cost and improve time-to-market for the vaccine industry. In fact, the molecular definition of vaccine product must be well formalized in the supply chain perimeter to be always compliant with the regulatory approved definition of the product. To ensure product data quality, we study in this paper the concepts of model- driven interoperability and we highlight their capabilities to connect some models related to heterogeneous information systems. Therefore, to deal with product complexity and the diversity of its definitions inside the supply chain perimeter, we propose in this work a five steps approach based on MDI concepts. The proposed architecture deals with some specific product data identified as critical in our context and allows ensuring their quality in the Enterprise Resource Planning (ERP), as the main production information system in the vaccine industry. When deployed, our work provides some interesting results at Sanofi Pasteur France company. Keywords: Model-Driven Interoperability, Product data quality, Reference frames, Vaccine supply chain. 1 Introduction Data quality is widely considered as a critical problem inside industry. According to [1, 2], more than 52 % of audited enterprises confirm that they suffer from problems related to the lack of data quality.
    [Show full text]
  • Model Driven Analysis and Synthesis of Textual Concrete Syntax
    Model Driven analysis and synthesis of textual concrete syntax Pierre-Alain Muller, Frédéric Fondement, Franck Fleurey, Michel Hassenforder, Rémi Schnekenburger, Sébastien Gérard, Jean-Marc Jézéquel To cite this version: Pierre-Alain Muller, Frédéric Fondement, Franck Fleurey, Michel Hassenforder, Rémi Schnekenburger, et al.. Model Driven analysis and synthesis of textual concrete syntax. Software and Systems Modeling, Springer Verlag, 2008, 7 (4), pp.423–442. 10.1007/s10270-008-0088-x. inria-00468231 HAL Id: inria-00468231 https://hal.inria.fr/inria-00468231 Submitted on 1 Apr 2010 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Model-Driven Analysis and Synthesis of Textual Concrete Syntax Pierre-Alain Muller1, Frédéric Fondement2, Franck Fleurey3, Michel Hassenforder2, Rémi Schnekenburger4, Sébastien Gérard4, Jean-Marc Jézéquel1 1 IRISA / INRIA Rennes Rennes, France {pierre-alain.muller, jean-marc.jezequel}@irisa.fr 2 Université de Haute-Alsace, MIPS Mulhouse, France {frederic.fondement, michel.hassenforder}@uha.fr 3 SINTEF Oslo, Norway [email protected] 4 CEA, LIST Gif-sur-Yvette, France {remi.schneckenburger, sebastien.gerard}@cea.fr Abstract. Meta-modeling is raising more and more interest in the field of language engineering. While this approach is now well understood for defining abstract syntaxes, formally defining textual concrete syntaxes with meta-models is still a challenge.
    [Show full text]
  • An Algebraic Semantics for MOF Artur Boronat, José Meseguer
    An algebraic semantics for MOF Artur Boronat, José Meseguer To cite this version: Artur Boronat, José Meseguer. An algebraic semantics for MOF. Formal Aspects of Computing, Springer Verlag, 2010, 22 (3), pp.269-296. 10.1007/s00165-009-0140-9. hal-00567269 HAL Id: hal-00567269 https://hal.archives-ouvertes.fr/hal-00567269 Submitted on 20 Feb 2011 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. Under consideration for publication in Formal Aspects of Computing An Algebraic Semantics for MOF Artur Boronat1 and Jos´eMeseguer2 1Department of Computer Science, University of Leicester, UK, 2Department of Computer Science, University of Illinois at Urbana-Champaign, USA Abstract. In model-driven development, software artifacts are represented as models in order to improve productivity, quality, and cost effectiveness. In this area, the Meta-Object Facility (MOF) standard plays a crucial role as a generic framework within which a wide range of modeling languages can be defined. The MOF standard aims at offering a good basis for model-driven development, providing some of the building concepts that are needed: what is a model, what is a metamodel, what is reflection in the MOF framework, and so on.
    [Show full text]
  • Model Transformation in Web Engineering and Automated Model Driven Development
    International Journal of Modeling and Optimization, Vol. 1, No. 1, April 2011 Model Transformation in Web Engineering and Automated Model Driven Development Nguyen Viet Cuong, Xhevi Qafmolla, of applicability of these techniques. In such terms we speak Abstract—When dealing with the complexity of IT systems about of models of a model, meta-models. The scale by during their development as well as maintenance processes, which this logic is applied directly affects using of modeling plays a very important role. The complexity and transformation methods and their optimization. diversity of these applications emerges the need of flexibility Model Driven Architecture (MDA) aims to separate and combining operations with existing models to create other new, more complex models. As more complex models are used, application structure PIM (Platform Independent Model) the importance of transformations between models grows. from its functionality, PSM (Platform specific Model). The Model transformations allow the definition and implementation mapping between these models is realized by model of operations on models and also provide a chain that can transformation. The problem of model transformation based enable the automated development of a system from its on Meta-Object Facility (MOF) can, then, be stated in the corresponding models. In this context, approaches to model following way: “Given a source model ‘m1’ described by a transformation techniques promise to bring productivity and efficiency to the whole process. This paper outlines practices meta-model ‘MM1’ we define an automatic process making it from current model transformation approaches. We explain possible to obtain a model ‘m2’ conforming to a meta-model our focused research in the Web domain and introduce a novel ‘MM2’; ‘MM1’ and ‘MM2’ being MOF compliant” [2].
    [Show full text]
  • Specification of Model Transformation and Weaving in Model Driven Engineering
    Dipartimento di Informatica Universit`adi L’Aquila Via Vetoio, I-67100 L’Aquila, Italy http://www.di.univaq.it PH.D. THESIS IN COMPUTER SCIENCE XIX SPECIFICATION OF MODEL TRANSFORMATION AND WEAVING IN MODEL DRIVEN ENGINEERING Ph.D. Thesis of: Davide Di Ruscio Advisor: Prof. Alfonso Pierantonio Supervisor of the Ph.D. Program: Prof. Michele Flammini CICLO XIX c Davide Di Ruscio, 2007. All rights reserved ABSTRACT Last years witnessed an increasing intricacy of both software systems and technologies. A num- ber of platforms (e.g. CORBA, J2EE, .NET) have been introduced which often came in bundle with their own programming language (e.g. C++, Java, C#). This has made the software develop- ment process a difficult and expensive task. Model driven engineering (MDE) aims at preserving the investments in building complex software systems against constantly changing technology solutions, by advocating the raising of the abstraction level in system specification and increas- ing automation in system development. The concept of model driven engineering emerged as a generalization of Model Driven Architecture (MDA) proposed by the Object Management Group (OMG) in 2001 [95]. The MDA based software development starts by building a Platform In- dependent Model (PIM) of that system which is refined and transformed to one or more Plat- form Specific Models (PSMs). Then, the PSMs are transformed to code. In this scenario, model transformation plays a central role. Many languages and tools have been proposed to specify and execute transformation programs. In 2002 the Object Management Group (OMG) issued the Query/View/Transformation (QVT) request for proposal [93] to define a standard transformation language, whereas in the meanwhile, a number of model transformation approaches have been proposed both from academia and industry.
    [Show full text]
  • Model Transformation Languages for Domain-Specific Workbenches
    Model Transformation Languages for Domain-Specific Workbenches DISSERTATION zur Erlangung des akademischen Grades doctor rerum naturalium (Dr. rer. nat.) im Fach Informatik eingereicht an der Mathematisch-Naturwissenschaftlichen Fakultät Humboldt-Universität zu Berlin von Arif Wider Präsident der Humboldt-Universität zu Berlin: Prof. Dr. Jan-Hendrik Olbertz Dekan der Mathematisch-Naturwissenschaftlichen Fakultät: Prof. Dr. Elmar Kulke Gutachter: 1. Prof. Dr. Joachim Fischer, Humboldt-Universität zu Berlin 2. Prof. Dr. Andreas Prinz, University of Agder, Norway 3. Prof. Dr. Krzysztof Czarnecki, University of Waterloo, Canada eingereicht am: 2. September 2014 Tag der Verteidigung: 18. November 2015 iii Abstract Domain-specific languages (DSLs) are software languages which are tailored to a specific application domain. DSLs enable domain experts to create domain-specific models, that is, high-level descriptions of domain knowledge. As any other software languages, DSLs rely on language tools which provide assistance for processing and managing domain-specific models. A domain-specific workbench is an integrated set of such tools for a DSL. A recently proposed approach is to automatically generate a domain-specific workbench for a DSL from a description of that DSL. However, existing tools which apply this approach do not support to describe and generate editable domain-specific views. A view is a part of domain-specific workbench that presents only one aspect of a model, for example, its hierarchical structure. This dissertation presents special model transformation languages which support the description of view synchronization in a generated domain-specific workbench. This allows a multi-view domain-specific workbench to be created with existing tools for language tool generation.
    [Show full text]
  • MDA-Based Modeling and Transformation to Generate N-Tiers Web Models
    Journal of Software MDA-Based Modeling and Transformation to Generate N-Tiers Web Models M'hamed Rahmouni*, Samir Mbarki Department of Computer Science, Faculty of Science, Ibn Tofail University, Kenitra, BP 133, Morocco. Corresponding author. Tel.: +212 664 79 94 44; email: [email protected] Manuscript submitted: August 8, 2014; accepted March 20, 2015. doi: 10.17706/jsw.10.3.222-238 Abstract: Data interchanges between companies are increasing. To improve this interchange and meet the increasing user needs, various frameworks and patterns are integrated for producing stable, maintainable and testable code. Some of the design patterns that will be used in the applications design and development are the MVC model, the DAO and DI (Dependency Injection) patterns. In this paper, we integrate these patterns to generate the N-tiers web model and thereafter generate the N-tiers application web code from this model. To obtain this, we start by modeling the Spring IoC, Struts2 and Hibernate frameworks for establishing their meta-models. Each framework from these is based on a pattern from the cited above. After establishing the different meta-models, we lead a model transformation process to generate N-tiers web model from the integrated meta-models. The model-to-model transformations are also clearly and formally established by using ATL transformation language. The model-to-code transformation will be the subject of the future work. Finally, a case study is provided to exemplify the generated PSM model respecting the architecture overview of MVC 2, DI and DAO patterns. Key words: MDA, hibernate DAO, spring IoC, struts, ATL transformation, n-tiers architecture.
    [Show full text]
  • A Framework to Formalise the MDE Foundations Xavier Thirioux, Benoit Combemale, Xavier Crégut, Pierre-Loïc Garoche
    A Framework to Formalise the MDE Foundations Xavier Thirioux, Benoit Combemale, Xavier Crégut, Pierre-Loïc Garoche To cite this version: Xavier Thirioux, Benoit Combemale, Xavier Crégut, Pierre-Loïc Garoche. A Framework to Formalise the MDE Foundations. International Workshop on Towers of Models (TOWERS 2007), Jun 2007, Zurich, Switzerland. pp.14-30. hal-00159748v2 HAL Id: hal-00159748 https://hal.archives-ouvertes.fr/hal-00159748v2 Submitted on 8 Jul 2007 HAL is a multi-disciplinary open access L’archive ouverte pluridisciplinaire HAL, est archive for the deposit and dissemination of sci- destinée au dépôt et à la diffusion de documents entific research documents, whether they are pub- scientifiques de niveau recherche, publiés ou non, lished or not. The documents may come from émanant des établissements d’enseignement et de teaching and research institutions in France or recherche français ou étrangers, des laboratoires abroad, or from public or private research centers. publics ou privés. A Framework to Formalise the MDE Foundations Xavier Thirioux, Benoît Combemale, Xavier Crégut, and Pierre-Loïc Garoche Institut de Recherche en Informatique de Toulouse (CNRS UMR 5505), Toulouse, France [email protected] Abstract. Domain-Specific Language (DSL) are getting more and more popular and are being used in critical systems like aerospace and car industries. Methods for simulating and validating DSL models are now necessary in order to make the new software generation more reliable and less costly. Developing analysis tools for DSL requires the definition of models semantics. In this paper, we propose a framework to give a formal foundation of the Model- Driven Engineering (MDE) approach.
    [Show full text]
  • Model-Driven Analysis and Synthesis of Textual Concrete Syntax
    Model-Driven Analysis and Synthesis of Textual Concrete Syntax Pierre-Alain Muller1, Frédéric Fondement2, Franck Fleurey3, Michel Hassenforder2, Rémi Schnekenburger4, Sébastien Gérard4, Jean-Marc Jézéquel1 1 IRISA / INRIA Rennes Rennes, France {pierre-alain.muller, jean-marc.jezequel}@irisa.fr 2 Université de Haute-Alsace, MIPS Mulhouse, France {frederic.fondement, michel.hassenforder}@uha.fr 3 SINTEF Oslo, Norway [email protected] 4 CEA, LIST Gif-sur-Yvette, France {remi.schneckenburger, sebastien.gerard}@cea.fr Abstract. Meta-modeling is raising more and more interest in the field of language engineering. While this approach is now well understood for defining abstract syntaxes, formally defining textual concrete syntaxes with meta-models is still a challenge. Textual concrete syntaxes are traditionally expressed with rules, conforming to EBNF-like grammars, which can be processed by compiler compilers to generate parsers. Unfortunately, these generated parsers produce concrete syntax trees, leaving a gap with the abstract syntax defined by meta- models, and further ad-hoc hand-coding is required. In this paper we propose a new kind of specification for concrete syntaxes, which takes advantage of meta- models to generate fully operational tools (such as parsers or text generators). The principle is to map abstract syntaxes to textual concrete syntaxes via bidirectional mapping-models with support for both model-to-text, and text-to- model transformations. 1 Introduction Meta-languages such as MOF [1], Ecore [2], Emfatic [3], KM3 [4] or Kermeta [5], model interchange facilities such as XMI [6] and tools such as Netbeans MDR [7] or Eclipse EMF [2] can be used for a wide range of purposes, including language engineering.
    [Show full text]