SDB
Scenario-based design and scenario-based testing has been established in the development process of automated vehicles. A scenario database is the core for traffic scenarios. The database includes all necessary scenarios for the ODD of an ADS. A common scenario database has not been yet established, but different implementations and workflows are currently applied.
The scenario database content covers different elements. The main element of a scenario database are scenarios. Scenarios are based on data, which covers the ODD and the specification of the ADS. It needs to be available and accessible. This data needs to be formatted according to the scenario database requirements, which allows it to be included into the database.
The quality and content of the data needs to be sufficient in order to fulfill the demand for designing and/or testing the ADS. These boundary conditions have to be ensured before a scenario database can be applied as a tool.
Based on the available data and resulting scenarios the scenario database is applicable. The overall tool chain of development process includes the concept of a scenario database. This tool chain focusses on the usage of the scenarios and the test cases derivation out of scenarios.
- Requirement – Identification of Critical Scenarios
- Functional Safety – Derivation of Test Cases
- HVI – Controllability of Vehicle from User’s Perspective
- SDB – Coverage of ODD in Scenario Database
- SDB – Identification of Necessary Scenarios for ODD
- SDB – Availability of Data for Scenario Creation
- SDB – Availability of Tool Chain for Scenario Application
- SDB – Sufficiency of Scenario Data Quality
- SDB – Availability of Scenario Format in Database
- SDB – Defined Process for Scenario Database Usage
- — Cross-References after this —
- AI – Quality of the Dataset(s) (including Training, Testing and Validation)
- AI – Maintenance and Update of the Dataset
- AI – Generation of Specific Scenarios of Interest
- Testing – Concept Safety Validation
- Testing – Testing ODD