You are reading part 2 of our series of articles on quality assurance for automotive software
Requirements for automotive software are growing on multiple levels simultaneously. Shorter development cycles demand more efficient testing processes. At the same time, regulatory requirements for functional safety and cybersecurity are tightening. Since July 2024, UN Regulations R155 and R156 apply to all new vehicles in the EU. These automotive software requirements can only be managed with an integrated approach combining automation and systematic validation.
Manual testing alone can no longer handle the growing test scope of modern automotive software. The variety of modern vehicle platforms, frequent software updates, and tight schedules require automated solutions. Typical challenges include:
Automated tests drastically reduce testing time and deliver reproducible, consistent results. They scale flexibly across platforms and variants. Modern approaches use virtualized ECUs and digital twins to test automotive software before physical hardware is available.
Safety-critical systems such as brakes, steering, and driver assistance are subject to ISO 26262. The standard defines Automotive Safety Integrity Levels (ASIL A to D) based on severity, probability of occurrence, and controllability of hazards. The higher the ASIL, the stricter the requirements for development and verification of automotive software.
The process begins with a comprehensive risk analysis (HARA). This leads to safety requirements that must be verified through specific verification and validation tests. The third edition of ISO 26262 is expected in 2027 and will include updates for AI-based systems.
With UN Regulations R155 and R156, binding cybersecurity requirements have applied since July 2024 to all new vehicles in UNECE member states. The core requirements for automotive software include:
Without appropriate certification, manufacturers do not receive type approval. The requirements cascade through the supply chain: Tier-1 and Tier-2 suppliers must also provide compliance evidence for their automotive software. ISO/SAE 21434 provides the engineering framework for implementation.
We combine expertise in test automation with in-depth safety and security know-how for automotive software:
Contact us about your requirements. Together we'll create the foundation for secure, reliable automotive software.
Automated tests are faster, reproducible, and scalable. They enable more frequent regression testing and provide consistent evidence for assessments and audits.
ISO 26262 addresses functional safety of automotive software, i.e., protection against malfunctions. UN R155 focuses on cybersecurity, i.e., protection against intentional attacks.
Since July 2024, UN R155 has applied to all newly registered vehicles in UNECE member states. The first phase from July 2022 only concerned new vehicle types.
A Cybersecurity Management System comprises processes, roles, and measures for identifying, evaluating, and treating cybersecurity risks for automotive software throughout the entire vehicle lifecycle.
Firstname:
Lastname:
E-Mail Address:
Phone:
Subject:
Your message:
Yes, I consent to my personal data being collected and stored electronically. My data will only be used for the purpose of responding to my inquiry. I have taken note of the privacy policy.
You are currently viewing a placeholder content from OpenStreetMap. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
You need to load content from hCaptcha to submit the form. Please note that doing so will share data with third-party providers.
You are currently viewing a placeholder content from Hubspot Meetings. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.
You are currently viewing a placeholder content from Google Maps. To access the actual content, click the button below. Please note that doing so will share data with third-party providers.