Home / Software FMEA / Mitigation
FMEA Step 7 — Mitigation Tab
Mitigation
Mitigating a failure mode typically involves more than a few lines of code — it can touch user manuals, specifications, design, code, and test procedures. A mitigation isn’t complete until it’s verified, which requires a test procedure that explicitly tests the failure mode.
Inputs
The mitigation columns
The Mitigation tab shows each failure mode row, ten to a page.
Column
Description
Read/write
CDE
Unique identifier for a failure mode that caused at least one world failure — see Effects.
Read only
Applicability
Depending on survey responses, some CDEs may not apply to your system — see Effects.
Read only
Potential corrective actions
General recommendations for correcting the CDE. Your software will likely need other corrective actions — use the remaining columns to identify how to mitigate it.
Read only
Corrective actions made
Summarizes the corrective actions taken.
Read only
Changes to user manual, specifications, design, code, test procedures
Five columns capturing what changed in each artifact. These mitigations don’t apply to software: replacing a component with another, or onsite code repair by the end user.
Read only
Closed status
The CDE is closed once all mitigations are made and verified.
Read/Write
Other comments
General comments.
Read/Write
Outputs
Auto-calculated from your survey
Likelihood is auto-calculated from the inputs you provided in the Survey tab. The worksheet can be exported using the Critical to Quality List tab.
Continue the FMEA workflow.
Finally, export the worksheet you need from the Critical to Quality list.