Belgium 2003 election vote-count error (cosmic-ray bit-flip)
A Belgian electronic voting machine in Schaerbeek briefly awarded one candidate over 4,000 extra votes during the 2003 federal election count, an anomaly caught only because it exceeded the number of registered voters.
The damage was public. The root cause was preventable.
A Belgian electronic voting machine in Schaerbeek briefly awarded one candidate over 4,000 extra votes during the 2003 federal election count, an anomaly caught only because it exceeded the number of registered voters.
What the software actually got wrong
Investigators concluded the most likely cause was a single bit in the voting machine's memory being spontaneously flipped by a cosmic ray strike, and the vote-tallying software had no plausibility check that would have flagged an implausible vote count before it was reported.
Investigators concluded the most likely cause was a single...
Investigators concluded the most likely cause was a single bit in the voting machine's memory being spontaneously flipped by a cosmic ray strike
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 vote-tallying software had no plausibility check that would...
the vote-tallying software had no plausibility check that would have flagged an implausible vote count before it was reported
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.