Functional scenario (abstract)
"AEB approaching stationary vehicle"
|
Logical scenario (parameter ranges)
speed: 30-80 km/h; distance: 20-60m; road: dry/wet
|
Concrete scenario (specific values)
speed=50 km/h; distance=35m; road=wet; rain=1mm/h;
target=white sedan; lighting=overcast
SOTIF testing requires coverage at all three levels:
- All functional scenarios within ODD: verified
- Critical parameter boundaries tested
- Representative concrete scenarios executedScenario Hierarchy for SOTIF Testing
Concrete Scenario Generator
"""Generate concrete test scenarios from logical scenario definition."""
import itertools
from dataclasses import dataclass
from typing import List
@dataclass
class ConcreteScenario:
scenario_id: str
ego_speed_kmh: float
target_dist_m: float
weather: str
lighting: str
target_type: str
expected_action: str
def generate_aeb_scenarios() -> List[ConcreteScenario]:
"""Generate boundary and representative AEB test scenarios."""
scenarios = []
idx = 1
# Boundary values
speeds = [10, 30, 50, 79, 80] # ODD: 10-80
distances = [15, 25, 35, 50] # detection range sweep
weathers = ["dry", "light_rain", "heavy_rain"]
lightings = ["daylight", "overcast", "night_urban"]
target_types = ["sedan", "truck", "pedestrian", "cyclist"]
for speed, dist, weather, light, target in itertools.product(
speeds, distances, weathers, lightings, target_types):
# Determine expected action based on conditions
if weather == "heavy_rain" or light == "night_unlit":
expected = "hmi_warning_only"
elif dist < 20 and speed > 60:
expected = "aeb_activate"
elif dist >= 40:
expected = "no_action"
else:
expected = "aeb_activate"
scenarios.append(ConcreteScenario(
scenario_id=f"SC_{idx:04d}",
ego_speed_kmh=speed, target_dist_m=dist,
weather=weather, lighting=light,
target_type=target, expected_action=expected
))
idx += 1
return scenarios
scenarios = generate_aeb_scenarios()
print(f"Generated {len(scenarios)} concrete scenarios")
activate = sum(1 for s in scenarios if s.expected_action=="aeb_activate")
print(f" AEB activate: {activate}")
print(f" Warning only: {sum(1 for s in scenarios if s.expected_action=="hmi_warning_only")}")Summary
Scenario-based testing for SOTIF is fundamentally a coverage problem: the question is not "did the system pass these tests?" but "do these tests cover the scenario space sufficiently to justify claiming the residual risk is acceptable?". The three-level scenario hierarchy (functional, logical, concrete) provides the framework for answering that question: functional scenario coverage shows all hazardous event types are addressed; logical scenario coverage shows the parameter space is covered at the boundaries; concrete scenario execution provides the actual evidence. The combinatorial explosion (5 speeds x 4 distances x 3 weathers x 3 lightings x 4 targets = 720 scenarios) is why simulation is essential for SOTIF -- running all combinations in real-world testing is not feasible.
🔬 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.