===== Common Tools =====

Interface between subprojects can be text files or XML files but this quite poor and each group will need to develop
tools on Java and Models. In order to get a standard vision of the usqble technologiesm we need to agree on the
model and metamodel tools used in each subproject.

=== Java/Annotation Tools ===

Several tools will be used in more than one subproject.

  - JavaCC, https://javacc.dev.java.net/
  - Java Development Kit, http://java.sun.com/
  - ANTLR, http://www.antlr.org/
  - Java CUP, http://www2.cs.tum.edu/projects/cup/
  - SableCC, http://sablecc.org/

=== Model Engineering Tools ===

We need tools for model management, preferably on Eclipse. We already discussed on a modeling tool around
Eclipse technologies (Ecore, XML, EMF, MOF...) that allows to:
  - describe and check component metamodels CMM (with structural and behavioural features, with a model that links to Java code)
  - describe and check component models CM
  - provide an API to navigate on and query models, to add operations and processing on models
  - ...

LCI should maintain this (CMM-CM) layer since it relates to metamodels.

At first sight OCLE can provide the main elements on points 1 and 2 but it doesn’t provide an API usable in
process A (structure) and B (behaviour).

Other tools exist that can help to use Ecore without handling it directly:

  * Kermeta (IRISA) http://www.kermeta.org/
  * ATL (LINA) http://www.eclipse.org/m2m/atl/
  * others...

Information on this aspect can be found here:

  * Generalities
http://en.wikipedia.org/wiki/Model-driven_architecture\\
http://en.wikipedia.org/wiki/Model_Transformation_Language

  * Eclipse Modeling Tools
http://www.eclipse.org/modeling/

  * Kermeta (IRISA)
http://www.kermeta.org/

  * ATL (LINA)
http://www.eclipse.org/m2m/atl/

  * Tools
http://planet-mde.org/index.php?option=com_xcombuilder&cat=Tool&Itemid=47

It would be helpful to compare tools