NORAD 1980 false missile-attack alarms
US strategic nuclear forces were briefly placed on alert after early-warning computers twice indicated a large-scale Soviet missile attack was underway, false alarms serious enough to prompt an emergency review of US nuclear command-and-control systems.
The damage was public. The root cause was preventable.
US strategic nuclear forces were briefly placed on alert after early-warning computers twice indicated a large-scale Soviet missile attack was underway, false alarms serious enough to prompt an emergency review of US nuclear command-and-control systems.
What the software actually got wrong
A hardware chip fault in a communications component caused test data used to simulate missile-attack scenarios for training to be intermittently substituted into the live data feed monitored by warning-system operators, and the systems' design did not clearly and reliably distinguish test data from real, live attack data.
A hardware chip fault in a communications component caused...
A hardware chip fault in a communications component caused test data used to simulate missile-attack scenarios for training to be intermittently substituted into the live data feed monitored by warning-system operators
Requs AI Edge Case flags this exact pattern at the requirements and architecture stage — before a single line of code implementing it exists — so the assumption behind it gets challenged while it is still cheap to fix.
The systems' design did not clearly and reliably distinguish...
the systems' design did not clearly and reliably distinguish test data from real, live attack data
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
Beyond code coverage and "shall" testing
Root causes like this one rarely show up in code coverage or requirements-compliance testing, because nobody wrote a requirement anticipating the specific edge case that broke. Requs AI Edge Case and Requs AI Software FMEA are built to surface exactly this class of overlooked failure mode — before the software is written.
Surfaces this before code exists
Identifies edge cases like this one at requirements and architecture time, using the Common Defect Enumeration to catalog failure patterns seen across hundreds of real-world software failures — including this one.
Connects the failure mode to the hazard
Traces this class of root cause directly to the system-level hazard it can produce, so a defect pattern like this one gets flagged during design review instead of after it ships.
Find the overlooked root causes before they ship.
Schedule a demonstration, or explore how Requs AI Edge Case and Software FMEA use the Common Defect Enumeration.