Model-Based System Architecture

400 Pages·2015·8.01 MB·English

by  Lamm

MODEL-BASED SYSTEM
ARCHITECTURE
WILEY SERIES IN SYSTEMS ENGINEERING AND
MANAGEMENT
AndrewP.Sage,FoundingEditor
Acompletelistofthetitlesinthisseriesappearsattheendofthisvolume.
MODEL-BASED SYSTEM
ARCHITECTURE
TIM WEILKIENS
JESKO G. LAMM
STEPHAN ROTH
MARKUS WALKER
Copyright©2016byJohnWiley&Sons,Inc.Allrightsreserved
OMGSysML,OMGSystemsModelingLanguage,UML,UnifiedModelingLanguage,ModelDriven
Architecture,MDA,BusinessMotivationModel,BMMandXMIaretrademarksorregistered
trademarksoftheObjectManagementGroup,Inc.intheUnitedStates,theEuropeanUnionandother
countries.
CameoisaregisteredtrademarkofNoMagic,Inc.
FASisaregisteredtrademarkofooseInnovativeInformatikeGinGermany.
SYSMODisaregisteredtrademarkofTimWeilkiensinGermany.
V-ModellisaregisteredtrademarkofBundesrepublikDeutschlandinGermany.
TOGAF®isatrademarkofTheOpenGroup.
PublishedbyJohnWiley&Sons,Inc.,Hoboken,NewJerseyPublishedsimultaneouslyinCanada.
Nopartofthispublicationmaybereproduced,storedinaretrievalsystem,ortransmittedinanyform
orbyanymeans,electronic,mechanical,photocopying,recording,scanning,orotherwise,exceptas
permittedunderSection107or108ofthe1976UnitedStatesCopyrightAct,withouteithertheprior
writtenpermissionofthePublisher,orauthorizationthroughpaymentoftheappropriateper-copyfee
totheCopyrightClearanceCenter,Inc.,222RosewoodDrive,Danvers,MA01923,[phone],fax
[phone],oronthewebatwww.copyright.com.RequeststothePublisherforpermissionshould
beaddressedtothePermissionsDepartment,JohnWiley&Sons,Inc.,111RiverStreet,Hoboken,NJ
07030,[phone],fax[phone],oronlineathttp://www.wiley.com/go/permissions.
LimitofLiability/DisclaimerofWarranty:Whilethepublisherandauthorhaveusedtheirbesteffortsin
preparingthisbook,theymakenorepresentationsorwarrantieswithrespecttotheaccuracyor
completenessofthecontentsofthisbookandspecificallydisclaimanyimpliedwarrantiesof
merchantabilityorfitnessforaparticularpurpose.Nowarrantymaybecreatedorextendedbysales
representativesorwrittensalesmaterials.Theadviceandstrategiescontainedhereinmaynotbe
suitableforyoursituation.Youshouldconsultwithaprofessionalwhereappropriate.Neitherthe
publishernorauthorshallbeliableforanylossofprofitoranyothercommercialdamages,including
butnotlimitedtospecial,incidental,consequential,orotherdamages.
Forgeneralinformationonourotherproductsandservicesorfortechnicalsupport,pleasecontactour
CustomerCareDepartmentwithintheUnitedStatesat(800)762-2974,outsidetheUnitedStatesat
[phone]orfax(317)572-4002.
Wileyalsopublishesitsbooksinavarietyofelectronicformats.Somecontentthatappearsinprintmay
notbeavailableinelectronicformats.FormoreinformationaboutWileyproducts,visitourwebsiteat
www.wiley.com.
LibraryofCongressCataloging-in-PublicationData:
Weilkiens,Tim.
Model-basedsystemarchitecture/TimWeilkiens,JeskoG.Lamm,StephanRoth,
MarkusWalker.
pagescm.–(Wileyseriesinsystemsengineeringandmanagement)
Includesindex.
ISBN978-1-118-89364-7(hardback)
1.Systemdesign.2.Computersimulation.3.SysML(Computerscience)I.Lamm,JeskoG.,1976-II.
Roth,Stephan,1968-III.Walker,Markus,1965-IV.Title.
TA168.W43382016
620′.0042–dc23
2015024774
Typesetin11pt/13ptTimesTenLTStdbySPiGlobal,Chennai,India
PrintedintheUnitedStatesofAmerica
10987654321
1 2016
Contents
Foreword xi
Preface xv
Aboutthe CompanionWebsite xix
1 Introduction 1
2 An Example:TheVirtual MuseumTourSystem 5
3 Better Products— TheValue of SystemsArchitecting 9
3.1 TheShareofSystemsArchitectinginMakingBetter
Products 9
3.2 TheBenefitsthatcanbeAchieved 10
3.3 TheBenefitsthatcanbeCommunicatedinsidethe
Organization 14
3.4 TheBeneficialElementsofSystemsArchitecting 15
3.5 BenefitsofModel-BasedSystemsArchitecting 16
4 Definition of SystemArchitecture 19
4.1 WhatisArchitecture? –DiscussionofSomeExisting
Definitions 20
4.2 ModelingtheDefinitionsof“System”and“System
Architecture” 22
v
vi CONTENTS
5 Model-BasedSystemArchitecture 27
6 ArchitectureDescription 35
6.1 WhySpendingEfforttoDescribetheArchitecture? 35
6.2 TheArchitectureDescription 37
6.3 HowtoGetanArchitectureDescription? 44
7 ArchitecturePatternsandPrinciples 49
7.1 TheSYSMODZigzagPattern 50
7.2 TheBaseArchitecture 57
7.3 CohesionandCoupling 61
7.4 SeparationofDefinition,UsageandRun-Time 63
7.5 SeparateStablefromUnstableParts 65
7.6 TheIdealSystem 65
7.7 ViewandModel 66
7.8 DiagramLayout 68
7.9 SystemModelStructure 69
7.10 Heuristics 71
8 Requirementsand UseCaseAnalysis 75
8.1 IdentifyandDefineRequirements 76
8.2 SpecifytheSystemContext 80
8.3 IdentifyUseCases 82
8.4 DescribeUseCaseFlows 84
8.5 ModeltheDomainKnowledge 86
9 Perspectives,Viewpoints andViews in System
Architecture 89
9.1 Overview 89
9.2 TheFunctionalPerspective 91
9.3 ThePhysicalPerspective 96
9.4 TheBehavioralPerspective 100
9.5 TheLayeredPerspective 100
9.6 SystemDeploymentPerspective 112
CONTENTS vii
9.7 OtherPerspectives 115
9.8 RelationtotheSystemContext 117
9.9 MappingDifferentPerspectivesandLevels 120
9.10 Traceability 125
9.11 PerspectivesandViewsinModel-BasedSystems
Architecting 125
10 TypicalArchitectureStakeholders 131
10.1 Overview 131
10.2 RequirementsEngineering 133
10.3 Verification 135
10.4 ConfigurationManagement 137
10.5 EngineeringDisciplines 138
10.6 ProjectandProductManagement 141
10.7 DevelopmentRoadmapPlanners 145
10.8 ProductionandDistribution 148
10.9 Suppliers 149
10.10 MarketingandBrandManagement 150
10.11 Management 152
11 Roles 157
11.1 Roles 157
11.2 TheSystemArchitectRole 158
11.3 SystemArchitectureTeams 162
11.4 SystemArchitectureStakeholders 164
11.5 RecruitingSystemArchitecturePeople 165
11.6 TalentDevelopmentforSystemArchitects 167
12 Processes 173
12.1 TheSystemsArchitectingProcesses 173
12.2 ChangeandConfigurationManagement
Processes 182
12.3 OtherProcessesInvolvingtheSystemArchitect 182
viii CONTENTS
13 Agile Approaches 183
13.1 TheHistoryofIterative-IncrementalandAgile
Development 184
13.2 SystemArchitectsinanAgileEnvironment 186
14 TheFASMethod 189
14.1 Motivation 190
14.2 FunctionalArchitecturesforSystems 192
14.3 TheFASMethod 195
14.4 FASHeuristics 199
14.5 FASwithSysML 202
14.6 ModelingToolSupport 210
14.7 MappingofaFunctionalArchitecturetoaPhysical
Architecture 215
14.8 ExperienceswiththeFASMethod 218
14.9 FASWorkshops 219
14.10 NonfunctionalRequirementsandtheFunctional
Architecture 222
14.11 CompletenessoftheFunctionalArchitecture 224
14.12 FunctionalArchitecturesandtheZigzagPattern 227
15 ProductLines & Variants 231
15.1 DefinitionsVariantModeling 232
15.2 VariantModelingwithSysML 233
15.3 OtherVariantModelingTechniques 239
16 ArchitectureFrameworks 243
16.1 EnterpriseArchitectures 244
16.2 SystemofSystems(SoS) 246
16.3 AnOverviewofArchitectureFrameworks 249
16.4 TheUPDMStandard 261
16.5 WhattodowhenweComeinTouchwithArchitecture
Frameworks 262
16.6 Conclusion 263