Software FMEA training

Software FMEA Training

In person, virtual self – guided, virtual instructor – guided, DVD

Software FMEA training covers effective methods for identifying software failure modes while cost-effectively addressing them. This class covers the top level, capability level, requirement level, and interface level failure modes as documented in the Common Defect Enumeration. Students will learn how to identify the software failure modes and assess the effects, controls, and likelihood. Most importantly, students will learn how to tailor the software FMEA to be both cost and time-effective. The class includes several real mission-critical examples. This class is appropriate for software engineers, systems engineers, software test engineers, and reliability engineers.

$ 500

VIRTUAL SELF - GUIDED
Complete example of top level and capability level failure modes for a real mission and safety critical system
A great way to kick start the training process
Illustrates that the FMEA identified critical failure modes before the code is even written

$ 1450

VIRTUAL SELF - GUIDED
Common Defect Enumerations that apply to the entire software system that are often overlooked
How to tailor the FMEA
How to assess likelihood, severity and tag the failure modes to hazards and failures
How to track the failure modes to closure

Knowledge Base

We wrote the book on software FMEAs. We have analyzed the root causes of hundreds of thousands of software failures.

Compliant

This training complies with the IEEE 1633 Recommended Practices for Software Reliability.

Flexible

The self guided training is can be taken on your schedule. The DVD option is also very flexible.

Cost Effective

The FMEA is built on the Common Defect Enumeration to ensure that the analysis stays targeted on the failure modes and root causes most likely to occur.

These approaches are popular – but ineffective – because they have faulty assumptions about how software fails:

Analyze each line of code for failure. This isn’t effective because software failures can be caused by several lines of codes or even lines of code that are missing. The majority of software failures originate before the code is even written. Analyzing code line by line is most expensive with least return on investment. It is used in cases in which it is known that the function has a particular defect and the effects need to be understand.
Analyze each CSCI as a black box. The hardware centric black box approach doesn’t work well for software because it fails due to functional causes.
Analyze each requirement for hundreds of failure modes. This isn’t cost effective because one individual specification may lead to a failure but typically it is the collection of specifications that result in a failure. The number of root causes that apply to a single specification are relatively small. This approach is used in sparyingly and conjunction with tools that analyze problems with software requirement language.

Related references

Effective application of software failure modes effects analysis

The Common Defect Enumeration

Additional modules/ DVD option

$ 1700

VIRTUAL SELF - GUIDED
The Common Defect Enumerations for the capability level
The Common Defect Enumerations for the software requirement level
How to apply the software FMEA for one particular feature, use case or capability
How to apply the software FMEA to specific software requirement statements