GAC Builds a Scalable Software-Quality Framework for Software-Defined Vehicles
Embedding Software Quality Throughout the Development Lifecycle
“We went beyond industry standards by introducing enterprise-level requirements and making run-time error verification mandatory. This takes us further than industry standards—and we believe it is what truly improves software quality.”
Key Outcomes
- Established a four-layer software-quality framework spanning development, code submission, formal verification, and defect management
- Standardized run-time error verification as part of the company’s software-quality requirements, while driving supplier management upgrades
- Built a unified workflow for static analysis, formal verification, quality management, and reporting using Polyspace products
As software-defined vehicle architectures increase software complexity, automotive manufacturers must ensure code quality across growing codebases while meeting stringent safety and compliance requirements. At GAC, the move toward centralized vehicle architectures and increasingly sophisticated software systems highlighted the need for a more scalable approach to software quality. Rather than relying on end-stage verification, the company sought to embed quality assurance throughout the software development lifecycle.
GAC initially used traditional static analysis tools to enforce coding standards in conventional controllers and support a shift-left testing strategy. However, a serious run-time error escaped detection before testbench testing, causing a system halt and threatening a critical development program. GAC used Polyspace Code Prover™ to identify issues such as array bounds violations, invalid pointers, and standard library misuse. Engineers resolved the problem, put the program back on track, and recognized the need for deeper verification capabilities.
Building on that experience, GAC established a four-layer software-quality framework using Polyspace® products. Engineers use Polyspace as You Code™ to identify issues while coding, Polyspace Bug Finder™ to enforce coding standards, Polyspace Code Prover™ to verify the absence of critical run-time errors, and Polyspace Access™ to manage results and analyze quality trends. GAC also integrated Polyspace products into its continuous integration system, establishing a quality gate to prevent coding-standard violations and software defects from escaping. Together, these capabilities embed quality checks throughout development, from coding and code submission through formal verification and closed-loop defect management.
Today, GAC is standardizing these practices across its software development lifecycle and extending them to supplier-quality management. The company has expanded the scope of supplier software verification and added run-time error verification reports, creating a scalable foundation for developing reliable software-defined vehicles.