Table of Contents
2.1 KEY RESPONSIBILITIES OF THE CHIEF SYSTEMS ENGINEER
2.1.1 Technical Management of the engineering process - Vision & Strategy
2.1.2 SE Products - Owning and Embracing the Document Tree
2.1.3 Processes and Procedures - Owning and promulgating good practices
2.1.4 Tools and Methodologies - Enabling, but managing
2.1.5 Team integration - coerce, cajole, and command the potential stovepipe engineering efforts: architecture, hardware, behavior, requirements, test, assembly, etc. into a synergistic whole.
2.1.6 Growing your team
2.1.7 Above all - Adult Supervision
3.1 DEFINING THE PROBLEM
3.2 THE OBJECTIVE - TEASING OUT THE REAL NEED AND DEFINING "A" NOT "THE" SYSTEM
3.3 THE METHODOLOGY
3.3.1 Use Case Identification
3.4 COMMENTS
4.1 THE OBJECTIVE - DEFINING "THE" SYSTEM
4.1.1 Design Derivation (Synthesis and Decomposition)
4.2 THE METHODOLOGY
4.2.1 Use Case Elaboration
4.2.2 Documentation
4.3 A TOOL
4.3.1 SSD and EFT via Visio tool
4.4 A WARNING ABOUT ANALYSIS PARALYSIS - OR - WHEN ARE WE DONE?
5.1 THE OBJECTIVE - SPECIFYING THE FUNCTIONS AND PERFORMANCE OF COMPONENTS OF THE SYSTEM
5.1.1 Hierarchy and Layers
5.2 THE METHODOLOGY
5.2.1 Requirement Writing
5.2.2 The Specification
7 DESIGN SYNTHESIS - CONSTRAINTS
7.1 THE OBJECTIVE - DOCUMENTING FUNDAMENTAL AND DERIVED CONSTRAINTS
7.2 THE METHODOLOGY
8.1 CEREMONY!
10.1 REQUIREMENTS VERIFICATION & SYSTEM VALIDATION
10.1.1 Knowledge Flow
11 MISSION SUCCESS - SUMMARY
12.2.1 Annotated Operations Concept Document Scenario Capture Outline
