Home Learning Paths ECU Lab Assessments Interview Preparation Arena Pricing Log In Sign Up

Role of Real-World Testing in SOTIF

Testing TypePurposeSOTIF Contribution
Closed-track testingReproduce specific TCs in controlled conditionsEvidence for known scenario performance
Public road testingEncounter organic real-world conditionsDiscover Q4 scenarios; build statistical evidence
Fleet operation dataLarge-scale naturalistic exposureStatistical evidence; rare scenario discovery
Induced scenario testingCreate specific environmental conditionsBoundary verification; TC-specific evidence

ODD Coverage Data Collection

Pythonodd_coverage_logger.py
"""Log ODD parameters during real-world test drives."""
import time
import json
from dataclasses import dataclass, asdict

@dataclass
class ODD_DataPoint:
    timestamp_ms:    int
    vehicle_speed_kmh: float
    rain_mmh:        float    # from wiper/rain sensor
    visibility_m:    float    # from camera/forward radar
    lighting:        str      # daylight/overcast/night
    road_type:       str      # from HD map
    aeb_active:      bool
    aeb_degraded:    bool     # in degraded mode
    in_odd:          bool     # all params within ODD

def log_odd_coverage(duration_s: int,
                      output_file: str):
    """Log ODD coverage data for a test drive."""
    log = []
    start = time.time()

    while time.time() - start < duration_s:
        # In real vehicle: read from CAN/SOME-IP
        dp = ODD_DataPoint(
            timestamp_ms=int(time.time() * 1000),
            vehicle_speed_kmh=read_speed(),
            rain_mmh=read_rain_sensor(),
            visibility_m=read_visibility(),
            lighting=read_lighting_condition(),
            road_type=read_map_road_type(),
            aeb_active=read_aeb_active(),
            aeb_degraded=read_aeb_degraded(),
            in_odd=check_in_odd()
        )
        log.append(asdict(dp))
        time.sleep(1.0)  # 1 Hz logging

    with open(output_file, "w") as f:
        json.dump(log, f, indent=2)

    in_odd_pct = sum(1 for d in log if d["in_odd"]) / len(log) * 100
    print(f"ODD coverage: {in_odd_pct:.1f}% of drive time in ODD")

Summary

Real-world testing provides the irreplaceable validation signal that simulation cannot: confirmation that the system behaves correctly in the genuine complexity of actual traffic. The ODD coverage logger is the tool that converts a test drive into a structured evidence contribution: by logging which ODD parameters were encountered and for how long, it enables the coverage claim "the system was tested for X hours in rain, Y hours at night, Z hours at ODD speed boundary". Without this logging, a test drive produces anecdotal evidence; with it, the same drive produces quantitative ODD coverage data that directly feeds the statistical evidence framework for SOTIF residual risk evaluation.

🔬 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

  1. 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'.
  2. 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.
  3. 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.
  4. 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.

← PreviousSimulation for Unknown ScenariosNext →Statistical Evidence and Confidence Levels