Component Interface Specification - System Architecture

Component Interface Types

Interface Type	Mechanism	Spec Format	Example
CAN signal	CAN frame/PDU on CAN bus	DBC file; AUTOSAR ARXML	VehicleSpeed CAN ID 0x1A3
SOME/IP service	UDP/TCP over Ethernet; SOME/IP SD	ARXML ServiceInterface; FIBEX	SpeedService::GetCurrentSpeed
DDS topic	DDS pub/sub over UDP multicast	OMG IDL; AUTOSAR DDS binding	Vehicle::Speed topic
AUTOSAR port/interface	AUTOSAR RTE; sender/receiver or C/S	ARXML PortInterface; SWC template	SWC-SpeedSensor RPort, SWC-AEB PPort
Hardware signal	Discrete I/O; PWM; ADC	Signal specification document	Brake pressure sensor 0–5V ADC

Signal Specification

YAMLsignal_spec.yaml

# Component interface signal specification
interface:
  provider:  "SpeedSensor_ECU"
  consumer:  "AEB_ECU"
  transport: "CAN-FD 500k/2M"

signals:
  - name:        VehicleSpeed
    can_id:      0x1A3
    byte_pos:    0
    bit_len:     16
    encoding:    unsigned
    factor:      0.01
    offset:      0.0
    unit:        km/h
    range:       [0.0, 250.0]
    cycle_ms:    10
    timeout_ms:  50
    asil:        ASIL-B
    e2e_profile: P02   # AUTOSAR E2E Profile 2 for ASIL-B
    note:        "CRC + counter per AUTOSAR E2E Lib"

  - name:        WheelSpeedFL
    can_id:      0x1A4
    byte_pos:    0
    bit_len:     16
    encoding:    unsigned
    factor:      0.01
    unit:        km/h
    cycle_ms:    5
    asil:        ASIL-B
    e2e_profile: P02

ARXML Interface Fragment

XMLSpeedService.arxml

<!-- AUTOSAR ARXML: SOME/IP ServiceInterface for speed service -->
<AR-PACKAGES>
  <AR-PACKAGE>
    <SHORT-NAME>Interfaces</SHORT-NAME>
    <ELEMENTS>
      <SERVICE-INTERFACE>
        <SHORT-NAME>SpeedService</SHORT-NAME>
        <SERVICE-ID>0x0A01</SERVICE-ID>
        <EVENTS>
          <I-SIGNAL-I-PDU-GROUP>
            <SHORT-NAME>VehicleSpeedEvent</SHORT-NAME>
            <EVENT-ID>0x0001</EVENT-ID>
            <DATA-ELEMENT-REFS>
              <DATA-ELEMENT-REF>VehicleSpeed_kmh</DATA-ELEMENT-REF>
            </DATA-ELEMENT-REFS>
          </I-SIGNAL-I-PDU-GROUP>
        </EVENTS>
        <METHODS>
          <CLIENT-SERVER-INTERFACE>
            <SHORT-NAME>RequestSpeedLimit</SHORT-NAME>
            <METHOD-ID>0x0010</METHOD-ID>
          </CLIENT-SERVER-INTERFACE>
        </METHODS>
      </SERVICE-INTERFACE>
    </ELEMENTS>
  </AR-PACKAGE>
</AR-PACKAGES>

Summary

Component interface specification is the contract between the OEM system architect and the Tier-1 ECU supplier. A complete interface specification removes the most common cause of ECU integration failures: signal interpretation ambiguity. The specification must define not just the signal name and range, but the encoding (is VehicleSpeed = 0x0000 a valid "zero speed" or an error code?), the E2E protection profile (which CRC polynomial, which counter wrapping), the timeout behaviour (what does the consumer do when the signal is missing for 50ms?), and the ASIL level. Each of these details, if left ambiguous, will be resolved differently by the OEM and the Tier-1 -- and the mismatch will be discovered during integration, which is the most expensive time to find it.

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