Hugendubel.info - Die B2B Online-Buchhandlung 

Merkliste
Die Merkliste ist leer.
Bitte warten - die Druckansicht der Seite wird vorbereitet.
Der Druckdialog öffnet sich, sobald die Seite vollständig geladen wurde.
Sollte die Druckvorschau unvollständig sein, bitte schliessen und "Erneut drucken" wählen.
Wileyerschienen am01.07.2022
MODEL-BASED SYSTEM ARCHITECTURE
AN UP-TO-DATE EXPLORATION OF THE NEWEST STANDARDS AND BEST PRACTICES IN SYSTEM ARCHITECTING
In the newly revised Second Edition of Model-Based System Architecture, 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.
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.
In addition to the latest definitions of the architecture governance and evaluation processes described in ISO 42020 and 42030, the book provides: A thorough introduction to the value of systems architecting, definitions of system architecture, and model-based system architecture
Comprehensive explorations of model governance, architecture descriptions, patterns, and principles, and the roles of typical architecture stakeholders
Practical discussions of Agile approaches to systems architecture, the FAS Method, and architecture frameworks
In-depth examinations of systems architecting work and necessary soft skills for systems architects
Modeling of system architectures with SysML including a brief overview of SysML v1 and an outlook to SysML v2

Perfect for system architects and system engineers, Model-Based System Architecture will also earn a place in the libraries of students and researchers studying functional architectures.


TIM WEILKIENS is Executive Board Member of Oose, a German engineering consultancy, and a co-author of the SysML specification.

JESKO G. LAMM is a Senior Systems Engineer in the European hearing healthcare industry.
STEPHAN ROTH is a coach, consultant, and trainer for systems and software engineering at oose. He is a certified systems engineer (GfSE)®- Level C.
MARKUS WALKER is Elevator System Architect in the CTO Division at Schindler Elevator. He is an INCOSE Certified Systems Engineering Professional (CSEP).mehr
Verfügbare Formate
BuchGebunden
EUR153,50
E-BookPDF2 - DRM Adobe / Adobe Ebook ReaderE-Book
EUR122,99
E-BookEPUB2 - DRM Adobe / EPUBE-Book
EUR122,99
E-BookEPUB2 - DRM Adobe / EPUBE-Book
EUR122,99
E-BookPDF2 - DRM Adobe / Adobe Ebook ReaderE-Book
EUR122,99

Produkt

KlappentextMODEL-BASED SYSTEM ARCHITECTURE
AN UP-TO-DATE EXPLORATION OF THE NEWEST STANDARDS AND BEST PRACTICES IN SYSTEM ARCHITECTING
In the newly revised Second Edition of Model-Based System Architecture, 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.
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.
In addition to the latest definitions of the architecture governance and evaluation processes described in ISO 42020 and 42030, the book provides: A thorough introduction to the value of systems architecting, definitions of system architecture, and model-based system architecture
Comprehensive explorations of model governance, architecture descriptions, patterns, and principles, and the roles of typical architecture stakeholders
Practical discussions of Agile approaches to systems architecture, the FAS Method, and architecture frameworks
In-depth examinations of systems architecting work and necessary soft skills for systems architects
Modeling of system architectures with SysML including a brief overview of SysML v1 and an outlook to SysML v2

Perfect for system architects and system engineers, Model-Based System Architecture will also earn a place in the libraries of students and researchers studying functional architectures.


TIM WEILKIENS is Executive Board Member of Oose, a German engineering consultancy, and a co-author of the SysML specification.

JESKO G. LAMM is a Senior Systems Engineer in the European hearing healthcare industry.
STEPHAN ROTH is a coach, consultant, and trainer for systems and software engineering at oose. He is a certified systems engineer (GfSE)®- Level C.
MARKUS WALKER is Elevator System Architect in the CTO Division at Schindler Elevator. He is an INCOSE Certified Systems Engineering Professional (CSEP).
Details
Weitere ISBN/GTIN9781119746669
ProduktartE-Book
EinbandartE-Book
FormatPDF
Verlag
Erscheinungsjahr2022
Erscheinungsdatum01.07.2022
Seiten467 Seiten
SpracheEnglisch
Dateigrösse23293
Artikel-Nr.9112584
Rubriken
Genre9201

Inhalt/Kritik

Inhaltsverzeichnis
1;Cover;1
2;Title Page;5
3;Copyright;6
4;Contents;7
5;Foreword;17
6;Preface;19
7;About the Companion Website;23
8;Chapter 1 Introduction;25
9;Chapter 2 An Example: The Scalable Observation and Rescue System;29
10;Chapter 3 Better Products?-?The Value of Systems Architecting;33
10.1;3.1 The Share of Systems Architecting in Making Better Products;33
10.2;3.2 Benefits that can be Achieved;34
10.2.1;3.2.1 Benefit for the Customer;34
10.2.2;3.2.2 Benefit for the Organization;36
10.3;3.3 Benefits that can be Communicated Inside the Organization;38
10.4;3.4 Beneficial Elements of Systems Architecting;39
10.5;3.5 Benefits of Model?Based Systems Architecting;40
11;Chapter 4 Systems, Systems of Systems, and Cyber?Physical Systems*;41
11.1;4.1 Definition of System ;41
11.1.1;4.1.1 System Elements;43
11.1.2;4.1.2 System Context;44
11.1.3;4.1.3 System Characteristics;45
11.1.4;4.1.4 Purpose;46
11.1.5;4.1.5 System Evolution;47
11.2;4.2 Definition of System of Systems ;47
11.3;4.3 Definition of Cyber?Physical System ;50
11.4;4.4 Composition of a Cyber?Physical System of Systems ;51
12;Chapter 5 Definition of System Architecture;55
12.1;5.1 What Is Architecture??-?Discussion of Some Existing Definitions;55
12.2;5.2 Relations Between Concepts of System, Architecture, and Architecture Description ;57
12.3;5.3 Definition of Architecture ;59
12.3.1;5.3.1 Interactions;60
12.3.2;5.3.2 Principles;61
12.3.3;5.3.3 Architecture Decisions;61
12.4;5.4 Functional and Physical Architecture;61
12.5;5.5 Taxonomy of Physical Architectures;63
12.5.1;5.5.1 Logical Architecture;64
12.5.2;5.5.2 Product Architecture;65
12.5.3;5.5.3 Base Architecture;65
12.6;5.6 Architecture Landscape for Systems;65
12.6.1;5.6.1 System Architecture;66
12.6.2;5.6.2 System Design;67
12.6.3;5.6.3 Discipline?Specific Architecture and Design;68
13;Chapter 6 Model?Based Systems Architecting;69
14;Chapter 7 Model Governance;75
14.1;7.1 Overview;75
14.2;7.2 Model Governance in Practice;76
15;Chapter 8 Architecture Description;81
15.1;8.1 Architecture Descriptions for Stakeholders;82
15.2;8.2 Definition of Architecture Description ;84
15.2.1;8.2.1 Architecture Viewpoints;86
15.2.2;8.2.2 Architecture Views;89
15.2.3;8.2.3 Architecture Decisions;91
15.2.4;8.2.4 Architecture Rationales;93
15.3;8.3 How to Get Architecture Descriptions?;93
15.3.1;8.3.1 Model?Based Vision;93
15.3.2;8.3.2 Forms and Templates;95
16;Chapter 9 Architecture Patterns and Principles;99
16.1;9.1 The SYSMOD Zigzag Pattern;100
16.2;9.2 The Base Architecture;106
16.3;9.3 Cohesion and Coupling;109
16.4;9.4 Separation of Definition, Usage, and Run?Time;111
16.5;9.5 Separate Stable from Unstable Parts;113
16.6;9.6 The Ideal System;113
16.7;9.7 View and Model;114
16.8;9.8 Diagram Layout;116
16.9;9.9 System Model Structure;117
16.10;9.10 System Architecture Principles;119
16.11;9.11 Heuristics;119
16.11.1;9.11.1 Heuristics as a Tool for the System Architect;119
16.11.2;9.11.2 Simplify, Simplify, Simplify: Strength and Pitfall;121
17;Chapter 10 Model?Based Requirements Engineering and Use Case Analysis;123
17.1;10.1 Requirement and Use Case Definitions;123
17.2;10.2 Model?Based Requirements and Use Case Analysis from the MBSA Viewpoint;126
17.2.1;10.2.1 Identify and Define Requirements;127
17.2.2;10.2.2 Specify the System Context;128
17.2.3;10.2.3 Identify Use Cases;129
17.2.4;10.2.4 Describe Use Case Flows;133
17.2.5;10.2.5 Model the Domain Knowledge;134
17.3;10.3 The SAMS Method;136
17.3.1;10.3.1 SAMS Method Definitions;137
17.3.2;10.3.2 SAMS Method;138
17.4;10.4 Use Cases 2.0;141
18;Chapter 11 Perspectives, Viewpoints and Views in System Architecture*;143
18.1;11.1 Introduction;143
18.2;11.2 The Functional Perspective;145
18.2.1;11.2.1 SysML Modeling of Functional Blocks;147
18.2.2;11.2.2 Architecture Views for the System Architect;148
18.2.3;11.2.3 Different Architecture Views for the Stakeholders of Different Functions;148
18.3;11.3 The Physical Perspective;149
18.3.1;11.3.1 Logical Architecture Example;150
18.3.2;11.3.2 Product Architecture Example;151
18.4;11.4 The Behavioral Perspective;154
18.5;11.5 The Layered Perspective;154
18.5.1;11.5.1 The Layered Approach;154
18.5.2;11.5.2 The Layered Perspective in Systems Architecting;156
18.5.3;11.5.3 Relation to the Domain Knowledge Model;158
18.5.4;11.5.4 Architecting the Layers;160
18.5.5;11.5.5 SysML Modeling of Layers;160
18.6;11.6 System Deployment Perspective;166
18.7;11.7 Other Perspectives;168
18.8;11.8 Relation to the System Context;170
18.8.1;11.8.1 Validity of the System Boundary;170
18.8.2;11.8.2 Using the System Context as a Part of the Stakeholder?Specific Views;170
18.8.3;11.8.3 Special System Context View for Verification;171
18.9;11.9 Mapping Different System Elements Across Different Levels;172
18.9.1;11.9.1 Functional?to?Physical Perspective Mapping;173
18.9.2;11.9.2 Mapping More Perspectives;177
18.9.3;11.9.3 Mapping Different Levels;177
18.10;11.10 Traceability;179
18.11;11.11 Perspectives and Architecture Views in Model?based Systems Architecting;179
18.11.1;11.11.1 Creating Different Architecture Views in a Model?Based Approach;179
18.11.2;11.11.2 Using SysML for Working with Different Perspectives and Architecture Views;181
18.11.3;11.11.3 The Importance of Architecture Viewpoints in Model?Based Systems Architecting;183
19;Chapter 12 Typical Architecture Stakeholders;185
19.1;12.1 Overview;185
19.2;12.2 Requirements Engineering;186
19.3;12.3 Verification;187
19.4;12.4 Configuration Management;190
19.5;12.5 Engineering and Information Technology Disciplines;191
19.6;12.6 Project and Product Management;195
19.7;12.7 Risk Managers;198
19.8;12.8 Development Roadmap Planners;198
19.9;12.9 Production and Distribution;201
19.10;12.10 Suppliers;202
19.11;12.11 Marketing and Brand Management;202
19.12;12.12 Management;204
20;Chapter 13 Roles;209
20.1;13.1 Roles;209
20.2;13.2 The System Architect Role;210
20.2.1;13.2.1 Objective;210
20.2.2;13.2.2 Responsibilities;210
20.2.3;13.2.3 Tasks;211
20.2.4;13.2.4 Competences;212
20.2.5;13.2.5 Required Skills of a System Architect;212
20.2.6;13.2.6 Required Skills for Model?Based Systems Architecting;214
20.3;13.3 System Architecture Teams;214
20.4;13.4 System Architecture Stakeholders;216
20.5;13.5 Recruiting System Architecture People;216
20.6;13.6 Talent Development for System Architects;218
21;Chapter 14 Processes;223
21.1;14.1 Systems Architecting Processes;223
21.1.1;14.1.1 Overview;223
21.1.2;14.1.2 Example of Generic Process Steps;225
21.1.3;14.1.3 Example of Concrete Process Steps;226
21.1.4;14.1.4 Validation, Review, and Approval in a Model?Based Environment;227
21.2;14.2 Design Definition Process;231
21.3;14.3 Change and Configuration Management Processes;231
21.4;14.4 Other Processes Involving the System Architect;231
22;Chapter 15 Tools for the Architect;233
23;Chapter 16 Agile Approaches;237
23.1;16.1 The History of Iterative-Incremental Approaches;238
23.1.1;16.1.1 Project Mercury (NASA, 1958);238
23.1.2;16.1.2 The New New Product Development Game (1986);239
23.1.3;16.1.3 Boehm's Spiral Model (1988);240
23.1.4;16.1.4 Lean (1945 Onwards);241
23.1.5;16.1.5 Dynamic Systems Development Method (DSDM, 1994);243
23.1.6;16.1.6 Scrum (1995);244
23.2;16.2 The Manifesto for Agile Software Development (2001);245
23.3;16.3 Agile Principles in Systems Engineering;247
23.3.1;16.3.1 Facilitate Face?to?Face Communication;247
23.3.2;16.3.2 Create a State of Confidence;248
23.3.3;16.3.3 Build Transdisciplinary and Self?Organized Teams;249
23.3.4;16.3.4 Create a Learning Organization;249
23.3.5;16.3.5 Design, but No Big Design (Up?Front);250
23.3.6;16.3.6 Reduce Dependencies;251
23.3.7;16.3.7 Foster a Positive Error Culture;252
23.4;16.4 Scaling Agile;252
23.5;16.5 System Architects in an Agile Environment;254
24;Chapter 17 The FAS Method;257
24.1;17.1 Motivation;258
24.2;17.2 Functional Architectures for Systems;260
24.3;17.3 How the FAS Method Works;263
24.4;17.4 FAS Heuristics;266
24.5;17.5 FAS with SysML;268
24.5.1;17.5.1 Identifying Functional Groups;268
24.5.2;17.5.2 Modeling the Function Structure;270
24.5.3;17.5.3 Modeling the Functional Architecture;273
24.6;17.6 SysML Modeling Tool Support;274
24.6.1;17.6.1 Create Initial Functional Groups;275
24.6.2;17.6.2 Changing and Adding Functional Groups;278
24.6.3;17.6.3 Creating Functional Blocks and their Interfaces;278
24.7;17.7 Mapping of a Functional Architecture to a Physical Architecture;278
24.8;17.8 Experiences with the FAS Method;280
24.9;17.9 FAS Workshops;282
24.10;17.10 Quality Requirements and the Functional Architecture;283
24.11;17.11 Functional Architectures and the Zigzag Pattern;286
24.12;17.12 CPS?FAS for Cyber?physical Systems;287
25;Chapter 18 Product Lines and Variants;293
25.1;18.1 Definitions Variant Modeling;294
25.2;18.2 Variant Modeling with SysML;295
25.3;18.3 Other Variant Modeling Techniques;300
26;Chapter 19 Architecture Frameworks;303
26.1;19.1 Enterprise Architectures;304
26.2;19.2 Characteristics of System of Systems (SoS);306
26.2.1;19.2.1 Emergence;307
26.3;19.3 An Overview of Architecture Frameworks;309
26.3.1;19.3.1 Zachman Framework(TM);309
26.3.2;19.3.2 The TOGAF® Standard;310
26.3.3;19.3.3 Federal Enterprise Architecture Framework (FEAF);312
26.3.4;19.3.4 Department of Defense Architecture Framework (DoDAF);313
26.3.5;19.3.5 Ministry of Defense Architecture Framework (MODAF);314
26.3.6;19.3.6 NATO Architecture Framework (NAF);315
26.3.7;19.3.7 TRAK;316
26.3.8;19.3.8 European Space Agency Architectural Framework (ESA?AF);317
26.3.9;19.3.9 OMG Unified Architecture Framework® (UAF®);319
26.4;19.4 System Architecture Framework (SAF);320
26.5;Together with Michael Leute;320
26.5.1;19.4.1 SAF and Enterprise Frameworks;320
26.5.2;19.4.2 SAF Ontology;322
26.6;19.5 What to Do When We Come in Touch With Architecture Frameworks;322
27;Chapter 20 Cross?cutting Concerns;325
27.1;20.1 The Game?Winning Nonfunctional Aspects;325
27.2;20.2 Human System Interaction and Human Factors Engineering;327
27.3;20.3 Risk Management;328
27.4;20.4 Trade Studies;329
27.5;20.5 Budgets;330
28;Chapter 21 Architecture Assessment;331
29;Chapter 22 Making It Work in the Organization;337
29.1;22.1 Overview;337
29.2;22.2 Organizational Structure for Systems Architecting;338
29.3;22.3 Recipes from the Authors' Experience;342
29.3.1;22.3.1 Be Humble;343
29.3.2;22.3.2 Appraise the Stakeholders;343
29.3.3;22.3.3 Care About Organizational Interfaces;343
29.3.4;22.3.4 Show that it Was Always There;345
29.3.5;22.3.5 Lead by Good Example;345
29.3.6;22.3.6 Collect Success Stories and Share them When Appropriate;346
29.3.7;22.3.7 Acknowledge that Infections Beat Dictated Rollout;347
29.3.8;22.3.8 Assign the System Architect Role to Yourself;348
29.3.9;22.3.9 Be a Leader;348
30;Chapter 23 Soft Skills;351
30.1;23.1 It's All About Communication;352
30.1.1;23.1.1 Losses in Communication;353
30.1.2;23.1.2 The Anatomy of a Message;354
30.1.3;23.1.3 Factors Influencing Communication;357
30.1.3.1;23.1.3.1 The Language;357
30.1.3.2;23.1.3.2 The Media Used;357
30.1.3.3;23.1.3.3 Spatial Distance;357
30.1.3.4;23.1.3.4 Various Connotations of Words;359
30.1.4;23.1.4 The Usage of Communication Aids and Tools;359
30.2;23.2 Personality Types;362
30.2.1;23.2.1 Psychological Types by C. G. Jung;362
30.2.2;23.2.2 The 4MAT System by Bernice McCarthy;364
30.3;23.3 Team Dynamics;365
30.4;23.4 Diversity and Psychological Safety;366
30.4.1;23.4.1 Project Aristotle (Google);366
30.4.2;23.4.2 Elements of Psychological Safety;367
30.5;23.5 Intercultural Collaboration Skills;368
31;Chapter 24 Outlook: The World After Artificial Intelligence;371
32;Appendix A OMG Systems Modeling Language;373
32.1;A.1 Architecture of the Language;374
32.2;A.2 Diagram and Model;376
32.3;A.3 Structure Diagrams;377
32.3.1;A.3.1 Block Definition Diagram;378
32.3.2;A.3.2 Internal Block Diagram;381
32.3.3;A.3.3 Parametric Diagram;385
32.3.4;A.3.4 Package Diagram;386
32.4;A.4 Behavior Diagrams;387
32.4.1;A.4.1 Use Case Diagram;388
32.4.2;A.4.2 Activity Diagram;390
32.4.3;A.4.3 State Machine Diagram;393
32.4.4;A.4.4 Sequence Diagram;395
32.5;A.5 Requirements Diagram;396
32.6;A.6 Extension of SysML with Profiles;398
32.7;A.7 Next?Generation Modeling Language SysML v2;400
33;Appendix B The V?Model;405
33.1;B.1 A Brief History of the V?Model or the Systems Engineering Vee;405
33.2;B.2 A Handy Illustration but No Comprehensive Process Description;407
33.3;B.3 Critical Considerations;409
33.3.1;B.3.1 The V?Model as Process Description;410
33.3.2;B.3.2 The V?Model Does Not Impose a Waterfall Process;410
33.3.3;B.3.3 The V?Model Accommodates Iterations;411
33.3.4;B.3.4 The V?Model Permits Incremental Development;411
33.3.5;B.3.5 The V?Model and Concurrent Engineering;412
33.3.6;B.3.6 The V?Model Accommodates Change;412
33.3.7;B.3.7 The V?Model Permits Early Verification Planning;412
33.3.8;B.3.8 The V?Model Shows Where to Prevent Dissatisfaction;412
33.4;B.4 Reading Instruction for a Modern Systems Engineering Vee;413
33.4.1;B.4.1 The Vertical Dimension;413
33.4.2;B.4.2 The Horizontal Dimension;413
33.4.3;B.4.3 The Left Side;413
33.4.4;B.4.4 The Right Side;414
33.4.5;B.4.5 The Levels;414
33.4.6;B.4.6 Life Cycle Processes;414
33.4.7;B.4.7 The Third Dimension;414
34;Appendix C Glossary;415
34.1;C.1 Heritage of the Term Glossary ;415
34.2;C.2 Terms with Specific Meaning;417
35;References;423
36;Index;441
37;EULA;467mehr