Software Failure Mode, Effects & Criticality Analysis (SFMECA)
Occasionally, Software Failure Mode, Effects and Criticality Analysis
is stipulated.
For example, 49CFR238.105 states:
"The hardware and software safety program shall be based on a formal
safety methodology that includes a Failure Modes, Effects, Criticality Analysis (FMECA); verification and
validation testing for all hardware and software components and their interfaces;
and comprehensive hardware and software integration testing to ensure that the hardware and software system
functions as intended."
As another example, a client of ours received a SOW which called for SFMECA per MIL-STD-1629A. Yeah, right!
SFMECA is not straight-forward!
Good luck locating guidance on software FMECA elsewhere.
FACT:
get ready to set fire to your bank if you do go elsewhere!
FACT: HCRQ is the de facto information source regarding SFMECA and SFMEA.
If you are looking for first-hand insight into this technique, contact our help desk!