- PDF Free Download

Size: px

Start display at page:

Download ""

Adelia McKinney
6 years ago
Views:

1 Rubby Casallas Grupo de Construcción de Software Uniandes 1

2 ATL and OCL Matched Rules Lazy Rules Called Rules ATL Execution modes ATL execution semantics ATL language is based on OMG OCL (Object Constraint Language: data types declarative expressions ATL language is an hybrid Language declarative : matched rules, and called rules body. imperative : called rules and lazy rules (imperatively called action blocks ("do", usable in any rules 2

3 ! Represent the possible instances of the OclType class #! ATL supports: comparison operators: =, <>; oclisundefined(: returns a boolean value stating whether self is undefined; ocliskindof(t : ocltype: returns a boolean value stating whether self is an either an instance of t or of one of its subtypes; oclistypeof(t : ocltype: returns a boolean value stating whether self is an instance of t. " 3

4 ATL and OCL Matched Rules Lazy Rules Called Rules ATL Execution modes ATL execution semantics $ & '( rule rule_name { in_var : in_type [( condition ]? [using { var1 : var_type1 = init_exp1; varn : var_typen = init_expn; ]? to out_var1 : out_type1 ( bindings1, out_var2 : distinct out_type2 foreach(e in collection( bindings2, out_varn : out_typen ( bindingsn [do { statements ]? % 4

5 & '(*( rule rule_name { in_var : in_type [( condition ]? [using { var1 : var_type1 = init_exp1; varn : var_typen = init_expn; ]? p : MMPerson!Person ( p.name = 'Smith' p : MMPerson!Person ( true is equivalent to: p : MMPerson!Person & '(*(,-. rule rule_name { in_var : in_type [( condition ]? [using { var1 : var_type1 = init_exp1; varn : var_typen = init_expn; ]? Local Variables to the rule c : GeometricElement!Circle using { pi : Real = 3.14; area : Real = pi *.radius.square(; + 5

6 & '(( rule Journal2Book { j : Biblio!Journal to b : Biblio!Book ( title <- j.title + '_(' + j.vol + ':' + j.num, authors <- j.articles ->collect(e e.authors->flatten(->asset(, chapters <- j.articles, pagesnb <- j.articles->collect(e e.pagesnb->sum( feature of b & '(( rule Journal2Book { j : Biblio!Journal to b : Biblio!Book ( title <- j.title + '_(' + j.vol + ':' + j.num, authors <- j.articles ->collect(e e.authors->flatten(->asset(, chapters <- j.articles, pagesnb <- j.articles->collect(e e.pagesnb->sum( binding = feature-name <- OCL_expr 6

7 ( /0 (1 rule Journal2Book { j : Biblio!Journal to b : Biblio!Book ( title <- j.title + '_(' + j.vol + ':' + j.num, authors <- j.articles ->collect(e e.authors->flatten(->asset(, chapters <- j.articles, pagesnb <- j.articles->collect(e e.pagesnb->sum( 1. the title of the Book corresponds to the title of the journal concatenated with its volume (vol and its number (num; 2. the chapters of the Book correspond to the model elements that will be generated for the articles of the source Journal; 3. the authors of the Book correspond to the authors of the different articles of the source Journal, without any duplicate; 4. the attribute pagesnb is initialized with the sum of the number of pages (pagesnb of the articles of the source Journal. ( 0 (1 assigning to a reference: 1. a target model element generated by the current rule; 2. the default target model element of another rule; 3. a non-default target model element of another rule. 7

8 ( 0 (1 assigning to a reference: 1. a target model element generated by the current rule; rule Case1 { i : MM_A!ClassA to o_1 : MM_B!Class1 ( linktoclass2 <- o_2, o_2 : MM_B!Class2 ( ( 0 (1 assigning to a reference: 2. the default target model element of another rule; rule Case2_R1 { i : MM_A!ClassA to o_1 : MM_B!Class1 ( linktoclass2 <- i.linktoclassb rule Class2Table { c : Class!Class to out : Relational!Table ( col <- union(c.attr, rule Case2_R2 { i : MM_A!ClassB to o_1 : MM_B!Class2 (, rule DataTypeAttribute2Column { a : Class!Attribute to out : Relational!Column ( name <- a.name, type <- a.type " 8

9 ( 0 (1 assigning to a reference: 3. a non-default target model element of another rule. rule Case2_R1 { i : MM_A!ClassA to o_1 : MM_B!Class1 ( linktoclass2 <- thismodule.resolvetemp(i.linktoclassb, 'o_n' rule Case2_R2 { i : MM_A!ClassB to o_1 : MM_B!Class3 (, o_n : MM_B!Class2 (, $ 0! 2/(3! ( A sequence of ATL imperative statements that are executed after the target initialization helper def : id : Integer = 0; rule Journal2Book { j : Biblio!Journal to b : Biblio!Book ( do { thismodule.id <- thismodule.id + 1; b.id <- thismodule.id; % 9

10 ATL and OCL Matched Rules Lazy Rules Called Rules ATL Execution modes ATL execution semantics 1 ( Imperative rules, called explicitly lazy rule getcross { i: ecore!eobject to rel: metamodel!relationship ( rule Example { s : ecore!eobject to t : metamodel!node ( name <- s.tostring(, edges <- thismodule.getcross(s rule Example { s : ecore!eobject to t : metamodel!node ( name <- s.tostring(, edges <- ecore!eclass.allinstancesfrom('yourmodel'-> collect(e thismodule.getcross(e + 10

11 (( [entrypoint]? rule rule_name(parameters{ [using { var1 : var_type1 = init_exp1; varn : var_typen = init_expn; ]? [ to out_var1 : out_type1 ( bindings1, out_var2 : distinct out_type2 foreach(e in collection ( bindings2, out_varn : out_typen ( bindingsn ]? [do { statements ]? Except for the entrypoint called rule, this kind of rules must be explicitly called an ATL imperative block (( no more than one entry point [entrypoint]? rule rule_name(parameters{ rule_name different any helper name [using { var1 : var_type1 = init_exp1; specified in the same way than for helpers varn : var_typen = init_expn; ]? declare and initialize local variables [ to out_var1 : out_type1 ( bindings1 target pattern, out_var2 : distinct out_type2 foreach(e in collection ( bindings2, out_varn : out_typen ( bindingsn ]? [do { statements ]? 11

12 45& Two different execution modes for ATL modules: Normal (default execution mode: Developer has to specify, (matched or called rules, the way to generate each of the expected target model elements (source metamodel is different target metamodel Refining execution mode Developers can focus on the ATL code dedicated to the generation of modified target elements (similar source and target metamodel &(5 Three phases: a module initialization phase: a matching phase of the source model elements a target model elements initialization phase 12

13 &(5 Three phases: a module initialization phase: first, attributes initialization then, called rule with an entrypoint (if any a matching phase of the source model elements: matching condition are tested with the model elements of the source. if it is matched, ATL engine allocates the set of target model elements a target model elements initialization phase: each allocated target model element is initialized by executing the code of the bindings that are associated 13

Model transformations. Overview of DSLE. Model transformations. Model transformations. The 4-layer architecture

Model transformations. Overview of DSLE. Model transformations. Model transformations. The 4-layer architecture Overview of DSLE Model driven software engineering g in general Grammars, signatures and meta-models DSL Design Code generation Models increase the level of abstraction used for both hardware and software