3 Terms and definitions

Abstract scenario

A formal scenario that conceptualizes scenarios to the level of the scenario intent.
For more information, see the detailed abstract scenario definition.

Abstraction

Generalization of one or more related specific implementations or situations. In this standard, abstraction refers to the generalization of scenarios. Abstraction is the opposite of concretization.
For more information, see the detailed abstraction definition.

Abstraction levels

Gradation spectrum of generalization (abstraction) of a scenario.
For more information, see the detailed abstraction levels definition.

Action

A fundamental, non-decomposable behavior of an actor. An action is a piece of behavior that can be executed or observed. Actions are abstract and their actual implementation is platform-specific and outside of the scope of this standard.
For more information, see the detailed action definition.

Actor

A participant in a scenario who can perform actions.

Agnostic

The method or format of data is irrelevant to the device or program’s function.

Concrete scenario

A scenario for which the exact evolution of any of its parameters and variables is completely determined to a fixed value for any point in time.
For more information, see the detailed concrete scenario definition.

Concretization

The opposite of abstraction.

Ego vehicle

The vehicle actor that is the focus of a scenario, meaning the vehicle under test.

Entity

Generic name for an element of the domain model. Entities can be classes, interfaces, or enums.

Event

A named trigger indicating the occurrence of a particular situation.

Functional scenario

Non-formal natural language description of a scenario.
For more information, see the detailed functional scenario definition.

Logical scenario

A scenario that does not specify all values for all parameters but provides a range of values that can be selected.
For more information, see the detailed logical scenario definition.

Operational design domain (ODD)

The complete range of space where the system under test is expected to operate.

OpenSCENARIO file

A file that contains code from ASAM OpenSCENARIO version 2.0.0 or greater and can be parsed by a compatible tool. Such files should make use of the file extension .osc to identify them. This differentiates them from the XML-based OpenSCENARIO files of previous versions that use the .xosc file extension.

Parameterization

The use of parameters.

Scenario

A description of the behavior or temporal evolution of physical objects and environmental conditions on the driving infrastructure over an interval of time, including the movement of traffic participants or the change of environmental conditions.
For more information, see the detailed scenario definition.

Scenario instance

The scenario that is executed, whether it is passively observed or actively controlled.
For more information, see the detailed scenario instance definition.