Details

Model-Based System Architecture


Model-Based System Architecture


Wiley Series in Systems Engineering and Management 2. Aufl.

von: Tim Weilkiens, Jesko G. Lamm, Stephan Roth, Markus Walker

122,99 €

Verlag: Wiley
Format: EPUB
Veröffentl.: 05.04.2022
ISBN/EAN: 9781119746676
Sprache: englisch
Anzahl Seiten: 464

DRM-geschütztes eBook, Sie benötigen z.B. Adobe Digital Editions und eine Adobe ID zum Lesen.

Beschreibungen

<b>MODEL-BASED SYSTEM ARCHITECTURE</b> <p><b>AN UP-TO-DATE EXPLORATION OF THE NEWEST STANDARDS AND BEST PRACTICES IN SYSTEM ARCHITECTING</b> <p>In the newly revised Second Edition of<i> Model-Based System Architecture,</i> a team of expert engineers deliver a detailed and authoritative review of the practice of system architecture in organizations that use models to support the systems engineering process. In the book, readers will find introductions to the fundamentals of architecting systems and using models to assist the architecting process. <p>The latest edition offers refreshed content based on ISO 15288:2015 and a renewed focus on the role of the system architect. New chapters on systems-of-systems, and cyber-physical systems, and system architect tools offer guidance to practicing professionals on how to apply the presented concepts in the real-world. <p>In addition to the latest definitions of the architecture governance and evaluation processes described in ISO 42020 and 42030, the book provides: <ul><li>A thorough introduction to the value of systems architecting, definitions of system architecture, and model-based system architecture</li> <li>Comprehensive explorations of model governance, architecture descriptions, patterns, and principles, and the roles of typical architecture stakeholders</li> <li>Practical discussions of Agile approaches to systems architecture, the FAS Method, and architecture frameworks</li> <li>In-depth examinations of systems architecting work and necessary soft skills for systems architects</li> <li>Modeling of system architectures with SysML including a brief overview of SysML v1 and an outlook to SysML v2</li></ul> <p>Perfect for system architects and system engineers, <i>Model-Based System Architecture</i> will also earn a place in the libraries of students and researchers studying functional architectures.
<p>Foreword xv</p> <p>Preface xvii</p> <p>About the Companion Website xxi</p> <p><b>1 Introduction </b><b>1</b></p> <p><b>2 An Example: The Scalable Observation and Rescue System </b><b>5</b></p> <p><b>3 Better Products – The Value of Systems Architecting </b><b>9</b></p> <p>3.1 The Share of Systems Architecting in Making Better Products 9</p> <p>3.2 Benefits that can be Achieved 10</p> <p>3.2.1 Benefit for the Customer 10</p> <p>3.2.2 Benefit for the Organization 12</p> <p>3.3 Benefits that can be Communicated Inside the Organization 14</p> <p>3.4 Beneficial Elements of Systems Architecting 15</p> <p>3.5 Benefits of Model-Based Systems Architecting 16</p> <p><b>4 Systems, Systems of Systems, and Cyber-Physical Systems </b><b>17</b></p> <p>4.1 Definition of “System” 17</p> <p>4.1.1 System Elements 19</p> <p>4.1.2 System Context 20</p> <p>4.1.3 System Characteristics 21</p> <p>4.1.4 Purpose 22</p> <p>4.1.5 System Evolution 23</p> <p>4.2 Definition of “System of Systems” 23</p> <p>4.3 Definition of “Cyber-Physical System” 26</p> <p>4.4 Composition of a “Cyber-Physical System of Systems” 27</p> <p><b>5 Definition of System Architecture </b><b>31</b></p> <p>5.1 What Is Architecture? – Discussion of Some Existing Definitions 31</p> <p>5.2 Relations Between Concepts of “System,” “Architecture,” and “Architecture Description” 33</p> <p>5.3 Definition of “Architecture” 35</p> <p>5.3.1 Interactions 36</p> <p>5.3.2 Principles 37</p> <p>5.3.3 Architecture Decisions 37</p> <p>5.4 Functional and Physical Architecture 37</p> <p>5.5 Taxonomy of Physical Architectures 39</p> <p>5.5.1 Logical Architecture 40</p> <p>5.5.2 Product Architecture 41</p> <p>5.5.3 Base Architecture 41</p> <p>5.6 Architecture Landscape for Systems 41</p> <p>5.6.1 System Architecture 42</p> <p>5.6.2 System Design 43</p> <p>5.6.3 Discipline-Specific Architecture and Design 44</p> <p><b>6 Model-Based Systems Architecting </b><b>45</b></p> <p><b>7 Model Governance </b><b>51</b></p> <p>7.1 Overview 51</p> <p>7.2 Model Governance in Practice 52</p> <p><b>8 Architecture Description </b><b>57</b></p> <p>8.1 Architecture Descriptions for Stakeholders 58</p> <p>8.2 Definition of “Architecture Description” 60</p> <p>8.2.1 Architecture Viewpoints 62</p> <p>8.2.2 Architecture Views 65</p> <p>8.2.3 Architecture Decisions 67</p> <p>8.2.4 Architecture Rationales 69</p> <p>8.3 How to Get Architecture Descriptions? 69</p> <p>8.3.1 Model-Based Vision 69</p> <p>8.3.2 Forms and Templates 71</p> <p><b>9 Architecture Patterns and Principles </b><b>75</b></p> <p>9.1 The SYSMOD Zigzag Pattern 76</p> <p>9.2 The Base Architecture 82</p> <p>9.3 Cohesion and Coupling 85</p> <p>9.4 Separation of Definition, Usage, and Run-Time 87</p> <p>9.5 Separate Stable from Unstable Parts 89</p> <p>9.6 The Ideal System 89</p> <p>9.7 View and Model 90</p> <p>9.8 Diagram Layout 92</p> <p>9.9 System Model Structure 93</p> <p>9.10 System Architecture Principles 95</p> <p>9.11 Heuristics 95</p> <p>9.11.1 Heuristics as a Tool for the System Architect 95</p> <p>9.11.2 Simplify, Simplify, Simplify: Strength and Pitfall 97</p> <p><b>10 Model-Based Requirements Engineering and Use Case Analysis </b><b>99</b></p> <p>10.1 Requirement and Use Case Definitions 99</p> <p>10.2 Model-Based Requirements and Use Case Analysis from the MBSA Viewpoint 102</p> <p>10.2.1 Identify and Define Requirements 103</p> <p>10.2.2 Specify the System Context 104</p> <p>10.2.3 Identify Use Cases 105</p> <p>10.2.4 Describe Use Case Flows 109</p> <p>10.2.5 Model the Domain Knowledge 110</p> <p>10.3 The SAMS Method 112</p> <p>10.3.1 SAMS Method Definitions 113</p> <p>10.3.2 SAMS Method 114</p> <p>10.4 Use Cases 2.0 117</p> <p><b>11 Perspectives, Viewpoints and Views in System Architecture </b><b>119</b></p> <p>11.1 Introduction 119</p> <p>11.2 The Functional Perspective 121</p> <p>11.2.1 SysML Modeling of Functional Blocks 123</p> <p>11.2.2 Architecture Views for the System Architect 124</p> <p>11.2.3 Different Architecture Views for the Stakeholders of Different Functions 124</p> <p>11.3 The Physical Perspective 125</p> <p>11.3.1 Logical Architecture Example 126</p> <p>11.3.2 Product Architecture Example 127</p> <p>11.4 The Behavioral Perspective 130</p> <p>11.5 The Layered Perspective 130</p> <p>11.5.1 The Layered Approach 130</p> <p>11.5.2 The Layered Perspective in Systems Architecting 132</p> <p>11.5.3 Relation to the Domain Knowledge Model 134</p> <p>11.5.4 Architecting the Layers 136</p> <p>11.5.5 SysML Modeling of Layers 136</p> <p>11.6 System Deployment Perspective 142</p> <p>11.7 Other Perspectives 144</p> <p>11.8 Relation to the System Context 146</p> <p>11.8.1 Validity of the System Boundary 146</p> <p>11.8.2 Using the System Context as a Part of the Stakeholder-Specific Views 146</p> <p>11.8.3 Special System Context View for Verification 147</p> <p>11.9 Mapping Different System Elements Across Different Levels 148</p> <p>11.9.1 Functional-to-Physical Perspective Mapping 149</p> <p>11.9.2 Mapping More Perspectives 153</p> <p>11.9.3 Mapping Different Levels 153</p> <p>11.10 Traceability 155</p> <p>11.11 Perspectives and Architecture Views in Model-based Systems Architecting 155</p> <p>11.11.1 Creating Different Architecture Views in a Model-Based Approach 155</p> <p>11.11.2 Using SysML for Working with Different Perspectives and Architecture Views 157</p> <p>11.11.3 The Importance of Architecture Viewpoints in Model-Based Systems Architecting 159</p> <p><b>12 Typical Architecture Stakeholders </b><b>161</b></p> <p>12.1 Overview 161</p> <p>12.2 Requirements Engineering 162</p> <p>12.3 Verification 163</p> <p>12.4 Configuration Management 166</p> <p>12.5 Engineering and Information Technology Disciplines 167</p> <p>12.6 Project and Product Management 171</p> <p>12.7 Risk Managers 174</p> <p>12.8 Development Roadmap Planners 174</p> <p>12.9 Production and Distribution 177</p> <p>12.10 Suppliers 178</p> <p>12.11 Marketing and Brand Management 178</p> <p>12.12 Management 180</p> <p><b>13 Roles </b><b>185</b></p> <p>13.1 Roles 185</p> <p>13.2 The System Architect Role 186</p> <p>13.2.1 Objective 186</p> <p>13.2.2 Responsibilities 186</p> <p>13.2.3 Tasks 187</p> <p>13.2.4 Competences 188</p> <p>13.2.5 Required Skills of a System Architect 188</p> <p>13.2.6 Required Skills for Model-Based Systems Architecting 190</p> <p>13.3 System Architecture Teams 190</p> <p>13.4 System Architecture Stakeholders 192</p> <p>13.5 Recruiting System Architecture People 192</p> <p>13.6 Talent Development for System Architects 194</p> <p><b>14 Processes </b><b>199</b></p> <p>14.1 Systems Architecting Processes 199</p> <p>14.1.1 Overview 199</p> <p>14.1.2 Example of Generic Process Steps 201</p> <p>14.1.3 Example of Concrete Process Steps 202</p> <p>14.1.4 Validation, Review, and Approval in a Model-Based Environment 203</p> <p>14.2 Design Definition Process 207</p> <p>14.3 Change and Configuration Management Processes 207</p> <p>14.4 Other Processes Involving the System Architect 207</p> <p><b>15 Tools for the Architect </b><b>209</b></p> <p><b>16 Agile Approaches </b><b>213</b></p> <p>16.1 The History of Iterative–Incremental Approaches 214</p> <p>16.1.1 Project Mercury (NASA, 1958) 214</p> <p>16.1.2 The New New Product Development Game (1986) 215</p> <p>16.1.3 Boehm’s Spiral Model (1988) 216</p> <p>16.1.4 Lean (1945 Onwards) 217</p> <p>16.1.5 Dynamic Systems Development Method (DSDM, 1994) 219</p> <p>16.1.6 Scrum (1995) 220</p> <p>16.2 The Manifesto for Agile Software Development (2001) 221</p> <p>16.3 Agile Principles in Systems Engineering 223</p> <p>16.3.1 Facilitate Face-to-Face Communication 223</p> <p>16.3.2 Create a State of Confidence 224</p> <p>16.3.3 Build Transdisciplinary and Self-Organized Teams 225</p> <p>16.3.4 Create a Learning Organization 225</p> <p>16.3.5 Design, but No Big Design (Up-Front) 226</p> <p>16.3.6 Reduce Dependencies 227</p> <p>16.3.7 Foster a Positive Error Culture 228</p> <p>16.4 Scaling Agile 228</p> <p>16.5 System Architects in an Agile Environment 230</p> <p><b>17 The FAS Method </b><b>233</b></p> <p>17.1 Motivation 234</p> <p>17.2 Functional Architectures for Systems 236</p> <p>17.3 How the FAS Method Works 239</p> <p>17.4 FAS Heuristics 242</p> <p>17.5 FAS with SysML 244</p> <p>17.5.1 Identifying Functional Groups 244</p> <p>17.5.2 Modeling the Function Structure 246</p> <p>17.5.3 Modeling the Functional Architecture 249</p> <p>17.6 SysML Modeling Tool Support 250</p> <p>17.6.1 Create Initial Functional Groups 251</p> <p>17.6.2 Changing and Adding Functional Groups 254</p> <p>17.6.3 Creating Functional Blocks and their Interfaces 254</p> <p>17.7 Mapping of a Functional Architecture to a Physical Architecture 254</p> <p>17.8 Experiences with the FAS Method 256</p> <p>17.9 FAS Workshops 258</p> <p>17.10 Quality Requirements and the Functional Architecture 259</p> <p>17.11 Functional Architectures and the Zigzag Pattern 262</p> <p>17.12 CPS-FAS for Cyber-physical Systems 263</p> <p><b>18 Product Lines and Variants </b><b>269</b></p> <p>18.1 Definitions Variant Modeling 270</p> <p>18.2 Variant Modeling with SysML 271</p> <p>18.3 Other Variant Modeling Techniques 276</p> <p><b>19 Architecture Frameworks </b><b>279</b></p> <p>19.1 Enterprise Architectures 280</p> <p>19.2 Characteristics of System of Systems (SoS) 282</p> <p>19.2.1 Emergence 283</p> <p>19.3 An Overview of Architecture Frameworks 285</p> <p>19.3.1 Zachman FrameworkTM 285</p> <p>19.3.2 The TOGAF® Standard 286</p> <p>19.3.3 Federal Enterprise Architecture Framework (FEAF) 288</p> <p>19.3.4 Department of Defense Architecture Framework (DoDAF) 289</p> <p>19.3.5 Ministry of Defense Architecture Framework (MODAF) 290</p> <p>19.3.6 NATO Architecture Framework (NAF) 291</p> <p>19.3.7 TRAK 292</p> <p>19.3.8 European Space Agency Architectural Framework (ESA-AF) 293</p> <p>19.3.9 OMG Unified Architecture Framework® (UAF®) 295</p> <p>19.4 System Architecture Framework (SAF) 296</p> <p>Together with Michael Leute 296</p> <p>19.4.1 SAF and Enterprise Frameworks 296</p> <p>19.4.2 SAF Ontology 298</p> <p>19.5 What to Do When We Come in Touch With Architecture Frameworks 298</p> <p><b>20 Cross-cutting Concerns </b><b>301</b></p> <p>20.1 The Game-Winning Nonfunctional Aspects 301</p> <p>20.2 Human System Interaction and Human Factors Engineering 303</p> <p>20.3 Risk Management 304</p> <p>20.4 Trade Studies 305</p> <p>20.5 Budgets 306</p> <p><b>21 Architecture Assessment </b><b>307</b></p> <p><b>22 Making It Work in the Organization </b><b>313</b></p> <p>22.1 Overview 313</p> <p>22.2 Organizational Structure for Systems Architecting 314</p> <p>22.3 Recipes from the Authors’ Experience 318</p> <p>22.3.1 Be Humble 319</p> <p>22.3.2 Appraise the Stakeholders 319</p> <p>22.3.3 Care About Organizational Interfaces 319</p> <p>22.3.4 Show that it Was Always There 321</p> <p>22.3.5 Lead by Good Example 321</p> <p>22.3.6 Collect Success Stories and Share them When Appropriate 322</p> <p>22.3.7 Acknowledge that Infections Beat Dictated Rollout 323</p> <p>22.3.8 Assign the System Architect Role to Yourself 324</p> <p>22.3.9 Be a Leader 324</p> <p><b>23 Soft Skills </b><b>327</b></p> <p>23.1 It’s All About Communication 328</p> <p>23.1.1 Losses in Communication 329</p> <p>23.1.2 The Anatomy of a Message 330</p> <p>23.1.3 Factors Influencing Communication 333</p> <p>23.1.3.1 The Language 333</p> <p>23.1.3.2 The Media Used 333</p> <p>23.1.3.3 Spatial Distance 333</p> <p>23.1.3.4 Various Connotations of Words 335</p> <p>23.1.4 The Usage of Communication Aids and Tools 335</p> <p>23.2 Personality Types 338</p> <p>23.2.1 Psychological Types by C. G. Jung 338</p> <p>23.2.2 The 4MAT System by Bernice McCarthy 340</p> <p>23.3 Team Dynamics 341</p> <p>23.4 Diversity and Psychological Safety 342</p> <p>23.4.1 Project Aristotle (Google) 342</p> <p>23.4.2 Elements of Psychological Safety 343</p> <p>23.5 Intercultural Collaboration Skills 344</p> <p><b>24 Outlook: The World After Artificial Intelligence </b><b>347</b></p> <p><b>Appendix A OMG Systems Modeling Language </b><b>349</b></p> <p>A.1 Architecture of the Language 350</p> <p>A.2 Diagram and Model 352</p> <p>A.3 Structure Diagrams 353</p> <p>A.3.1 Block Definition Diagram 354</p> <p>A.3.2 Internal Block Diagram 357</p> <p>A.3.3 Parametric Diagram 361</p> <p>A.3.4 Package Diagram 362</p> <p>A.4 Behavior Diagrams 363</p> <p>A.4.1 Use Case Diagram 364</p> <p>A.4.2 Activity Diagram 366</p> <p>A.4.3 State Machine Diagram 369</p> <p>A.4.4 Sequence Diagram 371</p> <p>A.5 Requirements Diagram 372</p> <p>A.6 Extension of SysML with Profiles 374</p> <p>A.7 Next-Generation Modeling Language SysML v2 376</p> <p><b>Appendix B The V-Model </b><b>381</b></p> <p>B.1 A Brief History of the V-Model or the Systems Engineering Vee 381</p> <p>B.2 A Handy Illustration but No Comprehensive Process Description 383</p> <p>B.3 Critical Considerations 385</p> <p>B.3.1 The V-Model as Process Description 386</p> <p>B.3.2 The V-Model Does Not Impose a Waterfall Process 386</p> <p>B.3.3 The V-Model Accommodates Iterations 387</p> <p>B.3.4 The V-Model Permits Incremental Development 387</p> <p>B.3.5 The V-Model and Concurrent Engineering 388</p> <p>B.3.6 The V-Model Accommodates Change 388</p> <p>B.3.7 The V-Model Permits Early Verification Planning 388</p> <p>B.3.8 The V-Model Shows Where to Prevent Dissatisfaction 388</p> <p>B.4 Reading Instruction for a Modern Systems Engineering Vee 389</p> <p>B.4.1 The Vertical Dimension 389</p> <p>B.4.2 The Horizontal Dimension 389</p> <p>B.4.3 The Left Side 389</p> <p>B.4.4 The Right Side 390</p> <p>B.4.5 The Levels 390</p> <p>B.4.6 Life Cycle Processes 390</p> <p>B.4.7 The Third Dimension 390</p> <p><b>Appendix C Glossary </b><b>391</b></p> <p>C.1 Heritage of the Term “Glossary” 391</p> <p>C.2 Terms with Specific Meaning 393</p> <p>References 399</p> <p>Index 417</p>
<p><b>TIM WEILKIENS </b>is Executive Board Member of Oose, a German engineering consultancy, and a co-author of the SysML specification.</p> <p><B>JESKO G. LAMM</b> is a Senior Systems Engineer in the European hearing healthcare industry. <p><b>STEPHAN ROTH</b> is a coach, consultant, and trainer for systems and software engineering at oose. He is a certified systems engineer (GfSE)<sup>®</sup>- Level C. <p><B>MARKUS WALKER</b> is Elevator System Architect in the CTO Division at Schindler Elevator. He is an INCOSE Certified Systems Engineering Professional (CSEP).
<p><b>AN UP-TO-DATE EXPLORATION OF THE NEWEST STANDARDS AND BEST PRACTICES IN SYSTEM ARCHITECTING</b></p> <p>In the newly revised Second Edition of<i> Model-Based System Architecture,</i> a team of expert engineers deliver a detailed and authoritative review of the practice of system architecture in organizations that use models to support the systems engineering process. In the book, readers will find introductions to the fundamentals of architecting systems and using models to assist the architecting process. <p>The latest edition offers refreshed content based on ISO 15288:2015 and a renewed focus on the role of the system architect. New chapters on systems-of-systems, and cyber-physical systems, and system architect tools offer guidance to practicing professionals on how to apply the presented concepts in the real-world. <p>In addition to the latest definitions of the architecture governance and evaluation processes described in ISO 42020 and 42030, the book provides: <ul><li>A thorough introduction to the value of systems architecting, definitions of system architecture, and model-based system architecture</li> <li>Comprehensive explorations of model governance, architecture descriptions, patterns, and principles, and the roles of typical architecture stakeholders</li> <li>Practical discussions of Agile approaches to systems architecture, the FAS Method, and architecture frameworks</li> <li>In-depth examinations of systems architecting work and necessary soft skills for systems architects</li> <li>Modeling of system architectures with SysML including a brief overview of SysML v1 and an outlook to SysML v2</li></ul> <p>Perfect for system architects and system engineers, <i>Model-Based System Architecture</i> will also earn a place in the libraries of students and researchers studying functional architectures.

Diese Produkte könnten Sie auch interessieren:

From Photon to Pixel
From Photon to Pixel
von: Henri Maître
PDF ebook
139,99 €
Computer Vision in Vehicle Technology
Computer Vision in Vehicle Technology
von: Antonio M. López, Atsushi Imiya, Tomas Pajdla, Jose M. Álvarez
PDF ebook
81,99 €
Foundations of Electromagnetic Compatibility
Foundations of Electromagnetic Compatibility
von: Bogdan Adamczyk
PDF ebook
117,99 €