11.12.2012 Views

Model-Driven Evolution of Software Architectures - Software and ...

Model-Driven Evolution of Software Architectures - Software and ...

Model-Driven Evolution of Software Architectures - Software and ...

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

64 Chapter4. Evaluation<br />

Describe<br />

Develop<br />

Architecture Scenarios<br />

Classify / prioritise<br />

scenarios<br />

Individually evaluate<br />

indirect scenarios<br />

Assess scenario<br />

interaction<br />

Create overall<br />

evaluation<br />

Figure 4.3:SAAMsteps[Clementsetal.,2002b].<br />

selectedmethodisavailable. Theseconstraintsimplytheexclusion<strong>of</strong><br />

many<strong>of</strong>theinventoriedmethodsbecausetheseeitherfocusonadifferent<br />

qualityattributeorlacksufficientdetail,e.g. manymethodsaredefined<br />

<strong>and</strong>explainedinonlyonepublishedarticle.<br />

Thebest-suitedmethodsdescribedintheinventoryseemtobeSAAM<strong>and</strong><br />

itssuccessor,theArchitectureTrade<strong>of</strong>fAnalysisMethod[Clementsetal.,<br />

2002b](ATAM). Bothaddressmaintainability<strong>and</strong>areextensivelydocumented.<br />

AlthoughATAMislikelytoproducemoreobjective<strong>and</strong>accurate<br />

results,italsoseemsmoredifficulttoapplyforinexperiencedassessors.<br />

Theuse<strong>of</strong>attribute-basedarchitecturestyles<strong>and</strong>theirassociatedqualityattributecharacterisationsforanalysis<strong>of</strong>architecturaldecisionsisnot<br />

straightforward. Alsotheidentification<strong>of</strong>sensitivity<strong>and</strong>trade-<strong>of</strong>fpoints<br />

<strong>and</strong>thegeneration<strong>of</strong>autilitytreerequiresmoreeffort<strong>and</strong>experience.<br />

DuetoOcé’srequirementswithrespecttotheneedfortraining(noneed)<br />

<strong>and</strong>organisationalimpact(low)<strong>of</strong>themethod,SAAMwasselected.<br />

InaSAAMevaluation, scenariosaredevelopedtoassessas<strong>of</strong>tware<br />

architecture’ssupportformaintainability. Thescenariosareusedtoexpresstherequiredtype<strong>of</strong>maintainability<strong>and</strong>thusSAAMcanalsobeusedtoevaluatethetype<strong>of</strong>maintainabilitywedescribedpreviously.Thedevelopedscenariosrepresentpossiblefuturechangestothes<strong>of</strong>twaresystem.Animportantaspect<strong>of</strong>SAAMisthatitinvolvesallstakeholders<strong>of</strong>as<strong>of</strong>twarearchitectureinajointevaluationsession,whichresultsinabetter<br />

appreciation <strong>and</strong> a more widely shared underst<strong>and</strong>ing <strong>of</strong> the s<strong>of</strong>tware<br />

architecture.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!