AMW

This use case shows how weaving models and model transformations are used to translate SQL-DDL (Data Definition Language) into KM3 (modeling technical space). The use case presents the complete bridging process: the injection of the SQL file, the weaving model, the transformations, and finally the extraction into a KM3 file.

Models are annotated to add extra information that are not defined in the metamodel. For instance, a model can be annotated with preprocessing informations, comments, etc. This use case presents a generic annotation framework built using AMW.

Nowadays, there are a large number of tools that can be used to solve similar problems. However, the tools have different data format and semantics. To support interoperability between different tools, it is necessary to identify the ... [More] heterogeneities between them. This use case shows how weaving models are used to capture the heterogeneities between different tools' metamodels. It uses two bug tracking tools as example. [Less]

Matching is the process of creating weaving models. It is very important to provide methods to easily create weaving models, because this is the starting point for several other use cases. This use case presents a general overview of ... [More] the matching process. It shows how AMW is integrated with ATL to be able to execute different matching transformations. This use case also provides a step-by-step 'HowTo' that explains how to execute these transformations, and a guide that explains how to develop user-defined methods. [Less]

Aspect oriented modeling aims at weaving business models and cross cutting models in a single model. A weaving can be applied in any model (e.g., weavings in the cross cutting concern AND/OR in the business model), because there is no ... [More] preferential model. This use case shows how AMW is used on an aspect oriented modeling appplication. The weaving model is interpreted by ATL transformations to weave the models. [Less]

A new AMW use case is available: traceability of model transformations. This use case considers traceability of model transformations. After executing a model transformation, it is often necessary to know the set of elements of the source ... [More] model that were used to produce the target elements. A weaving model is used to save this traceability information. [Less]

A new use case of AMW is available: metamodel comparison. The objective of this use case is to demonstrate how weaving models created with the AMW plug-in are used to compare different versions of a metamodel and to produce executable model ... [More] transformations. We use two different versions of a Scade metamodel (from the Atlantic zoo). Scade is a standard for development of embedded software for the Avionics Industry. [Less]

A new page with a set of use cases of AMW was created. It contains simple and documented use cases of weaving models and AMW.

There is a new release of AMW plugin. This release is compatible with the latest releases of ATL and AM3.

The integration of the AMW plugin with the execution of matching transformations was improved. The plugin uses the new ATL 2006 compiler . There is a new project "org.eclipse.weaver.transformation". This project is an extension to the ... [More] weaving core. It contains a set of matching and higher-order transformations that can be called directly from the Weaving panel. For the moment these transformations are available in the context menu of the weaving panel (right click). They are executed one-by-one. We plan to gradually add new transformations and also to combine them, as well as to provide documentation. [Less]