In order to identify limits and update the specification accordingly the identification of relevant driving scenarios is required. Apart from “black box testing” of an integrated function, which involves real world testing to try to find potential issues based on real world traffic in a representative environment, there are several other approaches that can be applied to test for such limitations at an early stage of development. One approach is to identify corner and edge cases combined with robustness tests (e.g. by introducing noise). The underlying assumption is that if the ADF can deal with these, it will also be capable of dealing with less critical scenarios. Thus, it is necessary to expose the ADF to a repeatable set of driving scenarios, an activity for which a simulation environment is most suitable.
The application of a test catalogue supports reuse of past experiences and company / vehicle specific test sets. A test catalogue will also be needed for regression testing to re-run past tests for a system after a modification has been introduced during development.
The tests should be defined in a way that they address all definition layers of a test – ranging from functional via logical up to concrete test scenarios. Additional information regarding this topic and a corresponding scenario database is for instance provided by the PEGASUS project (PEGASUS 2019).
Main Question
Is a scenario-based approach utilized that sufficiently covers the ADF’s ODD?
Sub-Questions
- Is a structured approach used to identify critical scenarios?
- Is a test catalogue utilised in order to guide the V&V activities?
- Are functional, logical and concrete scenarios considered for verification?