Real Time UML Workshop for Embedded Systems

Real Time UML Workshop for Embedded Systems

by Bruce Powel Douglass
Released April 2011
Publisher(s): Newnes
ISBN: 9780080492230

Read it now on the O’Reilly learning platform with a 10-day free trial.

O’Reilly members get unlimited access to books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.

Start your free trial

Book description

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

Table of contents

  1. Front Cover
  2. Real-Time UML Workshop for Embedded Systems
  3. Copyright Page
  4. Contents (1/2)
  5. Contents (2/2)
  6. Preface
    1. Audience
    2. Goals
    3. Where to Go After the Book
    4. Evaluate UML on ARM
  7. Acknowledgments
  8. About the Author
  9. What’s on the CD-ROM?
  10. Chapter 1. Introduction
    1. Basic Modeling Concepts of the UML
    2. Structural Elements and Diagrams (1/3)
    3. Structural Elements and Diagrams (2/3)
    4. Structural Elements and Diagrams (3/3)
    5. Behavioral Elements and Diagrams (1/3)
    6. Behavioral Elements and Diagrams (2/3)
    7. Behavioral Elements and Diagrams (3/3)
    8. Use Case and Requirements Models
    9. Summary
    10. Check Out the CD-ROM
  11. Chapter 2. The Harmony Process
    1. Introduction
    2. The Harmony Development Process (1/6)
    3. The Harmony Development Process (2/6)
    4. The Harmony Development Process (3/6)
    5. The Harmony Development Process (4/6)
    6. The Harmony Development Process (5/6)
    7. The Harmony Development Process (6/6)
    8. Summary
  12. Chapter 3. Specifying Requirements
    1. Overview
    2. Problem 3.1 Identifying Kinds of Requirements for Roadrunner Traffic Light Control System
    3. Problem 3.2 Identifying Use Cases for the Roadrunner Traffic Light Control System
    4. Problem 3.3 Mapping Requirements to Use Cases
    5. Problem 3.4 Identifying Use Cases for the Coyote UAV System
    6. Problem 3.5 Identifying Parametric Requirements
    7. Problem 3.6 Capturing Quality of Service Requirements in Use Cases
    8. Problem 3.7 Operational View: Identifying Traffic Light Scenarios
    9. Problem 3.8 Operational View: CUAVS Optical Surveillance Scenarios
    10. Problem 3.9 Specification View: Use-Case Description
    11. Specification View: State Machines for Requirements Capture
    12. Problem 3.10 Specification View: Capturing Complex Requirements
    13. Problem 3.11 Operational to Specification View: Capturing Operational Contracts
    14. References
  13. Chapter 4. Systems Architecture
    1. Overview
    2. Problem 4.1 Organizing the Systems Model
    3. Problem 4.2 Subsystem Identification
    4. Problem 4.3 Mapping Operational Contracts into Subsystem Architecture (1/2)
    5. Problem 4.3 Mapping Operational Contracts into Subsystem Architecture (2/2)
    6. Problem 4.4 Identifying Subsystem Use Cases (1/2)
    7. Problem 4.4 Identifying Subsystem Use Cases (2/2)
    8. Looking Ahead
  14. Chapter 5. Object Analysis
    1. Overview
    2. Key Strategies for Object Identification
    3. Problem 5.1 Apply Nouns and Causal Agents Strategies (1/2)
    4. Problem 5.1 Apply Nouns and Causal Agents Strategies (2/2)
    5. Problem 5.2 Apply Services and Messages Strategies
    6. Problem 5.3 Apply Real-World Items and Physical Devices Strategies
    7. Problem 5.4 Apply Key Concepts and Transaction Strategies
    8. Problem 5.5 Apply Identify Visual Elements and Scenarios Strategies
    9. Problem 5.6 Merge Models from the Various Strategies
    10. Looking Ahead
  15. Chapter 6. Architectural Design
    1. Overview
    2. Problem 6.1 Concurrency and Resource Architecture (1/3)
    3. Problem 6.1 Concurrency and Resource Architecture (2/3)
    4. Problem 6.1 Concurrency and Resource Architecture (3/3)
    5. Problem 6.2 Distribution Architecture
    6. Problem 6.3 Safety and Reliability Architecture (1/3)
    7. Problem 6.3 Safety and Reliability Architecture (2/3)
    8. Problem 6.3 Safety and Reliability Architecture (3/3)
    9. Looking Ahead
  16. Chapter 7. Mechanistic and Detailed Design
    1. Overview
    2. Mechanistic Design (1/2)
    3. Mechanistic Design (2/2)
    4. Detailed Design
    5. Problem 7.1 Applying Mechanistic Design Patterns—Part 1
    6. Problem 7.2 Applying Mechanistic Design Patterns—Part 2
    7. Problem 7.3 Applying Detailed-Design State Behavior Patterns
    8. Problem 7.4 Applying Detailed Design Idioms (1/2)
    9. Problem 7.4 Applying Detailed Design Idioms (2/2)
    10. Summary
  17. Chapter 8. Specifying Requirements: Answers
    1. Answer 3.1 Identifying Kinds of Requirements
    2. Answer 3.2 Identifying Use Cases for Roadrunner Traffic Light Control System
    3. Answer 3.3 Mapping Requirements to Use Cases
    4. Answer 3.4 Identifying Use Cases for Coyote UAV System
    5. Answer 3.5 Identifying Parametric Requirements
    6. Answer 3.6 Capturing Quality of Service Requirements
    7. Answer 3.7 Operational View: Identifying Traffic Light Scenarios
    8. Answer 3.8 Operational View: CUAVS Optical Surveillance Scenarios
    9. Answer 3.9 Specification View: Use-Case Descriptions
    10. Answer 3.10 Specification View: Capturing Complex Requirements (1/2)
    11. Answer 3.10 Specification View: Capturing Complex Requirements (2/2)
    12. Answer 3.11 Operational to Specification View: Capturing Operational Contracts
    13. References
  18. Chapter 9. Systems Architecture: Answers
    1. Answer 4.1 Organizing the Systems Model
    2. Answer 4.2 Subsystem Identification (1/2)
    3. Answer 4.2 Subsystem Identification (2/2)
    4. Answer 4.3 Mapping Operational Contracts into the Subsystem Architecture (1/3)
    5. Answer 4.3 Mapping Operational Contracts into the Subsystem Architecture (2/3)
    6. Answer 4.3 Mapping Operational Contracts into the Subsystem Architecture (3/3)
    7. Answer 4.4 Identifying Subsystem Use Cases (1/2)
    8. Answer 4.4 Identifying Subsystem Use Cases (2/2)
  19. Chapter 10. Object Analysis: Answers
    1. Answer 5.1 Apply Nouns and Causal Agents Strategies
    2. Answer 5.2 Apply Services and Messages Strategies (1/2)
    3. Answer 5.2 Apply Services and Messages Strategies (2/2)
    4. Answer 5.3 Applying the Real-World Items and Physical Devices Strategies
    5. Answer 5.4 Apply Key Concepts and Transaction Strategies
    6. Answer 5.5 Identify Visual Elements and Scenarios Strategies (1/3)
    7. Answer 5.5 Identify Visual Elements and Scenarios Strategies (2/3)
    8. Answer 5.5 Identify Visual Elements and Scenarios Strategies (3/3)
    9. Answer 5.6 Merge Models from the Various Strategies
  20. Chapter 11. Architectural Design: Answers
    1. Answer 6.1 Concurrency and Resource Architecture
    2. Answer 6.2 Distribution Architecture
    3. Answer 6.3 Safety and Reliability Architecture (1/4)
    4. Answer 6.3 Safety and Reliability Architecture (2/4)
    5. Answer 6.3 Safety and Reliability Architecture (3/4)
    6. Answer 6.3 Safety and Reliability Architecture (4/4)
  21. Chapter 12. Mechanistic and Detailed Design: Answers
    1. Answer 7.1 Applying Mechanistic Design Patterns—Part 1
    2. Answer 7.2 Applying Mechanistic Design Patterns—Part 2
    3. Answer 7.3 Applying Detailed-Design State Behavior Patterns
    4. Answer 7.4 Applying Detailed-Design Idioms (1/2)
    5. Answer 7.4 Applying Detailed-Design Idioms (2/2)
  22. Appendix A: The Roadrunner Intersection Controller System Specification
    1. Overview
    2. The Intersection Controller (IC)
  23. Appendix B: The Coyote Unmanned Air Vehicle System (CUAVS) Specification
    1. Overview
    2. Primary CUAV System Components
    3. Detailed Requirements
    4. The Coyote Mission Planning and Control System (CMPCS)
    5. The Coyote Reconnaissance Sensor Suite Payload (CSSP)
    6. The Coyote Hellfire Attack Payload (CHAP)
    7. The Coyote Datalink Subsystem (CDS)
  24. Appendix C: UML Notational Summary (1/5)
  25. Appendix C: UML Notational Summary (2/5)
  26. Appendix C: UML Notational Summary (3/5)
  27. Appendix C: UML Notational Summary (4/5)
  28. Appendix C: UML Notational Summary (5/5)
  29. Index (1/2)
  30. Index (2/2)

Product information

  • Title: Real Time UML Workshop for Embedded Systems
  • Author(s): Bruce Powel Douglass
  • Release date: April 2011
  • Publisher(s): Newnes
  • ISBN: 9780080492230