Functional Architecture Design - System Architecture

Vehicle Function Types

Function Type	Description	Examples	ASIL Typical
Safety function	Directly implements a safety goal; ASIL-allocated	AEB braking, EPS torque limit, airbag trigger	ASIL-B to ASIL-D
Driver assistance function	Enhances driving but not safety-critical	ACC gap hold, LKA lane centering, parking camera	QM to ASIL-B
Comfort/body function	Driver comfort; no safety implication	Seat memory, ambient lighting, climate control	QM
Infrastructure function	Platform service used by other functions	OTA update manager, diagnostic gateway, power management	QM to ASIL-A
Infotainment function	Media, navigation, connectivity	Navigation, streaming, voice assistant	QM

Function Decomposition Tree

YAMLfunction_tree.yaml

# Functional architecture: AEB function decomposition
function:
  id: F-AEB
  name: "Automatic Emergency Braking"
  asil: ASIL-B
  decomposition:
    - id: F-AEB-01
      name: "Object Detection"
      asil: ASIL-B
      inputs:  [camera_image_raw, radar_targets]
      outputs: [detected_objects_list]
      sub_functions:
        - id: F-AEB-01-01
          name: "Camera Object Classifier"
          inputs: [camera_image_raw]
          outputs: [camera_object_list]
        - id: F-AEB-01-02
          name: "Radar Target Processor"
          inputs: [radar_raw_targets]
          outputs: [radar_object_list]
        - id: F-AEB-01-03
          name: "Sensor Fusion"
          inputs: [camera_object_list, radar_object_list]
          outputs: [detected_objects_list]
    - id: F-AEB-02
      name: "Threat Assessment"
      asil: ASIL-B
      inputs:  [detected_objects_list, ego_speed, ego_accel]
      outputs: [ttc_s, threat_level]
    - id: F-AEB-03
      name: "Brake Request Generation"
      asil: ASIL-B
      inputs:  [ttc_s, threat_level]
      outputs: [aeb_brake_request_pct]
      safety_goal: "SG-AEB-01: Vehicle shall decelerate when AEB activated"

Summary

Functional architecture design is the activity that transforms a requirements list into a structured model of what the vehicle does -- independently of how or where it does it. The function decomposition tree is the key artefact: it makes the ASIL allocation auditable (each sub-function inherits or refines the ASIL of its parent), it makes interface dependencies explicit (F-AEB-01-03 Sensor Fusion depends on both camera and radar outputs, so those two sensors cannot be allocated to the same ECU without a careful independence argument), and it prepares the allocation decision by making the function granularity visible. Functions that are too coarse (whole ADAS domain as one function) cannot be allocated meaningfully; functions that are too fine (individual algorithm steps) make the allocation table unmanageable.

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