"Families to Persons"

Transcription

1 "" A simple illustration of model-to to-model transformation Freddy Allilaire Frédéric Jouault ATLAS group, INRIA & University of Nantes, France -1-

2 Context of this work The present courseware has been elaborated in the context of the Usine Logicielle project ( of the cluster Paris- Région with the support of the Direction Générale des Entreprises, Conseil Régional d Ile de France, Conseil Général des Yvelines, Conseil Général de l'essonne, and Conseil Général des Hauts de Seine. The MDD courseware provided here with the status of open source software is produced under the EPL 1.0 license. -2-

3 Overview This presentation describes a very simple model transformation example, some kind of ATL "hello world". It is intended to be extended later. The presentation is composed of the following parts: Prerequisites. Introduction. Metamodeling. Transformation. Conclusion. -3-

4 Prerequisites In the presentation we will not discuss the prerequisites. The interested reader may look in another presentation to these prerequisites on: MDE (MOF, XMI, OCL). Eclipse/EMF (ECORE). AMMA/ATL. -4-

5 Introduction The goal is to present a use case of a model to model transformation written in ATL. This use case is named:. Initially we have a text describing a list of families. We want to transform this into another text describing a list of persons. -5-

6 Goal of the ATL transformation we are going to write Transforming this Family March Father: Jim Mother: Cindy Son: Brandon Daughter: Brenda other Families into this. Mr. Jim March Mrs. Cindy March Mr. Brandon March Mrs. Brenda March other Persons Let's suppose these are not texts, but models (we'll discuss the correspondence between models and texts later). -6-

7 Input of the transformation is a model Family March Father: Jim Mother: Cindy Son: Brandon Daughter: Brenda Family Sailor Father: Peter Mother: Jackie Son: David Son: Dylan Daughter: Kelly This is the text. This is the corresponding model. It is expressed in XMI, a standard way to represent models. -7-

8 Output of the transformation should be a model Mr. Dylan Sailor Mr. Peter Sailor Mr. Brandon March Mr. Jim March Mr. David Sailor Mrs. Jackie Sailor Mrs. Brenda March Mrs. Cindy March Mrs. Kelly Sailor <?xml version="1.0" encoding="iso "?> <xmi:xmi xmi:version="2.0" xmlns:xmi=" xmlns="persons"> <Male fullname="dylan Sailor"/> <Male fullname="peter Sailor"/> <Male fullname="brandon March"/> <Male fullname="jim March"/> <Male fullname="david Sailor"/> <Female fullname="jackie Sailor"/> <Female fullname="brenda March"/> <Female fullname="cindy March"/> <Female fullname="kelly Sailor"/> </xmi:xmi> This is the text. This is the corresponding model (The corresponding XMI file is named "sample-persons.ecore"). -8-

9 Each model conforms to a metamodel Source metamodel Target metamodel conformsto conformsto Source model "sample-families.ecore" Target model "sample-persons.ecore" -9-

10 The general picture conformsto Metametamodel (ECORE) conformsto Source metamodel conformsto Target metamodel conformsto conformsto Source model Target model -10-

11 What we need to provide In order to achieve the transformation, we need to provide: 1. A source metamodel in KM3 ("Families"). 2. A source model (in XMI) conforming to "Families". 3. A target metamodel in KM3 ("Persons"). 4. A transformation model in ATL ("Families2Persons"). When the ATL transformation is executed, we obtain: A target model (in XMI) conforming to "Persons". -11-

12 Definition of the source metamodel "Families" What is Families : A collection of families. Each family has a name and is composed of members: A father A mother Several sons Several daughters Each family member has a first name. Family March Father: Jim Mother: Cindy Son: Brandon Daughter: Brenda Family Sailor Father: Peter Mother: Jackie Sons: David, Dylan Daughter: Kelly Family lastname : String familyfather familymother familyson familydaughter father 1 mother 1 sons * daughters * Member firstname : String -12-

13 "Families" metamodel (visual presentation and KM3) Family lastname : String familyfather father 1 familymother mother 1 familyson sons * familydaughter daughters * Member firstname : String -13-

14 "Persons" metamodel (visual presentation and KM3) Person fullname Male Female -14-

15 The big picture Eclipse Modeling Framework (EMF) 1. Our goal in this mini-tutorial is to write the ATL transformation, stored in the "Families2Persons" file. M3 Ecore.ecore 2. Prior to the execution of this transformation the resulting file "sample-persons.ecore" does not exist. It is created by the transformation. M2 Families.km3 ATL.km3 Persons.km3 3. Before defining the transformation itself, we need to define the source and target metamodels ("Families.km3" and "Person.KM3"). M1 sample- Families.ecore Families2Persons.atl sample- Persons.ecore 4. We take for granted that the definition of the ATL language is available (supposedly in the "ATL.km3" file). 5. Similarly we take for granted that the environment provides the recursive definition of the metametamodel (supposedly in the "Ecore.ecore" file). -15-

16 Architecture M3 Eclipse Modeling Framework (EMF) Ecore.ecore 1. Families and Persons metamodels have been created previously. 2. They have been written in the KM3 metamodel specification DSL (Domain Specific Language). M2 Families.km3 ATL.km3 Persons.km3 M1 Families2Persons.atl -16- sample- Families.ecore sample- Persons.ecore

17 Architecture M3 Eclipse Modeling Framework (EMF) Ecore.ecore 1. The following file is the sample that we will use as source model in this use case: M2 Families.km3 ATL.km3 Persons.km3 M1 Families2Persons.atl -17- sample- Families.ecore sample- Persons.ecore

18 Architecture M3 M2 Eclipse Modeling Framework (EMF) Ecore.ecore Families.km3 ATL.km3 Persons.km3 1. Now, let us start the creation of the ATL transformation Families2Persons.atl. 2. We suppose the ATL environment is already installed. 3. The creation of the ATL transformation will follow several steps as described in the next slides. M1 Families2Persons.atl -18- sample- Families.ecore sample- Persons.ecore

19 : project creation First we create an ATL project by using the ATL Project Wizard. -19-

20 : ATL transformation creation Next we create the ATL transformation. To do this, we use the ATL File Wizard. This will generate automatically the header section. IN: Name of the source model in the transformation OUT: Name of the target model in the transformation Families: Name of the source metamodel in the transformation Persons: Name of the target metamodel in the transformation -20-

21 : header section The header section names the transformation module and names the variables corresponding to the source and target models ("IN" and "OUT") together with their metamodels ("Persons" and "Families") acting as types. The header section of "Families2Persons" is: -21-

22 : helper "isfemale()" A helper is an auxiliary function that computes a result needed in a rule. The following helper "isfemale()" computes the gender of the current member: Family lastname : String familyfather familymother familyson familydaughter father 1 mother 1 sons * daughters * Member firstname : String -22-

23 : helper "familyname" The family name is not directly contained in class Member. The following helper returns the family name by navigating the relation between Family and Member : Family lastname : String familyfather familymother familyson familydaughter father 1 mother 1 sons * daughters Member firstname : String * -23-

24 : writing the rules After the helpers we now write the rules: Member to Male rule Member2Male { from s : Families!Member (not s.isfemale()) to t : Persons!Male ( fullname <- s.firstname + ' ' + s.familyname ) } Member to Female rule Member2Female { from s : Families!Member (s.isfemale()) to t : Persons!Female ( fullname <- s.firstname + ' ' + s.familyname ) } -24-

25 Summary of the Transformation Family lastname : String familyfather familymother familyson familydaughter Male + If isfemale() Female Else Male Person fullname : String father 1 mother 1 sons * daughters * Female Member firstname : String 1. For each instance of the class "Member" in the IN model, create an instance in the OUT model. 2. If the original "Member" instance is a "mother" or one of the "daughters" of a given "Family", then we create an instance of the "Female" class in the OUT model. 3. If the original "Member" instance is a "father" or one of the "sons" of a given "Family", then we create an instance of the "Male" class in the OUT model. 4. In both cases, the "fullname" of the created instance is the concatenation of the Member "firstname" and of the Family "lastname", separated by a blank. -25-

26 Architecture Eclipse Modeling Framework (EMF) 1. Once the ATL transformation Families2Persons is created, we can execute it to build the OUT model. M3 M2 Ecore.ecore Families.km3 ATL.km3 Persons.km3 M1 Families2Persons.atl -26- sample- Families.ecore sample- Persons.ecore

27 ATL Launch Configuration

28 ATL Launch Configuration

29 Summary We have presented here a "hello world" level basic ATL transformation. This is not a recommendation on how to program in ATL, just an initial example. Several questions have not been answered Like how to transform a text into an XMI-encoded model. Or how to transform the XMI-encoded result into text. For any further questions, see the documentation mentioned in the resource page (FAQ, Manual, Examples, etc.). -29-

30 ATL Resource page ATL Home page ATL Documentation page ATL Newsgroup news://news.eclipse.org/eclipse.modeling.m2m ATL Wiki

31 Working on the example Person fullname: String grandparent There are a lot of exercise questions that could be based on this simple example. Male Female For example, modify the target metamodel as shown and compute the "grandparent" for any Person. -31-