Agile Systems Engineering

Table of contents

1. Cover image
2. Title page
3. Table of Contents
4. Copyright
5. Dedication
6. About the Author
7. Preface
   1. Audience
   2. Goals
   3. Tooling
   4. Where to Go After the Book
8. Acknowledgments
9. Chapter 1. What Is Model-Based Systems Engineering?
   1. 1.1 Key Systems Engineering Activities
   2. 1.2 Systems Engineering Data
   3. 1.3 Lifecycles of the Systems Engineer
   4. 1.4 Model-Based Systems Engineering (MBSE)
   5. 1.5 Summary
   6. References
10. Chapter 2. What Are Agile Methods and Why Should I Care?
    1. 2.1 The Agile Manifesto
    2. 2.2 Benefits of Agile Methods
    3. 2.3 Applying the Agile Manifesto to Systems Engineering
    4. 2.4 Agile Best Practices for Systems Engineering
    5. 2.5 Putting It All Together: The Harmony Agile MBSE (aMBSE) Process
    6. 2.6 Summary
    7. References
11. Chapter 3. SysML Introduction
    1. 3.1 SysML at 30,000 Feet
    2. 3.2 UML Extension Mechanisms
    3. 3.3 Organize Your Models Like It Matters
    4. 3.4 Key SysML Views and Core Semantics
    5. 3.5 Minimal SysML Profile
    6. 3.6 Summary
    7. References
12. Chapter 4. Agile Stakeholder Requirements Engineering
    1. 4.1 Objectives
    2. 4.2 The Stakeholder Requirements Workflow
    3. 4.3 The Example Model: T-Wrecks, the Industrial Exoskeleton
    4. 4.4 Identifying Stakeholders
    5. 4.5 Generating Stakeholder Requirements
    6. 4.6 Modeling Stakeholder Use Cases Scenarios
    7. 4.7 Create/Update Validation Plan
    8. 4.8 Summary
    9. 4.9 Moving On
    10. Reference
13. Chapter 5. Agile Systems Requirements Definition and Analysis
    1. 5.1 Objectives
    2. 5.2 The Systems Requirements Workflow
    3. 5.3 Identify System Use Cases
    4. 5.4 Generating System Requirements
    5. 5.5 Analyzing Use Cases
    6. 5.6 Create/Update Logical Data Schema
    7. 5.7 Dependability Analysis
    8. 5.8 Create/Update Verification Plan
    9. 5.9 Summary
    10. 5.10 Moving On
    11. References
14. Chapter 6. Agile Systems Architectural Analysis and Trade Studies
    1. 6.1 Objectives
    2. 6.2 Architecture Analysis Workflow
    3. 6.3 Assessment Methodology
    4. 6.4 Identify Key System Functions (and Properties)
    5. 6.5 Define the Candidate Solutions
    6. 6.6 Perform the Architectural Trade Study
    7. 6.7 Merge the Solutions into the Systems Architecture
    8. 6.8 Summary
    9. 6.9 Moving On
    10. References
15. Chapter 7. Agile Systems Architectural Design
    1. 7.1 Objectives
    2. 7.2 Architectural Design Workflow
    3. 7.3 Identify Subsystems
    4. 7.4 Allocate System Requirements to Subsystems
    5. 7.5 Allocate Use Cases to Subsystems
    6. 7.6 Create/Update Logical Data Schema
    7. 7.7 Create/Update Subsystem Requirements
    8. 7.8 Develop Control Laws
    9. 7.9 Analyze Dependability
    10. 7.10 Summary
    11. 7.11 Moving On
    12. References
16. Chapter 8. The Handoff to Downstream Engineering
    1. 8.1 Objectives
    2. 8.2 The Handoff to Downstream Engineering Workflow
    3. 8.3 Gather Subsystem Specification Data
    4. 8.4 Create the Shared Model
    5. 8.5 Define Subsystem Physical Interfaces
    6. 8.6 Create Subsystem Model
    7. 8.7 Define Interdisciplinary Interfaces
    8. 8.8 Allocation Requirements to Engineering Disciplines
    9. 8.9 And Downstream Engineering Begins
    10. 8.10 And System Engineering Continues …
    11. References
17. Appendix A. T-Wrecks Stakeholder Requirements
    1. Project Overview
    2. T-Wrecks High Level Use Cases
    3. General Requirements
    4. Encase Use Case
    5. Balance Use Case
    6. Walk Use Case
    7. Monitor System Use Case
    8. Move Limbs Use Case
    9. Manage Power Use Case
    10. Startup Use Case
    11. Self Test Use Case
    12. Provide Visibility Use Case
    13. Monitor System Use Case
    14. Shutdown Use Case
    15. Proximity Detection Use Case
    16. Configure Use Case
    17. Communicate Use Case
18. Appendix B. T-Wrecks System Requirements
    1. T-Wrecks High Level Use Cases
    2. Requirements Table (Initial Set)
19. Index