PofoliaShared via Pofolia

SAE International Journal of Transportation Safety· 2016Q4

Challenges in Autonomous Vehicle Testing and Validation

Philip Koopman, Michael Wagner

Short summary

Autonomous vehicle development requires a more methodical testing approach than traditional bug hunting to ensure safety at scale. This paper identifies five key challenges in applying the ISO 26262 V-model process to autonomous systems.

AI-generated from the title and abstract; the full text is not read.

Key points

  • Traditional software testing is insufficient for safe autonomous vehicle deployment.
  • Five specific challenges exist when applying the ISO 26262 V-model to AVs.
  • Solutions include phased deployment, monitor/actuator architectures, and fault injection.
  • Architecting the system and design process can leverage existing safety approaches.

AI-generated from the title and abstract; the full text is not read.

Abstract

<div class="section abstract"><div class="htmlview paragraph">Software testing is all too often simply a bug hunt rather than a well-considered exercise in ensuring quality. A more methodical approach than a simple cycle of system-level test-fail-patch-test will be required to deploy safe autonomous vehicles at scale. The ISO 26262 development V process sets up a framework that ties each type of testing to a corresponding design or requirement document, but presents challenges when adapted to deal with the sorts of novel testing problems that face autonomous vehicles. This paper identifies five major challenge areas in testing according to the V model for autonomous vehicles: driver out of the loop, complex requirements, non-deterministic algorithms, inductive learning algorithms, and fail-operational systems. General solution approaches that seem promising across these different challenge areas include: phased deployment using successively relaxed operational scenarios, use of a monitor/actuator pair architecture to separate the most complex autonomy functions from simpler safety functions, and fault injection as a way to perform more efficient edge case testing. While significant challenges remain in safety-certifying the type of algorithms that provide high-level autonomy themselves, it seems within reach to instead architect the system and its accompanying design process to be able to employ existing software safety approaches.</div></div>

The authors' abstract, as published at the source. SAE International Journal of Transportation Safety, 2016 · DOI ↗

TakeawaysPremium
Ask the paperFree account

Continue with a free account

Ask the paper: 3 free questions a day about this paper; save it, get its citation, new summaries every day for your field. Takeaways are Premium.

Continue free on the web

Sign in with Google or Apple; no card needed. You come back to this paper.

On your phone:

Field: Software

SoftwareComputer Science