Elevating Software Quality in Automotive Engineering: The SQIL Approach by Volkswagen

Feb 2025 | Automotive, Quality

In the ever-evolving landscape of automotive engineering, ensuring high software quality is a key challenge. With the increasing complexity of vehicle functionalities and the integration of advanced driver-assistance systems (ADAS), maintaining stringent quality standards is essential. Volkswagen introduced the Software Quality Improvement Leader (SQIL) initiative to bridge the gap between software quality and supplier collaboration, ensuring the highest standards in automotive software development.

#automotive #software quality

We delve into the SQIL approach, the need for additional criteria beyond Automotive SPICE, insights from leading industry players such as BOSCH and HELLA, and the significance of monitoring software quality trends. By leveraging established methodologies, SQIL ensures a rigorous and structured approach to software quality improvement.

%

Software-Related Recalls

In 2024, software issues accounted for 15% of all vehicle recalls in the United States, a notable increase from 6% five years prior. Source: Financial Times

%

Quality Concerns Among Developers

A 2024 survey revealed that 29% of automotive software professionals identified software quality as their primary concern, surpassing safety. Source: DevPro Journal

The Need for Extending Automotive SPICE with KGAS

Understanding Automotive SPICE

Automotive SPICE (ASPICE) is a widely adopted framework for assessing and improving software development processes in the automotive industry. It ensures that suppliers follow a structured and quality-driven development process. However, Volkswagen identified areas where additional criteria were needed to enhance software quality further. This led to the development of Konzerngrundanforderungen Software (KGAS) or Group Basic Requirements Software.

KGAS – Strengthening Automotive SPICE

Vehicles today are not just assemblies of individual components but interconnected ecosystems of features and functionalities. A steering system, for example, is responsible for multiple interrelated tasks, such as:

  • Sending steering angle data to the Electronic Stability Program (ESP)
  • Interfacing with torque vectoring and active damping systems
  • Communicating with ADAS for self-driving capabilities

To manage this complexity, Volkswagen introduced KGAS, an extension of ASPICE that provides additional consistency and traceability requirements. Some key requirements include:

  • KGAS_3193: All requirements must be evaluated in terms of risks and feasibility.
  • KGAS_3247: Requirements must be unambiguous.
  • KGAS_3267: Specification of system/software requirements must follow a structured format (IF THEN ).

By enforcing these criteria, KGAS ensures that software development is robust, traceable, and aligned with functional safety standards.

The Role of the Software Quality Improvement Leader (SQIL)

Key Responsibilities of an SQIL

An SQIL is responsible for maintaining software quality across Volkswagen’s supplier network. The primary responsibilities include:

  1. Process Quality Assurance – Ensuring compliance with ASPICE and KGAS.
  2. Consistency Checks – Verifying the integrity and traceability of requirements, design, and test cases.
  3. Monitoring Trends – Using key performance metrics to track development progress and identify areas of improvement.
  4. Reporting – Monthly reporting to Volkswagen’s quality department to ensure transparency and continuous improvement.

SQIL Report Components

1. Process Reviews and KGAS Compliance

Process reviews are an integral part of SQIL activities. They involve:

  • Ensuring that project activities align with established processes.
  • Incorporating KGAS requirements into checklists.
  • Regular bi-monthly reviews to identify compliance gaps.

2. Consistency Check of Requirements

SQIL ensures that requirements maintain bidirectional traceability, meaning that every software requirement must be linked to its design, implementation, and test case. Poorly defined requirements often lead to software defects despite high test coverage. To mitigate this, SQIL reviews the entire development chain from system requirements to code implementation.

3. Monitoring Software Development Performance

SQIL reports leverage metrics based on Automotive SPICE Annex D, which defines key performance indicators for software traceability and verification. Some of the crucial metrics include:

  • Number of system/software features planned vs. implemented
  • Percentage of verified system/software requirements
  • Traceability of software components from requirements to test cases
  • Cyclomatic complexity analysis for code maintainability

Regular monitoring and trend analysis allow Volkswagen to proactively address potential quality issues before they escalate.

%

Warranty Cost Reduction Through AI

An automotive OEM implementing AI-driven quality management experienced a 15% reduction in annual warranty costs, decreasing from $2 billion to $1.7 billion. Source: Viaduct – The AI Revolution in Automotive Quality: A Data-Driven Perspective

%

Customer Satisfaction Improvement

The same OEM saw customer satisfaction scores rise from 72% to 86% after adopting AI-enhanced quality management strategies. Source: Viaduct – The AI Revolution in Automotive Quality: A Data-Driven Perspective

Case Studies: Industry Experiences with SQIL Implementation

BOSCH AS: Automated Metrics and Reusable Components

BOSCH Automotive Steering Systems implemented SQIL methodologies in Volkswagen’s MQB platform, which significantly streamlined quality tracking. Key strategies included:

  • Automating Metrics: The Q-Report was developed to automatically generate traceability and test coverage metrics, reducing manual effort.
  • Baukasten (Modular Approach): Standardized system and software functions were developed with reusability in mind, improving efficiency and consistency.
  • Safety and Non-Safety Coverage Separation: Separate tracking for ASIL-D (safety-critical) and QM (non-safety-critical) requirements enhanced functional safety assessments.

HELLA: Dashboard-Driven Quality Tracking

HELLA adopted SQIL principles through a dashboard-based quality monitoring system. This approach enabled:

  • Monthly tracking of system/software requirement implementation trends
  • Process compliance evaluation using ASPICE and KGAS criteria
  • Early identification of process deficiencies through consistency checks

By embedding SQIL methodologies into standard project workflows, HELLA ensured compliance with Volkswagen’s rigorous quality expectations.

Future Outlook for SQIL and Software Quality Improvement

Volkswagen is further refining the SQIL framework by introducing enhanced dashboard functionalities and expanded documentation requirements. The latest initiatives include:

  • Integrating AI-driven anomaly detection to predict potential software defects.
  • Aligning with cybersecurity frameworks to enhance protection against automotive cyber threats.
  • Extending SQIL to self-driving and cloud-connected functionalities, addressing new-age automotive software challenges.

Conclusion

The SQIL initiative by Volkswagen represents a significant leap in software quality assurance within the automotive sector. By extending Automotive SPICE with KGAS, enforcing rigorous traceability, and leveraging automated quality tracking, Volkswagen ensures that its suppliers deliver high-quality, safe, and reliable software.

As automotive technology advances towards full autonomy and cloud integration, structured quality management will remain the foundation of success. The SQIL framework serves as a model for other manufacturers aiming to enhance software quality in a rapidly evolving landscape.

References

  • Automotive SPICE 3.0, VDA AK13, July 2015.
  • KGAS (Group Basic Requirements Software), Volkswagen, 2015.
  • Messnarz, R., Kreiner, C., Riel, A. “Integrating Automotive SPICE, Functional Safety, and Cybersecurity Concepts.” Software Quality Professional, 2016.
  • VDA Yellow Book, Automotive SPICE Guidelines, 2017.
  • The SPI Manifesto, EuroSPI 2009, Alcala, Spain

Wanna know more? Let's dive in!