Real Time UML Workshop for Embedded Systems (eBook)

Bruce Powel Douglass (Autor)

eBook Download: PDF

2011 | 1. Auflage
432 Seiten
Elsevier Science (Verlag)
978-0-08-049223-0 (ISBN)

Infos

This practical new book provides much-needed, practical, hands-on experience capturing analysis and design in UML. It holds the hands of engineers making the difficult leap from developing in C to the higher-level and more robust Unified Modeling Language, thereby supporting professional development for engineers looking to broaden their skill-sets in order to become more saleable in the job market.

It provides a laboratory environment through a series of progressively more complex exercises that act as building blocks, illustrating the various aspects of UML and its application to real-time and embedded systems. With its focus on gaining proficiency, it goes a significant step beyond basic UML overviews, providing both comprehensive methodology and the best level of supporting exercises available on the market. Each exercise has a matching solution which is thoroughly explained step-by-step in the back of the book. The techniques used to solve these problems come from the author's decades of experience designing and constructing real-time systems. After the exercises have been successfully completed, the book will act as a desk reference for engineers, reminding them of how many of the problems they face in their designs can be solved.

*Tutorial style text with keen focus on in-depth presentation and solution of real-world example problems

*Highly popular, respected and experienced author

*CD includes test version of the popular Rhapsody tool, allowing engineers to capture and work out the exercises in the book

Inhalt

Front Cover 1
Real-Time UML Workshop for Embedded Systems 4
Copyright Page 5
Contents 8
Preface 14
Audience 15
Goals 16
Where to Go After the Book 16
Evaluate UML on ARM 16
Acknowledgments 18
About the Author 20
What’s on the CD-ROM? 22
Chapter 1. Introduction 24
Basic Modeling Concepts of the UML 24
Structural Elements and Diagrams 28
Behavioral Elements and Diagrams 42
Use Case and Requirements Models 54
Summary 56
Check Out the CD-ROM 56
Chapter 2. The Harmony Process 58
Introduction 58
The Harmony Development Process 59
Summary 86
Chapter 3. Specifying Requirements 88
Overview 88
Problem 3.1 Identifying Kinds of Requirements for Roadrunner Traffic Light Control System 90
Problem 3.2 Identifying Use Cases for the Roadrunner Traffic Light Control System 92
Problem 3.3 Mapping Requirements to Use Cases 92
Problem 3.4 Identifying Use Cases for the Coyote UAV System 93
Problem 3.5 Identifying Parametric Requirements 93
Problem 3.6 Capturing Quality of Service Requirements in Use Cases 94
Problem 3.7 Operational View: Identifying Traffic Light Scenarios 94
Problem 3.8 Operational View: CUAVS Optical Surveillance Scenarios 96
Problem 3.9 Specification View: Use-Case Description 96
Specification View: State Machines for Requirements Capture 97
Problem 3.10 Specification View: Capturing Complex Requirements 99
Problem 3.11 Operational to Specification View: Capturing Operational Contracts 100
References 105
Chapter 4. Systems Architecture 106
Overview 106
Problem 4.1 Organizing the Systems Model 108
Problem 4.2 Subsystem Identification 113
Problem 4.3 Mapping Operational Contracts into Subsystem Architecture 115
Problem 4.4 Identifying Subsystem Use Cases 124
Looking Ahead 130
Chapter 5. Object Analysis 132
Overview 132
Key Strategies for Object Identification 134
Problem 5.1 Apply Nouns and Causal Agents Strategies 139
Problem 5.2 Apply Services and Messages Strategies 148
Problem 5.3 Apply Real-World Items and Physical Devices Strategies 150
Problem 5.4 Apply Key Concepts and Transaction Strategies 151
Problem 5.5 Apply Identify Visual Elements and Scenarios Strategies 151
Problem 5.6 Merge Models from the Various Strategies 160
Looking Ahead 162
Chapter 6. Architectural Design 164
Overview 164
Problem 6.1 Concurrency and Resource Architecture 170
Problem 6.2 Distribution Architecture 181
Problem 6.3 Safety and Reliability Architecture 186
Looking Ahead 200
Chapter 7. Mechanistic and Detailed Design 202
Overview 202
Mechanistic Design 203
Detailed Design 210
Problem 7.1 Applying Mechanistic Design Patterns—Part 1 215
Problem 7.2 Applying Mechanistic Design Patterns—Part 2 219
Problem 7.3 Applying Detailed-Design State Behavior Patterns 224
Problem 7.4 Applying Detailed Design Idioms 229
Summary 237
Chapter 8. Specifying Requirements: Answers 238
Answer 3.1 Identifying Kinds of Requirements 238
Answer 3.2 Identifying Use Cases for Roadrunner Traffic Light Control System 239
Answer 3.3 Mapping Requirements to Use Cases 242
Answer 3.4 Identifying Use Cases for Coyote UAV System 243
Answer 3.5 Identifying Parametric Requirements 245
Answer 3.6 Capturing Quality of Service Requirements 246
Answer 3.7 Operational View: Identifying Traffic Light Scenarios 247
Answer 3.8 Operational View: CUAVS Optical Surveillance Scenarios 251
Answer 3.9 Specification View: Use-Case Descriptions 254
Answer 3.10 Specification View: Capturing Complex Requirements 255
Answer 3.11 Operational to Specification View: Capturing Operational Contracts 261
References 265
Chapter 9. Systems Architecture: Answers 266
Answer 4.1 Organizing the Systems Model 266
Answer 4.2 Subsystem Identification 273
Answer 4.3 Mapping Operational Contracts into the Subsystem Architecture 279
Answer 4.4 Identifying Subsystem Use Cases 290
Chapter 10. Object Analysis: Answers 296
Answer 5.1 Apply Nouns and Causal Agents Strategies 296
Answer 5.2 Apply Services and Messages Strategies 314
Answer 5.3 Applying the Real-World Items and Physical Devices Strategies 320
Answer 5.4 Apply Key Concepts and Transaction Strategies 322
Answer 5.5 Identify Visual Elements and Scenarios Strategies 326
Answer 5.6 Merge Models from the Various Strategies 338
Chapter 11. Architectural Design: Answers 340
Answer 6.1 Concurrency and Resource Architecture 340
Answer 6.2 Distribution Architecture 342
Answer 6.3 Safety and Reliability Architecture 346
Chapter 12. Mechanistic and Detailed Design: Answers 362
Answer 7.1 Applying Mechanistic Design Patterns—Part 1 362
Answer 7.2 Applying Mechanistic Design Patterns—Part 2 364
Answer 7.3 Applying Detailed-Design State Behavior Patterns 369
Answer 7.4 Applying Detailed-Design Idioms 374
Appendix A: The Roadrunner Intersection Controller System Specification 380
Overview 380
The Intersection Controller (IC) 380
Appendix B: The Coyote Unmanned Air Vehicle System (CUAVS) Specification 394
Overview 394
Primary CUAV System Components 394
Detailed Requirements 396
The Coyote Mission Planning and Control System (CMPCS) 397
The Coyote Reconnaissance Sensor Suite Payload (CSSP) 398
The Coyote Hellfire Attack Payload (CHAP) 399
The Coyote Datalink Subsystem (CDS) 400
Appendix C: UML Notational Summary 402
Index 424

Produkt-Details

• Erscheint lt. Verlag: 1.4.2011
• Sprache: englisch
• Themenwelt: Informatik ► Software Entwicklung ► Objektorientierung
• Themenwelt: Technik ► Elektrotechnik / Energietechnik
• Themenwelt: Wirtschaft ► Betriebswirtschaft / Management ► Unternehmensführung / Management
• Themenwelt: Wirtschaft ► Volkswirtschaftslehre ► Mikroökonomie
• ISBN-10: 0-08-049223-1 / 0080492231
• ISBN-13: 978-0-08-049223-0 / 9780080492230