Secc
The Software Safety Analysis approach concentrates on specific hardware and software components that support Safety Critical Functions. Initially, each software-controlled function will be assessed for criticality and a Safety Critical Functions (SCF) list created.
This process step will ensure that each individual module of code that performs these functions is officially labeled as "safety-critical" and is tracked to ensure that required design, coding and test activities, as appropriate to its assigned safety-criticality level, are accomplished.
Additional guidance that may be used to perform and document these analyses can be found in the IEEE 1228, MIL-STD-882, RTCA DO-178B and RTCA DO-254.
Perform Software Safety Analyses which includes:
Software Safety Requirements Analyses
(SSRA )
Software Safety
Design Analysis (SSDA)
Preliminary Software Safety Design Analysis (PSSDA)
Detailed Software Safety Design Analysis (DSSDA)
Software Safety Code Analysis (SSCA).
Software Safety Test Analysis (SSTA).
Software Safety Change Hazard Analysis (SSCHA
Perform Company Preliminary Design Review (PDR), Detailed Design Review which includes:
Software Safety will participate in software Preliminary Design Reviews (PDRs), detailed design reviews, and Technical Interchange Meetings (TIMs), as needed, to ensure resolution of technical/process issues identified during the software design product evaluation phase.
Coordinate the Software Product Evaluations (SPEs) of the Software Data Requirement Lists (SDRLs) (i.e., SRS, IRS, STP, STD, VDD, STR and SPS) with Supplier Software Safety/SQA. This activity will be conducted by using product review checklists.