United States

NASA NPR 7150.2D Software Engineering Requirements

135 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.

135 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
1Purpose, applicability and hierarchy of the directive0
2.2Principles for tailoring the requirements0
6Recommended software documentation contents0
CRequirements mapping matrix0
DSoftware classifications0
SWE-002OCE leads a NASA Software Engineering Initiative0
SWE-003Center Director maintains a plan to advance in-house software engineering capability and monitor contractors0
SWE-004OCE benchmarks each Center's software engineering capability0
SWE-005Center Director establishes and maintains software processes per the directive0
SWE-006Center Director maintains a reliable list of programmes and projects with Class A to D software0
SWE-013Develop, maintain and execute software plans covering the whole life cycle0
SWE-015Establish and maintain software cost estimate models and parameters0
SWE-016Document and maintain a software schedule that coordinates with the project0
SWE-017Plan, track and ensure project-specific software training0
SWE-018Hold regular software schedule reviews with stakeholders and track issues to resolution0
SWE-020Classify each system and subsystem containing software per Appendix D0
SWE-021Project manager updates plans and supplier contracts when software classification changes0
SWE-022Plan and implement software assurance, software safety and IV&V per NASA-STD-8739.80
SWE-023Implement the safety-critical software requirements of NASA-STD-8739.80
SWE-024Track actual results and performance against the software plans0
SWE-027Satisfy the conditions for COTS, GOTS, MOTS, OSS or reused software0
SWE-032Acquire, develop and maintain software from organisations with the required CMMI-DEV rating0
SWE-033Assess software acquisition versus development options0
SWE-034Define and document software acceptance criteria0
SWE-036Establish software processes, documentation plans, deliverables and Government actions on receipt0
SWE-037Define the milestones at which developer progress is reviewed and audited0
SWE-039Require developers to report status and give insight into development and test0
SWE-040Require developers to provide products, traceability, change tracking and nonconformances electronically0
SWE-042Require electronic access to source code in a modifiable format0
SWE-045Participate in joint NASA and developer audits0
SWE-046Require developers to provide a software schedule and updates for review0
SWE-050Establish, record, approve and maintain software requirements as part of the technical specification0
SWE-051Analyse software requirements from flowed-down and derived sources0
SWE-052Perform and maintain bi-directional traceability per software classification0
SWE-053Track and manage changes to the software requirements0
SWE-054Identify, correct and track to closure inconsistencies among requirements, plans and products0
SWE-055Validate requirements against intended performance in the customer environment0
SWE-057Transform the software requirements into a recorded software architecture0
SWE-058Develop, record and maintain a software design that describes the lower-level units0
SWE-060Implement the software design into code0
SWE-061Select, define and adhere to software coding methods, standards and criteria0
SWE-062Unit test the software code0
SWE-063Provide a software version description for each release0
SWE-065Establish and maintain software test plans, procedures, tests and reports0
SWE-066Test the software against its requirements0
SWE-068Evaluate test results and record the evaluation0
SWE-070Use validated and accredited models, simulations and analysis tools for qualification0
SWE-071Keep test and verification plans and procedures consistent with the requirements0
SWE-073Validate the software system on the target platform or a high-fidelity simulation0
SWE-075Plan and implement software operations, maintenance and retirement activities0
SWE-077Deliver the software product with the records needed for operations and maintenance0
SWE-079Develop a software configuration management plan0
SWE-080Track and evaluate changes to software products0
SWE-081Identify the software configuration items and versions to be controlled0
SWE-082Establish procedures for control levels and change authority0
SWE-083Prepare and maintain configuration status records0
SWE-084Perform software configuration audits0
SWE-085Establish procedures for storage, handling, delivery, release and maintenance of deliverable software0
SWE-086Record, analyse, plan, track, control and communicate software risks0
SWE-087Perform and report software peer reviews or inspections of the key products0
SWE-088Run each peer review with checklists, criteria, action tracking and required participants0
SWE-089Record the necessary measurements for each peer review0
SWE-090Establish, record, maintain, report and use software management and technical measurements0
SWE-091Center Director maintains a software measurement repository for Class A, B and C projects0
SWE-092Center Director uses measurement data to monitor capability and improve quality0
SWE-093Analyse measurement data using documented procedures0
SWE-094Provide access to measurement data, analyses and status on request0
SWE-095Center Director reports on the Center's software engineering discipline on request0
SWE-098OCE maintains an Agency-wide process asset library0
SWE-100OCE and Center training organisations provide software engineering training0
SWE-121Document approved tailoring in the controlling plans or procedures0
SWE-125Maintain a requirements mapping matrix against this directive0
SWE-126Technical and institutional authorities assess mapping matrices and tailoring0
SWE-129OCE authorises appraisals against selected requirements0
SWE-131Ensure an IV&V Project Execution Plan is developed, approved, maintained and executed0
SWE-134Build the safe-state and integrity behaviours into safety-critical and mission-critical software0
SWE-135Use static analysis tools during development and test0
SWE-136Validate and accredit the software tools required to develop or maintain software0
SWE-139Comply with the Appendix C requirements for the software classification0
SWE-140Center Director complies with the requirements marked for Centers in Appendix C0
SWE-141Ensure IV&V is performed on the designated categories of projects0
SWE-142Center Director maintains software cost repositories for Class A, B and C projects0
SWE-143Perform a software architecture review on the designated categories of projects0
SWE-144Center Director contributes process assets to the Agency library0
SWE-146Define the approach to automatic generation of source code0
SWE-147Specify reusability requirements to enable future reuse for Government purposes0
SWE-148Evaluate software for reuse and contribute candidates to the NASA sharing system0
SWE-150Engineering, CIO and SMA authorities review and agree all tailored requirements0
SWE-151Software cost estimates meet the stated conditions0
SWE-152OCE periodically reviews project requirements mapping matrices0
SWE-153Designated Engineering Technical Authorities define content requirements for software documents0
SWE-154Identify and plan mitigations for cybersecurity risks in flight and ground software0
SWE-156Perform a software cybersecurity assessment on the software components0
SWE-157Protect communicating software systems against unauthorised access per NASA-STD-10060
SWE-159Test and record the required cybersecurity mitigations0
SWE-174Submit software planning parameters to the Center measurement repository at major milestones0
SWE-176Keep records of classification determinations, mapping matrices and independent assessments for the project's life0
SWE-178Give IV&V access to development artefacts, products, source code and data0
SWE-179Respond to IV&V issues and risks and track them to closure0
SWE-184Include software-related safety constraints, controls, mitigations and assumptions in the requirements0
SWE-185Verify the code meets the secure coding standard using static analysis results0
SWE-186Assure that unit test results are repeatable0
SWE-187Place software items under configuration management before testing0
SWE-189Select, implement, track, record and report code coverage measurements0
SWE-190Verify code coverage by analysing the results of test execution0
SWE-191Plan and conduct regression testing0
SWE-192Verify by test the requirements that trace to hazards0
SWE-193Develop acceptance tests for loaded or uplinked data, rules and code0
SWE-194Verify before delivery that requirements are met, changes implemented and defects resolved0
SWE-195Maintain the software to the standards and processes of its classification0
SWE-196Identify the records and tools to archive and the access procedures for retirement0
SWE-199Monitor measures to ensure performance and functionality requirements will be met0
SWE-200Collect, track and report software requirements volatility metrics0
SWE-201Track and maintain software non-conformances0
SWE-202Define and implement clear severity levels for all software non-conformances0
SWE-203Assess reported non-conformances in all off-the-shelf and reused components0
SWE-204Run closed-loop process assessments for high-severity non-conformances0
SWE-205Determine with SMA whether each software component is safety-critical0
SWE-206Require electronic access to the models, simulations and data used for auto-generation0
SWE-207Identify, record and implement secure coding practices0
SWE-208Chief SMA leads a Software Assurance and Software Safety Initiative0
SWE-209Chief SMA benchmarks Center assurance and safety capability against NASA-STD-8739.80
SWE-210Identify requirements for collecting, reporting and storing adversarial action detection data0
SWE-211Test embedded off-the-shelf and reused components to the same level as custom components0
SWE-212Chief SMA periodically reviews project requirements mapping matrices0
SWE-214Center Director performs the prescribed actions for each type of internal software transfer0
SWE-215Center Director ensures Government rights before internal software sharing or reuse0
SWE-216Center Director ensures catalogued reuse software conforms to NASA software policy0
SWE-217Center Director keeps contributor lists and disclaimer provisions on reuse products0
SWE-218Contracting Officers and Agreement Managers include the required software clauses in every acquisition instrument0
SWE-219Achieve 100 percent MC/DC code test coverage of safety-critical components0
SWE-220Keep safety-critical components at cyclomatic complexity 15 or lower0
SWE-221Chief SMA authorises appraisals against selected requirements0
SWE-222Chief SMA provides for software assurance training0
SWE-223Chief SMA makes the final decision on tailoring of the IV&V requirement0

Tell me when NASA NPR 7150.2D Software Engineering Requirements 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 NPR 7150.2D Software Engineering Requirements, 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