Last modified by Richard Kreissig on 2023/09/14 11:14
<
From version < 9.1 >
edited by Alexander Schulz-Rosengarten
on 2014/01/02 11:18
To version < 7.1 >
edited by Alexander Schulz-Rosengarten
on 2013/12/18 16:30
>
Change comment: added content

Summary

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 bidirectional information transfer between abstract models and their resultant transformed models.
13 +The main propose of KTM is to allow 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-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.
31 +**Second part** (lower half) is object mapping. Concrete 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 object-mapping during transformation process.
47 +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-child-relations between EObjects.
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,12 @@
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 -
61 61  ----
62 62  
63 63  == Implementation Details ==
64 64  
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.
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 and matching functionality.
66 66  * 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.
68 68  
69 69  ----
70 70  
Confluence.Code.ConfluencePageClass[0]
Id
... ... @@ -1,1 +1,1 @@
1 -8651535
1 +8651531
URL
... ... @@ -1,1 +1,1 @@
1 -https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651535/Transformation Mapping (KTM)
1 +https://rtsys.informatik.uni-kiel.de/confluence//wiki/spaces/KIELER/pages/8651531/Transformation Mapping (KTM)

Navigation

Quick Links

KIELER on GitHub
RTSYS Homepage