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.
5.8. Conclusions 101<br />
UMLvs. MOF Theuse<strong>of</strong> UMLinalimiteddomainmakestransformation<br />
definitionsunnecessarycomplex<br />
Thegenericity<strong>and</strong>resultingcomplexity<strong>of</strong>theUMLmetamodelresult<br />
in,sometimes,inconvenientnavigationthroughsource<strong>and</strong>targetmodels<br />
toselectacertainelement. Anopenquestioniswhethertreetraversal<br />
strategiesaspresentinStratego 1 ortheJJTraveller[VanDeursen<strong>and</strong><br />
Visser,2004]librarycouldhelptoalleviatethisnavigationproblem.Also,<br />
<strong>of</strong>tenrelationsaredefinedasn:mwhileinaspecificcase1:1wouldsuffice.<br />
Theresultisthatsetshavetobeconvertedtosequences<strong>of</strong>whichthefirst<br />
elementhastobeselected. Thisisrequiredveryfrequently,resultingin<br />
unnecessarycomplexATLcode.<br />
Incases,whereonlylimitedparts<strong>of</strong>theUMLmetamodelareused,analternativecouldbeconsidered.Instead<strong>of</strong>usingtheUMLmetamodel,custom<br />
MOF-basedmetamodelscouldbeused,forinstance,forscenarios<strong>and</strong>state<br />
machines.Thesemetamodelscouldbemuchsimpler,resultinginsimpler<br />
transformationdefinitions.Thepricetopayisthatinordertoestablisha<br />
connectionwithactualUMLmodels(e.g.,asusedbyOcé),amappingbetweensuchcustommetamodels<strong>and</strong>theUMLmetamodelmustbespecified.<br />
InChapter8wediscusshowtomakesuchamappingfordomain-specific<br />
modellinglanguages(DSMLs).<br />
5.8 Conclusions<br />
Inthischapterweexploredtheuse<strong>of</strong>modeltransformationstocheckthe<br />
consistencybetweenbehaviouralspecifications. Forthiswepresentedan<br />
approachthatconsists<strong>of</strong>normalisation,transformation,<strong>and</strong>comparison<br />
steps.Weconsiderthefollowingtobethemaincontributions<strong>of</strong>thischapter:<br />
•Aspecification<strong>of</strong>themappingbetweenscenarios<strong>and</strong>statemachines<br />
usingmodeltransformationsthatismadeavailableviatheATLtransformationsrepository.Anadvantage<strong>of</strong>suchaspecificationisthatit<br />
canbeexecutedbytheATLtransformationengine. Furthermore,it<br />
iscompletelybasedonUML,makingintegrationinindustrialpractice<br />
easier.<br />
•<strong>Model</strong>lingconventionsforencodingtheinformationrequiredforthe<br />
transformationstepinasingleUMLmodel.Additionally,asanexample,wediscussedtherequirednormalisationstepforOcé’sreference<br />
architecture.<br />
1 http://www.stratego-language.org
Change language