Copying Subgraphs within Model Repositories

Transcription

1 Copying Subgraphs within Model Repositories Pieter van Gorp, Hans Schippers, Dirk Janssens April 2, / 37

2 Contents Languages 2 / 37

3 Outline Languages 3 / 37

4 : Model Driven Software Engineering Model A simplified representation of a part of the world, named the system [Sei03] Repositories Databases: serializing into standard formats (like XMI), exposing a query and transformation API (like OCL and JMI). Challenge Manage consistency between and within models: check and transform Platforms Matter Generative (more complex than interpretative, cfr. ToolNet pres.) 4 / 37

5 : Extending Graph Transformation Why Graph Transformation? Ability to model a model transformation Research Goal Extend graph transformation: model transformations can be programmed at a high level of abstraction, while the low-level APIs of mainstream model repositories are interfaced by means of compilers. not just interpreting the rules, execute them on a COTS modeling tool. 5 / 37

6 Outline Languages 6 / 37

7 Conceptual and Robustness Model Schedule +type : Schedule Type [1] +acceptablelimit : int +cancellimit : int Initiator +excludedby 0..* 1..* Attendee 0..* +participation 0..* +exclusion 0..* +from 1 Login Form Time Interval 0..* +preferredby 0..* +preference +to Moment 1 0..* Account Service Flexibility +level : int <<Entity>> Person 1 +user Person Attendee Main Screen Confirm Meeting Mail Status Service <<Entity>> Schedule <<Entity>> Meeting Location 7 / 37

8 Graphs? = Abstract Syntax Node n1. Type: Model Attribute values: name= "Data" Node n2.... Type: UmlPackage Links: Attribute values: l1 (to n2, label "ownedelement") name= "Examples" Links: l2 (to n3, label "ownedelement" ) l1 (to n1, label "namespace") Node n3. Type: UmlPackage Attribute values: Node n4. name= "Meeting Scheduler" Type: Model Links: Attribute values: l3 (to n4, label "ownedelement") name= "CM"... visibility= Public Links: l4 (to n7, label "stereotype") Node n5. Type: Stereotype Attribute values: name= "Foreign Key" baseclass= "Classifier"... Node n6. Type: UmlPackage Attributes values: name= "Robustness Modeling" Links: l5 (to n7, label "ownedelement") Node n7. Type: Stereotype Attributes values: name= "Conceptual Model" Links: l4 (to n4, label "extendedelement") l5 (to n6, label "namespace") 8 / 37

9 : Each class in the conceptual model should correspond to an entity in the robustness model. Constraint Violation Scenario only conceptual model has been developed, no robustness model yet Repairing Transformation generate robustness model from the conceptual model duplicate classes with their attributes as entities no services, no screens Consistency Constraint 9 / 37

10 Outline Languages 10 / 37

11 Trfo Language: Node instances are typed by classes (attributes, associations, inheritance) Primitive Operations: Create/Delete a Node/Edge, Update attribute values Control Structure: Sequence of rewrite rules: introduces bound nodes, loop, branch, method call UML-alike syntax: Fujaba (large community) Standard UML syntax: UML Profile for SDM (MoTMoT) 11 / 37

12 gencopyof_cm {motmot.transprimitive=gencopyof_cm} gencopyof_classincm {motmot.transprimitive=gencopyof_classincm} <<failure>> checkexists_classincmcopy {motmot.transprimitive=checkexistsclassincmcopy} <<failure>> checkexists_cmcopy {motmot.transprimitive=checkexistscmcopy} <<each time>> gencopyof_a {motmot.transprimitive=gencopyof_a} handleoncopy_classincm_null_a {motmot.transprimitive=handleoncopy_classincm_null_a} handleoncopy_cm_null_stereotypeonrm {motmot.transprimitive=handleoncopy_cm_null_stereotypeonrm} handleoncopy_cm_null_wodnapplication {motmot.transprimitive=handleoncopy_cm_null_wodnapplication} <<failure>> checkexists_acopy handleoncopy_classincm_null_entitystereotype {motmot.transprimitive=checkexistsacopy} {motmot.transprimitive=handleoncopy_classincm_null_entitystereotype} <<each time>> <<loop>> select_a_aspart {motmot.transprimitive=select_a_aspart} <<loop>> select_classincm_aspart Lookup Stereotypes in Profiles {motmot.transprimitive=select_classincm_aspart} {motmot.transprimitive=lookupstereotypes} <<success>> <<loop>> Deep Copy of Classes {motmot.transprimitive=docopy} <<failure>> <<each time>> <<success>> <<failure>> <<code>> Print name of RM <<code>> Print success 12 / 37

13 Selecting the conceptual model (CM) applicationmodel : Model <<closure>> +ownedelement * wodnapplication : UmlPackage {motmot.constraint=name.equals(this.getapplicationname())} * cm: Model +ownedelement +stereotype * stereotypeoncm : Stereotype <<copy>> removed Addition of <<Robustnes Model>> stereotype (using <<oncopy>> is removed stereotypeonrm : Stereotype Class and Attribute nodes removed Only used in subsequent stories entitystereotype : Stereotype 13 / 37

14 Is CM already copied? copyof_cm: Model cm: Model content 1 content 1 node node cmnode : be.ac.ua.fots.metamodels.traceability.node copyof_cmnode : be.ac.ua.fots.metamodels.traceability.node node node link 1 link 1 trlinkforcopy: Link 14 / 37

15 Generate Copy of CM node copyof_cm: be.ac.ua.fots.metamodels.traceability.node node content 1 copyof_cm: Model -isactive = cm.isactive() -visibility = cm.getvisibility() -isspecification = cm.isspecification() -isroot = cm.isroot() -isleaf = cm.isleaf() -isabstract = cm.isabstract() +name : String = "RM" this: CM2RMImpl traceabilitylinks * trlinkforcopy: Link link 1 link 1 node cmnode : be.ac.ua.fots.metamodels.traceability.node node content 1 cm: Model 15 / 37

16 Add Conceptual Model Stereotype to Copy copyof_cm: Model extendedelement stereotype * stereotypeonrm : Stereotype 16 / 37

17 Add Copy to containing package wodnapplication : UmlPackage namespace ownedelement * copyof_cm: Model 17 / 37

18 Selecting class in CM cm: Model +ownedelement 0..* classincm : UmlClass 18 / 37

19 Is class already copied? copyof_classincm: UmlClass classincm : UmlClass 1 content 1 content node node classincmnode : be.ac.ua.fots.metamodels.traceability.node copyof_classincmnode : be.ac.ua.fots.metamodels.traceability.node node node 1 1 trlinkforcopy: Link link link 19 / 37

20 Generate Copy of class node copyof_cm: be.ac.ua.fots.metamodels.traceability.node node content 1 copyof_cm: Model -isactive = cm.isactive() -visibility = cm.getvisibility() -isspecification = cm.isspecification() -isroot = cm.isroot() -isleaf = cm.isleaf() -isabstract = cm.isabstract() +name : String = "RM" this: CM2RMImpl traceabilitylinks * trlinkforcopy: Link link 1 link 1 node cmnode : be.ac.ua.fots.metamodels.traceability.node node content 1 cm: Model 20 / 37

21 Add Entity Stereotype to Copy copyof_classincm : UmlClass extendedelement stereotype * entitystereotype : Stereotype 21 / 37

22 Story Patterns for Attribute Once more: Check if already copied, Generate Copy Create links to copy Primitives for Attribute 22 / 37

23 from plain SDM This is not a model of the transformation! = Extend the UML Profile for SDM 23 / 37

24 Outline Languages 24 / 37

25 CM to RM using Copy Operator applicationmodel : Model <<closure>> * +ownedelement wodnapplication : UmlPackage {motmot.constraint=name.equals(this.getapplicationname())} * +ownedelement <<oncopy>> * +ownedelement <<copy>> cm: Model <<oncopy>>+name : String = "RM" +ownedelement 0..* classincm : UmlClass <<oncopy>> +ownedelement 0..* a: Attribute * +stereotype stereotypeoncm : Stereotype <<oncopy>> * +stereotype * +stereotype CM2RM Copy Operator stereotypeonrm : Stereotype entitystereotype : Stereotype 25 / 37

26 Extension to UML Profile copy entry point to the subgraph that needs to be copied root of decorated tree composition Each node and link on this path will be copied. oncopy instruction executed on the copy of an element. association ends of create attribute assignments Note: composition also specifies selection of source elements ( association with two oncopy ends) 26 / 37

27 Well-formedness Rules At least one link should be created from the host graph to a node from the copied subgraph. Apply oncopy instruction only on: attributes inside a copied node, or association ends connected to a copied node. A node should be part of at most one composition. ab1 <<copy>> a: A ab2 b b1: B * b b2: B * <<copy>> c: C a: A c 1 <<copy>> d: D ab * b1: B b db * 1 b2: B c: C b c ab1 <<copy>> a: A ab2 * b b: B c c: C 1 1 b 27 / 37

28 Part 2 of WFR 2: context inv : Remark: OCL Implementation AssociationEnd hasstereotype ( self, " oncopy ") implies ( -- connected class contains <<copy >> stereotype hasstereotype ( self. participant, " copy ") or ( -- or end of class at other side is composite self. participant. ocliskindof ( Classifier ) and self. participant. oclastype ( Classifier ). association. association. connection - > exists ( end2 self <> end2 and end2. aggregation = AggregationKind :: composite ) ) ) 28 / 37

29 Outline Languages 29 / 37

30 Hierarchical GT Assumption: transformed graphs can be decomposed into frames where edges are not allowed to cross frame boundaries. required for proving that rewrite rules do not violate grammatical constraints, but nested visual languages like the UML require a more flexible decomposition mechanism [DHP02], feedback for copy operator: automatically copy all edges between the nodes in a frame 30 / 37

31 Shape Grammars define frame variables in the scope of a rewrite rule instead of in the scope of the complete rewriting system [Ber03]. Refactoring Another model transformation case study can apply transformation model compiler! Extend case study from [HJE05]: consider more grammatical constructs. Strict grammar based approach more attractive than controlled GT? 31 / 37

32 Graph Transformation Theory New operation: copying subgraphs More compact specification in context of model refinement, refactoring Only implementation is specific to model repositories, concept is applicable to any graph with OO types In Practice Integrated into UML Profile for Story Driven Modeling M2M transformation most promising for making operator executable 32 / 37

33 Ongoing and Future Work Making Copy Operator Executable Extend M2C Templates for SDM M2M refinement into plain SDM: MoTMoT independent! Using conditionals presented here Using Reflective helper method Complete Case Studies Learn from Integrating: UML Profiles (CM, RM), MOF (Traceability), OCL (Check Consistency ), Graph Transfo (Realize Consistency), JMI, J2EE,... (Platforms) = Maximal Reuse, Minimal Lockin 33 / 37

34 The end Thank you! Questions? 34 / 37

35 References Berthold Hoffmann. Abstraction and Control for Shapely Nested Graph Transformation. Fundamenta Informaticae, 58(1):39 65, Frank Drewes, Berthold Hoffmann, and Detlef Plump. Hierarchical graph transformation. Journal of Computer and System Sciences, 64: , Berthold Hoffmann, Dirk Janssens, and Niels Van Eetvelde. Cloning and expanding graph transformation rules for refactoring. In International Workshop on Graph and Model Transformation, Tallinn, Estonia, A satellite event of GPCE 05. E Seidewitz. What models mean. IEEE Software, 20, Sept.-Oct / 37

36 Use of UML Profiles No restiction: CM and RM could have different MOF metamodels, could even reside in different repositories! Simple correspondence: baseclass property of stereotype indicates the superclass of a new metaclass with the name of the stereotype tags defined on stereotype become attributes of the new metaclass UML Tool Implementation: The new metaclasses (M2) could be referenced from UML XMI files (M1). Only accessible through MOF reflection, not through static (e.g. generated JMI) interfaces of repository. 36 / 37

37 Use of UML Profiles (cont) Unconventional: meta-object protocol using a conforms to relation different from the instance of relation Not dramatic: Concrete syntax of CM and RM is OK! Model transformation doesn t become more complex. Most Importantly: Copying subgraphs would still be required! 37 / 37