VDA 711 (03/2025) - English
VDA 711 Software-in-the-loop (SiL) Standardization / Phase II (03/2025) - Gruppenlizenz (group license), AGB (GTC) Art. 10, 2 - Language of the document English
Software-in-Loop (SiL) is the enabler for the continuous and agile development processes in the automobile industry. Without SiL, the release of open context systems (high number of combinations of possible input data), such as automated driving, is practically not possible. In the future, it can be assumed that most of the software tests in the automobile industry will be carried out in SiL-environments.
It is necessary to standardize the SiL interfaces across the industry to enable working across organizations, domains, and platforms. Without standardization, a large number of individual interfaces ay be developed. The resulting effort and the related costs would be enormous. Therefore, the SiL standardization is an essential requirement for the successful virtualization and the automation of software tests in the automotive industry.
In addition to a recommendation for SiL interfaces, this document also contains recommendations for simplified, common language use in the industry. Besides Separation of Concerns, in which the difference between different test objectives are described, the definitions for the individual SiL components are part of this recommendation.
This document is an extension of the VDA recommendation 710 (2022). Relevant use cases for implementation for Proof-of-Concepts are selected and added in the document. Different common tools are then selected for the Proof-of-Concepts. The objective of the Proof-of-Concepts is to generate relevant topics specific to configuration management. Aside to the Proof-of-Concepts, further topics were presented and worked on by the members of the project group. It was checked which topics were already covered by which possible standards. Through and exchange with the other standardization committees, the latest developments in the Proof-of-Concepts were implemented and best practices were collected and referenced in the document. Moreover, gaps that have already been identified, for example in the metadata for virtual ECUs, have been communicated to committees. A thorough workflow for the generation and validation of an SiL-test environment was created.
