Model-Based System Architecture - Jesko G Lamm

. .

Résumé :

Foreword xv

Preface xvii

About the Companion Website xxi

1 Introduction 1

2 An Example: The Scalable Observation and Rescue System 5

3 Better Products - The Value of Systems Architecting 9

3.1 The Share of Systems Architecting in Making Better Products 9

3.2 Benefits that can be Achieved 10

3.2.1 Benefit for the Customer 10

3.2.2 Benefit for the Organization 12

3.3 Benefits that can be Communicated Inside the Organization 14

3.4 Beneficial Elements of Systems Architecting 15

3.5 Benefits of Model-Based Systems Architecting 16

4 Systems, Systems of Systems, and Cyber-Physical Systems 17

4.1 Definition of System 17

4.1.1 System Elements 19

4.1.2 System Context 20

4.1.3 System Characteristics 21

4.1.4 Purpose 22

4.1.5 System Evolution 23

4.2 Definition of System of Systems 23

4.3 Definition of Cyber-Physical System 26

4.4 Composition of a Cyber-Physical System of Systems 27

5 Definition of System Architecture 31

5.1 What Is Architecture? - Discussion of Some Existing Definitions 31

5.2 Relations Between Concepts of System, Architecture, and Architecture Description 33

5.3 Definition of Architecture 35

5.3.1 Interactions 36

5.3.2 Principles 37

5.3.3 Architecture Decisions 37

5.4 Functional and Physical Architecture 37

5.5 Taxonomy of Physical Architectures 39

5.5.1 Logical Architecture 40

5.5.2 Product Architecture 41

5.5.3 Base Architecture 41

5.6 Architecture Landscape for Systems 41

5.6.1 System Architecture 42

5.6.2 System Design 43

5.6.3 Discipline-Specific Architecture and Design 44

6 Model-Based Systems Architecting 45

7 Model Governance 51

7.1 Overview 51

7.2 Model Governance in Practice 52

8 Architecture Description 57

8.1 Architecture Descriptions for Stakeholders 58

8.2 Definition of Architecture Description 60

8.2.1 Architecture Viewpoints 62

8.2.2 Architecture Views 65

8.2.3 Architecture Decisions 67

8.2.4 Architecture Rationales 69

8.3 How to Get Architecture Descriptions? 69

8.3.1 Model-Based Vision 69

8.3.2 Forms and Templates 71

9 Architecture Patterns and Principles 75

9.1 The SYSMOD Zigzag Pattern 76

9.2 The Base Architecture 82

9.3 Cohesion and Coupling 85

9.4 Separation of Definition, Usage, and Run-Time 87

9.5 Separate Stable from Unstable Parts 89

9.6 The Ideal System 89

9.7 View and Model 90

9.8 Diagram Layout 92

9.9 System Model Structure 93

9.10 System Architecture Principles 95

9.11 Heuristics 95

9.11.1 Heuristics as a Tool for the System Architect 95

9.11.2 Simplify, Simplify, Simplify: Strength and Pitfall 97

10 Model-Based Requirements Engineering and Use Case Analysis 99

10.1 Requirement and Use Case Definitions 99

10.2 Model-Based Requirements and Use Case Analysis from the MBSA Viewpoint 102

10.2.1 Identify and Define Requirements 103

10.2.2 Specify the System Context 104

10.2.3 Identify Use Cases 105

10.2.4 Describe Use Case Flows 109

10.2.5 Model the Domain Knowledge 110

10.3 The SAMS Method 112

10.3.1 SAMS Method Definitions 113

10.3.2 SAMS Method 114

10.4 Use Cases 2.0 117

11 Perspectives, Viewpoints and Views in System Architecture 119

11.1 Introduction 119

11.2 The Functional Perspectiv...

Biographie:
.

Sommaire:

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)....