model transformation

[Matthew Rawlings]

Please integrate a more powerful model transformation such as ATL or QVT.

The current integration is too basic to be useful to me. I need
transformation that will work with my custom UML Profiles.

[Andrius Strazdauskas]

Matthew,

could you explain what do you mean by "integrate QVT"?

Regards,
--
Andrius Strazdauskas
Product Research and Development Manager
No Magic Lithuanian Development Center
Savanoriu pr. 363, LT 49425 Kaunas
Phone: +370 37 705889 Fax: +370 37 320670
E-mail: andriuss
WWW: http://www.magicdraw.com
--
MagicDraw - UML Made Simple

[Matthew Rawlings]

I want to execute model transformations within MagicDraw. Today, I only have
MagicDraw's very simple transformations.

What I want is the ability to run a QVT model transformation from within
MagicDraw. Borland's Together allows me to execute QVT from inside Together.

[Andrius Strazdauskas]

Matthew,

First of all, QVT is not finalized yet.
I agree that QVT should be a part of MagicDraw and it is on our roadmap, but
the timeframe is not defined yet.

Best regards,
--
Andrius Strazdauskas
Product Research and Development Manager
No Magic Lithuanian Development Center
Savanoriu pr. 363, LT 49425 Kaunas
Phone: +370 37 705889 Fax: +370 37 320670
E-mail: andriuss
WWW: http://www.magicdraw.com
--
MagicDraw - UML Made Simple

----- Original Message -----
From: "nntp://news.nomagic.com/nomagic.products.magicdrawuml.suggestions"
<matthew>
To: "Andrius Strazdauskas" <andrius.strazdauskas>
Sent: Thursday, August 17, 2006 12:45 PM
Subject: Re: model transformation


> I want to execute model transformations within MagicDraw. Today, I only
have
> MagicDraw's very simple transformations.
>
> What I want is the ability to run a QVT model transformation from within
> MagicDraw. Borland's Together allows me to execute QVT from inside
Together.
>

[Matthew Rawlings]

Hi Andrius

I agree that the entirety of QVT is not finalized, but many technologies
referred to by QVT were finalized years ago. The best example is OCL.

My suggestion is: Do not implement all of QVT, but just those parts that
have been finalized such as OCL for identifying fields for mapping. MD has
OCL in version 12.0, so extending a later version's transformations to use
OCL functions seems reasonable.

[Andrius Strazdauskas]

Matthew,

I agree that current transformation lack extensibility and the QVT is the
only natural way.
I think that we will move to the QVT eventually, however no timeframes are
set yet.

Thanks for the feedback.

Best regards,
--
Andrius Strazdauskas
Product Research and Development Manager
No Magic Lithuanian Development Center
Savanoriu pr. 363, LT 49425 Kaunas
Phone: +370 37 705889 Fax: +370 37 320670
E-mail: andriuss
WWW: http://www.magicdraw.com
--
MagicDraw - UML Made Simple

[saulius_p]

QVT plugin is available for FREE!

QVT (Query/View/Transformation) is a standard defined by the Object Management Group for specifying model transformations. Model-to-model transformation is a key aspect in a model-driven development, and QVT is one of the most popular transformation languages.

The new QVT plugin significantly increases MagicDraw, Cameo Enterprise Architecture and Cameo Business Modeler usability while working with model transformations. There is no need to export your model to EMF UML2 XMI in order to run a QVT transformation. From now on, you can run model transformations directly in above mentioned products - the QVT plugin uses the Operational QVT implementation that is provided by the Eclipse M2M project.

Find more information on our website https://www.magicdraw.com/qvt_plugin

[lonniev@gmail.com]

Saulius,

I like that 2009 claim of yours that one can run the QVTO transforms within the current MD editing session. I'm curious, though, how that is actually done. The provided sample (the simple UML to RDB one) does not perform its transformation on the current model but, rather, loads an external model file, transforms that, and writes the in-memory generated output model to an external model file.

I understand that the special string "md:model" tells the QVTO script handler to pass the current MD model to the transformation. This works and I can observe (via logging) that my transformation runs. However, if the transformation's out model argument is also set to "md:model", I do not see the current model update with the artifacts that the transformation appears to be creating.

Is there another sample somewhere (back in the LT labs, maybe) where a QVTO script, run directly from within the Macro Engine, without a wrapping JS (or Groovy or Ruby or Python) script, generates new model content for the current model?

[lonniev@gmail.com]

I clarify that the issue is just about capturing the newly created model elements. If I only want to alter existing content, then I can do so using the tactic shown in the Change Root Element Name sample.

A few more samples for the highly useful use case of in-place model to model transformations would be very helpful.