Software Project Management Plan Software Configuration Management Plan Software Assurance Plan Software Requirements Specification Software Design Documentation Verification and Validation Plan Version Description Documentation Safety Analyses and Reports Test Documentation User Documentation and Procedures Operations and Maintenance Plan Risk Plans, Analyses and Reports Retirement/Replacement Plan The provider SMA shall have approval authority over the type and distribution (single or multiple software, system, or facility documents) of documentation which contain provider software safety requirements (process and technical). [SSS-009] This allows smaller projects to combine documentation without losing the benefit of provider SMA approval. SMA is seen as co-approval authority on documents that flow down software safety requirements. The acquirer SMA shall have approval authority over the type and distribution (single or multiple software, system, or facility documents) of documentation which contain acquirer software safety requirements (process and technical). [SSS-010] This allows smaller projects to combine documentation without losing the benefit of acquirer SMA approval. SMA is seen as co-approval authority on documents that flow down software safety requirements. Safety Requirements Traceability Traceability is a link or definable relationship between two or more entities. Requirements are linked from more general form (e.g., the system specification) to their more explicit form (e.g., subsystem specifications). They are also linked forward to the design, source code, and test cases. Because many software safety requirements are derived from the system safety analysis, risk assessments, or organizational, facility, vehicle, system specific generic hazards, these requirements; these will also be linked (traced) from those specific safety data products (examples include safety analysis, reliability analysis, etc.).
Software Project Management Plan Software Configuration Management Plan Software Assurance Plan Software Requirements Specification Software Design Documentation Verification and Validation Plan Version Description Documentation Safety Analyses and Reports Test Documentation User Documentation and Procedures Operations and Maintenance Plan Risk Plans, Analyses and Reports Retirement/Replacement Plan The provider SMA shall have approval authority over the type and distribution (single or multiple software, system, or facility documents) of documentation which contain provider software safety requirements (process and technical). [SSS-009] This allows smaller projects to combine documentation without losing the benefit of provider SMA approval. SMA is seen as co-approval authority on documents that flow down software safety requirements. The acquirer SMA shall have approval authority over the type and distribution (single or multiple software, system, or facility documents) of documentation which contain acquirer software safety requirements (process and technical). [SSS-010] This allows smaller projects to combine documentation without losing the benefit of acquirer SMA approval. SMA is seen as co-approval authority on documents that flow down software safety requirements. Safety Requirements Traceability Traceability is a link or definable relationship between two or more entities. Requirements are linked from more general form (e.g., the system specification) to their more explicit form (e.g., subsystem specifications). They are also linked forward to the design, source code, and test cases. Because many software safety requirements are derived from the system safety analysis, risk assessments, or organizational, facility, vehicle, system specific generic hazards, these requirements; these will also be linked (traced) from those specific safety data products (examples include safety analysis, reliability analysis, etc.).
nasa-std-8719.13c_0.docx