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

The Four-Quadrant Scenario Model

Known/Unknown Safe/Unsafe Matrix
                    KNOWN          |      UNKNOWN
                                   |
   SAFE    |  Q1: Known Safe       |  Q3: Unknown Safe
           |  Tested; verified     |  Not yet explored
           |  safe behaviour       |  Assumed safe but
           |                       |  not confirmed
           |  Goal: maximise Q1    |  Goal: reduce Q3
  ---------+--------- ------------+------------------
  UNSAFE   |  Q2: Known Unsafe     |  Q4: Unknown Unsafe
           |  Identified; measures |  Not yet identified
           |  applied or ODD       |  MOST DANGEROUS
           |  restricted           |  Goal: find these
           |                       |  and move to Q2

  SOTIF goal: maximise Q1; eliminate Q2 via design;
              reduce Q3+Q4 via systematic exploration

Scenario Population Tracking

Pythonscenario_tracker.py
"""Track SOTIF scenario population across four quadrants."""
from dataclasses import dataclass, field
from enum import Enum
from typing import List

class ScenarioStatus(Enum):
    KNOWN_SAFE   = "Q1_known_safe"
    KNOWN_UNSAFE = "Q2_known_unsafe"
    UNKNOWN_SAFE = "Q3_unknown_safe"    # assumption, not tested
    UNKNOWN_UNSAFE = "Q4_unknown_unsafe"  # not yet discovered

@dataclass
class SOTIFScenario:
    id: str
    description: str
    triggering_condition: str
    status: ScenarioStatus
    evidence: str = ""
    design_measure: str = ""

@dataclass
class ScenarioDatabase:
    feature: str
    scenarios: List[SOTIFScenario] = field(default_factory=list)

    def coverage_q1_pct(self) -> float:
        """Percentage of known-safe scenarios (SOTIF coverage KPI)."""
        known = [s for s in self.scenarios
                 if s.status in (ScenarioStatus.KNOWN_SAFE,
                                 ScenarioStatus.KNOWN_UNSAFE)]
        q1 = [s for s in self.scenarios
              if s.status == ScenarioStatus.KNOWN_SAFE]
        if not known: return 0.0
        return len(q1) / len(known) * 100

    def summary(self):
        counts = {s: 0 for s in ScenarioStatus}
        for sc in self.scenarios:
            counts[sc.status] += 1
        for status, count in counts.items():
            print(f"  {status.value}: {count}")
        print(f"  Q1 coverage: {self.coverage_q1_pct():.1f}%")

Summary

The four-quadrant model is the most operationally useful SOTIF concept because it converts the abstract goal of "SOTIF completeness" into a concrete engineering task: systematically move scenarios from Q3/Q4 (unknown) into Q1 (known safe) by testing them, while addressing Q2 (known unsafe) through design improvements or ODD restrictions. The most dangerous quadrant is Q4 (unknown unsafe) -- scenarios where hazardous behaviour exists but has not been discovered. Identifying Q4 scenarios requires adversarial testing techniques: simulation-based exploration, corner case generation, and real-world data analysis specifically designed to find failure modes that naive scenario databases miss.

🔬 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.

← PreviousISO 21448 Framework and ScopeNext →Triggering Conditions and Use Cases