SOFTWARE SAFETY hazards analysis TRAINING

An effective analysis starts with what really can and will go wrong

The software safety hazards analysis training class covers applying the Common Defect Enumerations to safety-critical software. This 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.  But rather, it provides a structured list of things that have historically cause safety and mission failures.  

These are approaches for software safety hazards analysis that aren’t as effective.

Ineffective software fmea approaches

1. Analyzing each software requirement for failure is ineffective because software safety issues often result from the requirements that should have been stated but weren’t. It’s more effective to analyze the collection or requirements against a complete list of failure modes to determine requirements that must be added or modified to meet safety criteria. Our course shows the standard defect enumerations, including the safety criteria in the NATO and DoD standards for safe software.

2. Analyzing software from a black box perspective isn’t effective because software fails due to defects in the specifications, design, and code. The viewpoint needs to be on functional root causes.

3. One software FMEA is conducted for safety, and another software FMEA is conducted . The FMEA software is highly effective for safety and reliability assessments. It is a bottom-up analysis so that the FMEA can focus on mission and safety. Then, the safety engineers analyze and track the safety hazards while the reliability engineers work on analyzing and tracking the mission hazards. The goal is safe software, especially in safety-critical software.

Software Safety Hazards Analysis Training

Virtual Self -Guided
$ 1500 per student
  • How to not analyze software safety
  • How to use the software FMEA to conduct a safety hazards analysis
  • How the common defect enumeration approach is more effective than analyzing each SRS or each CSCI

Knowledge Base

Our software safety hazards analysis training course  merges a software failure modes effects analysis and a software safety assessment into one analysis.  

Compliant

Complies with Mil-Std-882E, NATA AOP-52, and the Joint Software Systems Engineering Handbook.

Flexible

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

Cost effective

After taking this training class the student can conduct both the safety hazards analysis and the software  FMEA.  The student can also combine the software FMEA for safety with the software FMEA for reliability.

TERMS & CONDITIONS

As per the terms and conditions page of this website, software safety training classes are non-refundable.