Team Espresso

Overall Objectives
Scientific Foundations
Application Domains
New Results
Contracts and Grants with Industry
Other Grants and Activities

Section: New Results

Keywords : Metamodeling, Eclipse, Ecore, SIGNAL, Model transformation.

An Eclipse plugin for Polychrony

Participants : Christian Brunette, Jean-Pierre Talpin.

In the frame of the Topcased project and of the OpenEmbeDD project, we have to create an eclipse plugin for Polychrony. So, within a collaboration initiated at INRIA in the ATLAS team in Nantes, we study migration of existing GME projects, and particularly Signal-Meta, into Eclipse.

From GME to Eclipse

The ATLAS team has defined a model engineering support on top of the Eclipse Modeling Framework (EMF), called the AMMA (ATLAS Model Management Architecture) platform [28] . To be able to exchange models between an EMF based system and a corresponding GME assumes an abstract understanding of both architectures and a precise organization of the interoperability scheme. EMF and GME allows metamodel and model management. The designed models conforms to a previously defined metamodel. Any metamodel design assumes the existence of a metametamodel (implicit or explicit). So three levels have to be considered: metametamodel concepts mapping (M3), building metamodel projectors (M2) and building model projectors (M1). Projectors are operational bridges between different technical spaces, and are realize here using ATL (ATLAS Transformation Language), which allows model transformations in EMF technical space. The metamodel bridge is already effective. Only a part of the metamodel concepts are translated into the ATLAS file. All graphical information are lost. The file contains only information about concepts and their relations (e.g. inheritance, containment). So, it is possible to work on the old GME project into EMF. The GReAT [25] transformation language provided with GME can also be replaced by ATL to work on the produced artifacts. This work is described in [31] and has been pursued this year by some improvements to keep more information in the EMF Model. For example, the OCL constraints are added as specific comments, which can then be used by OCL constraints checker provided in Eclipse. The translation has also been improved to fit more precisely to EMF metamodels.

The new Polychrony environment

This translation gives a first EMF metamodel, which has been modified to exploit the power of the Eclipse environment. From this metamodel, EMF can generate a plugin to build models based on such metamodel (see figure 20 ). Using the modeling facilities provided with the Topcased framework, we create a graphical environment for Polychrony (see figure 19 ).

Figure 19. Signal-Meta environment in Eclipse.

The environment is complete concerning the modeling part. We reproduce in Eclipse the GME notion of Aspect . So, the modeling of a SIGNAL process is split in three diagrams: one to model the interface of the process, one to model the computation part, and one to model all explicit clock relations and dependences. Actually, the graphical environment under Eclipse cannot generate Signal code the way we did it in GME. Our objective in Eclipse is to deeply connect the graphical environment with the Polychrony compiler to dynamically check the correctness of the model. Through this connection to the compiler, we can use the facilities of the compiler to generate the SIGNAL program.

In the frame of the OpenEmbeDD project, we study the possibility of creating a unique environment for all tools (Polychrony, Syndex [44] , and Gaspard [34] ) based on the synchronous paradigm. So, we began this work by creating a UML metamodel in which we merge all common concepts of the three tools and we add all specific ones.

Figure 20. EMF plugin for Signal-Meta.


Logo Inria