Page History
...
| id | tabs-1 |
|---|
1. Requirements
2.2.1.2 For safety-critical software, the project shall develop a software safety plan.
1.1 Notes
...
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.
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:
...
| f | 1 |
|---|---|
| g | 1 |
| h | 1 |
| ansc | 1 |
| asc | 1 |
| bnsc | 1 |
| csc | 1 |
| bsc | 1 |
| esc | 1 |
| cnsc | 0 |
| dnsc | 0 |
| dsc | 1 |
| ensc | 0 |
...
| id | tabs-2 |
|---|
2. Rationale
...
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.
...
| id | tabs-3 |
|---|
3. Guidance
...
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 to determine the state of maturity of the Software Safety Plan at the various Milestone Reviews.
| Div | ||
|---|---|---|
| ||
4. Small ProjectsFor small projects, the safety plan may be part of an overall project management plan. |
...
| id | tabs-5 |
|---|
5. Resources
...
| toolstable |
|---|
| Div | ||
|---|---|---|
| ||
6. Lessons LearnedNo lessons learned have currently been identified for this requirement. |
