The question focuses on whether all test related aspects (test plan, test execution and test result) have been documented properly. The term “test” encompasses both the evaluation of ADF capabilities and the overall V&V of the ADF, including the validation of design decisions. Alongside the testing activities, the documentation should also include updates to the test plan, and for clarity, it’s advisable to document the rationale behind these changes.
If the documentation of testing activities needs to be shared with external stakeholders, such as for homologation or certification, it’s necessary to ensure that the format of the documentation meets their requirements. The questions also explore how lessons learned during testing can be gathered for the future development of ADF. Proper management of deficiencies identified during testing is crucial. For each deficiency, a suitable reporting procedure should be implemented, which not only reports the deficiency but also details how it was addressed. This procedure should encompass all testing methods.
If deficiencies are identified, this information should be reported to enable the reconstruction of the deficiency at a later date. Generally, the more information (both in quantity and detail) that is available, the better it is for reconstructing the deficiency. However, a balance often needs to be struck between the amount of information and the available on-board and off-board storage. At a minimum, the following information should be included:
- Time;
- Location;
- Weather conditions;
- Description of the test conducted;
- Description of the deficiency;
- State of the vehicle;
- State of the road and infrastructure;
- Traffic state;
- Software version of ADF.
The insights gained from testing activities or about deficiencies can be used not only for the ADF itself but also for updating the tests. These updates may involve changes to the parameters tested, the number of tests, and the methodology.
Main Question
Is a reporting process established to feedback the knowledge / lessons learnt during testing and development?
Sub-Questions
- Is a reporting process established in which faulty behaviour can be recorded during testing?
- Is a reporting process established to review the results obtained and to address reporting of identified deficiency?
- Is a reporting process established to update test cases based on the experiences of past projects?
- Does the reporting system cover the required steps to handle the identified deficiency?
- Does the reporting process consider data from all test methods (test track, simulation and tests on public roads, etc.)?