“On 2 to 3 million lines of code, we ran Klocwork against multiple competitors. It handled the code base very well and had the ability to deal with C++ templates in a useful way … there was also a low rate of false positives.”
-Mr Alexander Much, head of software systems engineering, Elektrobit.
Why use SCA?
Elektrobit touches nearly every car on the road today. Whether it’s an assistance system invisible to the driver or navigation technology built for complex human interaction. Over 25 years, Elektrobit has delivered products that major car manufacturers and suppliers trust to perform and perform safely. The cost of quality or functional safety defects in the field for systems that are hard to update is very high. Especially with the potential for damaging trusted relationships with customers.
With growing systems complexity and accelerating release cycles, Elektrobit’s software engineering group needed an SCA solution. Particularly that prevented code defects before they reached testing or the customer. Enter static code analysis. Alexander Much used his experience as a former programmer to bring SCA to the process improvement table. Code improvement and safety were foremost on his mind. But he knew that new tools would be a hard sell to programmers.
“Defects and recalls are expensive and we can’t afford to have them. My experience has taught me that if you’re not using SCA nowadays, you’re not state-of-the-art. This isn’t the first time we’ve introduced SCA at Elektrobit and the most important thing is gaining the trust of the programming teams.”
Like Elektrobit’s products, adopting SCA in the development process was as much about the technology as it was about establishing the confidence of programmers.
When Elektrobit chose to adopt a new Static Code Analysis (SCA) tool, it went through a thorough technical evaluation to get the right tool and people on board within the organization. This case study explains the process and the successful results achieved by choosing Klocwork.