The software safety hazards analysis training class covers the application of Common Defect Enumerations to safety-critical software. These methods shown in this class can be applied in any industry for any software safety hazards analysis. The Common Defect Enumeration doesn’t replace a subject matter expert. However, it provides a structured list of things that have historically contributed to safety and mission failures. These are approaches for software safety hazards analysis that aren’t as effective
These account for <30% and are exhaustive to find
By the time you have this data, the project can already be late due to resource misallocation
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
Our classes assume there aren't any unknown hazards
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
Sometimes the most significant hazard isn't on the PHA
Built from the hazard causes that are most likely to occur. Built on viewpoints that uncover most hazard causes.
Complies with Mil-Std-882E, NATA AOP-52, and the Joint Software Systems Engineering Handbook.
After completing this training class, the student will be able to conduct both safety hazards analysis and software FMEA. The student can also combine the software for FMEA safety with the software for FMEA reliability.