National foreword

This British Standard is the UK implementation of ISO 34505:2025.

The UK participation in its preparation was entrusted to Technical Committee AUE/15, Safety related to vehicles.

A list of organizations represented on this committee can be obtained on request to its committee manager.

Contractual and legal considerations

This publication has been prepared in good faith, however no representation, warranty, assurance or undertaking (express or implied) is or will be made, and no responsibility or liability is or will be accepted by BSI in relation to the adequacy, accuracy, completeness or reasonableness of this publication. All and any such responsibility and liability is expressly disclaimed to the full extent permitted by the law.

This publication is provided as is, and is to be used at the recipient’s own risk.

The recipient is advised to consider seeking professional guidance with respect to its use of this publication.

This publication is not intended to constitute a contract. Users are responsible for its correct application.

Compliance with a British Standard cannot confer immunity from legal obligations.

This British Standard was published under the authority of the Standards Policy and Strategy Committee on 30 June 2025.

Foreword

ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies (ISO member bodies). The work of preparing International Standards is normally carried out through ISO technical committees. Each member body interested in a subject for which a technical committee has been established has the right to be represented on that committee. International organizations, governmental and non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.

The procedures used to develop this document and those intended for its further maintenance are described in the ISO/IEC Directives, Part 1. In particular, the different approval criteria needed for the different types of ISO document should be noted. This document was drafted in accordance with the editorial rules of the ISO/IEC Directives, Part 2 (see www.iso.org/directives).

ISO draws attention to the possibility that the implementation of this document may involve the use of (a) patent(s). ISO takes no position concerning the evidence, validity or applicability of any claimed patent rights in respect thereof. As of the date of publication of this document, ISO had not received notice of (a) patent(s) which may be required to implement this document. However, implementers are cautioned that this may not represent the latest information, which may be obtained from the patent database available at www.iso.org/patents. ISO shall not be held responsible for identifying any or all such patent rights.

Any trade name used in this document is information given for the convenience of users and does not constitute an endorsement.

For an explanation of the voluntary nature of standards, the meaning of ISO specific terms and expressions related to conformity assessment, as well as information about ISO's adherence to the World Trade Organization (WTO) principles in the Technical Barriers to Trade (TBT), see www.iso.org/iso/foreword.html.

This document was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 33, Vehicle dynamics, chassis components and driving automation systems testing.

Any feedback or questions on this document should be directed to the user’s national standards body. A complete listing of these bodies can be found at www.iso.org/members.html.

Introduction

The rapid development of automated driving technology with the goal of improving safety and comfort has become an important aspect in the development of modern automobile technology. The evaluation of tests of automated driving systems (ADSs) based on test scenarios has become a common method.

A scenario is a sequence of scenes usually including the ADS(s)/subject vehicle(s) and their interactions in the process of performing a dynamic driving task (DDT). A test scenario is a scenario intended for the testing and assessment of ADS(s) or subject vehicle(s) in their operational environment (see ISO 34501). A test case is a set of test inputs (stimulation), steps, test platforms and expected results (pass/fail criteria) developed for a particular test objective (the test case is defined later in this document). In order to execute the test, some additional items are needed to supplement the scenario. Another important topic is how to choose the right test scenarios for a particular automated driving system (ADS) function.

This document is the basis of generating and evaluating scenario-based test cases for ADSs.

This document is intended to be used to harmonize and standardize the evaluation of scenarios and the procedure and methodology of the generation of test cases for ADSs.

1 Scope

This document defines a methodology to evaluate scenarios and provides a procedure for extending test scenarios to test cases. This document also defines the necessary characteristics of test cases, which include but are not limited to unified identifiers, test objectives, inputs, steps, platforms and expected results.

This document describes methods and criteria to evaluate test cases (e.g. frequency, criticality, complexity of a scenario), the coverage concerning functional and technical requirements, operational domain (OD), test criteria, and also the optimization of sets of prioritized test cases.

This document is applicable to Level 3 and higher ADSs as defined in ISO/SAE PAS 22736. The focus of this document is on scenarios, which will be tested to evaluate safety (functional safety and safety of the intended functionality (SOTIF)). The content, in general, is also applicable to non-safety related test scenarios.

2 Normative references

3 Terms and definitions

4 Introduction and overview

4.1 General

The traceability over all artefacts is a clause-overarching topic which is further described in ISO 26262‑2:2018. In Clause 5 the inputs are defined to evaluate the scenarios. Before the scenario evaluation the test objective is defined. In Clause 6 the scenario evaluation activities that need to be performed before the test execution are described. This is done by evaluating the scenario characteristics, extending the scenarios to test cases and optimizing the set of test cases. The relations between the scenarios and other artefacts which are defined in Clause 5 will be used as an input to Clause 6, to evaluate whether the selected scenarios are appropriate for the tested ADS feature. The test case generation is described in chapter 6.4. The investigations to analyse the test cases concerning initialization of the test run and monitoring during test execution are described in Clause 7. After test execution, the comparison of the initial specified and the resulting test case, the evaluation of the resulting test case concerning physical principle and probability in reality can be found in Clause 8. A detailed representation of the workflow described in this document can be found in Figure 1.

4.2 Requirements for compliance

When claiming compliance with this document, each requirement shall be met unless a rationale is provided demonstrating that the non-compliance is deemed acceptable, i.e. the corresponding objectives are still achieved.

5 Evaluation of scenario characteristics

5.1 Purpose

5.2 Set of scenarios

5.3 Relations between the scenarios and functional and technical requirements

5.4 Relation between scenarios and ODD

5.5 Relation between the scenarios and test objectives

6 Test case generation before test execution

6.1 Purpose

6.2 Selection of scenarios

6.3 Scenario priority

6.4 Extend scenarios to test cases

6.5 Methods to optimize the set of test cases

7 Test case evaluation during test execution

7.1 Purpose

7.2 Test initialization

7.3 Monitoring of test execution

8 Test case evaluation after test execution

8.1 Purpose

8.2 Comparison of specified and executed test case after execution

8.3 Evaluation of executed test cases concerning validity of simulation (for virtual testing only)

8.4 Evaluation of executed test cases concerning exposure in reality

8.5 Evaluation of traceability

8.6 Evaluation of coverage based on executed test cases

Bibliography

BS ISO 34505:2025

Road vehicles. Test scenarios for automated driving systems. Scenario evaluation and test case generation

Current

Published:

30 Jun 2025