ASAM Test Specification Study Group Report 2022

Scope

Mapping a Changing Landscape

When attempting to map the standardization landscape in its entirety, the first step is to define what is meant by “entirety.” Identifying the boundaries is an important part of the process, before examining the relevance of all aspects to achieve a comprehensive overview. The study group decided on a sequential project approach, a phase and milestone plan with intermediate results that build on each other. Methods and use cases were clustered to facilitate structure and exchange in sub–workgroups.

The report examines the relevant test techniques and use cases for testing and homologation of the ADAS/AD Domain in the automotive industry with a special focus on software-centric cars with modern E/E architectures. The goal is to identify relevant standards, potential workflows, and their variants, and the overall interplay between these parts to form a cohesive whole.
This analysis leads to a documented set of overarching use cases for testing and homologation, a set of potential workflows implementing them, and an overview of relevant users, standards, and their application.

Additionally, the study group identifies gaps in the workflows, leading to the identification of potentially necessary additions to existing standards, liaisons between standards, or completely new standards.

Recommendations for these standards or additions are collected and documented. The goal is to define a valid basis for follow-up activities and projects. As the safety arguments and homologation of modern vehicles are the key aspects, security-specific aspects such as fuzzing, pen testing, and TARA-driven testing are not currently receiving much attention.

In order to cover a large part of the automotive test landscape in the ADAS/AD domain, the group pursued a broad scope when considering possible test techniques and test environments. The goal is to prioritize these test techniques and to map them to user journeys and workflows in order to map their relevance (and also for standardization). It is important to us that we cover large parts of the test map, even though we will focus on certain aspects as we go along. For follow-up projects, we believe it is necessary to provide as complete an overview as possible. From our point of view, the test procedures presented represent a large part of the relevant test procedures, which, through combinations of test environments, enable us to provide an almost complete representation of the relevant tests from testing during development to homologation.