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

More documents

Recommendations

Info

46 Chapter3. StateofthePractice Figure 3.1:Thedecompositionoftheembedded-systems-developmentprocess temwillbeimplementedbyonediscipline.) Next,theprojectsallocated systemrequirementstothearchitecture’sdifferentelementsandrefined therequirements. Thisprocessisrepeatedforeachsubsystem. Finally, theprojectsdecomposedthesubsystemsintomonodisciplinarycomponents thatanindividualdeveloperorsmallgroupsofdeveloperscoulddevelop. Thelevelofdetailatwhichdecompositionresultedinmonodisciplinary subsystemsvaried. Insomecases,thefirstdesignordecompositionstep immediatelyresultedinmonodisciplinarysubsystemsandthecorrespondingrequirements. Inothercases,subsystemsremainedmultidisciplinary forseveraldesignsteps. Thisgenericembedded-systems-developmentprocessresultedinatree ofrequirementsanddesigndocuments(seeFigure3.1). Eachlevelrepresentedthesystemataspecificabstractionlevel. Themorecomplexthe system,themoreevidentthisconceptofabstractionlevelswasinthedevelopmentprocessanditsresultingartefacts(forexample,requirements documentation).
3.4. RequirementsEngineeringResults 47 Figure 3.2:Embedded-systems-developmentstakeholdersandotherfactors IntheprocessinFigure3.1,requirementsondifferentabstractionlevelsarerelatedtoeachotherbydesigndecisions,whichwererecordedin architectureanddesigndocumentation. Atthesystemlevel,thesedecisionsconcernedpartitioningofthefunctionalandnonfunctionalrequirementsoversoftwareandhardwarecomponents.Thecriteriausedforsuchconcurrentdesign(codesign)weremostlyimplicitandbasedonsystemarchitects’experience. 3.4 RequirementsEngineeringResults Typically, embedded-systems development involved many stakeholders. This was most apparent during requirements engineering. Figure 3.2 depictsourviewofthemostcommonstakeholdersandotherfactors. Inrequirementsengineering’sfirstphase,thecustomerdeterminesthe functionalandnonfunctionalrequirements.Dependingontheproductdomain,thecustomernegotiatestherequirementsviathemarketingand salesareaordirectlywiththedevelopers. Thefirstphase’soutputistheagreedrequirementsspecification,which isadescriptionofthesystemthatallstakeholderscanunderstand. This documentservesasacontractbetweenthestakeholdersanddevelopers.At thispoint,wenoticedacleardifferencebetweensmallandlargeprojects. Insmallprojects,thestakeholderrequirementsalsoservedasdeveloper requirements.Inlargeprojects,stakeholderrequirementsweretranslated intotechnicallyorienteddeveloperrequirements.
Page 1:
Model-DrivenEvolution ofSoftwareArc
Page 4 and 5:
Ditproefschriftisgoedgekeurddoordep
Page 6 and 7:
vi Preface Furthermore,Iwanttomenti
Page 8 and 9:
viii Contents 2.4 Model-DrivenEvolu
Page 10 and 11: x Contents 7.5 SourceMetamodel. ...
Page 12 and 13: xii ListofFigures 5.7 Examplescenar
Page 14 and 15: xiv ABBREVIATIONS MDA ModelDrivenAr
Page 16 and 17: 2 Chapter1. Introduction Figure 1.1
Page 18 and 19: 4 Chapter1. Introduction evolutiono
Page 20 and 21: 6 Chapter1. Introduction differenta
Page 22 and 23: 8 Chapter1. Introduction definedona
Page 24 and 25: 10 Chapter1. Introduction analysing
Page 26 and 27: 12 Chapter1. Introduction Figure 1.
Page 28 and 29: 14 Chapter1. Introduction Chapter3G
Page 31 and 32: Chapter2 Background Inthischapterwe
Page 33 and 34: 2.1. SoftwareEvolution 19 ofmainten
Page 35 and 36: 2.2. Architecture-DrivenSoftwareDev
Page 41 and 42: 2.3. Model-DrivenEngineering 27 are
Page 43 and 44: 2.3. Model-DrivenEngineering 29 sam
Page 45 and 46: 2.3. Model-DrivenEngineering 31 met
Page 47 and 48: 2.3. Model-DrivenEngineering 33 con
Page 49 and 50: 2.3. Model-DrivenEngineering 35 1mo
Page 51 and 52: 2.3. Model-DrivenEngineering 37 tin
Page 53: 2.4. Model-DrivenEvolutionofSoftwar
Page 56 and 57: 42 Chapter3. StateofthePractice toc
Page 58 and 59: 44 Chapter3. StateofthePractice Tab
Page 62 and 63: 48 Chapter3. StateofthePractice Req
Page 64 and 65: 50 Chapter3. StateofthePractice but
Page 66 and 67: 52 Chapter3. StateofthePractice IBM
Page 68 and 69: 54 Chapter3. StateofthePractice pro
Page 70 and 71: 56 Chapter3. StateofthePractice des
Page 72 and 73: 58 Chapter4. Evaluation Onestrategy
Page 74 and 75: 60 Chapter4. Evaluation Startingpoi
Page 76 and 77: 62 Chapter4. Evaluation p1 p2 p3 p4
Page 78 and 79: 64 Chapter4. Evaluation Describe De
Page 80 and 81: 66 Chapter4. Evaluation Theincrease
Page 82 and 83: 68 Chapter4. Evaluation scenarioswe
Page 84 and 85: 70 Chapter4. Evaluation kindofcompo
Page 86 and 87: 72 Chapter4. Evaluation Withrespect
Page 88 and 89: 74 Chapter4. Evaluation manyindirec
Page 90 and 91: 76 Chapter4. Evaluation 4.7 Conclus
Page 92 and 93: 78 Chapter5. Model-DrivenConformanc
Page 110 and 111:
96 Chapter5. Model-DrivenConformanc
Page 112 and 113:
98 Chapter5. Model-DrivenConformanc
Page 114 and 115:
100 Chapter5. Model-DrivenConforman
Page 116 and 117:
102 Chapter5. Model-DrivenConforman
Page 118 and 119:
104 Chapter6. ConformanceCheckingII
Page 120 and 121:
Page 122 and 123:
Page 124 and 125:
Page 126 and 127:
Page 128 and 129:
Page 130 and 131:
Page 132 and 133:
Page 134 and 135:
Page 136 and 137:
Page 138 and 139:
Page 140 and 141:
Page 143 and 144:
Chapter7 Model-driven Migration of
Page 145 and 146:
7.1. Introduction 131 viewisitsprim
Page 147 and 148:
7.3. MigrationContext 133 requests
Page 149 and 150:
7.3. MigrationContext 135 waferhasb
Page 151 and 152:
7.4. Model-DrivenMigration 137 Sour
Page 153 and 154:
7.5. SourceMetamodel 139 0..1 0..1
Page 155 and 156:
7.5. SourceMetamodel 141 WAIT_MEASU
Page 157 and 158:
7.6. NormalisationRules 143 7.6 Nor
Page 159 and 160:
7.6. NormalisationRules 145 Subsyst
Page 161 and 162:
7.7. TargetMetamodel 147 tworesourc
Page 163 and 164:
7.7. TargetMetamodel 149 > WAIT_FOR
Page 165 and 166:
7.8. Transformation 151 + capabilit
Page 167 and 168:
7.8. Transformation 153 Foreveryele
Page 169 and 170:
7.8. Transformation 155 SystemDefin
Page 171 and 172:
7.8. Transformation 157 rule Resour
Page 173 and 174:
7.8. Transformation 159 rule Condit
Page 175 and 176:
7.9. Evaluation 161 resentedbythesu
Page 177 and 178:
7.9. Evaluation 163 morecomplicated
Page 179 and 180:
7.10. ConclusionsandFutureWork 165
Page 181 and 182:
Chapter8 Visualisation of Domain-Sp
Page 183 and 184:
8.2. Background 169 Inpractice,thee
Page 185 and 186:
8.2. Background 171 Inpracticethear
Page 187 and 188:
8.3. Model-DrivenArchitecturalViews
Page 189 and 190:
8.4. UsingMDAVtoGenerateViews 175 S
Page 191 and 192:
8.4. UsingMDAVtoGenerateViews 177 8
Page 193 and 194:
8.4. UsingMDAVtoGenerateViews 179 .
Page 195 and 196:
8.5. IndustrialApplication 181 rule
Page 197 and 198:
8.5. IndustrialApplication 183 rule
Page 199 and 200:
8.6. Discussion 185 8.6 Discussion
Page 201 and 202:
8.8. ConcludingRemarks 187 Wherewep
Page 203 and 204:
Chapter9 Conclusion Thegoalofthisth
Page 205 and 206:
9.2. IntegrationinPractice(RQ1) 191
Page 207 and 208:
9.3. SoftwareProductLines(RQ2) 193
Page 209 and 210:
9.4. Model-DrivenEngineering(RQ3) 1
Page 211 and 212:
9.4. Model-DrivenEngineering(RQ3) 1
Page 213 and 214:
9.5. SupportforEvolutionofSoftwareA
Page 215 and 216:
9.6. FutureWorkandRecommendations 2
Page 217:
9.6. FutureWorkandRecommendations 2
Page 220 and 221:
206 BIBLIOGRAPHY Bass,Len,PaulCleme
Page 222 and 223:
208 BIBLIOGRAPHY Clements,PaulandLi
Page 224 and 225:
210 BIBLIOGRAPHY Favre,Jean-Marie.
Page 226 and 227:
212 BIBLIOGRAPHY Graaf,Bas,Hylkevan
Page 228 and 229:
214 BIBLIOGRAPHY Klein, Mark H., Ri
Page 230 and 231:
216 BIBLIOGRAPHY Proceedingsofthe6
Page 232 and 233:
218 BIBLIOGRAPHY Shaw,Mary,RobertDe
Page 234 and 235:
220 BIBLIOGRAPHY VanOmmering,Rob,Fr
Page 236 and 237:
222 Summary ellingandtheimportanceo
Page 239 and 240:
Samenvatting Tweebekendewettenindes
Page 241:
Samenvatting 227 Inmeerderehoofdstu
Page 244 and 245:
TitlesintheIPADissertationSeriessin
Page 246 and 247:
L.Cruz-Filipe. ConstructiveReal Ana
Page 248 and 249:
Sciences, Mathematics, andComputerS
Page 250:
Processes. Faculty of Electrical En
show all

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

Create successful ePaper yourself

Delete template?

Save as template?