Changes for page Transformation Mapping (KTM)
Last modified by Richard Kreissig on 2023/09/14 11:14
<
>
edited by Alexander Schulz-Rosengarten
on 2013/12/18 16:30
on 2013/12/18 16:30
edited by Alexander Schulz-Rosengarten
on 2014/01/03 17:00
on 2014/01/03 17:00
Change comment:
added example for Mapping and TransformationTree creation
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Objects (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -10,7 +10,7 @@ 10 10 11 11 This subproject provides a tracing mechanism for arbitary model-elements across multiple model transformations, based on EMF. 12 12 13 -The main propose of KTM is to allow information transfer between abstract models and their resultant transformed models. 13 +The main propose of KTM is to allow bidirectional information transfer between abstract models and their resultant transformed models. 14 14 15 15 ---- 16 16 ... ... @@ -26,9 +26,9 @@ 26 26 27 27 The structure of the model can be separated into two parts. 28 28 29 -**First part** (upper half) is a tree of transformations. Each Model- Class is a representation of a concrete model which is transformed. So models are nodes and ModelTransformations are edges. Thus the Model representing the root-model of a tree is also the root of a concrete TransformationTree-Model.29 +**First part** (upper half) is a tree of transformations. Each Model-class is a representation of a concrete model which is transformed. So models are nodes and ModelTransformations are edges. Thus the Model representing the root-model of a tree is also the root of a concrete TransformationTree-model. 30 30 31 -**Second part** (lower half) is object Concretemodels contain EObjects as their elements, which are represented by Element-Class in TransformationTree metamodel. The Elements of two models are connected with ElementTransformations-Class to model their origination relationship in corresponding model transformation.31 +**Second part** (lower half) is object-mapping. Instances of models contain EObjects as their elements, which are represented by Element-class in TransformationTree metamodel. The Elements of two models are connected with ElementTransformations-class to model their origination relationship in corresponding model transformation. 32 32 33 33 34 34 ... ... @@ -44,9 +44,9 @@ 44 44 45 45 === TransformationMapping ([[JavaDoc>>attach:TransformationMapping.html]]) === 46 46 47 -The main propose of this class is generation of a Object47 +The main propose of this class is generation of a object-mapping during transformation process. 48 48 49 -Therefor it provides different functions for incremental registering of single parent 49 +Therefor it provides different functions for incremental registering of single parent-child-relations between EObjects. 50 50 51 51 Furthermore, the extension allows to extract the mapping and check completeness of mapped elements against content of transformed models. 52 52 ... ... @@ -56,15 +56,117 @@ 56 56 57 57 Furthermore, it allows to modify trees by creating, deleting or appending new transformations and transformed models. 58 58 59 +Additionally this extension provides functionality to extract a concrete mapping between two arbitary model intances from a TransformationTree. 60 + 59 59 ---- 60 60 61 61 == Implementation Details == 62 62 63 -* All references to EObjects are references to a copy of the original EObject. This allows to represent immutable mapping. To reidentify corresponding EObjects TransformationTreeExtensions provides search functions a ndmatchingfunctionality.65 +* All references to EObjects are references to a copy of the original EObject. This allows to represent immutable mapping. To reidentify corresponding EObjects TransformationTreeExtensions provides search functions which will check for structural matching models. 64 64 * Models in TransformationTrees may be transient. This indicates that all references to EObjects in all Elements of the transient model are removed. Thus these models can't be source of a new appended transformation and can not be associated with it's original model. The main propose of this feature is to improve scalability of TransformationTrees by removing unnecessary references to internal model, but preserve traversing functionality of the ObjectMapping. 67 +* Mappings can be incomplete causing resulting transfromation tree to be incomplete. A incomplete tree does not represent every object in a model with a corresponding Element. This may break some paths of element transformations, but allows to omit model-immanent objects like annotations from mapping. TranformationMapping extension provies a function to check completeness of mapping against its models. 65 65 66 66 ---- 67 67 68 68 == Example == 69 69 70 -coming soon 73 +=== Creating Mapping during Transformation === 74 + 75 +The following code is a modifcation of the tranformation "Spilt Trigger and Effects" of SCCharts. 76 + 77 +{{code title="Modified SCChart Transformation" theme="Eclipse" linenumbers="true" language="java" firstline="1" collapse="true"}} 78 +package de.cau.cs.kieler.ktm.test.transformations 79 + 80 +import com.google.inject.Inject 81 +import de.cau.cs.kieler.ktm.extensions.TransformationMapping 82 +import de.cau.cs.kieler.sccharts.Region 83 +import de.cau.cs.kieler.sccharts.Transition 84 +import de.cau.cs.kieler.sccharts.extensions.SCChartsExtension 85 +/** 86 + * @author als 87 + */ 88 +class SCChartTestTransformation { 89 + @Inject 90 + extension TransformationMapping 91 + @Inject 92 + extension SCChartsExtension 93 + 94 + // -- Mapping Access 95 + def extractMapping() { 96 + extractMappingData; 97 + } 98 + 99 + //------------------------------------------------------------------------- 100 + //-- S P L I T T R A N S I T I O N -- 101 + //------------------------------------------------------------------------- 102 + // For every transition T that has both, a trigger and an effect do the following: 103 + // For every effect: 104 + // Create a conditional C and add it to the parent of T's source state S_src. 105 + // create a new true triggered immediate effect transition T_eff and move all effects of T to T_eff. 106 + // Set the T_eff to have T's target state. Set T to have the target C. 107 + // Add T_eff to C's outgoing transitions. 108 + def Region transformTriggerEffect(Region rootRegion) { 109 + // Clone the complete SCCharts region 110 + var targetRootRegion = rootRegion.mappedCopy; //NEW - mapping information (changed copy to mappedCopy) 111 + // Traverse all transitions 112 + for (targetTransition : targetRootRegion.getAllContainedTransitions) { 113 + targetTransition.transformTriggerEffect(targetRootRegion); 114 + } 115 + targetRootRegion; 116 + } 117 + def void transformTriggerEffect(Transition transition, Region targetRootRegion) { 118 + // Only apply this to transition that have both, a trigger and one or more effects 119 + if (((transition.trigger != null || !transition.immediate) && !transition.effects.nullOrEmpty) || transition.effects.size > 1) { 120 + val targetState = transition.targetState 121 + val parentRegion = targetState.parentRegion 122 + val transitionOriginalTarget = transition.targetState 123 + var Transition lastTransition = transition 124 + for (effect : transition.effects.immutableCopy) { 125 + val effectState = parentRegion.createState(targetState.id + effect.id) 126 + effectState.mapParents(transition.mappedParents); //NEW - mapping information 127 + effectState.setTypeConnector 128 + val effectTransition = createImmediateTransition.addEffect(effect) 129 + effectTransition.mapParents(transition.mappedParents); //NEW - mapping information 130 + effectTransition.setSourceState(effectState) 131 + lastTransition.setTargetState(effectState) 132 + lastTransition = effectTransition 133 + } 134 + lastTransition.setTargetState(transitionOriginalTarget) 135 + } 136 + } 137 +} 138 +{{/code}} 139 + 140 +=== Create TransformationTree with Mapping === 141 + 142 +To test the transformation and mapping we will transform th following ABO-SCChart. 143 + 144 +[[image:attach:example_abo.jpeg]] 145 + 146 +The following code snipped performs the transformation on our ABO-example, extracts the mapping and creates a transformation tree. 147 + 148 +{{code title="Transform and create TranformationTree" theme="Eclipse" linenumbers="true" language="java" firstline="1" collapse="true"}} 149 +aboSplitTE = transformation.transformTriggerEffect(abo); 150 + 151 +Model aboSplitTEModel = transformationTreeExtensions.initializeTransformationTree( 152 + transformation.extractMapping(), 153 + "splitTriggerEffect", 154 + abo, "ABO", 155 + aboSplitTE, "ABO-splitTriEff"); 156 + 157 +tranformationTree = transformationTreeExtensions.root(aboSplitTEModel); 158 +{{/code}} 159 + 160 +The result of transformation is the following SCChart. ABO-splitTriEff. 161 + 162 +[[image:attach:example_abo_splitTE.jpeg]] 163 + 164 +Resulting TransformationTree has following structure. 165 + 166 +[[image:attach:example_tree.jpeg]] 167 + 168 +Furthermore the TransformationTree now contains the following mapping information. 169 + 170 +[[image:attach:example_tree_transformation.jpeg]] 171 + 172 +Here you can see the effect of the transformation causing the transformation to split up.
- Confluence.Code.ConfluencePageClass[0]
-
- Id
-
... ... @@ -1,1 +1,1 @@ 1 -865153 11 +8651563 - URL
-
... ... @@ -1,1 +1,1 @@ 1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/865153 1/Transformation Mapping (KTM)1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651563/Transformation Mapping (KTM)