SOFTWARE FAILURE MODE AND EFFECTS ANALYSIS (SFMEA)

The application of Failure Mode and Effects Analysis (FMEA) to software (SFMEA) was first proposed in 1979.

Since that time, SFMEA, sometimes known as Software Error Effect Analysis (SEEA), has been refined and applied successfully at functional, interface and detailed levels.

Some of the approaches taken to SFMEA; however, are flawed.

Software FMEA has also been useful in conjunction with requirements analysis.

Extreme caution is advised as this technique, in the wrong hands, will burn investment dollars at a rapid rate and provide little "bang for the buck".

HCRQ has years of experience applying SFMEA.  In addition, we teach SFMEA in our Software Safety Course and in our SFTA & SFMEA Webinar.  Attendees from both the customer side and the contractor side come from around the world.

Occasionally, Software Failure Mode, Effects and Criticality Analysis {that's right, SFMECA not SFMEA} 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.

SFMECA is not straight-forward.  HCRQ conceived an approach to comply with the requirement for SFMECA should it be impossible to escape from.

HCRQ has over 33 years experience in SFMEA.  We wrote the book.