|
|
The tool manages IDs for all model elements and mappings between them for traceability reasons.
|
|
|
|
|
|
## Code -> Architecture
|
|
|
|
|
|
### Code <-> Implementation Model
|
|
|
First, each implementation model element gets an ID via the ID2ObjectMapper. It creates a map (EObject, UUID).
|
|
|
Then, a map (UUID, Transformation) from a model element's UUID to the element's transformation object is created using the method EmbedTransformationRegistry.createID(..), based on the first (EObject, UUID) map.
|
... | ... | @@ -25,4 +27,13 @@ The TransformationManager gives the Initial Model (EObject, UUID) to the next mo |
|
|
The IL module transformations do not change any IDs. It just forwards the eObjectInstance2id_before as Initial Model (EObject, UUID) to the Result Model (EObject, UUID).
|
|
|
|
|
|
### IL <-> Architecture Model
|
|
|
Here, the same mechanism is used as in Implementation Model <-> IL. |
|
|
\ No newline at end of file |
|
|
Here, the same mechanism is used as in Implementation Model <-> IL.
|
|
|
|
|
|
### End of Code -> Architecture
|
|
|
In the end, the TransformationManager keeps the last TransformationResult, that contains:
|
|
|
* the model roots
|
|
|
* the 4 maps (UUID, EObject) and (EObject, UUID) for the transformed IL model and the architecture model
|
|
|
* the map (Architecture Model UUID*, Transformed IL Model UUID*)
|
|
|
|
|
|
## Code <- Architecture
|
|
|
|