Trimble Develops ISO 26262–Compliant GNSS Software with Polyspace
Software Was Built from the Ground Up to Ensure Safety Compliance
“Using Polyspace, we avoid flaws and critical issues from the beginning of our project, so the code converges to a high level of quality very fast. The project is easier to maintain and to enrich with new functionalities. Polyspace was key to meeting ISO 26262 requirements for our automotive projects.”
Key Outcomes
- Met automotive electronic systems safety and security standards using Polyspace
- Reduced project development time and enabled developers to write better code
- Easily maintained project with enriched functionality and out-of-the-box reporting
Using Polyspace, Trimble developed safety-compliant software for the automotive industry from the ground up.
Trimble delivers leading positioning and orientation technology to major industrial markets worldwide. This approach is built on decades of engineering expertise, system intelligence, and field-proven solutions—covering billions of acres and millions of miles. Trimble’s autonomous technology enables advanced and precise operations on-road, which are designed to meet the unique needs of their customers no matter where they are on their journey.
The company had previously developed and implemented GNSS receivers and associated software for several industries. But attempting to modify the existing software for automotive safety compliance was judged too risky to finish on time. Instead, new software for the automotive industry was created from the ground up to ensure compliance with the Automotive Safety Integrity Level scheme defined by the ISO® 26262 Functional Safety for Road Vehicles standard.
Trimble selected Polyspace® because it was ISO 26262 certified and could be incorporated without additional tool qualification. It fits the DevOps continuous integration pipeline to provide traceable justifications and support evidence in assessment, analyze every change in the code, and generate functional reports out of the box.
The project was easier to maintain with enriched functionality because the code converges to a high level of quality very fast. Complex modules could be analyzed, flaws and critical issues could be avoided from the start, and complex code scenarios—which could not be covered by unit tests—were detected. Developers quickly adapted safe patterns to avoid Polyspace warnings. This helped speed up the overall project since fewer iterations were needed, and it sharpened the ability of developers to write better code.
