Behaviour logic of the model transformation engine

[Tonu]

Hello,

This might be a stupid question, but can anyone direct me to a source where I could read the general idea of the logic behind model transformation (no blame on authors of the help files - I was looking for a specific feature and was not sure if it should be there at all ... see below). Something in line with use-case descriptions where we describe step-by-step to a programmer how the system behaves. I have read through the help files several times and all I found was descriptions for transforming different element types and for launching/configuring the transformation in the tool. I could not find the general description of the logic how new packages are created, in what sequence the transformation operations are executed, what are the limitations etc.

What I would like to do is to select a set of elements on a diagram (actors). The transformation for the selected elements should
- create a new package
- copy there the selected elements
- copy all elements (requirements in my case) linked to the selected ones through a specific connection type
- copy all elements linked to the set of copied elements (requirements).

Based on the documentation I could not determine if this is something I could do using the transformation script. Is it? If it is, could you please direct me to the documentation I was overlooking.

Thank you beforehand!
Tonu

[Eve]

The transformation basically works by reading the model and generating a text form of what the new model should look like.

This text form is then parsed to create (or synchronise) the new model.

From what I understand of what you're trying to do, it's not possible using the transform templates.  You currently can't follow a link and start evaluating what's at the other end.  It's something we have in the works though.

The other alternative is to use an addin to do the parts that the template language can't manage.  (Search for EXEC_ADD_IN in the forum for more information)