Annex B: Use cases and workflows (informative)

B.1 Introduction

This section contains a collection of use cases and pre-defined workflows for a variety of tasks.

This is a working document of the project and provided as is, it is not consistent and contains errors.
The project felt that it could be beneficial to users and ASAM intends to refine this in future projects.

B.1.1 Use cases and standard language

OpenSCENARIO 2.0 not only provides a domain model but also a high-level declarative language. This language is used for capturing abstract scenarios, setting the V&V goals in a measurable way and checking for correct DUT behavior.

As part of the standard creation process - and based on industry needs - multiple use cases that the standard and its language should support were identified.

The main features of the OpenSCENARIO 2.0 standard language are:

  1. Introduction of new capabilities to address the growing industry challenges for scale, human-readability, and thoroughness.

  2. Providing a cross-industry input format that allows both vendors and users to build tools and to collaborate.

The set of use cases in this user guide helps both defining the standard scope and consulting users on how to maximize the OpenSCENARIO 2.0 standard value.

B.1.2 Status of use cases

  1. The use cases collection is partial and will grow in the future.

    1. A few use cases were postponed and will be delivered in the upcoming releases of the standard.

    2. The industry might find new ways to leverage the standard input format in unanticipated ways. The plan is to update the use cases list accordingly.

  2. The suggested workflows are recommendations.

    1. The use cases define the best-known ways to-date to leverage the OpenSCENARIO 2.0 capabilities.

    2. If more efficient flows or steps are introduced, this user guide is updated accordingly.

B.2 Target group

This section helps you to find relevant use cases depending on your role.

Workflow descriptions for the following users are available:

The workflows can be accessed by clicking on the corresponding role name.