Mizuho Bank repeated system failures
Japan's Mizuho Bank suffered a string of at least 8 major system outages within about a year, disrupting ATMs and transfers for customers; Japan's Financial Services Agency issued a formal business-improvement order and the bank's president resigned.
The damage was public. The root cause was preventable.
Japan's Mizuho Bank suffered a string of at least 8 major system outages within about a year, disrupting ATMs and transfers for customers; Japan's Financial Services Agency issued a formal business-improvement order and the bank's president resigned.
What the software actually got wrong
Years of complex, poorly integrated legacy IT systems (the product of a costly, delayed core-banking-system merger project after a 2013 bank merger) left the bank vulnerable to cascading failures whenever hardware faults or capacity limits were hit.
Years of complex, poorly integrated legacy IT systems (the...
Years of complex, poorly integrated legacy IT systems (the product of a costly, delayed core-banking-system merger project after a 2013 bank merger) left the bank vulnerable to cascading failures whenever hardware faults or capacity limits were hit.
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.