iOS 6 Apple Maps launch failure
Apple's replacement mapping app shipped with widespread inaccuracies (missing towns, misplaced landmarks) drawing global ridicule; CEO Tim Cook issued a public apology and the executive most associated with the project, Scott Forstall, departed the company.
The damage was public. The root cause was preventable.
Apple's replacement mapping app shipped with widespread inaccuracies (missing towns, misplaced landmarks) drawing global ridicule; CEO Tim Cook issued a public apology and the executive most associated with the project, Scott Forstall, departed the company.
What the software actually got wrong
Apple replaced Google's mature mapping data and software with its own newly built mapping service before it had sufficiently accurate map data or mature routing/search software, rushing the switch to reduce reliance on a competitor.
Apple replaced Google's mature mapping data and software with...
Apple replaced Google's mature mapping data and software with its own newly built mapping service before it had sufficiently accurate map data or mature routing/search software, rushing the switch to reduce reliance on a competitor.
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.