These account for <30% and are exhaustive to find
Sounds good, but it isn't good. This is how you analyze hardware, not software.
Only about 9% of all defects originate in a single shall statement. Very expensive. It's more efficient to run requirements analyzers.
Other classes skimp on the root causes or teach a boilerplate of 5 or 6 causes that aren't really tagged to most failures
Other classes show hardware-centric approaches for estimating occurrence that don't work
Other classes focus only on reliability or safety
That's where most failure modes originate, AND where they are the easiest to see
We built the Common Defect Enumeration list from the unique root causes behind hundreds of thousands of failures
We spent 35 years refining our approach on real software-intensive systems, reducing analysis time while increasing effectiveness.
We show how to do ONE software FMEA for both safety and reliability
No one has more experience performing effective software FMEAs on mission- and safety-critical systems than we do.
We have demonstrated, through dozens of real-world programs, that you can generate an effective FMEA in two weeks or less with a multi-functional team.
With your knowledge of software bugs, you are a key contributor to the software FMEA. You understand the effects of seemingly minor issues. Modules 2 and 4 will help you develop good test procedures for fault injection. Modules 1 and 3 will help you and the rest of the team connect the dots between defects and mission, as well as safety hazards.
Other methods cause you to be late in developing your software. This one doesn't. You will find oodles of potential design issues and understand how those issues can wreak havoc in the field. Module 4 demonstrates how to utilize CDE to enhance your design and mitigate technical debt in the future.
This is the fastest way to complete software FMEAs and not be behind schedule in a rapid agile environment.
The software FMEA is a great way to start a software safety hazards analysis. In fact, if you join forces with the other team members, you can do one software FMEA that covers both safety and availability failures.