Quantitative software failure mode and effects analysis

At least one non-transitory machine-readable medium including instructions for performing a software failure mode and effects analysis (SW FMEA), which when executed by a machine, cause the machine to:

• receive threshold values for safety integrity levels for a software component within a system;
• monitor the software component, wherein to monitor the software component includes to monitor an interaction between the software component and at least one of:
• a second component or a subcomponent;
• determine, based at least in part on a result of the monitoring of the software component, a preliminary risk priority number for the software component, the risk priority number based on a ranking of a possibility of failure of the software component, the ranking determined by a severity, an occurrence likelihood, and a detectability of a failure of the software component;
• compare the preliminary risk priority number to the threshold values to identify a preliminary safety integrity level corresponding to the software component;
• apply a mitigation to the system for the software component, wherein the mitigation is at least one of:
• improving a code in at least one of:
• the software component, the second component, or the subcomponent, swapping at least a portion of at least one of:
• the software component, the second component or the subcomponent, rewriting at least a portion of:
• the software component, the second component or the subcomponent, or changing an interaction between the software component and at least one of the second component or the subcomponent;
• and
• output the preliminary safety integrity level for display.

A method for performing a software failure mode and effects analysis (SW FMEA) comprising:

• receiving, at a processor, threshold values for safety integrity levels for a software component within a system;
• monitoring the software component, wherein monitoring the software component includes to monitor an interaction between the software component and at least one of:
• a second component or a subcomponent;
• determining, based at least in part on a result of the monitoring of the software component, using the processor, a preliminary risk priority number for the software component, the risk priority number based on a ranking of a possibility of a failure of the software component, the ranking determined by a severity, an occurrence likelihood, and a detectability of a failure of the software component;
• comparing the preliminary risk priority number to the threshold values to identify a preliminary safety integrity level corresponding to the software component;
• applying a mitigation to the system for the software component, wherein the mitigation is at least one of:
• improving a code in at least one of:
• the software component, the second component, or the subcomponent, swapping at least a portion of at least one of:
• the software component, the second component or the subcomponent, rewriting at least a portion of:
• the software component, the second component or the subcomponent, or changing an interaction between the software component and at least one of the second component or the subcomponent;
• and
• outputting the preliminary safety integrity level for display.