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.
4.4. ConductingtheEvaluation 69<br />
givesanimpression<strong>of</strong>thefinalresult<strong>of</strong>theSAAMsession.Scenarioswere<br />
classifiedin directly<strong>and</strong> indirectlysupportedscenarios.<br />
Priority<br />
1<br />
2<br />
3<br />
Direct scenarios Indirect scenarios<br />
concrete floating<br />
low impact high impact<br />
scenario ID<br />
description<br />
characterisation<br />
scenario ID<br />
description<br />
characterisation<br />
scenario ID<br />
description<br />
scenario ID<br />
characterisation<br />
description<br />
characterisation<br />
scenario ID<br />
description<br />
scenario ID<br />
characterisation<br />
description<br />
characterisation<br />
scenario ID<br />
description<br />
scenario ID<br />
characterisation<br />
description<br />
scenario ID<br />
characterisation<br />
description<br />
characterisation<br />
scenario ID<br />
description<br />
characterisation<br />
Figure 4.4:SAAMresults<br />
scenario ID<br />
description<br />
characterisation<br />
scenario ID<br />
description<br />
characterisation<br />
Ingeneral,firsttheimpact<strong>of</strong>ascenarioonaspecificproductwasevaluated,<strong>and</strong>thenitsimpactonthereferencearchitecture.Classification<strong>and</strong>evaluationrequiredadifferentattitudebecausewewereevaluatingareferencearchitectureinstead<strong>of</strong>aproductarchitecture.Thedifficultyliedinthefactthatwhilescenariosareconcrete,representingfuturefunctionality,orthequality<strong>of</strong>actualproducts,thereferencearchitectureisabstract.<br />
Thequestion:“Whatistheimpactonthereferencearchitecture?”neededto<br />
beansweredconsistentlyforallscenarios.Thereforewedefinedtwotypes<br />
<strong>of</strong>directscenarios:<br />
1.Scenariosthataresupportedbythereferencearchitectureasis<strong>and</strong><br />
forwhichitprovides concreteguidelinesonhowtorealisethemin<br />
productinstantiations,<strong>and</strong><br />
2.Scenariosthatcanberealisedbysystemsbasedonthereference<br />
architecture,butforwhichitdoesnot(yet)providedetailedinformationonhowtorealizethem(floating).<br />
Theclass<strong>of</strong> floatingscenarioscallsforacookbookwithrecipesthatdescribesolutionsforvariationpointsinthereferencearchitecture.Cookbookrecipesdescribehowthereferencearchitecturecanbeusedtorealizeaspecific(floating)scenario.Forexample,itmightbenecessarytodescribewhat
Change language