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.
6 Chapter1. Introduction<br />
differentabstractionlevelsisnotaddressed. Moreover,mostapproaches<br />
dictatetheintroduction<strong>of</strong>specificmodellinglanguages,requiringachange<br />
tocurrentways<strong>of</strong>working.<br />
Migration Aset<strong>of</strong>consistentdevelopmentartefactsasdeterminedbythe<br />
conformancecheckingtask,reducestherisk<strong>of</strong>anactualmigration<strong>of</strong>the<br />
architecture<strong>and</strong>dependentdevelopmentartefacts. Themigrationtoa<br />
newproduct-linearchitecture<strong>and</strong>associateds<strong>of</strong>twareplatformthatbettersupportsforeseenrequirements,requiresthemigration<strong>of</strong>allproducts<br />
supportedbythelegacyplatform. Thereisnopreviousworkthatconsiderss<strong>of</strong>tware(architecture)migrationasamodeltransformationproblem.<br />
Severalotherworkdoesaddressthetransformation<strong>of</strong>s<strong>of</strong>twaresystems.<br />
However, they consider single-product architectures [Bosch <strong>and</strong> Molin,<br />
1999], simple graphs [Fahmy <strong>and</strong> Holt, 2000b], or the level <strong>of</strong> source<br />
code[Terekhov<strong>and</strong>Verhoef,2000]. Thelanguagemigrationprocessused<br />
byTerekhov<strong>and</strong>Verhoef[2000]isparticularlyinteresting.Itseparatesa<br />
migrationinthreephasesthatincluderestructuring<strong>of</strong>sourceprograms<br />
toenablethe(automatic)transformationphase. Althoughitwasusedfor<br />
sourcecodemigration,suchapreparatorystepisalsorequiredforthemigrationonthearchitecturalleveltotakeintoaccountindustrialmodelling<br />
conventions.<br />
Documentation Afteramigration<strong>of</strong>the(product-line)architecture<strong>and</strong>the<br />
product-line membersit supports, documentationneeds tobeupdated.<br />
Itisgenerallyacceptedthatthedocumentation<strong>of</strong>s<strong>of</strong>twarearchitectures<br />
consists<strong>of</strong>multipleviews[Kruchten,1995;H<strong>of</strong>meisteretal.,2005]. OftentheUnified<strong>Model</strong>ingLanguage<br />
1 (UML)isusedintheseviews. On<br />
theotherh<strong>and</strong>,specialisedarchitecturedescriptionlanguages(ADLs)(see<br />
Medvidovic<strong>and</strong>Taylor[1997]foranoverview)<strong>and</strong>MDEsupportthecreation<strong>of</strong>modelstoautomateseverals<strong>of</strong>twareengineeringtasks,suchas<br />
codegeneration. However,noapproachaddressestheproblem<strong>of</strong>keeping<br />
documentation<strong>and</strong>modelsconsistent. Withtheupcoming<strong>of</strong> MDEapproachesthisbecomesahighlyrelevantproblem.<br />
Inthisthesis,weaimatincreasingourunderst<strong>and</strong>ing<strong>of</strong>each<strong>of</strong>these<br />
fours<strong>of</strong>twareevolutiontasksaswellas<strong>of</strong>feringsupportforthem.<br />
1 http://www.uml.org(June2007)
Change language