The [http://www.eclipse.org/gmt/am3/ AM3] ('''ATLAS MegaModel Management''') project is a [[GMT]] subproject which is being developed by the [http://www.inria.fr/recherche/equipes/atlas.fr.html ATLAS Team], [http://www.inria.fr/ INRIA].

The [http://www.eclipse.org/gmt/am3/ AM3] ('''ATLAS MegaModel Management''') project is a [[GMT]] subproject which is being developed by the [http://www.inria.fr/recherche/equipes/atlas.fr.html ATLAS Team], [http://www.inria.fr/ INRIA].

−

The aim of the GMT project is to produce a set of prototypes in the area of Model Driven Engineering (MDE). The AM3 project acts in this way by providing a practical support for modeling in the large, i.e. dealing with global resource management in a model-engineering environment.

+

The aim of the GMT project is to produce a set of prototypes in the area of Model Driven Engineering (MDE). The AM3 project acts in this way by providing a practical support for modeling in the large, i.e. dealing with global resource management in a model-engineering environment.

+

AM3 is part of the [[AMMA]] platform.

==Abstract==

==Abstract==

Revision as of 14:47, 17 July 2006

The AM3 (ATLAS MegaModel Management) project is a GMT subproject which is being developed by the ATLAS Team, INRIA.
The aim of the GMT project is to produce a set of prototypes in the area of Model Driven Engineering (MDE). The AM3 project acts in this way by providing a practical support for modeling in the large, i.e. dealing with global resource management in a model-engineering environment.
AM3 is part of the AMMA platform.

Contents

Abstract

The goal of AM3 (ATLAS MegaModel Management) is to provide a practical support for modeling in the large, i.e. managing global resources in the field of MDE (Model-Driven Engineering). These global resources are usually heterogeneous and distributed. To access them without increasing the accidental complexity of MDE, we need to invent new ways to create, store, view, access, and modify the global entities that may be involved in developing a solution. To this intent, the notion of a megamodel (i.e. a model which elements are themselves models) is being used. In order to achieve this overall goal, AM3 provides a set of tools and artifacts that implement our Global Model Management (GMM) approach which is based on the concept of "megamodel".

Description

Global management tools have plenty of potential applications. They can provide a lot of leverage over common problems. The idea of modeling in the large is to establish and use global relationships and metadata on the basic macroscopic entities (mainly models and metamodels), ignoring the internal details of these global entities.
A megamodel is a model recording global information on tools, services and other models. A model may be a terminal model, a metamodel or a metametamodel. Models are considered as a whole together with tools, services and other global entities. Within a model management environment, the main elements produced or consumed are models, metamodels or transformations. With the AM3 supported megamodels, we want also to allow the manipulation of other resources such as XML documents, database tables or flat files. For this reason, we have introduced the notion of artifacts as basic entity. A megamodel gives the representation of the user-working context (a zone). A zone is a set of resources and each zone is represented by a given megamodel. It is the set of all the artifacts, which are accessible in a given context. One goal of the megamodel management tool is to manage artifacts with all necessary functionalities, and to allow executing the control actions associated with the artifacts.

AM3 is part of the AMMA platform (ATLAS Model Management Architecture). The AMMA platform has been implemented on top of the Eclipse/EMF framework. The AM3 plug-in is based on the availability of the megamodel's metamodel. The main features of AM3 are:

The AM3 plugins implement a framework that provides an environment for modelling in the large with the following basic initial features:

Managing megamodels:

Adding, editing metadata and deleting artifacts

Adding, editing and deleting relations

Using megamodels:

Sharing artifacts

Searching artifacts

Managing tools and services:

Using tools with artifacts:

Running transformations:

Model transformations

Projectors:

Injectors

Extractors

Launching several transformations in batch mode

Editing artifacts

In addition to these, it is very likely that additional functionality will be found useful and implemented in this environment.

Available Resources

The AM3 project provides many MDE resources which are, at the time, different domains' metamodels, ATL transformations, weaving metamodels and extensions of weaving metamodels. These resources are gathered in what we call "zoos" and are expressed in different formats (as an example, metamodels are expressed in KM3 as well as in Ecore or Microsoft DSL Tools format, etc).

FAQ

Coming Soon

References

Bézivin, J, Jouault, F, and Valduriez, P : On the Need for Megamodels. In: Proceedings of the OOPSLA/GPCE: Best Practices for Model-Driven Software Development workshop, 19th Annual ACM Conference on Object-Oriented Programming, Systems, Languages, and Applications.