Jump to: navigation, search

Difference between revisions of "MoDisco"

(All releases)
(Luna)
(7 intermediate revisions by the same user not shown)
Line 82: Line 82:
 
==== Release Train Required Documents====
 
==== Release Train Required Documents====
 
=====All releases=====
 
=====All releases=====
* [http://www.eclipse.org/projects/project-plan.php?projectid=modeling.mdt.modisco Project Plan]
+
* [http://www.eclipse.org/projects/project-plan.php?projectid=modeling.mdt.modisco Project Plan] (Deprecated project mangement tool)
 +
* [http://projects.eclipse.org/projects/modeling.mdt.modisco Project Plan]
 
* [[MoDisco/API_Policy|API Policy]]
 
* [[MoDisco/API_Policy|API Policy]]
 
* [[MoDisco/Unit_Tests|Running Unit Tests]]
 
* [[MoDisco/Unit_Tests|Running Unit Tests]]
Line 119: Line 120:
 
* [[MoDisco/JunoReview| Juno Review docuware]]
 
* [[MoDisco/JunoReview| Juno Review docuware]]
 
* [[Juno/Simultaneous_Release_Plan|Juno Simultaneous Release]] (Calendar)
 
* [[Juno/Simultaneous_Release_Plan|Juno Simultaneous Release]] (Calendar)
* [http://www.eclipse.org/projects/project-plan.php?projectid=modeling.mdt.modisco Juno Project Plan for MoDisco]
 
  
=====Juno=====
+
=====Kepler=====
 +
* [http://projects.eclipse.org/projects/modeling.mdt.modisco/releases/0.11.0 Kepler Project Plan for MoDisco]
 +
 
 +
=====Luna=====
 +
 
 +
* [[MoDisco/Restructuring_Reviews_MetaclassInstancesAdapter_From_MoDisco_To_EMF_Facet]]
 +
* [http://projects.eclipse.org/projects/modeling.mdt.modisco/releases/0.12.0 Luna Project Plan for MoDisco]
  
 
===== Project plan =====
 
===== Project plan =====

Revision as of 04:40, 3 May 2013

< To: MDT

LogoMoDiscoSmall.jpg
MoDisco
Website
Download
Community
Mailing ListForums
Bugzilla
Open
Help Wanted
Bug Day
Contribute
Browse SourceProject Set File

MoDisco provides an extensible framework to develop model-driven tools to support use-cases of existing software modernization.


Overview

Modernizing an existing software system implies :

  • Describing the information extracted out of the artifacts of this system
  • Understanding the extracted information in order to take the good modernization decisions
  • Transforming this information to new artifacts facilitating the modernization (metrics, document, transformed code, ...)


To support these activities, MoDisco aims at providing :

  • Metamodels to describe existing systems
  • Discoverers to automatically create models of these systems
  • Generic tools to understand and transform complex models created out of existing systems
  • Use-cases illustrating how MoDisco can support modernization processes


To facilitate reuse of components between several modernization solutions, MoDisco is organized in three layers:

Modisco-Architecture.PNG
  • Use-Cases: tools providing a solution for a specific modernization use-case.



  • Technologies: components dedicated to one legacy technology but independent from any specific modernization use case.



  • Infrastructure: generic components independent from any legacy technology.


Documentation

Reference Documentation

How to download and install ?

Publications

Screencasts & Slides

Project documents

Release Train Required Documents

All releases
GMT to MDT migration
Helios
Indigo
Juno
Kepler
Luna
Project plan

Service, Support and Maintenance: committed, proposed, deferred

Project Creation Documents

Support

Getting involved

The MoDisco project is open to contributors!

What can you provide?

  • new modernization use-cases
  • extensions of MoDisco components
  • metamodels of legacy technologies
  • discoverers and model transformations


See the MoDisco Wishlist for ideas of contributions.

Get the source of MoDisco projects

See the SVN Howto

How to contribute your code?

Meetings


Bugzilla Queries

Tracking

Checking

Reports

Others

Relationship with other Eclipse Projects

MoDisco reuses lots of EMP projects:

  • EMF to describe and manipulate models of existing systems.
  • M2M to implement transformation of models into other models
  • M2T to implement generation of text (documentation or code)


MoDisco also reuses other projects such as:

  • JDT to create models out of Java source code


Team

MoDisco has been initiated by the AtlanMod Team (INRIA & Ecole des Mines de Nantes), and is now strongly supported by Mia-Software:

  • Hugo Bruneliere - AtlanMod (project co-leader)
  • Grégoire Dupé - Mia-Software (project co-leader)
  • Fabien Giquel - Mia-Software (committer)
  • Nicolas Bros - Mia-Software (committer)
  • Gabriel Barbier - Thales (committer)
  • Frédéric Madiot - Obeo (committer)


MoDisco
Components Infrastructure: KDM · SMM · GASTM · Model Browser · Discovery Manager · MoDisco Workflow · Query Manager · Facet Manager · Metrics Visualization Builder · KDM Source Extension
Technologies: Java · JEE · EjbJar · WebApp · XML
Use Cases: Simple Transformation Chain · Model Filter
Help Installation · SVN
Project API Policy · Retention Policy · Project Plan · metrics · Accessibility Guidelines · Capabilities Disablement