Print Friendly, PDF & Email

Software Failure Modes Effects Analysis Training, Software FMEA Training course

FMEA, Failure Modes and Effects Analysis, is a proactive approach to defect prevention and can be applied to the software development process.

Failure Modes and Effects Analysis, 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 has several objectives. These include:

  • Identifying and mitigating single point failures that can result in catastrophic failures
  • Analyzing interfaces in addition to functions
  • Analyzing output variables
  • Identifying missing software requirements
  • Identifying software response to hardware anomalies

Similar to System FMEAs, software system FMEAs should be performed early in the design process, as soon as the software design team has determined initial software architecture and transferred the functional requirements to the software design.

Software FMEAs at the detail-level are typically done later in the software design process, when detailed design description and preliminary code exists.

Software FMEA teams generally follow a specific “to-do” list to make sure software accomplishes its functions and is fail-safe. The procedure normally goes something like this:

  • Design out the failure mode
  • Use redundancy to achieve fault tolerance
  • Go into fail-safe mode
  • Implement early prognostic warning
  • Implement training to reduce risk for human error

When following these steps, software FMEA professionals need to focus on potential hazardous outcomes as well as paying special attention to identify any need for new or modified software requirements.

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

Audience

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.