Software Failure Mode, Effects & Criticality Analysis (SFMECA)

Occasionally, Software Failure Mode, Effects and Criticality Analysis {that's right! SFMECA not SFMEA} is stipulated.

For example, 49CFR238.105 - "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."

Good luck locating guidance on software FMECA elsewhere and
get ready to set fire to your bank if you do go elsewhere!

If you are looking for first-hand insight into this technique, contact us!

You better as yourself this question though: "am I absolutely sure I need to OR want to do this?"