Application of FMEA (Failure Modes and Effects Analysis) to software allows organizations to anticipate defects before they occur.
This is important because it allows organizations to build in quality into their software products.
FMEA 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.
Failure Modes and Effects Analysis can be performed at System Level and at Network Element/Component level. The High level process steps for performing Software FMEA generally follow these steps:
- Planning for System Software FMEA
- Train and familiarize the team with traditional FMEA process
- Cause and Effect Analysis
- Identifying Potential Failure Modes
- Assigning original RPN ratings pre-risk mitigation
- Assigning resulting RPN ratings post-risk mitigation
- Conduct Software System, Software Sub-system (Network Element level), or Software Component (Sub-sub-system Level) Failure Modes Analysis, as required.
- Collect appropriate metrics to analyze Return on Investment (ROI) on the Software FMEA effort
Want to learn more? Tonex offers Software FMEA Training, a 2-day course that covers all the steps, techniques, and tools necessary to develop and execute a software FMEA.
Software FMEA 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.
Tonex also offers several other courses in FMEA, such as:
For more information, questions, comments, contact us.