Real-time UML workshop for embedded systems
Written as a workbook with a set of guided exercises that teach by example, this book gives a practical, hands-on guide to using UML to design and implement embedded and real-time systems. A review of the basics of UML and the Harmony process for embedded software development: two on-going case exam...
| Autor principal: | |
|---|---|
| Formato: | Libro electrónico |
| Idioma: | Inglés |
| Publicado: |
Waltham, MA :
Newnes
2014.
|
| Edición: | 2nd ed |
| Colección: | Embedded technology series.
|
| Materias: | |
| Ver en Biblioteca Universitat Ramon Llull: | https://discovery.url.edu/permalink/34CSUC_URL/1im36ta/alma991009628646206719 |
Tabla de Contenidos:
- Front Cover; Real-Time UML Workshop for Embedded Systems; Copyright; Dedication; Contents; Preface; Acknowledgements; About the Author; Chapter 1 - Introduction to UML; 1.1 UML Basic Modeling Concepts; 1.2 Structural Elements and Diagrams; 1.3 Behavioral Elements and Diagrams; 1.4 Use Case and Requirements Models; Chapter 2 - The Harmony Process; 2.1 Introduction; 2.2 The Harmony Development Process; 2.3 The Systems Engineering Harmony Workflows in Detail; 2.4 The Hand-off from Systems Engineering; 2.5 The Software Workflows in Detail; Chapter 3 - Meeting Industry Standards; 3.1 Overview
- 3.2 On the Importance of Being Standard3.3 Architectural Framework Standards (I'm looking at you UPDM); 3.4 IEC 61508; 3.5 DO-178B/C; 3.6 IEC 62304; 3.7 CMMI-DEV; References; Chapter 4 - Specifying Requirements; 4.1 Overview; 4.2 Representing Requirements in UML and SysML; 4.3 Specification View: State Machines for Requirements Capture; References; Chapter 5 - Systems Architecture: Deployment and Subsystems Architecture; 5.1 Overview; 5.2 The Hand-off from Systems to Downstream Engineering; 5.3 Looking Ahead; Chapter 6 - Dependability Architecture; 6.1 Overview
- 6.2 A (Not-So) Quick Note about Design Patterns56.3 What is a Design Pattern?; 7.1 Overview; Chapter 7 - High-Fidelity Modeling1; 7.2 A Quick Note about Structured Design with UML; 7.3 High-Fidelity Modeling Workflow; 7.4 Key Strategies for Object Identification; Chapter 8 - Distribution Architecture; 8.1 Overview; Chapter 9 - Concurrency and Resource Architecture; 9.1 What is the Concurrency and Resource Architecture?; 9.2 Harmony Concurrency and Resource Architecture Workflow; Chapter 10 - Collaboration and Detailed Design; 10.1 Overview; 10.2 Collaboration Design; 10.3 Detailed Design
- Chapter 11 - Specifying Requirements: Answers11.1 Answer 4.1: Identifying Kinds of Requirements; 11.2 Answer 4.2: Identifying Use Cases for the Roadrunner Traffic Light Control System; 11.3 Answer 4.3: Mapping Requirements to Use Cases; 11.4 Answer 4.4: Identifying Use Cases for the Coyote UAV System; 11.5 Answer 4.5: Create a Requirements Table; 11.6 Answer 4.6: Capturing Quality of Service Requirements; 11.7 Answer 4.7: Operational View: Identifying Traffic Light Scenarios; 11.8 Answer 4.8: Operational View: Coyote UAV Optical Surveillance Scenarios
- 11.9 Answer 4.9: Specification View: Use Case Descriptions11.10 Answer 4.10: Simple State Machine Specification; 11.11 Answer 4.11: Specification View: Capturing Complex Requirements; 11.12 Answer 4.12: Operational to Specification View: Capturing Operational Contracts; References; Chapter 12 - Deployment and Subsystems Architecture: Answers; 12.1 Answer 5.1: Organizing the Systems Model; 12.2 Answer 5.2: Subsystem Identification; 12.3 Answer 5.3: Mapping Operational Contracts into the Subsystem Architecture; 12.4 Answer 5.4: Identifying Subsystem Use Cases
- 12.5 Answer 5.5: Creating the Shared Model
