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.
68 Chapter4. Evaluation<br />
scenarioswereespeciallytargetedatinteractionswhichgobeyondthedomainlevel,suchascommunicationswiththemechatronics,testing,<strong>and</strong><br />
manufacturinggroups.<br />
Finally,aminorsource<strong>of</strong>scenariosinvolvedanupgrade<strong>of</strong>thefunctionality,suchascolour<strong>and</strong>wide-formatprinting.Anexamplescenariois<br />
depictedinTable4.3inaformatdescribedbyBassetal.[2003].<br />
Stimulus<br />
Table 4.3:Anexamplescenario.<br />
Reduce power consumption by turning <strong>of</strong>f<br />
parts <strong>of</strong> the copier machine during low-power<br />
mode<br />
Response Solve in engine specific projects<br />
Source Electronics department<br />
Environment Engine development time<br />
Stimulated arte- Reference architecture documentation<br />
fact<br />
Response measure<br />
4.4.3 Execution<br />
Reuse percentage remains on same level<br />
Inthejointsessioneacharchitectrepresentedaproductasauser<strong>of</strong>the<br />
referencearchitecture.Additionally,allarchitectsplayedtherole<strong>of</strong>assessor.Assome<strong>of</strong>theparticipantshadnoexperienceinSAAMevaluations<strong>and</strong><br />
toexplainthesteps<strong>of</strong>theDSAAMprocess,thesessionstartedwithabrief<br />
introduction<strong>of</strong>theprocess. Fortheprocessobserversalsotherole<strong>of</strong>the<br />
referencearchitectureintheorganisation<strong>of</strong>Océwasexplained.<br />
The step ‘describe the architecture’ was largely omitted during the<br />
DSAAM session, since the DSAAM session only involved people that are<br />
well-informed with respect to the reference architecture <strong>and</strong> extensive<br />
documentationwasalreadyavailable.<br />
Thesecondpart<strong>of</strong>thestep‘developscenarios’wasdoneduringthe<br />
DSAAMsession.Thisinvolvedonlyarchitects<strong>of</strong>productsonwhichthereferencearchitecturewasbased.<br />
Apparently,thescenarioscontributedby<br />
thestakeholdersconsultedpriortothejointsessionarerepresentativefor<br />
whatmaychangeinthefuture,assolicitingforextrascenariosgaveno<br />
results.Assuch,thescenariosgathered<strong>and</strong>elaboratedbytheevaluation<br />
leaderwereused.<br />
Scenarioswereclassified,prioritised,<strong>and</strong>evaluatedasinSAAM,that<br />
is,duringthesessionitself. Thescenarioswereclassified<strong>and</strong>evaluated<br />
onebyone,bypassingprioritisation(Figure4.3onpage64). Figure4.4
Change language