The automotive industry has never before experienced such a rapid period of change.
And that rate of change is only going to increase as vehicles become:
- More connected.
- More able to take over some of the driving functions.
- (Eventually) able to drive themselves.
The major part of this change will be in software.
Already, over 90% of automotive innovations are based on software-driven electronic components. These account for nearly half of a vehicle’s development costs.
Such development also requires changes to the way the industry works. And it requires autonomous vehicle standards for safety.
📕 Related Resource: Get an example using automotive hypervisors >>
How Autonomous Vehicle Technology Impacts Architecture
The AUTOSAR open systems architecture is a good example of changes in the industry.
This was developed to help carmakers deal with growing software complexity — and keep costs under control.
The original version — the Classic Platform — provided guidelines for basic microcontrollers. These had to handle real-time and safety-critical requirements.
But the industry is moving to more connected and autonomous vehicles. So, AUTOSAR has evolved with the Adaptive Platform. It covers 32- and 64-bit microprocessors with external memory, parallel processing, and high bandwidth communications.
AUTOSAR will be the platform on which future applications will be implemented.
Why Autonomous Vehicle Standards Are Important
Autonomous vehicle standards are important for ensuring safe, secure, and reliable code.
AUTOSAR recently produced a coding standard for C++14, with help from Perforce's static analysis experts (formerly PRQA). This standard will be critical for developers of autonomous vehicle technology.
Find out:
- Why these coding guidelines are needed.
- Who will use them.
- What are the best practices for automotive embedded software.
- How software engineers can ensure that their code complies with autonomous vehicle standards.