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.
126 Chapter6. ConformanceCheckingII<br />
Analternativetocheckingconformanceafterdevelopment,wouldinvolvetheuse<strong>of</strong>MDEtogeneratesourcecodeorextendtheimplementation<br />
languagewitharchitecturalconstructsaswasdoneinArchJava[Aldrich<br />
etal.,2002]. Suchapproachesdirectlyconnectarchitecturetoimplementation,improvingconsistency.However,thisrequiresatleastachangein<br />
theway<strong>of</strong>working<strong>of</strong>theimplementationphase,forinstancetheuse<strong>of</strong>a<br />
newlanguage.Thisposesabarrierforimplementingsuchanapproachin<br />
practicalsettings.<br />
6.8 Conclusions<br />
Inthischapterweproposeaconformancecheckingsystem(CCS)tosystematicallydeterminediscrepanciesbetweenanintendedarchitecture<strong>and</strong><br />
therealisedarchitecture. Illuminatingthesedifferencesisapreparatory<br />
stepforarchitecturemigrationinwhichpreviouslydevelopedartefactsare<br />
reusedforreasons<strong>of</strong>efficiency. Ourtheconformancecheckingsystem<br />
(CCS)isnon-intrusive. Itcoordinatestheinteractionbetweenthearchitecture<strong>and</strong>theimplementationdomain<strong>of</strong>expertise,whileregardingthem<br />
autonomously. Itusesreadilyavailable,possiblytailored,technologyfor<br />
theactualimplementation<strong>of</strong>CCS.Assuch,themaincontributions<strong>of</strong>this<br />
chapterare:<br />
•agenericprocessforconformancechecking<strong>of</strong>architecturalviews;<br />
•extensible metamodels for C&C <strong>and</strong> module viewpoints, including<br />
mappingsfromimplementation<strong>and</strong>architecturalartefacts;<strong>and</strong><br />
•ademonstration<strong>of</strong>howtocombinedifferenttypes<strong>of</strong>technologies<br />
(inside<strong>and</strong>outsidethemodelwaretechnologicalspace)intoanintegratedapproach,<br />
whilereusingseveralexistingmetamodels<strong>and</strong><br />
transformations<br />
Althoughourapproachislargelyautomated,checkingtheconformance<br />
forparticulartype<strong>of</strong>viewsmightrequireaspecificapproach. Still,the<br />
CCSprovidesagenericprocessbasedonacommondesign-spaceviewpoint.<br />
TheCCSreliesonacleardefinition<strong>of</strong>associatedmetamodel<strong>and</strong>themappingsfromthearchitectural<strong>and</strong>implementationartefactstothiscommon<br />
metamodel.<br />
Thedesign-spacemetamodel(e.g., Figure6.6onpage113)captures<br />
checkableconcepts,whicharetheconsensusbetweenverifyingabstract<br />
properties<strong>of</strong>thearchitecture<strong>and</strong>emergingproperties<strong>of</strong>theimplementation.Possiblediscrepanciesbetweenthetwoarerevealedasmismatches<br />
betweenthederivedconformancemodels<strong>and</strong>theimpact<strong>of</strong>amismatch.
Change language