Hands-On: SDV Architecture Analysis - Software-Defined Vehicle

Lab: SDV Architecture Analysis

Exercise	Goal	Tool
Architecture comparison	Compare domain vs zone for a C-segment sedan	Spreadsheet / diagram
Zone ECU sizing	Determine compute requirements for front-left zone	Requirements analysis
Compute budget	Allocate HPC workloads across cores and accelerators	CPU/GPU/NPU utilisation model

Exercise 1: Architecture Comparison

YAMLarchitecture_comparison.yaml

# C-segment sedan: domain vs zone architecture comparison

domain_architecture:
  ecus: 87
  wiring_harness_kg: 52
  wiring_harness_km: 4.2
  bus_protocols: [CAN, CAN-FD, LIN, FlexRay, MOST]
  software_update:
    method: dealer_flash_each_ecu
    time_hours: 4
    cost_per_recall_usd: 500
  compute_total_mips: 12000  # distributed across all ECUs
  bom_cost_usd: 1800

zone_architecture:
  central_compute_nodes: 1  # + 3 zone ECUs
  zone_ecus: 3
  wiring_harness_kg: 28    # -46% vs domain
  wiring_harness_km: 1.8   # -57% vs domain
  bus_protocols: [1000BASE-T1, CAN-FD-bridge, LIN-bridge]
  software_update:
    method: ota_full_vehicle
    time_hours: 0.5  # overnight wireless
    cost_per_recall_usd: 0  # no dealer visit needed
  compute_total_tops: 254   # NVIDIA Orin
  bom_cost_usd: 1400       # lower ECU count despite HPC premium

# Key insight: wiring harness savings alone justify zone arch investment
# $400 BOM saving + $500/recall OTA saving = strong business case

Exercise 2: Zone ECU Requirements

YAMLzone_ecu_sizing.yaml

# Front-left zone ECU: function inventory and compute sizing

zone: front_left
functions:
  - name: window_lift_control
    type: actuator_control
    safety_asil: QM
    cpu_load_percent: 2
  - name: door_lock_control
    type: actuator_control
    safety_asil: QM
    cpu_load_percent: 1
  - name: exterior_mirror_fold
    type: actuator_control
    safety_asil: QM
    cpu_load_percent: 2
  - name: side_camera_aggregation
    type: sensor_fusion
    safety_asil: QM
    cpu_load_percent: 15
    requires_isp: true  # image signal processor
  - name: door_ajar_detection
    type: safety_monitor
    safety_asil: ASIL-B
    cpu_load_percent: 3
  - name: ethernet_gateway
    type: network
    cpu_load_percent: 8

total_cpu_load_percent: 31  # comfortable headroom on NXP S32G3
selected_mcu: NXP S32G3
rationale: S32G3 provides network processing + ASIL-D capable MCU cores
           + hardware security module (HSM) for secure OTA

Summary

The architecture analysis exercises reveal the concrete engineering trade-offs behind SDV design decisions. The 46% wiring harness weight reduction in zone architecture is not just a cost saving - it also reduces vehicle weight (fuel efficiency), reduces assembly complexity (fewer connectors), and improves reliability (fewer electrical connections). The zone ECU sizing exercise shows that even simple body functions accumulate to meaningful compute loads when aggregated: a zone with 6 body functions, a camera, and Ethernet gateway needs a real-time capable processor with networking support - not a small 8-bit MCU. The NXP S32G3 is the dominant choice for zone gateways because it combines automotive-grade Ethernet switching, CAN/LIN bridges, ASIL-capable lockstep cores, and a hardware security module in one package.

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