We recently held a webinar discussing the unique challenges in automotive software development and three ways to help teams deliver code that’s secure from hacking vulnerabilities, conforms to critical standards, and free of defects.
Navigating the day-to-day issues of automotive software development can be overwhelming, so the strategies we talked about here are intended to make them easier to avoid altogether.
Our attendees were a mix of developers, analysts, and other people interested in automotive development. We always try to understand our attendees so here are some interesting results from the audience polls we conducted during the webinar:
Does your organization require adherence to ISO 26262?
No – 57%
Yes – 43%
This result wasn’t that surprising. As automotive safety and recalls gain prominence in the news, more teams are required to follow some sort of standard to ensure hazards are minimized. It follows suit that, compared to our last webinar on the topic, there’s a significant increase in the number of people concerned about ISO 26262. You can fast forward to 12:10 in the webinar to see what standards compliance means and how to achieve it with less work.
How much time does your development team spend on fixing defects?
Less than 25% – 50%
Between 26% and 50% – 25%%
Between 51% and 75% – 25%
More than 75% – 0%
When does your team fix defects in the software development process?
Implementation – 25%
Build – 37.5%
Test – 37.5%
Maintenance – 0%
Based on this audience, it would appear that most teams spend less than a quarter of their overall time fixing defects, which is a good thing, but that defects are fixed mostly during the build and test phases. This is too late for a number of reasons, not the least of which is that defects are costlier to fix. If you go to 25:40 in the webinar, you’ll learn how one technique, static code analysis, brings defect discovery into the implementation phase, where bugs are the easiest and cheapest to fix.
(Testing later in the lifecycle is all too common, unfortunately – we found the same results during one of our security webinars)
There was also an extensive Q&A session at the end of the webinar, where our participants asked everything from “can you really ensure that software is free of defects?” to “do these tools support continuous integration servers (e.g. Jenkins)?” Jump to 31:00 in the webinar to hear the answers to these and many more questions about incorporating these strategies into your automotive development project.
As a final tidbit, one of our audience members recommended a book, “Car Hacks and Mods for Dummies.”
• Sign up for our educational series of exclusive videos, articles, and white papers geared towards making you a better automotive developer here
• Watch this webinar on how static analysis improves automotive functional safety, including more details on ISO 26262 certification
• Read this white paper for three steps towards protecting software against attack, identifying critical coding errors, and managing functional safety issues