Cited by 675Safety Systems Engineering in AutonomyAutonomous Vehicle Technology and SafetySoftware Testing and Debugging Techniques

Challenges in autonomous vehicle testing and validation

Koopman, Philip, Wagner, Michael·2016·SAE International Journal of Transportation Safety

Abstract

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.

Integrity signals

Registry

Crossref · 10.4271/2016-01-0128

Cites

29 of 29 references verified0 citation errors · 0 not checkable

Statistics

Recomputing p-values needs the paper’s full text.

Claims the paper makes

This paper’s full text isn’t openly available, so its claims and self-check weren’t run. The registry and citation checks still apply.

Claims other papers make about this one

Each is checked against this paper’s own text: does it say what the citing paper says it does?

  • Design issues on data collection, pre-processing, cleaning, labeling and augmentation, including big data challenges, exist for ML applications.

    “-Data Design: Design issues on data collection, pre-processing, cleaning, labeling and augmentation, including big data challenges [17,23,25-27, 31,33,41,44,74-76,105,114-116].”
  • Data management for ML applications, including tools for data dependencies, automatic data validation and cleaning during runtime, and concept drift adaptation, is a maintenance challenge.

    “-Data Management: Tools for data dependencies, automatic data validation and cleaning during runtime, and concept drift adaptation [17,23,60,69].”
  • Training data, ML models and ML platforms are key components of ML applications, and challenges on the quality of each component have been discussed, including data anomaly, imbalanced or biased data, encrypted data, data evaluation/cleaning, and novelty detection.

    “-Component Quality: Training data, ML models and ML platforms (e.g.scikit-learn [125], Tensor flow [126], Weka [127]) is the key components of ML applications.The challenges on the quality of each components have been discussed.The challenge issues on data quality for ML applications includes data anomaly [23], imbalanced or biased data, encrypted data [60], data evaluation/cleaning [39][40][41]74”

Cites

Flagged first, then by citations

Cited by

Sorted by citations

Authors
Koopman, P., & Wagner, M.
Affiliations
  • Carnegie Mellon University (US)
  • Edge Case Research (United States) (US)
Venue
SAE International Journal of Transportation Safety
Published
2016-04-05
Volume
04
Issue
1
Pages
15-24
ISSN
  • 2327-5626 (ISSN-L)
  • 2327-5634
OpenAlex
W2328067583
Cited by
675
References
29
Citations by year
2026: 67 · 2025: 83 · 2024: 68 · 2023: 73 · 2022: 71 · 2021: 84 · 2020: 89 · 2019: 66 · 2018: 47 · 2017: 26 · 2016: 1
FWCI
88.44
Type
journal article
Language
en
Open access
closed
Locations
SAE International Journal of Transportation Safety (publishedVersion)
Topics
  • Physical Sciences › Engineering › Safety, Risk, Reliability and Quality › Safety Systems Engineering in Autonomy
  • Physical Sciences › Engineering › Automotive Engineering › Autonomous Vehicle Technology and Safety
  • Physical Sciences › Computer Science › Software › Software Testing and Debugging Techniques
Keywords
autonomous vehicles, software testing, ISO 26262, V-model, safety certification, non-deterministic algorithms, inductive learning algorithms, fail-operational systems, phased deployment, fault injection, software safety

About these checks

Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.

Statistics and arithmetic are recomputed, not judged.

Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.

What counts as a claim ›How we measure confidence ›How we check this ›

Are you an author, or do you see a problem with this page? Request a review