List of figures

Figure Description

Figure 1

Levels of scenario abstraction (Source: [13])

Figure 2

From abstract to concrete

Figure 3

From concrete to abstract

Figure 4

An illustration of a set of traces accepted by an ASAM OpenSCENARIO model

Figure 5

An illustration of how the set of traces accepted by a scenario is a subset of the composition of the traces accepted by the scenario invocations, which themselves are subsets of the traces accepted by their type scenario.

Figure 6

Different behavior invocation overlappings allowed by overlap kinds equal, start, end, initial, and final

Figure 7

Different behavior invocation overlappings allowed by overlap kinds inside, full, and any

Figure 8

An illustration of minimum and maximum start_to_start offsets

Figure 9

An illustration of an ASAM OpenSCENARIO scenario execution state showing scenario instances and field bindings.

Figure 10

Entity overview

Figure 11

Yaw, pitch, and roll angle in an ISO 8855:2011 compliant coordinate system

Figure 12

Route-based s/t-coordinate system with origin at the beginning of the route

Figure 13

Vehicle coordinate system

Figure 14

Entity overview

Figure 15

Entity overview

Figure 16

Entity overview

Figure 17

Entity overview

Figure 18

Basic junction

Figure 19

Junction routes

Figure 20

A typical crossing

Figure 21

A crossing

Figure 22

Entity overview

Figure 23

Actions that prioritize exact reproduction

Figure 24

Actions that prioritize respecting physical movement constraints

Figure 25

A remain_stationary action

Figure 26

Example of icon_positive==false (left) and icon_positive==true (right)

Figure 27

Crossing with line from free space points

Figure 28

Picture of crossing with specified start_angle

Figure 29

Understanding product testing

Figure 30

Recommending scenarios and parameter

Figure 31

Understanding AV/ADAS developer scenarios

Figure 32

Specifying regulation scenarios

Figure 33

Tracing back requirements

Figure 34

Sharing scenarios with other companies

Figure 35

Scenario sharing with auditors and regulators

Figure 36

Sharing scenarios with customers

Figure 37

Including traffic models and agents

Figure 38

Describing real world with scenarios

Figure 39

Creating self-checking scenarios

Figure 40

Creating abstract scenarios for documentation purposes

Figure 41

Re-utilizing scenarios for research

Figure 42

Deriving a simulation scenario from findings of a SOTIF analysis

Figure 43

Deriving new hazardous events, system insufficiencies or triggering conditions for SOTIF from findings during a simulation run

Figure 44

Replaying different variants of a critical scenario observed on the road in simulation, to derive new SOTIF insights from it.

Figure 45

Evaluating of residual risk because of unknown scenario

Figure 46

Integrating tools from other vendors

Figure 47

Processing and comparing results

Figure 48

Creating natural language scenarios without technical details

Figure 49

Tracing back verification

Figure 50

Workflow for cross-company scenario testing

Figure 51

Creating platform independent scenarios

Figure 52

Tracing back requirements

Figure 53

Specifying a driving mission

Figure 54

Accomplishing driving missions

Figure 55

Converting abstract test descriptions into scenarios

Figure 56

Reuse/combine of scenario elements to avoid copy-paste

Figure 57

Specifying test aspects

Figure 58

Converting between abstraction levels

Figure 59

Using real-world data for scenarios

Figure 60

Performing automated scenario execution

Figure 61

Using different tool chains

Figure 62

Converting abstract to concrete scenarios

Figure 63

Running tests in different environments

Figure 64

Describing test track scenarios

Figure 65

Measuring the verification progress

Figure 66

Migrating from ASAM OpenSCENARIO XML 1.3.0 to ASAM OpenSCENARIO

Figure 67

Re-using constructs, artifacts and libraries

Figure 68

Migrating from ASAM OpenSCENARIO XML 1.3.0 to ASAM OpenSCENARIO

Figure 69

Executing simulations randomly