MF Global collapse and customer-fund tracking failure
The brokerage MF Global collapsed after risky sovereign-debt bets went bad, and roughly $1.6 billion in customer funds went missing for weeks before being partially recovered.
The damage was public. The root cause was preventable.
The brokerage MF Global collapsed after risky sovereign-debt bets went bad, and roughly $1.6 billion in customer funds went missing for weeks before being partially recovered.
What the software actually got wrong
Regulators and the bankruptcy trustee found MF Global's systems for tracking and segregating customer funds from the firm's own money were inadequate and poorly integrated, so the firm could not reliably identify or prevent customer money being commingled with and consumed by its own trading losses as the crisis unfolded.
Regulators and the bankruptcy trustee found MF Global's systems...
Regulators and the bankruptcy trustee found MF Global's systems for tracking and segregating customer funds from the firm's own money were inadequate and poorly integrated, so the firm could not reliably identify or prevent customer money being commingled with and consumed by its own trading losses as the crisis unfolded.
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.