Documentation

From IDMPP

Revision as of 14:38, 4 March 2011

Needs

Eclipse Plugin Management

This use case is focused on the Eclipse plugin management from the extraction of the information to its representation. It intends to reveal problems involving the management of complex systems and to provide solutions based on model driven engineering techniques. It involves several new DSLs for different purpose such as the Eclipse plugin management, contraint representation or graphical projection generation.

This use case will be use in different work packages of the project:

• In WP2, it offers a good use case for the management of complex systems using a Global Model Management approach.
• In WP3, it will be use to apply configuration techniques for the management of this kind of systems.

The PetStore

This use case present a snapshot taken during the software development cycle of a simplified Pet Store application. This snapshot provides a static view of the development process artifacts (mostly models) taken at a given point in time.

It addresses the problems involved by the need, from a single engineer, to consider several interrelated models at once, even when these models have different natures (i.e. conform to different metamodels or abstract syntaxes) and are represented by various concrete syntaxes. We need to allow this engineer to navigate all these models in a seamless and efficient way. To make the problem more concrete, we present a motivating example concerning the design and development of a given software system. This example involves several different DSLs and thus several models describing different aspects of this same software system.

This use case is actually available on Eclipse.org at PetStore use case.

Rule Interchange Technologies

There are different rule languages in the market. Each language (and associated engine) has different concepts, syntax and set of features. The interchange of rule technologies has different motivations:

• migrating from different versions of a same language,
• importing thirdy-part rules,
• producing rules targeted to business users, etc.

MDE enables the rapid development of such bridges. However, rule languages may have different expressiveness, which hardens the task of writing transformations between them.

We address the migration between technical languages and business languages. Such a bridge has several operations that must be correctly coordinated, due to the existence of several input and output artifacts. This issue is addressed by global model management solutions (WP2). A complete description of this use case is available at the INRIA Research Report, number 6747

Solutions

MegaModeling

Model Driven Cartography

Model-Driven Cartography

Resource on the PetStore use case.

• Inter-DSL Traceability and Navigability Support by Combining Megamodeling and Model Weaving
• The PetStore use case on Eclipse.org.
• Navigability between models demo with the PetStore.
• The Eclipse bundle with the AMMA Platform (ATL, AMW, AM3, TCS) and the PetStore use case is available for download (~235Mo).

Resources on the Rule Interoperability Technologies use case.

• Industrial-strength Rule Interoperability using Model Driven Engineering

Resources on the Eclipse Configuration use case.

• Neptune Days 2010, Applying MDE for the validation of correct Eclipse Plugin Bundles
• Eclipse CPP configuration dependency matrix

Other Resources

• Creation of a zoo of SBVR vocabularies definitions describing metamodels (more than 300), by Guillaume Doux.

Other Publications

• ECMFA 2010:
  • Model Driven Tool Interoperablility in Practice, Jean Bézivin, Hugo Brunelière, Jordi Cabot and Guillaume Doux,
  • Model Driven Interoperablility of Dependencies Visualization, Vincent Mahé, Hugo Brunelière, Frédéric Jouault, Jean Bézivin, and Jean Pierre Talpin
• Models'09: Parsing SBVR-based controlled languages, by Mathias Kleiner, Patrick Albert and Jean Bézivin.

User Manual