NASA Systems Engineering Handbook¶
National Aeronautics and Space Administration. (2016). NASA Systems Engineering Handbook.
Cited by¶
11 citations across 11 artifacts.
Each citation links to the sentence it supports in the citing article.
Domain-specific¶
- Decision Method
- Listed in the references but not attached to a specific claim.
- Engineered System
- Listed in the references but not attached to a specific claim.
- System Requirements (Spacecraft System)
Mechanisms¶
- Boundary Update Log
- … boundary evolution auditable: it defeats the hindsight illusion that "we always knew," ties every revision to the evidence that forced it, and — because it demands a record for shrinking the boundary as much as for growing it — it catches the dangerous asymmetry where an impact that arrived never actually leaves.
This sourceRequires controlled changes to remain visible, traceable, justified, evaluated, and recorded across a system’s life cycle.
- … boundary evolution auditable: it defeats the hindsight illusion that "we always knew," ties every revision to the evidence that forced it, and — because it demands a record for shrinking the boundary as much as for growing it — it catches the dangerous asymmetry where an impact that arrived never actually leaves.
- Design Tradeoff Curve
- Its strength is making a physical trade explicit and honest: it shows that the exchange rate is not constant, marks where returns collapse, and gives every point a clear verdict against the requirement — the engineering discipline of a trade study
This sourceTreats systematic comparison of design alternatives against explicit criteria as an engineering trade study.
- Its strength is making a physical trade explicit and honest: it shows that the exchange rate is not constant, marks where returns collapse, and gives every point a clear verdict against the requirement — the engineering discipline of a trade study
- Frontier Readiness Gate
- It is a close relative of the operational readiness review used before high-stakes launches, where a system may not go live until every supporting function has demonstrably passed its checks.
This sourceMakes successful operational readiness review a prerequisite for placing a system and all enabling products into operational status.
- It is a close relative of the operational readiness review used before high-stakes launches, where a system may not go live until every supporting function has demonstrably passed its checks.
- Holon Interface Registry
- This is precisely the role of an Interface Control Document in systems engineering
This sourceStates that interface control documentation captures interface information and approved changes under configuration management.
- This is precisely the role of an Interface Control Document in systems engineering
- Launch Readiness Review
- The discipline that guards against this is to require each owner's go to rest on its own function's evidence rather than the room's mood, to log every no-go with the specific open dependency named, and to treat the launch date as a movable output of the review rather than a fixed input.
This sourceTreats readiness reviews as evidence-based decision gates that record open issues and allow the planned transition date to depend on demonstrated readiness.
- The discipline that guards against this is to require each owner's go to rest on its own function's evidence rather than the room's mood, to log every no-go with the specific open dependency named, and to treat the launch date as a movable output of the review rather than a fixed input.
- Readiness Review
- Weighing readiness against downstream reliance is what makes a review a gate rather than a formality
This sourceExplains that a production readiness review functions as a formal go/no-go gate by weighing production readiness and downstream dependencies.
- Weighing readiness against downstream reliance is what makes a review a gate rather than a formality
- Summary-Diff Review
- The discipline is that each material change gets a named owner and an explicit re-sign-off, never a bulk approve — the review exists precisely because a one-word change like "shall" versus "may" can change an obligation while looking like a typo fix.
This sourceRequires requirements changes to pass through a documented review and approval cycle under formal configuration control.
- The discipline is that each material change gets a named owner and an explicit re-sign-off, never a bulk approve — the review exists precisely because a one-word change like "shall" versus "may" can change an obligation while looking like a typo fix.
- Transition Readiness Review
- Its strength is that it forces evidence before commitment: a readiness review of the kind formalized as a Flight Readiness Review
This sourceDescribes formal readiness reviews as evidence-based decision points used to determine whether a system is ready to proceed and to record a go or no-go outcome.
- Its strength is that it forces evidence before commitment: a readiness review of the kind formalized as a Flight Readiness Review
Verification¶
Does it exist? Not checked yet. This entry carries no identifier to resolve. It was extracted from the citation as written in the article, normalized, and deduplicated against the rest of the registry.
Does it back the claim? Not recorded. Neither this nor any other of the 11 citations of this work carries a recorded support check.
Was it audited? Yes. A second, independent pass read the citation against the article text and recorded a verdict.
Support is checked per citation rather than per work — the same source can be cited soundly in one article and wrongly in another. Per-citation recording began recently, so a citation with no recorded check is a gap in the record rather than evidence it went unchecked.
See how references were verified.
Links previously used in the corpus¶
Before the registry existed this work was also linked 2 other ways.
- https://www.nasa.gov/wp-content/uploads/2018/09/nasa_systems_engineering_handbook_0.pdf ×2
- https://ntrs.nasa.gov/api/citations/20170001761/downloads/20170001761.pdf ×1
Registry ID ref:1b31eb4c5d0c · see in the full table