Chapter | |
List of Authors | |
Preface | |
Space Systems Engineering | p. 1 |
The Art and Science of Systems Engineering | p. 3 |
Apply Systems Engineering Across the Lifecycle | p. 15 |
Create and Maintain the Technical Baseline | p. 20 |
Establish a Systems Engineering Framework | p. 22 |
Identify Capabilities of the Systems Engineer | p. 28 |
Introduction to the End-to-End Case Study-FireSAT | p. 31 |
Stakeholder Expectations and Requirements Definition | p. 37 |
Define Initial Customer Expectations | p. 39 |
Identify the Stakeholders | p. 45 |
Solicit and Synthesize Stakeholder Expectations and Requirements | p. 47 |
Articulate Stakeholder Expectations and Requirements | p. 57 |
Rank Order Mission Requirements and Identify Critical Acceptance Criteria | p. 57 |
Synthesize Essential Mission Requirements | p. 61 |
Validate and Baseline Requirements. Translate Into Technical Requirements | p. 62 |
Concept of Operations and System Operational Architecture | p. 65 |
Validate the Mission Scope and the System Boundary | p. 67 |
Describe the System's Operational Environment, Primary Constraints, and Drivers | p. 71 |
Develop Operational Scenarios and Timelines | p. 74 |
Synthesize, Analyze, and Assess Key Implementing Concepts for the System and Its Elements | p. 80 |
Document the Concept of Operations and the System's Operational Architecture; Apply Architectural Frameworks | p. 83 |
Validate and Baseline the System's Operational Architecture | p. 89 |
Engineering and Managing System Requirements | p. 95 |
Before Requirements | p. 98 |
Engineer the System Requirements | p. 106 |
Document the Requirements | p. 121 |
Baseline the Requirements | p. 129 |
Manage the Requirements | p. 133 |
System Functional and Physical Partitioning | p. 141 |
Specify the System Context | p. 147 |
Define the Functional Partitions | p. 151 |
Create the Physical Partitions and Allocate Functions to the Physical Components | p. 173 |
Assess the Architecture | p. 186 |
Allocate Requirements to the Components and Generate Detailed Specifications | p. 191 |
Trace Requirements | p. 193 |
Decision Making | p. 201 |
Identify What We Need to Decide | p. 203 |
Frame the Decision | p. 205 |
Select a Method to Evaluate Alternatives | p. 209 |
Generate Alternatives | p. 217 |
Choose the Best Solution | p. 217 |
Test and Evaluate | p. 223 |
Consider a Case Study | p. 223 |
Lifecycle Cost Analysis | p. 233 |
Develop a Work Breakdown Structure (WBS) | p. 236 |
Gather Space System Characteristics | p. 238 |
Compute the System Development Cost | p. 245 |
Estimate Operations and Support Costs | p. 256 |
Estimate Cost of Developing the Launch Site's Infrastructure | p. 284 |
Estimate Total Lifecycle Cost and Assess Cost Risk | p. 288 |
Conduct Cost-Risk Analysis | p. 290 |
Technical Risk Management | p. 293 |
Prepare a Technical Risk Management Strategy | p. 296 |
Identify and Document Technical Risks | p. 299 |
Conduct Technical Risk Assessments | p. 301 |
Determine an Initial Risk Handling Approach | p. 319 |
Plan Risk Mitigations and Triggers | p. 319 |
Monitor Risk Status | p. 321 |
Implement Risk Mitigations | p. 324 |
Capture Technical Risk Management Products | p. 324 |
Product Implementation | p. 327 |
Prepare for Implementation | p. 329 |
Participate in Buying the Product | p. 334 |
Participate in Acquiring the Reuse End Product | p. 340 |
Evaluate the Readiness of Items that Enable Product Implementation | p. 340 |
Make the Product | p. 341 |
Prepare Appropriate Product Support Documentation | p. 348 |
Capture Product Implementation Work Products | p. 348 |
Ensure Effective Communication | p. 349 |
System Integration | p. 351 |
Define the Role of System Integration within Systems Engineering | p. 351 |
Select a System Integration Approach and Strategy | p. 356 |
Set Up a Test and Integration Plan | p. 365 |
Schedule in the Presence of Unknowns | p. 373 |
Form the Integration Team | p. 375 |
Manage a Changing Configuration | p. 377 |
Adapt Integration to the Project Specifics | p. 380 |
Solve Typical Problems | p. 381 |
Verification and Validation | p. 385 |
Validate Requirements | p. 391 |
Validate Models | p. 396 |
Verify Products | p. 404 |
Validate Products | p. 432 |
Certify Products for Flight | p. 444 |
Address Special Challenges of Commercial Off-the-Shelf and Non-Developmental Items Product Verification | p. 452 |
Verify and Validate Software | p. 454 |
Document and Iterate | p. 475 |
Product Transition | p. 479 |
Plan the Transition | p. 481 |
Verify that the Product is Ready for Transition | p. 487 |
Prepare the Product for Transportation to the Launch Site | p. 488 |
Transport to the Launch Site | p. 489 |
Unpack and Store the Product | p. 492 |
Integrate With the Launch Vehicle | p. 496 |
Roll Vehicle Out to the Launch Pad | p. 497 |
Integrate With the Launch Pad | p. 497 |
Conduct Launch and Early Operations | p. 501 |
Transfer to the End User | p. 503 |
Document the Transition | p. 506 |
Plan and Manage the Technical Effort | p. 507 |
Prepare for Technical Planning | p. 509 |
Define the Technical Work | p. 513 |
Schedule, Organize, and Cost the Technical Work | p. 529 |
Prepare the Systems Engineering Management Plan and Other Technical Plans | p. 547 |
Get Stakeholder Commitments to Technical Plans | p. 551 |
Execute the Technical Plan | p. 553 |
Document and Iterate | p. 555 |
Technical Direction and Management: The Systems Engineering Management Plan (SEMP) in Action | p. 565 |
Introduction to the Systems Engineering Management Plan | p. 565 |
Determine the Contents of the SEMP | p. 567 |
Develop the Systems Engineering Management Plan (SEMP) | p. 580 |
Characteristics of Good and Bad Plans | p. 589 |
Necessary Elements for Executing a SEMP | p. 593 |
A Look at DoD's SEP | p. 598 |
Manage Interfaces | p. 603 |
Prepare or Update Interface Management Procedures | p. 607 |
Decompose the System Physically and Functionally | p. 609 |
List Interfaces and Prepare Initial Interface Requirements Documents (IRDs) | p. 614 |
Develop NxN and IxI Diagrams | p. 615 |
Develop Sub-level Work Breakdown Structure (WBS) of the Lifecycle Interface Design and Verification Tasks | p. 621 |
Develop an Interface Control Document (ICD) for Each Interface | p. 621 |
Manage Interfaces during Product Integration | p. 628 |
Design Interfaces, Iterate, and Trade | p. 631 |
Build Interfaces | p. 632 |
Verify Interfaces Including Integration with the System | p. 633 |
Document, Iterate, and Control the Configuration | p. 633 |
Develop Operating Procedures and Training | p. 634 |
Manage Configuration | p. 639 |
The Configuration Management Process | p. 639 |
Develop the Configuration Management Plan | p. 642 |
Establish Configuration Identification | p. 648 |
Manage Change | p. 652 |
Communicate Progress with Configuration Status Accounting | p. 661 |
Conduct Verifications and Audits | p. 664 |
Manage Technical Data | p. 669 |
Prepare a Strategy for Managing Technical Data | p. 670 |
Collect and Store Required Technical-data Artifacts During the Engineering Lifecycle | p. 687 |
Maintain Stored Technical Data | p. 691 |
Provide Technical Data to Authorized Parties | p. 701 |
Collaborate by Effectively Using System and Process Artifacts | p. 708 |
Technical Assessment and Reviews | p. 715 |
Define the Subject and Scope of the Review | p. 716 |
Establish the Entrance Criteria | p. 717 |
Identify and Invite the Review Team | p. 718 |
Conduct the Review | p. 719 |
Ensure that the System Meets Success Criteria | p. 721 |
Specify and Document the Decisions | p. 721 |
Clarify and Document the Action Items | p. 722 |
Baseline the Design | p. 722 |
Improve the Process for Technical Reviews | p. 730 |
FireSAT End-to-End Case Study: A Parable of Space Systems Engineering in Seven Parts | p. 733 |
Certify the As-deployed Baseline | p. 735 |
Define the Mission Baseline | p. 741 |
Create the System Baseline | p. 772 |
Establish the Functional Baseline | p. 795 |
Reach the Design-to Baseline | p. 817 |
Set the Build-to Baseline | p. 834 |
Achieve the As-built Baseline | p. 856 |
Index | p. 873 |
Table of Contents provided by Ingram. All Rights Reserved. |
The New copy of this book will include any supplemental materials advertised. Please check the title of the book to determine if it should include any access cards, study guides, lab manuals, CDs, etc.
The Used, Rental and eBook copies of this book are not guaranteed to include any supplemental materials. Typically, only the book itself is included. This is true even if the title states it includes any access cards, study guides, lab manuals, CDs, etc.