NASA NPR 7150.2D Software Engineering Requirements

Chapter 3: Software management requirements – NASA NPR 7150.2D Software Engineering Requirements

NASA NPR 7150.2D Software Engineering Requirements SWE-220: Keep safety-critical components at cyclomatic complexity 15 or lower

What does SWE-220 require?

Where the project's software includes safety-critical components, the project manager ensures that every identified safety-critical software component has a cyclomatic complexity of 15 or lower; any value above that is reviewed by the project manager or the technical approval authority, who may waive it with a recorded rationale.

Maintained by Gerard Blokdyk

Other controls in Chapter 3: Software management requirements – NASA NPR 7150.2D Software Engineering Requirements

SWE-013 Develop, maintain and execute software plans covering the whole life cycle
SWE-015 Establish and maintain software cost estimate models and parameters
SWE-016 Document and maintain a software schedule that coordinates with the project
SWE-017 Plan, track and ensure project-specific software training
SWE-018 Hold regular software schedule reviews with stakeholders and track issues to resolution
SWE-020 Classify each system and subsystem containing software per Appendix D
SWE-022 Plan and implement software assurance, software safety and IV&V per NASA-STD-8739.8
SWE-023 Implement the safety-critical software requirements of NASA-STD-8739.8

Query this from an agent

The graph holds this control, the 0 it maps to, and the evidence behind each claim, over MCP and REST.

MCP endpoint All NASA NPR 7150.2D Software Engineering Requirements controls