Friends of Eclipse,
Eclipse is an open source community that benefits millions of developers around the world each and every day! During the month of September, we are asking you to give back to our wonderful open source community. All donations will be used to improve Eclipse technology. Your contribution counts!
We thank you for this gesture, and for giving back to our community.
A new version of AMW that is compatible with the latest versions of Eclipse, EMF and ATL3 is available.The plug-ins are available for download in the download section. The sources can be checked-out in the AMW SVN. The plug-ins have been tested using Eclipse Mdeling bundle, to simplify the installation. This version has different modifications:
- The model manager has been updated to be compatible with ATL 3.
- The AMW model handler plug-in has been removed. Now AMW uses the ATL org.eclipse.m2m.atl.engine.emfvm.libextension extension point for registering new operations. New operations can be easily added.
- The ATL transformation model generated after the execution of the matching transformations is automatically extracted into the corresponding .atl file
- The KM3 import feature is temporarily disabled.
The sources of AMW have just been committed under AMW SVN. The plug-ins have been tested using Eclipse Ganimede, and ATL branch "R2_1_0dev".
The AMW component has been restructured, which means a couple of links have been changed.The CVS is no longer available. The new sources will be committed soon under SVN. The newsgroup has changed to news://news.eclipse.org/eclipse.amw.
Nowadays different notations for architectural modeling have been proposed, each one focusing on a specific application domain, analysis type, or modeling environment. No effective interoperability is possible to date. DUALLY is an automated framework that aims to offer an answer to this need allowing both languages and tools interoperability. DUALLY has been implemented as an Eclipse plugin that extends AMW and it is based on model transformation techniques (ATL). This use case shows the DUALLy approach to achieve interoperability between two outstanding architectural notations, Darwin and Acme.
The sources of AMW have been updated to be compatible with the latest ATL, EMF and Eclipse releases (3.4M5)
This use case shows how model weaving is used to help in the development of model transformations. In some cases, the gap between the input and output metamodels makes it difficult to develop a model transformation that works for every input model. In such cases a weaving model can be used to enrich the input model by annotation. This process can be thought of as a way to parameterize the model transformation.
The sources of AMW have been updated to be compatible with Eclipse 3.3, EMF 2.3 and the latest versions of ATL and AM3 plug-ins. A binary release will be available soon.
This use case follows the approach of the use case (Metamodel comparison and model migration) in order to show how model weaving can be used to compare two versions of a very large metamodel used in Automotive Systems.
This use case illustrates an approach to manage variability in a Model-Driven Software Product Line. The approach proposes the generation of different applications from metamodels, feature models, weaving models, and special transformation rules. The proposal was developed by the Software Construction Group of The University of Los Andes (Colombia). The use case provides an example, publication and user guide.
Back to the top