With the growing prevalence of electric and autonomous/connected vehicles, software is even more central to automotive development. Increasing the extent of software in vehicles, however, leads to many safety considerations during the development process, according to a new survey conducted by Perforce Software.
The survey found that automotive software developers' top three leading concerns are safety (43%), security (22%), and quality (21%).
"Electric, autonomous, and connected vehicles are the future of the industry," said Stuart Foster, Product Manager for Klocwork and Helix QAC at Perforce. "With more software components being added to these vehicles, ensuring the safety and security of that software will remain a top concern for automotive teams."
For those most concerned with safety, 40% said their biggest concern is meeting customer expectations of compliance with safe coding standards, such as MISRA.
"MISRA has been a cornerstone of automotive software development for many years, but ensuring that software is compliant can be a time-consuming endeavor without the right tools, such as a static code analyzer," said Jill Britton, Director of Compliance at Perforce.
The report states: “22% of those that we surveyed cited security as their top concern in automotive software development. As more software comes onboard a vehicle, there is a greater risk that hackers could infiltrate onboard/offboard systems. In fact, the number of cyberattacks on connected automobiles have increased by 99% from 2019 to 2020.
The most common security concern is unauthorized access onboard/offboard systems (cited by 46% of those concerned with security.)
Other security concerns include:
■ Enforcing secure coding practices (28%)
■ Lacking skills needed to combat security threats (20%)
■ Security testing takes too long and slows down development (6%)
Quality is the top concern for 21% of those surveyed.
“Customers expect their vehicle to be high quality and feature the maximum amount of functionality and connectivity,” the report states. “With the growing demand for electric and autonomous vehicles, this puts development teams under pressure to deliver innovative technology in shortened development cycles.”
“However, quality should never come at the expense of speed as the number of software-based electronic defects have been steadily rising over the past several years.”
Other quality concerns include:
■ Enforcing coding best practices (33%)
■ Testing efforts are not exhaustive enough and time is limited for further tests (30%)
■ Complexity of codebase (25%)
■ Peer code review inconsistency (12%).
8% of respondents are most concerned about testing. The leading concern is struggling to test efficiently — specifically that testing and software validation are time-consuming (the top issue for 45% of those concerned about testing).
Other testing concerns include:
■ Bugs are found too late (23%)
■ Difficulty documenting automated and manual testing efforts (19%)
■ Coordinating efforts across teams (13%)
5. Team Productivity
6% of respondents are most concerned about team productivity. The top productivity concern is managing the lack of integration or alignment between disparate teams in parallel development (58%).
Other productivity concerns include:
■ Managing and reusing design and IP assets across hardware and software teams (19% of those concerned with team productivity)
■ QA cycles are long (19%)
■ Having to extend release cycles due to merge conflicts and broken builds (3%)