Skip to main content
Jump to: navigation, search



is Modisco during reverse engineering from legacy code able to generated .ecore file or only produce .xmi file ?

XMI is the standard serialization format for models, and it is the same independently from the metamodels the models conform to (e.g.; the Java one, the UML2 one or any other metamodel). Even if the extension name may change, there are still XMI files (I invite you to open them in a textual editor to realize this). There are often confusions when someone talks about generating a metamodel (i.e. a Ecore file, which is also a XMI file but with a specific extension name) from its Java code. A metamodel describes the viewpoint from which your want to model a given system, not the view on this system (which is represented as a model that conforms to this metamodel). It's possible to model the global architecture of the system, its detailed structure, the internal of its implementation, its provided features, its business or domain, etc. Once you will have chosen/define this viewpoint, and so the correponding metamodel (i.e. Ecore file), you will be able to produce models (XMI files) that conforms to this metamodel and actually represent your required view of the system. In order to do this, MoDisco provides some basic bricks that will help you to start and chain the various steps of your process.


How to install MoDisco 0.8.0M7

How to test/install the latest MoDisco 0.8.x integration build

How to test/install the latest MoDisco 0.9.x integration build

Back to the top