Updates to one software component can cause unintended behavior and performance issues to interrelated vehicle functionality. Auto Validate enables car manufactures to validate the effect a software update has on the entire system, identify the affected software components, and detect the resulting functional change.
Through a dynamic UI, engineers receive full visibility into all configurations and variations of every line of code, its behavior, functions and dependencies, even from multiple suppliers and sources.
“An amendment shall be designated a ‘revision’ where an approval authority finds that the vehicle continues to comply with the applicable requirements, therefore, no inspections or tests need to be repeated.
The amendment shall be designated an ‘extension’ where the approval authority finds that further inspections or tests are required to verify continued compliance with the requirements or that new requirements become applicable to the approved vehicle.“
UN TYPE APPROVAL REGULATION, CHAPTER 5, ARTICLE 34
Auto Validate creates a digital thumbprint of functionality relationships to prove which code has been affected by the update for Type Approval and in accordance to UNECE WP29.
ASIL-D certification requires there be no unused code in the vehicle. However, code often comes from multiple software sources and can include legacy car software, open source and third party bundles – complexities that create obstacles for developers to track every piece of code.
Aurora Labs provides specific evidence for software updates that do not affect functionality behavior. This evidence and documentation can be used to provide type-approval exemptions for non-affected functionality.