Skip to main content
Jump to: navigation, search

Difference between revisions of "MoDisco/Components/JavaComposition/Architecture"

m
m (Benchmark)
Line 4: Line 4:
  
 
= Benchmark =
 
= 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 :

Revision as of 04:49, 6 August 2010

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

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