Model-Driven Evolution of Software Architectures - Software and ...
Model-Driven Evolution of Software Architectures - Software and ...
Model-Driven Evolution of Software Architectures - Software and ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
7.4. <strong>Model</strong>-<strong>Driven</strong>Migration 137<br />
Source<br />
view<br />
Source<br />
viewpoint<br />
specifies<br />
normalise<br />
specifies<br />
Normalised<br />
source view<br />
Canonical<br />
source viewpoint<br />
source<br />
specifies<br />
transform<br />
Transformation<br />
rules<br />
Figure 7.3:Generictwo-phasedmigrationapproach<br />
Target<br />
view<br />
Target<br />
viewpoint<br />
specifies<br />
target<br />
makesitinfeasibletospecifygenericcorrespondingtransformationrules.<br />
Assuch,weintroduceanintermediatenormalisationstepthatusesaset<strong>of</strong><br />
normalisationrulestoobtainanormalisedsourcemodel. Thenormalisationrulesaredefinedasmappingsfromthesourcemetamodeltothenormalisedsourcemetamodel.Thisnormalisedmetamodeldescribesasubset<br />
<strong>of</strong>themodelsdescribedbythesourcemetamodel. Next,aset<strong>of</strong>transformationrulescanbeappliedtotransformanormalisedsourcemodelinto<br />
thetargetmodel.Thesetransformationrulesaredefinedasmappingsfrom<br />
thenormalisedsourcemetamodeltothetargetmetamodel.<br />
Inall,weseemigrationasaseries<strong>of</strong>automatedmodeltransformationsthataredefinedonmetamodelstotransformasourcemodelintoa<br />
targetmodelusingadistinctnormalisationstep.Thisapproachisgeneric<br />
inthesensethatitcanbeappliedtoanyconformingsource<strong>and</strong>target<br />
modelwithoutloss<strong>of</strong>generality. Toactuallyimplementthisapproachwe<br />
require(normalised)source<strong>and</strong>targetmetamodels,normalisationrules,<br />
<strong>and</strong>transformationrules.<br />
Althoughtheapproachisgeneric, ourindustrialcaseimposessome<br />
practicalrestrictionsontheenablingtechnologies.Spurredbythefactthat<br />
theexistingarchitecturedocumentationcontainedsourcemodels(partly)<br />
in UMLstatecharts, wedecidedtoimplementthedifferentsteps<strong>of</strong>our<br />
migrationapproachusingMDAtechnologies. IntheMDAvision,s<strong>of</strong>tware<br />
developmentisconsideredtobeaseries<strong>of</strong>modeltransformations. Similarly,weconsiders<strong>of</strong>twaremigrationasaseries<strong>of</strong>modeltransformations.<br />
StartingfromUML,technologiescompatiblewithMDA<strong>of</strong>ferconvenient<strong>and</strong><br />
<strong>of</strong>f-the-shelfmeanstodefine<strong>and</strong>manipulatemodels. Furthermore,the<br />
MetaObjectFacility 1 (MOF)canbeusedforthedefinition<strong>of</strong>metamodels.<br />
1 http://www.omg.org/m<strong>of</strong>(June2007)
Change language