Front Cover 1
Real-Time UML Workshop for Embedded Systems 4
Copyright 5
Dedication 6
Contents 8
Preface 14
Acknowledgements 18
About the Author 20
Chapter 1 - Introduction to UML 22
1.1 UML Basic Modeling Concepts 22
1.2 Structural Elements and Diagrams 25
1.3 Behavioral Elements and Diagrams 39
1.4 Use Case and Requirements Models 49
Chapter 2 - The Harmony Process 54
2.1 Introduction 54
2.2 The Harmony Development Process 55
2.3 The Systems Engineering Harmony Workflows in Detail 65
2.4 The Hand-off from Systems Engineering 67
2.5 The Software Workflows in Detail 71
Chapter 3 - Meeting Industry Standards 88
3.1 Overview 88
3.2 On the Importance of Being Standard 88
3.3 Architectural Framework Standards (I’m looking at you UPDM) 89
3.4 IEC 61508 93
3.5 DO-178B/C 97
3.6 IEC 62304 105
3.7 CMMI-DEV 105
References 109
Chapter 4 - Specifying Requirements 110
4.1 Overview 110
4.2 Representing Requirements in UML and SysML 111
4.3 Specification View: State Machines for Requirements Capture 122
References 130
Chapter 5 - Systems Architecture: Deployment and Subsystems Architecture 132
5.1 Overview 132
5.2 The Hand-off from Systems to Downstream Engineering 157
5.3 Looking Ahead 167
Chapter 6 - Dependability Architecture 170
6.1 Overview 170
6.2 A (Not-So) Quick Note about Design Patterns5 173
6.3 What is a Design Pattern? 176
Chapter 7 - High-Fidelity Modeling1 201
7.1 Overview 200
7.2 A Quick Note about Structured Design with UML 201
7.3 High-Fidelity Modeling Workflow 202
7.4 Key Strategies for Object Identification 203
Chapter 8 - Distribution Architecture 240
8.1 Overview 240
Chapter 9 - Concurrency and Resource Architecture 246
9.1 What is the Concurrency and Resource Architecture? 246
9.2 Harmony Concurrency and Resource Architecture Workflow 255
Chapter 10 - Collaboration and Detailed Design 264
10.1 Overview 264
10.2 Collaboration Design 265
10.3 Detailed Design 272
Chapter 11 - Specifying Requirements: Answers 298
11.1 Answer 4.1: Identifying Kinds of Requirements 298
11.2 Answer 4.2: Identifying Use Cases for the Roadrunner Traffic Light Control System 298
11.3 Answer 4.3: Mapping Requirements to Use Cases 301
11.4 Answer 4.4: Identifying Use Cases for the Coyote UAV System 302
11.5 Answer 4.5: Create a Requirements Table 304
11.6 Answer 4.6: Capturing Quality of Service Requirements 304
11.7 Answer 4.7: Operational View: Identifying Traffic Light Scenarios 305
11.8 Answer 4.8: Operational View: Coyote UAV Optical Surveillance Scenarios 312
11.9 Answer 4.9: Specification View: Use Case Descriptions 315
11.10 Answer 4.10: Simple State Machine Specification 316
11.11 Answer 4.11: Specification View: Capturing Complex Requirements 317
11.12 Answer 4.12: Operational to Specification View: Capturing Operational Contracts 326
References 333
Chapter 12 - Deployment and Subsystems Architecture: Answers 334
12.1 Answer 5.1: Organizing the Systems Model 334
12.2 Answer 5.2: Subsystem Identification 337
12.3 Answer 5.3: Mapping Operational Contracts into the Subsystem Architecture 344
12.4 Answer 5.4: Identifying Subsystem Use Cases 352
12.5 Answer 5.5: Creating the Shared Model 358
12.6 Answer 5.6: Initiating the Subsystem Model 361
Chapter 13 - Dependability Architecture: Answers 370
13.1 Answer 6.1: Safety Architecture 370
13.2 Answer 6.2: Reliability Architecture 381
13.3 Answer 6.3: Security Architecture 382
Chapter 14 - High-Fidelity Modeling: Answers 390
14.1 Answer 7.1: Apply Nouns and Causal Agents Strategies 390
14.2 Answer 7.2: Apply Services and Messages Strategies 403
14.3 Answer 7.3: Apply the Strategies with a Test-Driven Development Approach 406
Chapter 15 - Distribution Architecture: Answers 432
15.1 Answer 8.1: Roadrunner Distribution Architecture 432
15.2 Answer 8.2: Coyote UAV Distribution Architecture 432
Chapter 16 - Concurrency and Resource Architecture: Answers 440
16.1 Answer 9.1: Roadrunner Concurrency and Resource Architecture 440
16.2 Answer 9.2: Reconnaissance Concurrency and Resource Architecture 440
Chapter 17 - Collaboration and Detailed Design: Answers 444
17.1 Answer 10.1: Applying Collaboration Design Patterns: Part 1 444
17.2 Answer 10.2: Applying Collaboration Design Patterns: Part 2 445
17.3 Answer 10.3: Applying Detailed Design State Behavioral Patterns 450
17.4 Answer 10.4: Applying Detailed Design Idioms 455
Appendix A - The Roadrunner™ Intersection Controller System Specification 464
Overview 464
The Intersection Controller 464
Front Panel Display 472
Remote Communications 475
Power 475
Appendix B - The Coyote Unmanned Aerial Vehicle System (CUAVS) 476
Overview 476
Primary CUAV System Components 476
Detailed Requirements 479
Appendix C - UML Notational Summary 488
Index 512