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.4. ConductingtheEvaluation 67<br />
4.4 ConductingtheEvaluation<br />
Theevaluationconsisted<strong>of</strong>roughlythreephases. First,thejointDSAAM<br />
sessionhadtobeprepared.Second,theDSAAMevaluationsessionitselfwas<br />
executed. Andfinallyanoverallevaluation<strong>of</strong>thereferencearchitecture<br />
wascreated.Threearchitectsinvolvedinthedevelopment<strong>of</strong>thereference<br />
architecture<strong>and</strong>twoexternalobserversparticipatedinthejointsession.<br />
One<strong>of</strong>thearchitectsplayedtherole<strong>of</strong>evaluationleader<strong>and</strong>prepared,<br />
chaired,<strong>and</strong>evaluatedthejointsession<strong>of</strong>DSAAM. ForeachSAAMstepin<br />
Figure4.3onpage64,weexplainbelowhowitwasincludedinthedifferent<br />
phases<strong>of</strong>theDSAAMassessment.<br />
4.4.1 Preparation<br />
Inpreparationtotheexecution<strong>of</strong>thejointDSAAMsessiontheavailable<br />
documentation(onthereferencearchitecture<strong>and</strong>onSAAM)wasdistributed<br />
amongtheparticipants. Thereferencearchitecture’sdocumentationwas<br />
especiallyusefulfortheexternalobserversasitexplainsthearchitecture<br />
<strong>and</strong>theappliedarchitecturalmechanisms. ThedocumentsonSAAMwere<br />
onlyusedbytheevaluationleader.<br />
Thestep‘developscenarios’wascarriedoutintwostages. Duringthe<br />
preparationphase,theevaluationleaderconsultedstakeholders<strong>of</strong>f-line.<br />
Thisresultedinaninitialset<strong>of</strong>high-levelscenariosrepresentingpossible<br />
futuresfromastakeholder’sperspective.Theset<strong>of</strong>stakeholdersincluded<br />
thesponsor<strong>of</strong>thereferencearchitecture,members<strong>of</strong>thes<strong>of</strong>twarereuse<br />
group,<strong>and</strong>hardware<strong>and</strong>domainexperts. Unfortunately,themarketing<br />
<strong>and</strong>maintenancegroupswerenotconsulted,whichlimitedtheviewon<br />
theroadmapsforOcécopiermachines. Thescenarioswererelatedtoeitherexistingproductsorforeseenproducts.Whetherthereferencearchitecturewasbasedontheseproductsisirrelevant.<br />
Theevaluationleader<br />
thenaddedmoredetailtothesescenariosaccordingtoatemplateforscenariosbasedonBassetal.[2003].<br />
4.4.2 Scenarios<br />
Intotalsixteenscenariosweredeveloped<strong>of</strong>f-line.Themajority<strong>of</strong>thescenariosaimedatreducingmaterialcosts,forexamplebysharingresources,<br />
usinglow-powerdesigns,or<strong>of</strong>floadingorre-mappingfunctionality. One<br />
scenario,forinstance,aimedatmovingfunctionalityfromtheengines<strong>of</strong>twaretothemaincontroller,anothersubsystem<strong>of</strong>acopier.<br />
Asecondkind<strong>of</strong>scenarioswasdevelopedtoreducedevelopmentcosts.<br />
Forinstance,introduction<strong>of</strong>codegenerationforcontrollers<strong>of</strong>sensors<strong>and</strong><br />
actuatorsbasedonmathematicalmodels<strong>of</strong>thosehardwaredevices.These