Book A.

Book B.
7150 Requirements Guidance

Book C.

References, & Terms

(NASA Only)

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migration of unmigrated content due to installation of a new plugin
Wiki Markup
1. The Requirement
12. Rationale
23. Guidance
34. Small Projects
45. Resources
56. Lessons Learned
1. The Requirement
Wiki Markup

h1. 1. Requirements For safety-critical software, the project shall develop a software safety plan.

h2. {color:#003366}{*}1.1 Notes{*}{color}

The requirement for the content of the software safety plan (whether stand-alone or condensed into one or more project level or software documents) is defined in Chapter 5 \[section 5.1.9 of NPR 7150.2, NASA Software Engineering Requirements\]. NASA-STD-8719.13 \[NASA Software Safety Standard\] contains detailed requirements {sweref:271} and guidance on development of software safety plans. Software engineering and the software safety disciplines jointly are responsible for providing project management with the optimal solution for software to meet the engineering, safety, quality, and reliability needs of the project.

Typically, Class F through H software is not considered safety critical; however, a piece of non-engineering software (Class F through H) could have a safety critical nature to it. One example is an emergency notification system for natural disasters. In this example, if the software did not work it could result in loss of life or injury or significant impact to assets. For this reason, this requirement includes applicability for safety critical Class F through H.

h2. 1.2 Applicability Across Classes

This requirement applies to all classes and safety criticalities _including_ _safety critical_ _Class F thru H,_ with exceptions noted in the following table:
Wiki Markup

h1. 2. Rationale

The project team creates the Software Safety Plan to define the processes, risks, resources, stakeholders, interfaces, and safety design methodologies, necessary for the development of the software. The development of this plan allows for the review and agreement of the approach prior to implementation. NASA-STD-8719.13 {sweref:271} defines the contents of the Software Safety Plan.

Effective planning assures that adequate safety features are included within the system and software. Developing a plan early in the project ensures that software safety will be an integral part of the software development or acquisition process.
Wiki Markup

h1. 3. Guidance

NASA-STD-8719.13 {sweref:271}defines the contents of the Software Safety Plan, and identifies who approves/concurs on it.  The format for a Software Safety Plan  is not mandated by this NPR or NASA-STD-8719.13.  The project team checks with the Center's Safety and Mission Assurance (S&MA) organization for possible format requirements. 

Based on the size and complexity of a project, the Software Safety Plan can be an independent document or part of another software document, such as a Software Assurance Plan, software development plan, or a software management plan.

If a project transitions from non-safety-critical to safety-critical, the project team will need to create the Software Safety Plan that includes the past, the transition, and the forward plan for meeting software safety requirements.

*{+}Best practices{+}*

Because the Software Safety Plan covers the life cycle of the project, it is periodically evaluated as the project matures, to verify accuracy and continued implementation approaches. Typically, the project and the responsible software assurance engineer perform the evaluation at major milestone reviews. See [Topic 7.8 - Maturity of Life Cycle Products at Milestone Reviews|7.8 - Maturity of Life Cycle Products at Milestone Reviews] to determine the state of maturity of the Software Safety Plan at the various Milestone Reviews.
Wiki Markup

h1. 4. Small Projects

For small projects, the safety plan may be part of an overall project management plan.
Wiki Markup

h1. 5. Resources


Wiki Markup

h1. 6. Lessons Learned

No lessons learned have currently been identified for this requirement.