M
"

Directory

Introduction

Glossary

Input

Data Framework

Performance Assurance

Scenario

Create

Format

Store

Environment

Query & Concretise

Allocate

Execute

Safety Argument

Coverage

Test Evaluate

Safety Case

Decide

Audit

Use Cases

SAF Solutions

Submit Feedback

SUNRISE Safety Assurance Framework

Format

Input Scenario Create Format Store Environment Query & Concretise Allocate Execute Safety Argument Coverage Test Evaluate Safety Case Decide Audit

Once the scenarios are created, the next step is to Format them in a way that represents the scenario effectively. The Format block therefore involves the structuring of the scenario, preferably using a standardized scenario description language such as ASAM OpenSCENARIO and OpenDRIVE for logical and concrete scenarios, and BSI Flex 1889 for abstract scenarios. This formatting of scenarios takes place in external SCDBs, and is not covered in the scope of the SUNRISE project. Nevertheless, the Format block forms an integral part of the SUNRISE SAF.

Given the multiple stakeholders involved in scenario-based testing, there is a need to use multiple abstraction levels in scenario formatting. These abstraction levels serve different purposes and audiences. For example, more abstract levels focus on human readability, while more concrete levels focus on machine readability. The following overview explains the main scenario abstraction levels used in the SUNRISE SAF (see also image below):

  • Functional Scenarios – Describes scenarios at a semantic level using linguistic notation. This is the highest level of abstraction that details entities and their relationships using natural language-based expressions. It focuses on the semantic meaning and purpose of the scenario without specific technical parameters.
  • Abstract Scenarios – Intermediate level between functional and logical scenarios. This level was introduced to bridge the gap between functional and logical scenarios. It provides a formalized format to organize scenario descriptions while maintaining some level of abstraction from specific parameter values.
  • Logical Scenarios – Targets scenario content at a state space level using parameter ranges. Represents entities and their relationships using parameter ranges rather than specific values. This level therefore describes the parameter space of scenarios.
  • Concrete Scenarios – Uses specific or concrete values to represent entities and relationships. Also targets scenario content at a state space level but uses exact, specific values rather than ranges. These scenarios are extracted from logical scenarios and can be directly simulated and evaluated as pass or fail based on specific parameter values.

 

SAF Application Guidelines for the Format block are combined with those of the Create and Store blocks, and can be found on the Scenario page.