MoDisco News
The KDM-to-UML2 Converter has just been published into the MoDisco "Tool box" section. This tool, provided by the MIA-Software company, is about converting KDM models into UML2 models in order to allow integrating KDM-compliant tools (i.e. discoverers) with UML2-compliant tools (e.g. modelers, model transformation tools, code generators, etc).
See http://www.eclipse.org/gmt/modisco/toolBox/KDMtoUML2Converter/ for accessing the tool.
The "Visual Basic 6" discovery tool has just been published into the MoDisco "Tool box" section. This tool, provided by the Obeo company, allows building models representing the structural parts (and their interdependencies) of Visual Basic source code.
See http://www.eclipse.org/gmt/modisco/toolBox/VisualBasic/ for accessing the tool.
The "Java 2 Standard Edition 5.0 Discovery Tool" specification has just been published into the MoDisco "Tool Box" section. This specification, proposed by the MIA-Software company, currently contains a general description of the tool and provides a J2SE5 metamodel.
See http://www.eclipse.org/gmt/modisco/toolBox/J2SE5/ for getting more information about the tool.
The "Performance-Annotated UML2 State Charts" use case has just been published into the MoDisco "Use Cases" section. This complex use case contains a general description but also a complete implementation.
It is about discovering performance information from an Excel file and building a Trace model from these data. Then, this generated model is computed in order to produce a Metrics model whose data are finally used to automatically apply a "Performance" profile to a UML2 state chart.
See http://www.eclipse.org/gmt/modisco/useCases/PerformanceAnnotatedUmlStateCharts/ for consulting the use case.
The "Generating Java Platform Ontologies" use case has just been published into the MoDisco "Use Cases" section. This complex use case, developed by Dennis Wagelaar (VUB), contains a general description but also a complete implementation.
It is about reverse engineering the Java API from the class library JAR files using the Jar2UML discovery tool (part of the MoDisco tool box), generating OWL ontologies from the created UML models using ATL model transformations, and finally bundling these ontologies with the PlatformKit Eclipse plugin.
See http://www.eclipse.org/gmt/modisco/useCases/JavaPlatformOntologies/ for consulting the use case.
The "Visual Basic Code Analysis" use case has just been published into the MoDisco "Use Cases" section. This complex use case, developed by the Obeo Company, currently contains a general description and is intented to reach completion by September 2007.
See http://www.eclipse.org/gmt/modisco/useCases/VBCodeAnalysis/ for consulting the use case.
The "Metrics Visualization Builder" tool has just been published into the MoDisco "Tool box" section. This simple generic tool (which is an ATL project for Eclipse) provides facilities for building visualizations (in several formats) from Metrics models.
See http://www.eclipse.org/gmt/modisco/toolBox/MetricsVisualizationBuilder/ for accessing the tool.
The double page flyer-poster describing the MoDisco component has just been published in the "Documentation" section.
See http://www.eclipse.org/gmt/modisco/doc/MoDisco_Flyer-Poster_1.0.pdf for getting the flyer-poster.
The "SharenGo Java Legacy Reverse-Engineering" use case has just been published into the MoDisco "Use Cases" section. This complex use case, developed by the Argia-Engineering Company, contains a general description but also a complete implementation.
It is about reverse engineering a Java application. It uses the Java Abstract Syntax discovery tool (from the MoDisco tool box) to discoverer the abstract syntax tree (AST) of each Java compilation unit (i.e. each source file). The generated models are then analyzed by model transformations in order to produce a SharenGo business model.
See http://www.eclipse.org/gmt/modisco/useCases/JavaLegacyRE/ for consulting the use case.
The "Java Abstract Syntax" discovery tool has just been published into the MoDisco "Tool box" section. This simple tool (which is an Eclipse plug-in based upon MoDisco) is fully implemented and provides facilities for buidling Java AST models from Java compilation units.
See http://www.eclipse.org/gmt/modisco/toolBox/JavaAbstractSyntax/ for accessing the tool.
The "Eclipse/BIRT Project Sample Database" use case has just been published into the MoDisco "Use Cases" section. This complex use case contains a general description but also a complete implementation.
It is about discovering the information on the content of the "Classic Models" BIRT sample database, by using the database content discovery facility of the generic "Relational Database Information" discovery tool (from the MoDisco tool box), and then generating a specific ClassicModels model.
See http://www.eclipse.org/gmt/modisco/useCases/BIRTSampleDB/ for consulting the use case.
The "Relational Database Information" discovery tool has just been published into the MoDisco "Tool box" section. This simple tool (which is an Eclipse plug-in based upon MoDisco) is fully implemented and provides facilities for buidling database schema or content models from already existing databases.
See http://www.eclipse.org/gmt/modisco/toolBox/RelationalDBInformation/ for accessing the tool.
We just create and initialize the MoDisco tool box. In the initial version, we provide the "Relational Database Information" discovery tool as well as pointers to the already existing ATL and AMW Eclipse components. Of course, the tool box will be updated regularly: documentation and implementations will be added to already existing tools, new ones will be described, etc.
Do not hesitate to post messages on the MoDisco newsgroup (eclipse.modeling.gmt.modisco) if you have any particular interests and/or questions about any of the presented tools. We are also always interested by new ideas and propositions of possible other model discovery tools based upon the MoDisco approach.
See http://www.eclipse.org/gmt/modisco/toolBox for accessing the tool box.
Interfaces and implementation for EMF have been committed. A model handler's implementation is a driver for handling models, either by wrapping an existing modeling framework (EMF, MDR/JMI, etc) or by implementing a brand new one.
New model handler implementations will be committed soon.
This first abstraction layer will let MoDisco use some models from different sources (XMI 1.x/XMI 2.x for instance) and from different modeling spaces (MOF, Ecore, KM3...).
The source code of MoDisco's model handlers is available on CVS: http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/MoDisco/plugins/
The "Bugzilla Metrics" and "Unix File System" use cases sources have just been committed into the MoDisco CVS.
See http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/MoDisco for navigating through the MoDisco CVS.
See http://dev.eclipse.org/viewcvs/indextech.cgi/org.eclipse.gmt/MoDisco/use-cases for getting the use cases sources.
The "Bugzilla Metrics" use case has just been published into the MoDisco "Use Cases" section. This complex use case contains a general description but also a complete implementation.
See http://www.eclipse.org/gmt/modisco/useCases/BugzillaMetrics/ for consulting the use case.
The "Unix File System" use case has just been published into the MoDisco "Use Cases" section. This use case contains a general description but also a first available implementation of the discoverer.
See http://www.eclipse.org/gmt/modisco/useCases/UnixFileSystem/ for consulting the use case.
The presentation providing the overview of the MoDisco component has just been published in the "Documentation" section.
See http://www.eclipse.org/gmt/modisco/doc/MoDisco_Overview_1.0.pdf for getting the slides.
We just create and initialize the list of the MoDisco "model discovery" use cases. In the initial version, we only provide general descriptions of three different use cases: Java Abstract Syntax, Relational DB Schema and Relational DB Content. Of course, the use cases will be updated regularly: documentation and implementations will be added to already existing use cases, new ones will be described, etc.
Do not hesitate to post messages on the MoDisco newsgroup (eclipse.modeling.gmt.modisco) if you have any particular interests and/or questions about any of the presented use cases. We are also always interested by new ideas and propositions of possible other model discovery use cases.
See http://www.eclipse.org/gmt/modisco/useCases for consulting the use cases list.
We just update the list of the related projects by providing its initial version. Of course, this list will be updated regularly.
Do not hesitate to post messages on the MoDisco newsgroup (eclipse.modeling.gmt.modisco) if you want your project to be indexed on this list or if you want to add a link to the Eclipse/GMT MoDisco component on your own site!
See http://www.eclipse.org/gmt/modisco/relatedProjects.php for consulting the related projects list.
Creation of MoDisco component under GMT.
MoDisco (for Model Discovery) is an Eclipse GMT component for model-driven reverse engineering. The objective is to allow practical extractions of models from legacy systems. Because of the widely different nature and technological heterogeneity of legacy systems, there are several different ways to extract models from such systems. MoDisco proposes a generic and extensible metamodel-driven approach to model discovery. A basic framework and a set of guidelines are provided to the Eclipse contributors to bring their own solutions to discover models in various kinds of legacy.
More details are available here: http://www.eclipse.org/gmt/modisco/about.php.
