California DMV database modernization project failure
The California DMV spent seven years and $44 million trying to merge its driver's-license and vehicle-registration databases onto a new system, then scrapped the entire project without a working replacement.
The damage was public. The root cause was preventable.
The California DMV spent seven years and $44 million trying to merge its driver's-license and vehicle-registration databases onto a new system, then scrapped the entire project without a working replacement.
What the software actually got wrong
State auditors found the DMV continued pouring money into the project without first resolving known technical and performance problems, and the finished software could not perform basic lookups reliably and ran up to ten times slower than the decades-old system it was meant to replace.
State auditors found the DMV continued pouring money into...
State auditors found the DMV continued pouring money into the project without first resolving known technical and performance problems
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.
The finished software could not perform basic lookups reliably...
the finished software could not perform basic lookups reliably and ran up to ten times slower than the decades-old system it was meant to replace
Requs AI Software FMEA traces this failure mode back to the system-level hazard it feeds, tagging it against the Common Defect Enumeration so it surfaces in review instead of in the field.
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.