Real-time UML workshop for embedded systems
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...
Saved in:
| Main Author: | |
|---|---|
| Format: | eBook Book |
| Language: | English |
| Published: |
Amsterdam ; Tokyo
Elsevier/Newnes
2007
Elsevier Science & Technology Newnes |
| Edition: | 1 |
| Series: | Embedded Technology Series |
| Subjects: | |
| ISBN: | 0750679069, 9780750679060, 0080492231, 9780080492230 |
| Online Access: | Get full text |
| Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
Table of Contents:
- Front Cover -- Real-Time UML Workshop for Embedded Systems -- Copyright Page -- Contents -- Preface -- Audience -- Goals -- Where to Go After the Book -- Evaluate UML on ARM -- Acknowledgments -- About the Author -- What's on the CD-ROM? -- Chapter 1. Introduction -- Basic Modeling Concepts of the UML -- Structural Elements and Diagrams -- Behavioral Elements and Diagrams -- Use Case and Requirements Models -- Summary -- Check Out the CD-ROM -- Chapter 2. The Harmony Process -- Introduction -- The Harmony Development Process -- Summary -- Chapter 3. Specifying Requirements -- Overview -- Problem 3.1 Identifying Kinds of Requirements for Roadrunner Traffic Light Control System -- Problem 3.2 Identifying Use Cases for the Roadrunner Traffic Light Control System -- Problem 3.3 Mapping Requirements to Use Cases -- Problem 3.4 Identifying Use Cases for the Coyote UAV System -- Problem 3.5 Identifying Parametric Requirements -- Problem 3.6 Capturing Quality of Service Requirements in Use Cases -- Problem 3.7 Operational View: Identifying Traffic Light Scenarios -- Problem 3.8 Operational View: CUAVS Optical Surveillance Scenarios -- Problem 3.9 Specification View: Use-Case Description -- Specification View: State Machines for Requirements Capture -- Problem 3.10 Specification View: Capturing Complex Requirements -- Problem 3.11 Operational to Specification View: Capturing Operational Contracts -- References -- Chapter 4. Systems Architecture -- Overview -- Problem 4.1 Organizing the Systems Model -- Problem 4.2 Subsystem Identification -- Problem 4.3 Mapping Operational Contracts into Subsystem Architecture -- Problem 4.4 Identifying Subsystem Use Cases -- Looking Ahead -- Chapter 5. Object Analysis -- Overview -- Key Strategies for Object Identification -- Problem 5.1 Apply Nouns and Causal Agents Strategies
- Chapter 10. Object Analysis: Answers -- Answer 5.1 Apply Nouns and Causal Agents Strategies -- Answer 5.2 Apply Services and Messages Strategies -- Answer 5.3 Applying the Real-World Items and Physical Devices Strategies -- Answer 5.4 Apply Key Concepts and Transaction Strategies -- Answer 5.5 Identify Visual Elements and Scenarios Strategies -- Answer 5.6 Merge Models from the Various Strategies -- Chapter 11. Architectural Design: Answers -- Answer 6.1 Concurrency and Resource Architecture -- Answer 6.2 Distribution Architecture -- Answer 6.3 Safety and Reliability Architecture -- Chapter 12. Mechanistic and Detailed Design: Answers -- Answer 7.1 Applying Mechanistic Design Patterns-Part 1 -- Answer 7.2 Applying Mechanistic Design Patterns-Part 2 -- Answer 7.3 Applying Detailed-Design State Behavior Patterns -- Answer 7.4 Applying Detailed-Design Idioms -- Appendix A: The Roadrunner Intersection Controller System Specification -- Overview -- The Intersection Controller (IC) -- Appendix B: The Coyote Unmanned Air Vehicle System (CUAVS) Specification -- Overview -- Primary CUAV System Components -- Detailed Requirements -- The Coyote Mission Planning and Control System (CMPCS) -- The Coyote Reconnaissance Sensor Suite Payload (CSSP) -- The Coyote Hellfire Attack Payload (CHAP) -- The Coyote Datalink Subsystem (CDS) -- Appendix C: UML Notational Summary -- Index
- Problem 5.2 Apply Services and Messages Strategies -- Problem 5.3 Apply Real-World Items and Physical Devices Strategies -- Problem 5.4 Apply Key Concepts and Transaction Strategies -- Problem 5.5 Apply Identify Visual Elements and Scenarios Strategies -- Problem 5.6 Merge Models from the Various Strategies -- Looking Ahead -- Chapter 6. Architectural Design -- Overview -- Problem 6.1 Concurrency and Resource Architecture -- Problem 6.2 Distribution Architecture -- Problem 6.3 Safety and Reliability Architecture -- Looking Ahead -- Chapter 7. Mechanistic and Detailed Design -- Overview -- Mechanistic Design -- Detailed Design -- Problem 7.1 Applying Mechanistic Design Patterns-Part 1 -- Problem 7.2 Applying Mechanistic Design Patterns-Part 2 -- Problem 7.3 Applying Detailed-Design State Behavior Patterns -- Problem 7.4 Applying Detailed Design Idioms -- Summary -- Chapter 8. Specifying Requirements: Answers -- Answer 3.1 Identifying Kinds of Requirements -- Answer 3.2 Identifying Use Cases for Roadrunner Traffic Light Control System -- Answer 3.3 Mapping Requirements to Use Cases -- Answer 3.4 Identifying Use Cases for Coyote UAV System -- Answer 3.5 Identifying Parametric Requirements -- Answer 3.6 Capturing Quality of Service Requirements -- Answer 3.7 Operational View: Identifying Traffic Light Scenarios -- Answer 3.8 Operational View: CUAVS Optical Surveillance Scenarios -- Answer 3.9 Specification View: Use-Case Descriptions -- Answer 3.10 Specification View: Capturing Complex Requirements -- Answer 3.11 Operational to Specification View: Capturing Operational Contracts -- References -- Chapter 9. Systems Architecture: Answers -- Answer 4.1 Organizing the Systems Model -- Answer 4.2 Subsystem Identification -- Answer 4.3 Mapping Operational Contracts into the Subsystem Architecture -- Answer 4.4 Identifying Subsystem Use Cases