Difference between revisions of "AMW"
|Line 17:||Line 17:|
The different kind of semantics of the weaving metamodel are defined in extensions to the core weaving metamodel.
The different kind of semantics of the weaving metamodel are defined in extensions to the core weaving metamodel. [[weaving metamodel extensions]] can be applied in different application scenarios.
Revision as of 11:01, 22 August 2006
The AMW project supports the creation of different kinds of links between model elements. The links are saved in a weaving model. The weaving model conforms to an extensible weaving metamodel. <p/>
Weaving models can be used in different application scenarios, such as tool interoperability, transformation specification, traceability, model merging.
Core weaving metamodel
The AMW project is developed based on a core weaving metamodel. This core weaving metamodel supports basic link management, i.e., this metamodel supports n:n relationships between model elements. The ID of elements of the referred elements can be saved using different identification methods. The core weaving metamodel is illustrated below.
WElement is the base element from which all other elements inherit. It has a name and a description. WModel represents the root element that contains all model elements. WLink denotes the link type. WLink has a reference end to associate it with a set of link endpoints (WLinkEnd). Each WLinkEnd references one WElementRef. The attribute ref contains the identifier of the linked elements. WElementRef is not referenced directly by WLink because it is possible to reference the same model element by different link endpoints, for example one model element may participate in more than one mapping expression. WModelRef is similar to WElementRef, but it contains references to the models.
The different kind of semantics of the weaving metamodel are defined in extensions to the core weaving metamodel. The different weaving metamodel extensions can be applied in different application scenarios.
The AMW prototype is developed as an Eclipse plugin. It uses EMF as base model handler. The prototype provides a set of extension points definition to enable to customize the interface according to different metamodel extensions. An example of the interface is shown below.
AMW plugin extensions
The first contribution to the AMW interface is the base weaver extension plugin (org.eclipse.weaver.extension). This extension enables to use the AMW plugin with the basic functionalities. This extension is provided for download together with the core weaver plugin (org.eclipse.weaver).
The Examples HowTo contains additional information about the examples available for download in the AMW project web site.
Didonet Del Fabro, M, Bézivin, J, and Valduriez, P : Model-driven Tool Interoperability:
an Application in Bug Tracking. To appear in: ODBASE'06(OTM Federated Conferences). 2006.
BDA2005 Didonet Del Fabro, M, Bézivin, J, Jouault, F, and Valduriez, P : Applying Generic Model Management to Data Mapping. In: Proceedings of Bases de Données Avancées (BDA05), 17-20 october 2005, Saint-Malo, France.
The AMW project provides an Eclipse plugin to create weaving models and to compose metamodel extensions.
The plugin can be downloaded in the AMW Download Page.
A set of application scenarios is available at AMW Examples. There are examples of weaving models, metamodel extensions, weaving models generated automatically through matching transformations, AM3 Ant Tasks, higher-order transformations that take a weaving model and that produce model transformations, etc. These examples are sorted in different categories.
AMW Wish List
AM3, The ATLAS MegaModel Management Eclipse wiki page
AM3, The ATLAS MegaModel Management project's Eclipse homepage
ATL, The ATLAS Transformation Language project's Eclipse homepage
ATL, The ATLAS Transformation Language Eclipse wiki page
ATL, The ATL homepage