| [ATL] verification [message #45235] |
Fri, 08 June 2007 10:10  |
Eclipse User |
|
|
|
Originally posted by: browngr3.msu.edu
Hello,
I want to write a tool that can automatically convert a UML model to an
arbitrary language. What I want to do as the first step in this tool is
to convert the UML model to the target language model with ATL.
I am interested in doing some verification of the ATL transformation rules.
I want to have this tool check the ATL rules against a provided source
metamodel and a provided target metamodel. I want to check for
completeness, in that there is some target language entity for every
entity in the source metamodel. I also want to make sure that the rules
in the ATL ruleset is consistent with the source and target metamodels.
Is there some support for this already in the AMMA tools?
Any pointers to this functionality would be appreciated.
Thanks,
Greg Brown
|
|
|
| Re: [ATL] verification [message #45333 is a reply to message #45235] |
Fri, 08 June 2007 12:45  |
| Eclipse User |
|
|
|
Originally posted by: rchevrel.sodius.com
This is a multi-part message in MIME format.
--------------010501070208080005040201
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 8bit
Hi Gregory,
I think you have three ways to do that:
- model measure: some tools are in development in order to measure some
aspect of models and metamodels. You could use these kind of tools in
order to verify if the x Ma entities could be find in Mb for example.
- AMW: Atlas Model Weaver. You weave two metamodels (MMa entities will
be linked with one or more MMb entities). The AMW tool then produce an
ATL transformation depending of the specification you give to the tools.
So, you can specify two transformation generator, the first produce the
real ATL transformation, the second will generate a verification
transformation which can take as parameter the input and the output
models and then verify some aspect. For example, if your input and
output elements are identificable, you can check if every key in input
model is present in output model, etc. (http://www.eclipse.org/gmt/amw/)
- HOT: High Order Transformation. It is transformations which produce
some transformation model or take as input a transformation. The AMW lie
on the first concept. You can also use the second. You can write a
transformation which take your transformation model as input and produce
a verification transformation, which are similar to the transformation
presented in AMW. AMMA tools give you a mechanism to have the
transformation model from an .atl file (right click on eclipse on the
..atl file)
An other way, MDAless, is to use .debug() operation to trace
transformation execution.
For example:
rule RuleA {
from
a : MMa!Ea (
...
)
to :
b : MMb!Eb (
)
do
a.debug('source').id.debug('id');
b.debug('target')...;
}
}
Regards,
*R
|
|
|
Powered by
FUDForum. Page generated in 0.05437 seconds
] 
Search
Help
Register
Login
Home
