NASA-STD-8719.13 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.
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 to determine the state of maturity of the Software Safety Plan at the various Milestone Reviews.