| |
| |
| Preface | |
| |
| |
| Audience | |
| |
| |
| Goals | |
| |
| |
| Where to Go After the Book | |
| |
| |
| Evaluate UML on ARM | |
| |
| |
| Acknowledgments | |
| |
| |
| About the Author | |
| |
| |
| What's on the CD-ROM? | |
| |
| |
| |
| Introduction | |
| |
| |
| Basic Modeling Concepts of the UML | |
| |
| |
| Structural Elements and Diagrams | |
| |
| |
| Small Things: Objects, Classes, and Interfaces | |
| |
| |
| Relations | |
| |
| |
| Big Things: Subsystems, Components, and Packages | |
| |
| |
| Behavioral Elements and Diagrams | |
| |
| |
| Actions and Activities | |
| |
| |
| Operations and Methods | |
| |
| |
| Activity Diagrams | |
| |
| |
| Statecharts | |
| |
| |
| Interactions | |
| |
| |
| Use Case and Requirements Models | |
| |
| |
| Summary | |
| |
| |
| Check Out the CD-ROM | |
| |
| |
| |
| The Harmony Process | |
| |
| |
| Introduction | |
| |
| |
| The Harmony Development Process | |
| |
| |
| Why Process? | |
| |
| |
| Harmony Process Overview | |
| |
| |
| The Systems Engineering Harmony Workflows in Detail | |
| |
| |
| The Incremental (Spiral) Development Workflows in Detail | |
| |
| |
| Increment Review (Party!) Workflow | |
| |
| |
| Design with the Harmony Process | |
| |
| |
| Implementation | |
| |
| |
| Test | |
| |
| |
| Summary | |
| |
| |
| |
| Specifying Requirements | |
| |
| |
| Overview | |
| |
| |
| |
| Identifying Kinds of Requirements for Roadrunner Traffic Light Control System | |
| |
| |
| |
| Identifying Use Cases for the Roadrunner Traffic Light Control System | |
| |
| |
| |
| Mapping Requirements to Use Cases | |
| |
| |
| |
| Identifying Use Cases for the Coyote UAV System | |
| |
| |
| |
| Identifying Parametric Requirements | |
| |
| |
| |
| Capturing Quality of Service Requirements in Use Cases | |
| |
| |
| |
| Operational View: Identifying Traffic Light Scenarios | |
| |
| |
| |
| Operational View: CUAVS Optical Surveillance Scenarios | |
| |
| |
| |
| Specification View: Use-Case Description | |
| |
| |
| Specification View: State Machines for Requirements Capture | |
| |
| |
| |
| Specification View: Capturing Complex Requirements | |
| |
| |
| |
| Operational to Specification View: Capturing Operational Contracts | |
| |
| |
| References | |
| |
| |
| |
| Systems Architecture | |
| |
| |
| Overview | |
| |
| |
| |
| Organizing the Systems Model | |
| |
| |
| |
| Subsystem Identification | |
| |
| |
| |
| Mapping Operational Contracts into Subsystem Architecture | |
| |
| |
| |
| Identifying Subsystem Use Cases | |
| |
| |
| Looking Ahead | |
| |
| |
| |
| Object Analysis | |
| |
| |
| Overview | |
| |
| |
| Key Strategies for Object Identification | |
| |
| |
| Underline the Noun Strategy | |
| |
| |
| Identify the Causal Agents | |
| |
| |
| Identify Services (Passive Contributors or Server Objects) | |
| |
| |
| Identify Messages and Information Flows | |
| |
| |
| Identify Real-World Items | |
| |
| |
| Identify Physical Devices | |
| |
| |
| Identify Key Concepts | |
| |
| |
| Identify Transactions | |
| |
| |
| Identify Persistent Information | |
| |
| |
| Identify Visual Elements | |
| |
| |
| Identify Control Elements | |
| |
| |
| Apply Scenarios | |
| |
| |
| |
| Apply Nouns and Causal Agents Strategies | |
| |
| |
| |
| Apply Services and Messages Strategies | |
| |
| |
| |
| Apply Real-World Items and Physical Devices Strategies | |
| |
| |
| |
| Apply Key Concepts and Transaction Strategies | |
| |
| |
| |
| Apply Identify Visual Elements and Scenarios Strategies | |
| |
| |
| |
| Merge Models from the Various Strategies | |
| |
| |
| Looking Ahead | |
| |
| |
| |
| Architectural Design | |
| |
| |
| Overview | |
| |
| |
| |
| Concurrency and Resource Architecture | |
| |
| |
| |
| Distribution Architecture | |
| |
| |
| |
| Safety and Reliability Architecture | |
| |
| |
| Looking Ahead | |
| |
| |
| |
| Mechanistic and Detailed Design | |
| |
| |
| Overview | |
| |
| |
| Mechanistic Design | |
| |
| |
| Delegation Pattern Strategy | |
| |
| |
| Interface Abstraction Pattern Strategy | |
| |
| |
| Detailed Design | |
| |
| |
| |
| Applying Mechanistic Design Patterns-Part 1 | |
| |
| |
| |
| Applying Mechanistic Design Patterns-Part 2 | |
| |
| |
| |
| Applying Detailed-Design State Behavior Patterns | |
| |
| |
| |
| Applying-Detailed Design Idioms | |
| |
| |
| Summary | |
| |
| |
| |
| Specifying Requirements: Answers | |
| |
| |
| |
| Identifying Kinds of Requirements | |
| |
| |
| |
| Identifying Use Cases for Roadrunner Traffic Light Control System | |
| |
| |
| |
| Mapping Requirements to Use Cases | |
| |
| |
| |
| Identifying Use Cases for Coyote UAV System | |
| |
| |
| |
| Identifying Parametric Requirements | |
| |
| |
| |
| Capturing Quality of Service Requirements | |
| |
| |
| |
| Operational View: Identifying Traffic Light Scenarios | |
| |
| |
| |
| Operational View: CUAVS Optical Surveillance Scenarios | |
| |
| |
| |
| Specification View: Use-Case Descriptions | |
| |
| |
| |
| Specification View: Capturing Complex Requirements | |
| |
| |
| |
| Operational to Specification View: Capturing Operational Contracts | |
| |
| |
| References | |
| |
| |
| |
| Systems Architecture: Answers | |
| |
| |
| |
| Organizing the Systems Model | |
| |
| |
| |
| Subsystem Identification | |
| |
| |
| |
| Mapping Operational Contracts into the Subsystem Architecture | |
| |
| |
| |
| Identifying Subsystem Use Cases | |
| |
| |
| |
| Object Analysis: Answers | |
| |
| |
| |
| Apply Nouns and Causal Agents Strategies | |
| |
| |
| |
| Apply Services and Messages Strategies | |
| |
| |
| |
| Applying the Real-World Items and Physical Devices Strategies | |
| |
| |
| |
| Apply Key Concepts and Transaction Strategies | |
| |
| |
| |
| Identify Visual Elements and Scenarios Strategies | |
| |
| |
| |
| Merge Models from the Various Strategies | |
| |
| |
| |
| Architectural Design: Answers | |
| |
| |
| |
| Concurrency and Resource Architecture | |
| |
| |
| |
| Distribution Architecture | |
| |
| |
| |
| Safety and Reliability Architecture | |
| |
| |
| |
| Mechanistic and Detailed Design: Answers | |
| |
| |
| |
| Applying Mechanistic Design Patterns-Part 1 | |
| |
| |
| |
| Applying Mechanistic Design Patterns-Part 2 | |
| |
| |
| |
| Applying Detailed-Design State Behavior Patterns | |
| |
| |
| |
| Applying Detailed-Design Idioms | |
| |
| |
| |
| The Roadrunner Intersection Controller System Specification | |
| |
| |
| Overview | |
| |
| |
| The Intersection Controller (IC) | |
| |
| |
| Configuration Parameters | |
| |
| |
| Intersection Modes | |
| |
| |
| The Vehicle Detector | |
| |
| |
| Vehicular Traffic Light | |
| |
| |
| Pedestrian Light and Sensor | |
| |
| |
| Front Panel Display | |
| |
| |
| Remote Communications | |
| |
| |
| Power | |
| |
| |
| |
| The Coyote Unmanned Air Vehicle System (CUAVS) Specification | |
| |
| |
| Overview | |
| |
| |
| Primary CUAV System Components | |
| |
| |
| The Unmanned Air Vehicle (UAV) | |
| |
| |
| The Coyote Mission Planning and Control System (CMPCS) | |
| |
| |
| Coyote Payloads | |
| |
| |
| The Coyote Datalink Subsystem (CDS) | |
| |
| |
| Detailed Requirements | |
| |
| |
| The Unmanned Air Vehicle (UAV) | |
| |
| |
| Flight Modes | |
| |
| |
| Mission Modes | |
| |
| |
| 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) | |
| |
| |
| |
| UML Notational Summary | |
| |
| |
| Index | |