Jeep Grand Cherokee shift-by-wire software recall
Fiat Chrysler recalled about 1.1 million vehicles after dozens of injuries and at least one death (actor Anton Yelchin) linked to drivers mistakenly believing their vehicle was in park.
The damage was public. The root cause was preventable.
Fiat Chrysler recalled about 1.1 million vehicles after dozens of injuries and at least one death (actor Anton Yelchin) linked to drivers mistakenly believing their vehicle was in park.
What the software actually got wrong
The electronic 'monostable' gear-selector software gave drivers no physical or tactile confirmation of gear position and had no safeguard to stop the car rolling if a door was opened while it was not actually in park; NHTSA required a software update adding an automatic-park safety feature.
The electronic 'monostable' gear-selector software gave drivers no physical...
The electronic 'monostable' gear-selector software gave drivers no physical or tactile confirmation of gear position and had no safeguard to stop the car rolling if a door was opened while it was not actually in park
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.
NHTSA required a software update adding an automatic-park safety...
NHTSA required a software update adding an automatic-park safety feature
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.