• 1 Status
• 2 Failure Mode
• 3 Effect
• 4 Cause
• 5 Severity
• 6 Occurrence
• 7 Detection
• 8 Mitigation
• 9 Residual Severity
• 10 Residual Occurrence
• 11 Residual Detection
• 12 Affected Documents
• 13 Monitoring

FMEA-001: Silent Data Corruption ¶

1 Status ¶

2 Failure Mode ¶

A record saved while the storage is under pressure is written incompletely, without any error being raised.

3 Effect ¶

The user's data is silently lost or altered; the corruption surfaces much later, when the record is next opened, and cannot be traced back to its cause.

4 Cause ¶

The save path acknowledges the write before the storage layer confirms it, and no checksum protects the record on disk.

5 Severity ¶

9

6 Occurrence ¶

4

7 Detection ¶

6

8 Mitigation ¶

Write through to the storage layer and acknowledge only on its confirmation; add a per-record checksum verified on every read, so a corrupted record is refused instead of shown.

9 Residual Severity ¶

9

10 Residual Occurrence ¶

2

11 Residual Detection ¶

2

12 Affected Documents ¶

13 Monitoring ¶

Checksum verification failures are counted per release; any non-zero count reopens the analysis.