Re-imagining ISO 26262 in the Age of Autonomous Vehicles: Enhancing Controllability through Transferability and Predictability
Chaitanya Shinde, Hadi Hajieghrary, Paul Schmitt, Adam Shoemaker, Bodo Seifert, Steve Kenner
THE PROBLEM
This paper focuses on safety. This paper gives you a framework to make autonomous vehicle safety claims auditable and measurable by decomposing ISO 26262's vague 'controllability' into two concrete concepts: whether the AV can hand off to fallback systems (Transferability) and whether humans can predict its behavior (Predictability). You get mathematical metrics to verify these properties actually work in real driving scenarios, not just in theory. Read the paper by tracking the Core ConceptsTaskThe job the robot is supposed to complete, such as pick-and-place, navigation, or drawer opening. definition, the Core ConceptsRobotA physical system with sensors and actuators that can observe the world and take actions. or data assumptions, and the evidence that supports the claimed improvement.
HOW IT WORKS
Task framing
Core method
Data and supervision
Evaluation evidence
KEY RESULTS
This paper gives you a framework to make autonomous vehicle safety claims auditable and measurable by decomposing ISO 26262's vague 'controllability' into two concrete concepts: whether the AV can hand off to fallback systems (Transferability) and whether humans can predict its behavior (Predictability). You get mathematical metrics to verify these properties actually work in real driving scenarios, not just in theory.
WHY DEVELOPERS SHOULD CARE
This paper gives you a framework to make autonomous vehicle safety claims auditable and measurable by decomposing ISO 26262's vague 'controllability' into two concrete concepts: whether the AV can hand off to fallback systems (Transferability) and whether humans can predict its behavior (Predictability). You get mathematical metrics to verify these properties actually work in real driving scenarios, not just in theory.
LIMITATIONS
The main limitation to check is whether the claimed behavior holds outside the paper's reported setup. That means testing across different Core ConceptsRobotA physical system with sensors and actuators that can observe the world and take actions. embodiments, scenes, objects, and data distributions.
WHAT COMES NEXT
The practical next step is independent reproduction with clear baselines, ablations, and stress tests. For a developer, the useful follow-up is to map the paper's safety assumptions onto a concrete Core ConceptsRobotA physical system with sensors and actuators that can observe the world and take actions. stack, then test the smallest version of the method that could run end to end.