Software FMEA Training

Effective Software FMEA Training

Methods proven to work in an agile environment

Traditional FMEA approaches often fail with modern software development. That’s why Mission Ready Software developed a unique and practical approach to Software Failure Mode and Effects Analysis (FMEA) that integrates seamlessly with Agile development. Our software FMEA training methodology focuses on the most common root causes of failure, delivering a superior return on investment.
  • Code view approach

    These account for <30% and are exhaustive to find

  • CSCI black box approach

    Sounds good, but it isn't good. This is how you analyze hardware, not software.

  • One "shall" statement at a time

    Only about 9% of all defects originate in a single shall statement. Very expensive. It's more efficient to run requirements analyzers.

  • Unlikely failure modes/root causes

    Other classes skimp on the root causes or teach a boilerplate of 5 or 6 causes that aren't really tagged to most failures

  • Subjective approaches for occurrence

    Other classes show hardware-centric approaches for estimating occurrence that don't work

  • Narrow hazards focus

    Other classes focus only on reliability or safety

  • Our class focuses on system design and specifications

    That's where most failure modes originate, AND where they are the easiest to see

  • Learn about the likely root causes

    We built the Common Defect Enumeration list from the unique root causes behind hundreds of thousands of failures

  • In our class you learn simple objective methods for estimating occurrence

    We spent 35 years refining our approach on real software-intensive systems, reducing analysis time while increasing effectiveness.  

  • Learn to expand coverage at same cost

    We show how to do ONE software FMEA for both safety and reliability

  • Learn from "the" expert

    No one has more experience performing effective software FMEAs on mission- and safety-critical systems than we do.

  • Proven effectiveness

    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.

Ineffective FMEA software approaches

How stakeholders benefit from effective software FMEA

 

Software test engineers

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.

Software engineers

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.

Software management

This is the fastest way to complete software FMEAs and not be behind schedule in a rapid agile environment.

Safety engineers

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.

The only software FMEA training with real world examples

Example of an effective software FMEA training module

An end to end example
Free
  • VIRTUAL SELF - GUIDED
  • An end to end example of a few failure modes applied to a real example
  • Illustrates that the FMEA identified critical failure modes before the code is even written
  • Illustrates how little work is required to identify big edge cases

How to use the Common Defect Enumeration to jump start the software FMEA

The root causes are key to effective software FMEA
$ 950
  • VIRTUAL SELF - GUIDED
  • Determine which CDEs are relevant for your software and system
  • Learn where to put the CDEs in the FMEA template
  • Learn how to spot the edge cases hiding in plain site

How to tag the CDEs to Effects and Hazards

Feed the edge cases into MBSE and automated tested
$ 500
  • VIRTUAL SELF - GUIDED
  • Connect the dots between the local and system effects
  • Connect the dots between the system effects and safety hazards or mission failures
  • Assess occurrence objectively