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.
4.3. EvaluationApproach 65<br />
Figure4.3 showsthedifferentphases<strong>of</strong>SAAM.ASAAMevaluationsessionstartswithscenariodevelopment<strong>and</strong>description<strong>of</strong>thearchitecture.Theseareiterativeactivities.Newscenarioscanmakeitnecessarytodescribethearchitecturefurther,sothatthearchitectscananalysethem,<br />
whiledescribingaspects<strong>of</strong>thearchitectureforcestothinkaboutpossible<br />
scenariosaddressingtheseaspects.<br />
Next,thescenariosareprioritised<strong>and</strong>classified.Scenariosthatcanbe<br />
realisedwithoutmakingchangestothecurrentarchitectureareclassified<br />
asdirect. Scenariosthatdorequirechangestothecurrentarchitecture<br />
areclassifiedasindirect.Theindirectscenariosareevaluatedfortheirimpact.Furthermore,thescenariointeractionisdetermined.<br />
Twoscenarios<br />
interactwhentheyrequirechangestothesamearchitecturalcomponent.<br />
Informationonscenariointeractionisindicative<strong>of</strong>thequality<strong>of</strong>thedecomposition.Finally,theclassification,prioritisation,analysis<strong>of</strong>theindividualscenarios,<strong>and</strong>thescenariointeractionareusedtocreateanoverallevaluation.ASAAMevaluationsessiontypicallytakestwodays<strong>and</strong>involvesanexternalevaluationteam<strong>of</strong>threet<strong>of</strong>ourpeople.Asessionalsoinvolvessystemarchitects<strong>and</strong>otherstakeholders.<br />
Thetype<strong>of</strong>stakeholdersinvolved<br />
isverydiverse:architects,developers,maintainers,integrators,managers,<br />
customers,endusers,<strong>and</strong>soon.<br />
4.3.2 TailoringSAAM<br />
SAAMhasbeenselectedastheevaluationmethod,yetithadtobetailored<br />
toOcé’ssituation.ThecurrentsituationatOcémakesitnecessarytomodifySAAMfortworeasons:1)theorganisationalimpact<strong>of</strong>SAAM<strong>and</strong>2)the<br />
level<strong>of</strong>abstraction<strong>of</strong>thereferencearchitecture.<br />
Inthesituation<strong>of</strong>Océtheimpact<strong>of</strong>gatheringallpotentialstakeholders<br />
(asindicatedinTable4.2onthenextpage),wasconsideredtoolarge.The<br />
mainreasonwasthatthestakeholders<strong>of</strong>as<strong>of</strong>twarearchitecturetypically<br />
includesome<strong>of</strong>theimportantmembers<strong>of</strong>anorganisationthatusually<br />
haveverybusyschedules.Forthereferencearchitecturethisisespecially<br />
trueasitisthedevelopmentgroup’sambitiontomakeitareferencearchitecturethatwillimpactdevelopment<strong>of</strong>many<strong>of</strong>Océ’scopiersforyears.<br />
Furthermore,thescope<strong>of</strong>areferencearchitectureislargerthanthat<strong>of</strong>a<br />
single-productarchitecture<strong>and</strong>therefore,nexttoagroup<strong>of</strong>directstakeholdersalargegroup<strong>of</strong>indirectstakeholders(asindicatedinTable4.2on<br />
thefollowingpage)exist,whichmakesthecompletegroup<strong>of</strong>peoplewith<br />
aninterestinareferencearchitecturemuchlarger.