Canada's Phoenix pay system disaster
Canada's new federal payroll system caused under-, over-, or non-payment of tens of thousands of government employees for years; the government has spent over CAD 2.2 billion trying to stabilize and remediate the system.
The damage was public. The root cause was preventable.
Canada's new federal payroll system caused under-, over-, or non-payment of tens of thousands of government employees for years; the government has spent over CAD 2.2 billion trying to stabilize and remediate the system.
What the software actually got wrong
The system was launched without adequate testing against the full complexity of federal pay rules and collective agreements, and cost-cutting measures eliminated experienced compensation staff who might otherwise have caught the software's errors before they reached employees' paychecks.
The system was launched without adequate testing against the...
The system was launched without adequate testing against the full complexity of federal pay rules and collective agreements
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.
Cost-cutting measures eliminated experienced compensation staff who might otherwise...
cost-cutting measures eliminated experienced compensation staff who might otherwise have caught the software's errors before they reached employees' paychecks
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.