Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "MoDisco/Components/Java/Composition/Architecture"

(New page: {{MoDiscoJavaCompositionTabs}} = Metamodel = = Benchmark = Java Composition Model, weaving KDM Model Source and Java Model, can easily become a big model, in terms of XMI size as well a...)
 
m (Metamodel)
Line 2: Line 2:
  
 
= Metamodel =
 
= Metamodel =
 +
[[Image:JavaApplicationMetaModel.png|frame|center|JavaApplication MetaModel]]
  
 
= Benchmark =
 
= Benchmark =

Revision as of 10:51, 9 August 2010

DEPRECATED use Template:MoDiscoTabs and Template:MoDiscoTab as explain here : Wiki Template for MoDisco

Metamodel

JavaApplication MetaModel

Benchmark

Java Composition Model, weaving KDM Model Source and Java Model, can easily become a big model, in terms of XMI size as well as number of model elements.

First implementation resulted in a single XMI file containing all the weaving elements between both models.

Second implementation results in a root XMI file, referencing other xmi fragment Splitting was done following this repartition :

Back to the top