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.
This matching transformation is used to create a weaving model with links between Class x Class and Structural Features x Structural Features (a restricted cartesian product).
This transformation is an adapted MDE implementation the Similarity Flooding algorithm (created by Sergey Melnik).
This transformation creates a propagation model that enables to execute the similarity flooding algorithm. The propagation model defines the way the similarities are propagated, for example using containment relationships or the inheritance tree.
This transformation increases the similarity value of links between elements with the same cardinality (lower or higher bounds).
This transformation increases the similarity value of links between elements with the same name.
This transformation analyses a weaving model with previously calculated similarity values and selects the links with the best values.
It also transforms simple equality links into type-based links, e.g., AttributeEqual, ReferenceEqual.
This transformation increases the similarity value of links between elements with the same type.
This matching transformation compares the values of the model elements that conform to the woven metamodels. If the model elements have the same value, it increases the similary values of the links between the metamodel elements.
This example automatically produces a weaving model used to compare two versions of the same Scade metamodel. A complete description of this example is available in the use cases section.
This is a complex scenario of management of "systems of systems". It uses many features of AMMA (ATLAS Model Management Architecture) to interoperate between different views of the same system. It uses different types of matching transformations to produce weaving models that capture the overlapping concepts of the different views.
This example uses matching transformations to produce a weaving model between two versions of the same metamodel. It uses the same algorithms from the AMW_Match_SF example (see below). This example automatically produces an ATL transformation.
This example contains a set of matching transformations (in ATL) used to produce a weaving model. The example contains three transformations:
The example is an implementation of an adapted version of the Similarity Flooding algorithm (created by Sergey Melnik)
- The first transformation calculates similarity values between model elements.
- The second transformation propagates the similarity values through neighbor nodes.
- The third transformation selects the best similarity values and creates a weaving model.
This example is a complete scenario that uses the weaving model from the example "Weaving Mantis and Bugzilla bug trackers" to generate an ATL transformation. This transformation translates a model conforming to the Mantis.ecore metamodel into a model conforming to the Bugzilla.ecore metamodel.
This example is a complete bridge between KM3 and SQL DDL that uses injection, extraction, weaving and transformations. It is similar to the example that transforms SQL to KM3, but in the opposite direction. This example uses a weaving model between a KM3 metamodel and a SQL DDL metamodel. The weaving model is used to produce an ATL transformation that translates KM3 models into SQL models.
We used an KM3 file generated by the example "Translating SQL into KM3".
This example is a complete bridge between SQL and KM3 that uses injection, extraction, weaving and transformations. This example uses a weaving model between a SQL DDL metamodel and a KM3 metamodel. The weaving model is used to produce an ATL transformation that translates SQL DDL models into KM3 models. We used an SQL extracted from Mantis bug tracker.
This example generates XSLT and ATL transformations from the same weaving model. It contains two ATL HOTs (higher-order transformations). The first HOT transforms a weaving model into an ATL model. The second HOT transform a weaving model into an XSLT model.
This example is an complement that uses the metamodel extension between foreign keys and nested structures. It provides a HOT (higher-order transformation) that transforms a weaving model into a transformation model.
With UML, it is possible to describe domain specific concepts using Profiles. In the DSL approach, a new metamodel is created for each domain-specific language. This example identifies more precisely the relation between UML profiles and metamodels, and presents a tool enabling to bridge these two approaches. This tool is implemented using two ATL (Atlas Transformation Language) transformations combined with a weaving model. It illustrates an AMW example and the simultaneous use of AMW and ATL..
This example contains an extension of the core weaving metamodel to create correspondences between a metamodel with foreign key relationships (as in a relational database) and a metamodel that contains nested structures (as in XML).
Extension to the core weaving metamodel to merge between elections and geographical data (provided by GML) into an SVG metamodel.
This example generates an ATL execution trace in a weaving model. We create a higher-order transformation that takes an ATL transformation as input (e.g., Class to Relational) and produces an ATL transformation as output. The output ATL transforms Class to Relational models, and additionally generates a traceability model. The traceability model conforms to a traceability model that is an exentension to the core weaving metamodel.
Back to the top