Model-Driven Evolution of Software Architectures - Software and ...
Model-Driven Evolution of Software Architectures - Software and ...
Model-Driven Evolution of Software Architectures - Software and ...
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
78 Chapter5. <strong>Model</strong>-<strong>Driven</strong>ConformanceChecking<br />
Requirements<br />
Use cases<br />
Architecture<br />
Scenarios<br />
Stakeholders<br />
Architect<br />
State machines<br />
Maintenance<br />
Mistakes<br />
Developers<br />
Shortcuts<br />
Inconsistencies<br />
Tools/Developers<br />
Problems<br />
Components<br />
Product<br />
Figure 5.1:Typicaldevelopmentprocess<br />
Integrator<br />
behaviouralmodels. Theuse<strong>of</strong>suchspecificationsisillustratedbythe<br />
developmentprocessdepictedinFigure5.1.Itisbasedonthewell-known<br />
V-model[Bröhl<strong>and</strong>Dröschel,1995]<strong>and</strong>thestartingpoint<strong>of</strong>ourresearch.<br />
Ontheleftbranch<strong>of</strong>the‘V’analysisactivitiestakeplace.Basedon Requirements,thehigh-level<br />
Architectureisdefined.Thisarchitectureidentifies<br />
themaincomponents<strong>of</strong>thesystem<strong>and</strong>assignsresponsibilities.Inparallelrequirementsaremademoreconcreteby<br />
Use casesthatspecifytypical<br />
interactionsausermayhavewiththesystem. Onedistinctiveproperty<br />
<strong>of</strong>usecasesisthatthesystemisconsideredtobeablackbox[Jacobson,<br />
1992].Theseusecasesarethefirstinteraction-basedbehaviouralmodels.<br />
Basedontheusecasesaset<strong>of</strong> Scenariosisdefinedthatspecifiesthe<br />
interactions<strong>of</strong>thesystem’scomponentsinterms<strong>of</strong>exchangedmessages.<br />
Typically,everyusecaseresultsinone(normalbehaviour)ormore(includingexceptionalbehaviour)scenarios.Thesescenariosarealsointeractionbasedbehaviouralmodels,butnowthesystemisconsideredtobeawhitebox;<br />
theyshowtheinteractionsbetweenthecomponentsdefinedbythe<br />
architecture.<br />
Eventually,thearchitecture’scomponentsneedtobeimplemented.This<br />
requiresacompletebehaviouralspecification.Scenariosare,however,not<br />
intendedtoprovidesuchaspecificationforanindividualcomponent.First,<br />
thespecification<strong>of</strong>acomponent’sbehaviourisscatteredacrossmultiple<br />
scenarios.Second,theyareusuallyonlydefinedforthecomponents’most<br />
typical<strong>and</strong>importantbehaviours. Therefore,acompletestate-basedbehaviouralmodel,aState<br />
machine,iscreatedforeachcomponentbasedon<br />
theset<strong>of</strong>scenarios. Thisstatemachineisusedtoimplementorgener-