2008 financial crisis CDO risk-model failure
Mortgage-backed securities rated as extremely safe suffered massive, correlated losses during the 2008 financial crisis, contributing to a global financial meltdown and trillions of dollars in losses.
The damage was public. The root cause was preventable.
Mortgage-backed securities rated as extremely safe suffered massive, correlated losses during the 2008 financial crisis, contributing to a global financial meltdown and trillions of dollars in losses.
What the software actually got wrong
A widely adopted mathematical model (the Gaussian copula function) used across the finance industry to price the risk of mortgage-backed securities systematically underestimated the likelihood that many mortgages would default together during a housing downturn, giving a false sense of safety to instruments that were far riskier than modeled.
A widely adopted mathematical model (the Gaussian copula function)...
A widely adopted mathematical model (the Gaussian copula function) used across the finance industry to price the risk of mortgage-backed securities systematically underestimated the likelihood that many mortgages would default together during a housing downturn, giving a false sense of safety to instruments that were far riskier than modeled.
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.
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.
See real failures this would have caught
Failures like this one can be found before release. See how Requs AI finds them early:
- Software FMEA tool — find failure modes and root causes before code ships
- Software reliability prediction — predict defects before code is written (IEEE 1633)
- Software risk assessment checklist — spot the risks behind failures like this