Subproject 4: Result reflection and embedding
“Result reflection & embedding” verifies that the results and procedures can also be transferred to further applications and higher automation levels, and that the tools and processes developed within PEGASUS can be integrated into the company.
The results from PEGASUS constitute the basis for testing as well as for the safeguarding of highly-automated driving functions for future serial products. In order to ensure these, the results must be consistent and integrate, as much as it is possible, into the existent corporate structures. The subproject should critically reflect the obtained results and ensure a sustainable concept. By incorporating the results into the corporate structures, it will be guaranteed, that these can be practically used and further developed.
The starting point for the testing of the new HAF functionality is, in addition to the description of the function, the identification of relevant situations, quality and criticality measures. Here, it will be assessed, if the used test scenarios are sufficient and whether the methodology for data collection is consistent. Thus, an assessment of the interfaces as well as a plausibility check of the procedure will take place.
For the tests made to safeguard the new automation functions, two processes will be defined within the subproject, which describe the procedure for testing and the necessary elements for implementation. In order to enable the transferability to other HAF application scenarios, the processes should be designed as flexible. In the 4th subproject, it will be assessed, whether the test objective can be achieved, with the used processes and methods.
It will be verified, whether, for example, a test result of a software-in-the-loop test has sufficient meaning, to be able to partially dispense with a vehicle test. In addition, the transferability is checked for other automation systems. A maturity stage control is set up for this purpose. For the tests made to safeguard the new automation functions, two processes will be defined within the subproject, which describe the procedure for testing and the necessary elements for implementation. In order to enable the transferability to other HAF application scenarios, the processes should be designed as flexible. In the 4th subproject, it will be assessed, whether the test objective can be achieved, with the used processes and methods. The objective is to simulate as many tests as possible, so as to reduce testing costs and times. Here, a thorough testing process is necessary. The subproject analyzes the consistency of the information chain developed within PEGASUS, from the requirements regarding the described necessary processes to the test cases.
The developed processes, methods and tools for carrying out the tests in form should thereby be reflected in the form of blueprints, within the companies. Thus, the tests are comparable within individual companies. For this reason, the reusability of the results is constantly monitored and, after the successful testing, their embedding by the partners is accompanied until the end of the project. Based on this, the project results are assessed and a procedure developed, with further usage within the industry.