October 2014 US Treasury market 'flash rally'
US Treasury bond yields swung dramatically within minutes during a period of thin liquidity, in one of the largest intraday moves in the market's history without any apparent news trigger.
The damage was public. The root cause was preventable.
US Treasury bond yields swung dramatically within minutes during a period of thin liquidity, in one of the largest intraday moves in the market's history without any apparent news trigger.
What the software actually got wrong
A joint report by the Treasury, Federal Reserve, SEC and CFTC found that automated and high-frequency trading algorithms interacting with each other and with thinning liquidity amplified the price swings well beyond what conventional trading would have produced, though no single cause was identified.
A joint report by the Treasury, Federal Reserve, SEC...
A joint report by the Treasury, Federal Reserve, SEC and CFTC found that automated and high-frequency trading algorithms interacting with each other and with thinning liquidity amplified the price swings well beyond what conventional trading would have produced, though no single cause was identified.
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.