Print Friendly, PDF & Email

Software Failure Modes Effects Analysis Training, Software FMEA

Software FMEA Training is a 2-day course where participants learn to identify the defects that hardware control methods such as redundancy cannot address. Participants also learn how to prepare an SFMEA as well as how to follow SFMEA steps.


Mission Critical Software FMEA Workshop by Tonex

Application of FMEA (failure modes and effects analysis) to software allows software engineers to anticipate defects before they occur, which allows building a higher level of quality into software products.

Software FMEA generally involves structured brainstorming to analyze potential failure modes in software, rate and rank the risk to the software and take appropriate actions to mitigate the risk.

This process is used to improve software quality, reduce Cost of Quality (CoQ), Cost of Poor Quality, (CoPQ) and defect density.

Software FMEA can result in significant cost savings by detecting defects early that would have otherwise been detected in the test phases or by the customer.

Studies show that the later a defect is detected, the more the cost – up to $70,000 per defect.

There are many scenarios when software FMEA can be used. For example, software FMEA is useful when a process, product, or service is being designed or redesigned, after quality function deployment (QFD).

Software FMEA should be used when an existing process, product, or service is being applied in a new way or before developing control plans for a new or modified process.

Many software engineers also employ an FMEA approach when improvement goals are planned for an existing process, product, or service as well as when analyzing failures of an existing process, product, or service.

Then again, FMEA is exceptionally useful periodically throughout the life of the process, product, or service.

Software FMEA can be performed at system level and at network element/component level.

Experts in this field contend that earlier detection of defects is a paradigm change, but may not be obvious to software managers or leaders.

Consequently, with results from a software FMEA, software matter personnel are armed with information that can help convince senior leaders and management to commit to making necessary adjustments in software before it is released to the public.

Software FMEA Training Course by Tonex

Software failure modes effects analysis training, software FMEA training course covers all the steps, techniques, and tools necessary to develop and execute a software FMEA. SFMEA training course will also teach you to perform software reliability failure modes and root causes associated with the standards, interface design, detailed design and code, vulnerabilities, corrective actions, serviceability, applicability, and processes.

The use of Failure Mode and Effects Analysis (FMEA) in software (SFMEA) was projected in 1979 for the first time. Since then, SFMEA, which also is often called as Software Error Effect Analysis (SEEA), has been modified and employed effectively at functional, interface and detailed levels. Software FMEA has also come in handy in combination with requirements analysis.

Software FMEA Viewpoints

  • Functional
  • Interface
  • Detailed
  • Production
  • Maintenance
  • Usage

What Do You Gain from Applying Software FMEA?

  • Effective requirements, design, and code reviews
  • Software single point failure identification
  • Identification of the defects that hardware control methods such as redundancy cannot address
  • Identification of the abnormal behaviors that requirements or design specifications missed
  • Unwritten assumption identification
  • Identification of the specifications that require fault handling design

Who Would You Need in Your Software FMEA Team?

  • Facilitator: who understands the SFMEA process
  • Software manager: accountable for the software project
  • Software engineers:
    • One engineer for functional SFMEA
    • One engineer for interface SFMEA
    • Once engineer for detailed SFMEA
  • Domain experts: knowledgeable about the application of the software and what features are critical to the end-users

Software FMEA Limitations

  • The success of SFMEA depends on the amount of experience of the analyst with the system under development
  • The results depends on where the analyst look for possibilities of failure modes
  • Depends on the adequate software requirements and design
  • Most effective when the riskiest software with the most failure modes is being focused on
  • Not successful when it is applied too early or too late, timing matters a lot

Software vs Hardware FMEA

  • Software FMEA is assessed through different “viewpoints” than the hardware
  • Software has its specific failure modes
  • A software FMEA can evaluate how software responds to a hardware failure

Applications of Software FMEA

  • Software components
  • Firmware components
  • The interfaces of Commercial Off The Shelf
  • The interfaces of Free Open Source Software
  • Government Furnished Software
  • New and currently existing codes


Software FMEA training is a 2-day course designed for:

  • Reliability engineers
  • Software engineers
  • Systems engineers
  • All individuals involved with identifying risks associated with software related failure modes

What Will You Learn?

Below are the major topics Software FMEA training will cover (more details can be found under the full course description):

  • Overview
  • Introduction to Failure Analysis (FA)
  • Preparing the SFMEA
  • SFMEA Steps
  • SFMEA and Software Quality
  • Analyze the Software Failure Modes and Root Causes
  • Analyze Consequences
  • Generate a Critical Items List (CIL)
  • Tonex Hands-On Workshop Sample

Software Failure Modes Effects Analysis Training

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.