| |
| |
Chapter | |
| |
| |
List of Authors | |
| |
| |
Preface | |
| |
| |
| |
Space Systems Engineering | |
| |
| |
| |
The Art and Science of Systems Engineering | |
| |
| |
| |
Apply Systems Engineering Across the Lifecycle | |
| |
| |
| |
Create and Maintain the Technical Baseline | |
| |
| |
| |
Establish a Systems Engineering Framework | |
| |
| |
| |
Identify Capabilities of the Systems Engineer | |
| |
| |
| |
Introduction to the End-to-End Case Study-FireSAT | |
| |
| |
| |
Stakeholder Expectations and Requirements Definition | |
| |
| |
| |
Define Initial Customer Expectations | |
| |
| |
| |
Identify the Stakeholders | |
| |
| |
| |
Solicit and Synthesize Stakeholder Expectations and Requirements | |
| |
| |
| |
Articulate Stakeholder Expectations and Requirements | |
| |
| |
| |
Rank Order Mission Requirements and Identify Critical Acceptance Criteria | |
| |
| |
| |
Synthesize Essential Mission Requirements | |
| |
| |
| |
Validate and Baseline Requirements. Translate Into Technical Requirements | |
| |
| |
| |
Concept of Operations and System Operational Architecture | |
| |
| |
| |
Validate the Mission Scope and the System Boundary | |
| |
| |
| |
Describe the System's Operational Environment, Primary Constraints, and Drivers | |
| |
| |
| |
Develop Operational Scenarios and Timelines | |
| |
| |
| |
Synthesize, Analyze, and Assess Key Implementing Concepts for the System and Its Elements | |
| |
| |
| |
Document the Concept of Operations and the System's Operational Architecture; Apply Architectural Frameworks | |
| |
| |
| |
Validate and Baseline the System's Operational Architecture | |
| |
| |
| |
Engineering and Managing System Requirements | |
| |
| |
| |
Before Requirements | |
| |
| |
| |
Engineer the System Requirements | |
| |
| |
| |
Document the Requirements | |
| |
| |
| |
Baseline the Requirements | |
| |
| |
| |
Manage the Requirements | |
| |
| |
| |
System Functional and Physical Partitioning | |
| |
| |
| |
Specify the System Context | |
| |
| |
| |
Define the Functional Partitions | |
| |
| |
| |
Create the Physical Partitions and Allocate Functions to the Physical Components | |
| |
| |
| |
Assess the Architecture | |
| |
| |
| |
Allocate Requirements to the Components and Generate Detailed Specifications | |
| |
| |
| |
Trace Requirements | |
| |
| |
| |
Decision Making | |
| |
| |
| |
Identify What We Need to Decide | |
| |
| |
| |
Frame the Decision | |
| |
| |
| |
Select a Method to Evaluate Alternatives | |
| |
| |
| |
Generate Alternatives | |
| |
| |
| |
Choose the Best Solution | |
| |
| |
| |
Test and Evaluate | |
| |
| |
| |
Consider a Case Study | |
| |
| |
| |
Lifecycle Cost Analysis | |
| |
| |
| |
Develop a Work Breakdown Structure (WBS) | |
| |
| |
| |
Gather Space System Characteristics | |
| |
| |
| |
Compute the System Development Cost | |
| |
| |
| |
Estimate Operations and Support Costs | |
| |
| |
| |
Estimate Cost of Developing the Launch Site's Infrastructure | |
| |
| |
| |
Estimate Total Lifecycle Cost and Assess Cost Risk | |
| |
| |
| |
Conduct Cost-Risk Analysis | |
| |
| |
| |
Technical Risk Management | |
| |
| |
| |
Prepare a Technical Risk Management Strategy | |
| |
| |
| |
Identify and Document Technical Risks | |
| |
| |
| |
Conduct Technical Risk Assessments | |
| |
| |
| |
Determine an Initial Risk Handling Approach | |
| |
| |
| |
Plan Risk Mitigations and Triggers | |
| |
| |
| |
Monitor Risk Status | |
| |
| |
| |
Implement Risk Mitigations | |
| |
| |
| |
Capture Technical Risk Management Products | |
| |
| |
| |
Product Implementation | |
| |
| |
| |
Prepare for Implementation | |
| |
| |
| |
Participate in Buying the Product | |
| |
| |
| |
Participate in Acquiring the Reuse End Product | |
| |
| |
| |
Evaluate the Readiness of Items that Enable Product Implementation | |
| |
| |
| |
Make the Product | |
| |
| |
| |
Prepare Appropriate Product Support Documentation | |
| |
| |
| |
Capture Product Implementation Work Products | |
| |
| |
| |
Ensure Effective Communication | |
| |
| |
| |
System Integration | |
| |
| |
| |
Define the Role of System Integration within Systems Engineering | |
| |
| |
| |
Select a System Integration Approach and Strategy | |
| |
| |
| |
Set Up a Test and Integration Plan | |
| |
| |
| |
Schedule in the Presence of Unknowns | |
| |
| |
| |
Form the Integration Team | |
| |
| |
| |
Manage a Changing Configuration | |
| |
| |
| |
Adapt Integration to the Project Specifics | |
| |
| |
| |
Solve Typical Problems | |
| |
| |
| |
Verification and Validation | |
| |
| |
| |
Validate Requirements | |
| |
| |
| |
Validate Models | |
| |
| |
| |
Verify Products | |
| |
| |
| |
Validate Products | |
| |
| |
| |
Certify Products for Flight | |
| |
| |
| |
Address Special Challenges of Commercial Off-the-Shelf and Non-Developmental Items Product Verification | |
| |
| |
| |
Verify and Validate Software | |
| |
| |
| |
Document and Iterate | |
| |
| |
| |
Product Transition | |
| |
| |
| |
Plan the Transition | |
| |
| |
| |
Verify that the Product is Ready for Transition | |
| |
| |
| |
Prepare the Product for Transportation to the Launch Site | |
| |
| |
| |
Transport to the Launch Site | |
| |
| |
| |
Unpack and Store the Product | |
| |
| |
| |
Integrate With the Launch Vehicle | |
| |
| |
| |
Roll Vehicle Out to the Launch Pad | |
| |
| |
| |
Integrate With the Launch Pad | |
| |
| |
| |
Conduct Launch and Early Operations | |
| |
| |
| |
Transfer to the End User | |
| |
| |
| |
Document the Transition | |
| |
| |
| |
Plan and Manage the Technical Effort | |
| |
| |
| |
Prepare for Technical Planning | |
| |
| |
| |
Define the Technical Work | |
| |
| |
| |
Schedule, Organize, and Cost the Technical Work | |
| |
| |
| |
Prepare the Systems Engineering Management Plan and Other Technical Plans | |
| |
| |
| |
Get Stakeholder Commitments to Technical Plans | |
| |
| |
| |
Execute the Technical Plan | |
| |
| |
| |
Document and Iterate | |
| |
| |
| |
Technical Direction and Management: The Systems Engineering Management Plan (SEMP) in Action | |
| |
| |
| |
Introduction to the Systems Engineering Management Plan | |
| |
| |
| |
Determine the Contents of the SEMP | |
| |
| |
| |
Develop the Systems Engineering Management Plan (SEMP) | |
| |
| |
| |
Characteristics of Good and Bad Plans | |
| |
| |
| |
Necessary Elements for Executing a SEMP | |
| |
| |
| |
A Look at DoD's SEP | |
| |
| |
| |
Manage Interfaces | |
| |
| |
| |
Prepare or Update Interface Management Procedures | |
| |
| |
| |
Decompose the System Physically and Functionally | |
| |
| |
| |
List Interfaces and Prepare Initial Interface Requirements Documents (IRDs) | |
| |
| |
| |
Develop NxN and IxI Diagrams | |
| |
| |
| |
Develop Sub-level Work Breakdown Structure (WBS) of the Lifecycle Interface Design and Verification Tasks | |
| |
| |
| |
Develop an Interface Control Document (ICD) for Each Interface | |
| |
| |
| |
Manage Interfaces during Product Integration | |
| |
| |
| |
Design Interfaces, Iterate, and Trade | |
| |
| |
| |
Build Interfaces | |
| |
| |
| |
Verify Interfaces Including Integration with the System | |
| |
| |
| |
Document, Iterate, and Control the Configuration | |
| |
| |
| |
Develop Operating Procedures and Training | |
| |
| |
| |
Manage Configuration | |
| |
| |
| |
The Configuration Management Process | |
| |
| |
| |
Develop the Configuration Management Plan | |
| |
| |
| |
Establish Configuration Identification | |
| |
| |
| |
Manage Change | |
| |
| |
| |
Communicate Progress with Configuration Status Accounting | |
| |
| |
| |
Conduct Verifications and Audits | |
| |
| |
| |
Manage Technical Data | |
| |
| |
| |
Prepare a Strategy for Managing Technical Data | |
| |
| |
| |
Collect and Store Required Technical-data Artifacts During the Engineering Lifecycle | |
| |
| |
| |
Maintain Stored Technical Data | |
| |
| |
| |
Provide Technical Data to Authorized Parties | |
| |
| |
| |
Collaborate by Effectively Using System and Process Artifacts | |
| |
| |
| |
Technical Assessment and Reviews | |
| |
| |
| |
Define the Subject and Scope of the Review | |
| |
| |
| |
Establish the Entrance Criteria | |
| |
| |
| |
Identify and Invite the Review Team | |
| |
| |
| |
Conduct the Review | |
| |
| |
| |
Ensure that the System Meets Success Criteria | |
| |
| |
| |
Specify and Document the Decisions | |
| |
| |
| |
Clarify and Document the Action Items | |
| |
| |
| |
Baseline the Design | |
| |
| |
| |
Improve the Process for Technical Reviews | |
| |
| |
| |
FireSAT End-to-End Case Study: A Parable of Space Systems Engineering in Seven Parts | |
| |
| |
| |
Certify the As-deployed Baseline | |
| |
| |
| |
Define the Mission Baseline | |
| |
| |
| |
Create the System Baseline | |
| |
| |
| |
Establish the Functional Baseline | |
| |
| |
| |
Reach the Design-to Baseline | |
| |
| |
| |
Set the Build-to Baseline | |
| |
| |
| |
Achieve the As-built Baseline | |
| |
| |
Index | |