Residual Risk Evaluation Methods

Residual Risk in SOTIF Context

What Is Residual Risk?

Residual risk in SOTIF is the remaining probability of hazardous behaviour after all design measures have been applied and V&V has been completed. Unlike ISO 26262 where residual risk can be calculated from failure rates and diagnostic coverage, SOTIF residual risk is an estimate based on:

Scenario coverage: what fraction of the scenario space has been verified safe?
Statistical evidence: how many test exposures were completed without failure?
Known limitations: what known unsafe scenarios (Q2) remain with their risk levels?
Unknown exposure: what is the estimated size of the unknown scenario space?

Method	Description	Strength	Limitation
Statistical (binomial)	N scenarios without failure -> confidence bound on failure rate	Quantitative; ISO-accepted	Only covers tested parameter space
Scenario coverage argument	Coverage metric: % of ODD scenarios verified safe	Systematic; traceable	Coverage metric accuracy depends on scenario taxonomy completeness
Comparative benchmark	Compare to human driver baseline	Practical reference point	Human driver baseline data difficult to obtain
Expert judgment	Safety manager assessment of residual risk	Captures tacit knowledge	Subjective; difficult to defend to regulator

Safety Argument for Residual Risk Acceptability

YAMLsotif_safety_argument.yaml

# SOTIF safety argument structure (GSN notation in YAML)
goal:
  id: G1
  claim: "AEB residual risk is acceptable per ISO 21448 Cl.9"
  strategy: "Argue via scenario coverage + statistical evidence"

sub_goals:
  - id: G2
    claim: "All identified Q2 (known unsafe) scenarios addressed by design"
    evidence:
      - "TC register: 12 TCs identified; all with design measures"
      - "Q2 scenario list: 0 remaining unaddressed Q2 scenarios"

  - id: G3
    claim: "Q3/Q4 (unknown) scenario space is acceptably small"
    evidence:
      - "Adversarial simulation: 50k scenarios; 0 new Q4 discovered"
      - "TC taxonomy coverage: all 9 TC categories addressed"
      - "50,000 km public road: 0 new failure modes observed"

  - id: G4
    claim: "Statistical confidence in Q1 scenario performance achieved"
    evidence:
      - "3,000 rain scenarios: 0 failures; C=95% for P < 0.001"
      - "Closed-track: 150 physical scenarios; all pass"

conclusion:
  "Residual risk acceptable. Proceed to production release."

Summary

The residual risk evaluation is the culminating SOTIF activity that converts testing results into a release decision. The structured safety argument (using GSN or similar notation) is important because it makes the reasoning explicit and auditable: each claim maps to specific evidence, and the chain from evidence to goal is traceable. A common weakness in SOTIF safety arguments is the treatment of G3 (unknown scenario space): claims like "we have identified all scenarios" are very difficult to defend. The more defensible argument is "our adversarial simulation and diverse real-world testing program did not discover new failure modes, providing evidence that the unknown scenario space does not contain easily discoverable Q4 hazards".

🔬 Deep Dive — Core Concepts Expanded

This section builds on the foundational concepts covered above with additional technical depth, edge cases, and configuration nuances that separate competent engineers from experts. When working on production ECU projects, the details covered here are the ones most commonly responsible for integration delays and late-phase defects.

Key principles to reinforce:

Configuration over coding: In AUTOSAR and automotive middleware environments, correctness is largely determined by ARXML configuration, not application code. A correctly implemented algorithm can produce wrong results due to a single misconfigured parameter.
Traceability as a first-class concern: Every configuration decision should be traceable to a requirement, safety goal, or architecture decision. Undocumented configuration choices are a common source of regression defects when ECUs are updated.
Cross-module dependencies: In tightly integrated automotive software stacks, changing one module's configuration often requires corresponding updates in dependent modules. Always perform a dependency impact analysis before submitting configuration changes.

🏭 How This Topic Appears in Production Projects

Project integration phase: The concepts covered in this lesson are most commonly encountered during ECU integration testing — when multiple software components from different teams are combined for the first time. Issues that were invisible in unit tests frequently surface at this stage.
Supplier/OEM interface: This is a topic that frequently appears in technical discussions between Tier-1 ECU suppliers and OEM system integrators. Engineers who can speak fluently about these details earn credibility and are often brought into critical design review meetings.
Automotive tool ecosystem: Vector CANoe/CANalyzer, dSPACE tools, and ETAS INCA are the standard tools used to validate and measure the correct behaviour of the systems described in this lesson. Familiarity with these tools alongside the conceptual knowledge dramatically accelerates debugging in real projects.

⚠️ Common Mistakes and How to Avoid Them

Assuming default configuration is correct: Automotive software tools ship with default configurations that are designed to compile and link, not to meet project-specific requirements. Every configuration parameter needs to be consciously set. 'It compiled' is not the same as 'it is correctly configured'.
Skipping documentation of configuration rationale: In a 3-year ECU project with team turnover, undocumented configuration choices become tribal knowledge that disappears when engineers leave. Document why a parameter is set to a specific value, not just what it is set to.
Testing only the happy path: Automotive ECUs must behave correctly under fault conditions, voltage variations, and communication errors. Always test the error handling paths as rigorously as the nominal operation. Many production escapes originate in untested error branches.
Version mismatches between teams: In a multi-team project, the BSW team, SWC team, and system integration team may use different versions of the same ARXML file. Version management of all ARXML files in a shared repository is mandatory, not optional.

📊 Industry Note

Engineers who master both the theoretical concepts and the practical toolchain skills covered in this course are among the most sought-after professionals in the automotive software industry. The combination of AUTOSAR standards knowledge, safety engineering understanding, and hands-on configuration experience commands premium salaries at OEMs and Tier-1 suppliers globally.