← Back to the 300 Software Failures Timeline
Case Study #142 — 300 Software Failure Case Studies

ASX CHESS replacement project failure

The Australian Securities Exchange abandoned its multi-year project to replace its core clearing and settlement system with a blockchain-based platform after spending hundreds of millions of dollars, delaying the market's critical infrastructure upgrade by years.

2017-2022
When it happened
Finance
Sector
#142 of 300
Ranked by documented impact
01 — What Happened

The damage was public. The root cause was preventable.

The Australian Securities Exchange abandoned its multi-year project to replace its core clearing and settlement system with a blockchain-based platform after spending hundreds of millions of dollars, delaying the market's critical infrastructure upgrade by years.

Finance
Sector affected
2017-2022
Date of the event
#142
Rank in the 300 Software Failure Case Studies
1
Distinct root-cause clause identified below
02 — The Root Cause

What the software actually got wrong

An independent review found the new software was far more complex to build than anticipated and was not sufficiently mature or tested to safely replace the exchange's mission-critical settlement system, forcing ASX to scrap years of blockchain-based development work.

01Root Cause

An independent review found the new software was far...

What Happened

An independent review found the new software was far more complex to build than anticipated and was not sufficiently mature or tested to safely replace the exchange's mission-critical settlement system, forcing ASX to scrap years of blockchain-based development work.

How Requs AI Catches This

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.

03 — How This Gets Caught Before It Happens

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.

Requs AI Edge Case

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.

Requs AI Software FMEA

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.