United States

NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2)

189 controls. 0 other frameworks in our corpus share controls with it. Here is all of it, and how much of it you are already doing.

Page built . This page is derived from the framework corpus, which changes when the corpus is extended rather than daily.

189 controls 0 frameworks share controls with it United States verified against its source document

Every control below is one this framework asks for. The right hand column counts how many other frameworks in our corpus carry the same control, which is the difference between doing this work once and doing it again for the next standard.

There is no implementation kit for this framework yet. The control list and the overlap above are free and complete.

What you already have

Frameworks whose controls overlap this one, most first. If you run any of them, the count is roughly what you have already evidenced.

No measured overlap with another framework in the corpus.

Every control

CodeControlAlso in
1.1Purpose of the systems engineering handbook0
1.2Scope and depth of the handbook0
2.1Common technical processes and the SE engine0
2.2SE engine use across project phases0
2.3Worked example of engine use by phase0
2.4Verification and validation compared0
2.5Cost effectiveness and design tradeoffs0
2.6Human systems integration in systems engineering0
2.7Competency model for systems engineers0
3.1Program Formulation phase purpose and reviews0
3.10Budget cycle reference only0
3.11Tailoring and customization of NPR requirements0
3.2Program Implementation phase purpose and reviews0
3.3Pre-Phase A concept studies phase0
3.4Phase A architecture and technology development0
3.5Phase B baseline and preliminary design0
3.6Phase C final design and fabrication0
3.7Phase D assembly, integration, test and launch0
3.8Phase E operations and sustainment0
3.9Phase F closeout and disposal0
4.0System design processes chapter overview0
4.1Stakeholder expectations definition process0
4.1.1.1Inputs to stakeholder expectations0
4.1.1.2.1Identify stakeholders0
4.1.1.2.10Capture work products0
4.1.1.2.2Understand stakeholder expectations0
4.1.1.2.3Identify needs, goals and objectives0
4.1.1.2.4Concept of operations and support strategy development0
4.1.1.2.5Define stakeholder expectations in acceptable statements0
4.1.1.2.6Analyze expectation statements for measures of effectiveness0
4.1.1.2.7Validate bidirectional traceability of expectations0
4.1.1.2.8Obtain stakeholder commitments to validated expectations0
4.1.1.2.9Baseline stakeholder expectations0
4.1.1.3Outputs of stakeholder expectations definition0
4.2Technical requirements definition process overview0
4.2.1.1Inputs to requirements definition0
4.2.1.2.1Define constraints and functional expectations0
4.2.1.2.2Define the complete requirement set0
4.2.1.2.3Write requirements as acceptable statements0
4.2.1.2.4Validate the technical requirements0
4.2.1.2.5Define measures of performance and technical performance0
4.2.1.2.6Baseline the technical requirements0
4.2.1.2.7Capture work products and decisions0
4.2.1.3Outputs of requirements definition0
4.3Logical decomposition process overview0
4.3.1.1Inputs to logical decomposition0
4.3.1.2.1Define logical decomposition models0
4.3.1.2.2Allocate requirements, resolve conflicts, baseline0
4.3.1.2.3Capture logical decomposition work products0
4.3.1.3Outputs of logical decomposition0
4.4Design Solution Definition process overview0
4.4.1.1Inputs to design solution definition0
4.4.1.2.1Define alternative design solutions0
4.4.1.2.10Baseline the design solution0
4.4.1.2.2Create alternative design concepts0
4.4.1.2.3Analyze each alternative design solution0
4.4.1.2.4Select the best design solution alternative0
4.4.1.2.5Increase the resolution of the design0
4.4.1.2.6Fully describe the design solution0
4.4.1.2.7Verify the design solution0
4.4.1.2.8Validate the design solution0
4.4.1.2.9Identify enabling products0
4.4.1.3Outputs of design solution definition0
5.0Product realization chapter overview0
5.1Product implementation process overview0
5.1.1.1Inputs to product implementation0
5.1.1.2.1Prepare to conduct implementation0
5.1.1.2.2Purchase, make, or reuse the product0
5.1.1.2.3Capture implementation work products0
5.1.1.3Outputs from product implementation0
5.2Product Integration Process Overview0
5.2.1.1Product Integration Process Inputs0
5.2.1.2.1Prepare to Conduct Product Integration0
5.2.1.2.2Obtain Lower-Level Products for Integration0
5.2.1.2.3Confirm Received Products Are Validated0
5.2.1.2.4Prepare the Integration Environment0
5.2.1.2.5Assemble and Integrate Received Products0
5.2.1.2.6Prepare Product Support Documentation0
5.2.1.2.7Capture Product Integration Work Products0
5.2.1.3Product Integration Process Outputs0
5.3Product verification process overview0
5.3.1.1Inputs to product verification0
5.3.1.2.1Prepare to conduct product verification0
5.3.1.2.2Perform product verification0
5.3.1.2.3Analyze verification results and report0
5.3.1.2.4Capture product verification work products0
5.3.1.3Outputs from product verification0
5.4Product validation process overview0
5.4.1.1Inputs to product validation0
5.4.1.2.1Preparing for product validation0
5.4.1.2.2Performing product validation0
5.4.1.2.3Analysing validation results0
5.4.1.2.4Validation reporting and work product capture0
5.4.1.3Outputs of product validation0
5.5Product transition process overview0
5.5.1.1Inputs to product transition0
5.5.1.2.1Prepare to conduct transition0
5.5.1.2.2Prepare receiving site for product0
5.5.1.2.3Prepare product for safe transition0
5.5.1.2.4Transition and install the product0
5.5.1.2.5Capture transition work products0
5.5.1.3Outputs from product transition0
6.0Crosscutting technical management processes overview0
6.1Technical planning process overview0
6.1.1.1Technical planning inputs0
6.1.1.2.1Technical planning preparation and planning strategy0
6.1.1.2.2Define the technical work and contingency0
6.1.1.2.3Schedule, organize and budget the technical effort0
6.1.1.2.4Prepare SEMP, verification and validation plans0
6.1.1.2.5Obtain stakeholder commitments to technical plans0
6.1.1.2.6Issue technical work directives0
6.1.1.2.7Capture technical planning work products0
6.1.1.3Technical planning outputs0
6.2Requirements management scope and purpose0
6.2.1.1Inputs to requirements management0
6.2.1.2.1Preparing to manage requirements0
6.2.1.2.2Running requirements management0
6.2.1.2.3Recording bidirectional requirements traceability0
6.2.1.2.4Evaluating and approving requirement changes0
6.2.1.2.5Avoiding requirement creep and assessing change impact0
6.2.1.2.6Capturing requirements management work products0
6.2.1.3Outputs of requirements management0
6.3Interface management process overview0
6.3.1.1Inputs to interface management0
6.3.1.2.1Prepare or update interface management procedures0
6.3.1.2.2Interface management during system design0
6.3.1.2.3Interface management during product integration0
6.3.1.2.4Conduct interface control0
6.3.1.2.5Capture interface management work products0
6.3.1.3Outputs of interface management0
6.4Technical risk management scope and risk concept0
6.4.1.1Inputs to technical risk management0
6.4.1.2.1Preparing the technical risk management strategy0
6.4.1.2.2Identifying technical risks continuously0
6.4.1.2.3Assessing technical risk through both decision strands0
6.4.1.2.4Preparing for technical risk mitigation0
6.4.1.2.5Monitoring technical risk status periodically0
6.4.1.2.6Implementing mitigation and contingency actions0
6.4.1.2.7Capturing technical risk management work products0
6.4.1.3Outputs of technical risk management0
6.5Configuration management process overview0
6.5.1.1Inputs to configuration management0
6.5.1.2.1Plan and resource the configuration management effort0
6.5.1.2.2Select configuration items and establish baselines0
6.5.1.2.3Operate the configuration control board0
6.5.1.2.4Maintain configuration status accounting0
6.5.1.2.5Conduct functional and physical configuration audits0
6.5.1.2.6Capture configuration management work products0
6.5.1.3Outputs of configuration management0
6.6Technical Data Management process overview0
6.6.1Process description and flow0
6.6.1.1Inputs to technical data management0
6.6.1.2Plan data management and assign responsibility0
6.6.1.2.1Prepare for data management implementation0
6.6.1.2.2Collect and store technical data0
6.6.1.2.3Provide data to authorized parties0
6.6.1.3Outputs of technical data management0
6.6.2Technical data management guidance pointer0
6.7Technical Assessment process overview0
6.7.1.1Inputs to technical assessment0
6.7.1.2.1Prepare strategy for technical assessments0
6.7.1.2.2Assess productivity and quality, conduct reviews0
6.7.1.2.3Capture work products and lessons learned0
6.7.1.3Outputs of technical assessment0
6.8Decision analysis process overview0
6.8.1.1Inputs triggering decision analysis0
6.8.1.2.1Define criteria for evaluating alternatives0
6.8.1.2.2Identify alternative solutions for the decision0
6.8.1.2.3Select evaluation methods and tools0
6.8.1.2.4Evaluate alternatives against criteria and methods0
6.8.1.2.5Recommend a solution and report to decision maker0
6.8.1.2.6Report analysis results to stakeholders0
6.8.1.2.7Capture decision analysis work products0
6.8.1.3Alternative selection and decision support outputs0
APP-CAppendix C: Checklist for writing good requirements0
APP-DAppendix D: Requirements verification matrix example0
APP-EAppendix E: Building a validation plan and matrix0
APP-GAppendix G: Technology assessment and insertion guidance0
APP-HAppendix H: Integration plan outline0
APP-IAppendix I: Verification and validation plan outline0
APP-JAppendix J: SEMP content outline structure0
APP-KAppendix K: Expected maturity of key technical plans0
APP-LAppendix L: Interface Requirements Document outline0
APP-MAppendix M: Configuration Management Plan outline topics0
APP-NAppendix N: Technical peer reviews guidance relocated0
APP-PAppendix P: SOW review checklist relocated0
APP-RAppendix R: HSI Plan content outline0
APP-SAppendix S: Concept of Operations annotated outline0
APP-TAppendix T: Systems engineering during operations phase0

Tell me when NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2) files something new

One email when a public company newly discloses something this framework governs, naming the company and what our corpus says it puts in scope. Nothing else, and one click to stop.

What this page is

A control-level reference for NASA Systems Engineering Handbook (NASA/SP-2016-6105 Rev 2), drawn from our framework corpus. Control codes and titles are references to the standard, not reproductions of it. The overlap counts and the auditor artefacts are our own work and are the part you will not find elsewhere.

Measure this against what you already run · All frameworks · Today's edition