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.
74 Chapter4. Evaluation<br />
manyindirectstakeholderscanbeidentified. Thesetwogroups<strong>of</strong>stakeholdersseemtohavedifferentinterests.<br />
Raisingthescope<strong>of</strong>reuse<strong>of</strong>thereferencearchitecturedirectlyconcerns<br />
thearchitects<strong>of</strong>compatibleproductsasitsusers<strong>and</strong>architects.Itimplies<br />
thatthereferencearchitecturenotonlyshouldidentifyvariationpoints<br />
butalsoexplicitlygivealternatives. Thecookbook<strong>of</strong>theprevioussection<br />
providesthese.<br />
Scenariosthatdescribefuturedevelopment<strong>of</strong>existing<strong>and</strong>foreseen<br />
productsaretheconcern<strong>of</strong>thestakeholders<strong>of</strong>thoseproducts.Thedevelopment<strong>of</strong>thesescenariosistheresponsibility<strong>of</strong>thesestakeholders,which<br />
arenotnecessarilyalsodirectstakeholders<strong>of</strong>thereferencearchitecture.<br />
Ontheotherh<strong>and</strong>theresultingscenariosareinputtoDSAAMsession,thus<br />
indirectlytheyare.<br />
Onemeasurewetooktoincludeindirectstakeholdersintheevaluation<br />
wastosplittheprocess<strong>of</strong>developingtheset<strong>of</strong>scenariosintwostages:an<br />
<strong>of</strong>f-linestagewiththeindirectstakeholders,<strong>and</strong>aDSAAMstagewiththe<br />
directstakeholders. Thescenariosprovidedbytheindirectstakeholders<br />
wereproductspecific.Evaluatingtheimpactonthereferencearchitecture<br />
wasnottheirconcern,butthat<strong>of</strong>thedirectstakeholders. Furthermore<br />
thedirectstakeholdersaretheonlyonescapable<strong>of</strong>doingso. Therefore<br />
becauseonlytheindirectstakeholderswereexcludedfromthejointsession,<br />
thescope<strong>of</strong>theDSAAMsessionwasnotaffectedbythelack<strong>of</strong>stakeholder<br />
interactionduringevaluation.<br />
However,thisalsopreventedindirectstakeholderstointerfereorinteractduringscenarioprioritisation.DuringtheDSAAMsession,thearchitectsconcentratedonthemostlikelyscenarios,fromtheperspective<strong>of</strong>anarchitect.Althoughscenarioswereprioritisedwithrespecttotheirimpact,there<br />
wasnoclearrationaleforthisranking. HenceDSAAM’sscopewasstillat<br />
riskduetothepossibility<strong>of</strong>awrongscenarioprioritisation.<br />
InordertovalidateDSAAM’sscopewerecommendtoorganiseindirect<br />
stakeholder involvement after the joint session. During this feedback<br />
phasestakeholdersmightbeconsultedinsmallsessionsorindividualinterviews,inthesamewayaswedidinpreparationtothesession.<br />
This<br />
timetheindirectstakeholderscancommentonthescenariosprioritisation<strong>and</strong>verifywhethertheevaluationcoveredallrelevantaspects<strong>of</strong>the<br />
architecture. Thispreservesthesmallimpactontheorganisation<strong>of</strong>fered<br />
byDSAAM.Duringthefeedbackphase,indirectstakeholdersmayconclude<br />
thatsomelikelyscenarioshavenotbeenevaluatedthoroughlyenough.<br />
Thusthefeedbackphasemayyieldnewlydevelopedscenarios. Thisnew<br />
set<strong>of</strong>scenarioshastobeevaluatedinanewDSAAMsession.<br />
FutureworkExtendDSAAMwithan<strong>of</strong>f-linefeedbackphaseafterthejointsessionforindirectstakeholders.
Change language