Skip to main content


Eclipse Community Forums
Forum Search:

Search      Help    Register    Login    Home
Home » Archived » M2M (model-to-model transformation) » [ATL] what formalism to use to represent model transformation ?
[ATL] what formalism to use to represent model transformation ? [message #38586] Wed, 16 May 2007 11:59 Go to next message
Eclipse UserFriend
Originally posted by: sylvain.maillard.univ-nantes.fr

Hi All,

I have a question non directly related to ATL: What is the most
appropriate formalism that can be used to represent a model to model
transformation ?
What is your experience with this ? Do you use UML ? and how ???

Thanks,
Sylvain

--
Sylvain
Re: [ATL] what formalism to use to represent model transformation ? [message #38674 is a reply to message #38586] Wed, 16 May 2007 17:20 Go to previous messageGo to next message
Frédéric Jouault is currently offline Frédéric JouaultFriend
Messages: 572
Registered: July 2009
Senior Member
Hi,

> I have a question non directly related to ATL: What is the most
> appropriate formalism that can be used to represent a model to model
> transformation ?
> What is your experience with this ? Do you use UML ? and how ???

The best complete representation I can think of that would work for any
ATL transformation is the ATL textual representation (i.e., the .atl file).


However, several AMW use cases
(http://www.eclipse.org/gmt/amw/usecases/) show that model weaving is
quite appropriate to visually represent transformations:

- completely: when a weaving extension can be used to represent
everything that needs to be represented,

or

- partially: by mapping metamodel classes and structural features, but
without detailing complex OCL expressions (you can generate the skeleton
of the transformation), or by encoding them textually in the Properties
view (which many UML tools do for OCL constraints).


Regards,

Frédéric Jouault
Re: [ATL] what formalism to use to represent model transformation ? [message #39109 is a reply to message #38674] Fri, 18 May 2007 09:25 Go to previous message
Eclipse UserFriend
Originally posted by: marcos.didonet-del-fabro.univ-nantes.fr

Hi,

As Frédéric said, you can use AMW to represent model transformations in a higher
abstraction level. We create different metamodel extensions with the desired structures,
e.g., the mapping between classes and structural features, attributes, etc.

I have some precisions about a couple of use cases:

- the tool interoperability use case
(http://www.eclipse.org/gmt/amw/usecases/interoperability/) has a relatively complex
weaving model that allows to represent several different transformation expressions.

- the metamodel comparison use case (http://www.eclipse.org/gmt/amw/usecases/compare/) has
simple kinds of links (equality between elements of the same type). The advantage is that
the weaving models are created semi-automatically, and then translated into ATL.

- finally, we have created a simple metamodel extension that has structures very close to
the ATL metamodel (called SimpleATL), e.g., rules, input and output elements, and
bindings. You can get more information about it at
http://wiki.eclipse.org/index.php/AMW#Graphical_development_ of_ATL_transformations.

For the time being, we have developed transformations from weaving models into
transformation models. We intend to do the opposite (from ATL to a more abstract
representation) in a near future.


Regards,

Marcos D. Del Fabro


ps.: I am copying the message to the AMW newsgroup as well.


Frédéric Jouault wrote:
> Hi,
>
> > I have a question non directly related to ATL: What is the most
> > appropriate formalism that can be used to represent a model to model
> > transformation ?
> > What is your experience with this ? Do you use UML ? and how ???
>
> The best complete representation I can think of that would work for any
> ATL transformation is the ATL textual representation (i.e., the .atl file).
>
>
> However, several AMW use cases
> (http://www.eclipse.org/gmt/amw/usecases/) show that model weaving is
> quite appropriate to visually represent transformations:
>
> - completely: when a weaving extension can be used to represent
> everything that needs to be represented,
>
> or
>
> - partially: by mapping metamodel classes and structural features, but
> without detailing complex OCL expressions (you can generate the skeleton
> of the transformation), or by encoding them textually in the Properties
> view (which many UML tools do for OCL constraints).
>
>
> Regards,
>
> Frédéric Jouault
Previous Topic:[ATL] Complete ATL bundle for running ATL transformations programatically !
Next Topic:Conditional model element creation in ATL
Goto Forum:
  


Current Time: Tue Jan 19 21:46:17 GMT 2021

Powered by FUDForum. Page generated in 0.01855 seconds
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.2.
Copyright ©2001-2010 FUDforum Bulletin Board Software

Back to the top