The scenario database is a tool, which can be used for many different purposes in the development of ADFs. The scenario database is often claimed to solve testing and evaluation problems, see (Mazzega, J. et al., 2019) or (Taniguchi, S et al., 2021).
Scenario database are usually used for higher level automation functions (e.g. level 2 hands-off, level 3 or level 4).
But in many cases only some selected test scenarios are necessary and the scenario database is much too powerful for the actual need.
Before a scenario database is selected as a necessary tool in the overall tool chain, it needs to be checked, if such a scenario database is really necessary and if it is the correct tool for the purpose / research question.
The integration of the scenario database into tool chain requires interfaces for all design parameters of a scenario and a clear description of the ODD for scenario selection.
Main Question
Is the tool chain fully available to apply scenario databases within the development and evaluation process?
Sub-Questions
- Can design parameters be extracted form scenarios of the scenario database?
- Can test cases be derived from scenarios of the scenario database?
- Are the required test cases already avaialble from different sources?
References
- Mazzega, J. et al. (2019) PEGASUS METHOD. Zenodo. doi: 10.5281/ZENODO.6595201.
- Taniguchi, S. et al. (2021) ‘Automated Driving Safety Evaluation Framework Ver 2.0’. Available at: https://www.jama.or.jp/english/reports/docs/Automated_Driving_Safety_Evaluation_Framework_Ver2.0.pdf (Accessed: 05 February 2024)