Page History
| Alias | ||
|---|---|---|
|
...
| id | tabs-1 |
|---|
1. Requirements
2.2.8.3 The project, in conjunction with the Safety and Mission Assurance organization, shall determine the software safety criticality in accordance with NASA-STD-8739.8.
1.1 Notes
...
1.2 Applicability Across Classes
...
| f | 1 |
|---|---|
| g | 1 |
| h | 1 |
| asc | 1 |
| ansc | 1 |
| bnsc | 1 |
| csc | 1 |
| bsc | 1 |
| esc | 1 |
| cnsc | 1 |
| dsc | 1 |
| dnsc | 1 |
| ensc | 1 |
...
| id | tabs-2 |
|---|
2. Rationale
...
| id | tabs-3 |
|---|
3. Guidance
...
The software safety criticality assessment process and the location of the assessment results are documented within the Software Safety Plan (or equivalent). Most projects document the software safety criticality with the software classification. The project's system safety documentation also addresses it.
...
| Div | ||
|---|---|---|
| ||
4. Small ProjectsNo additional guidance is available for small projects. The community of practice is encouraged to submit guidance candidates for this paragraph. |
...
| id | tabs-5 |
|---|
5. Resources
...
| toolstable |
|---|
...
| id | tabs-6 |
|---|
6. Lessons Learned
A documented lesson from the NASA Lessons Learned database notes the following:
...
