| Required Content | Description | Example (EPS) |
|---|---|---|
| Functional description | What the item does at vehicle level | 'Provides steering assistance proportional to vehicle speed and steering torque' |
| Interfaces | All inputs/outputs at item boundary | 'CAN: vehicle speed, engine torque; PWM: motor current; hardwired: steering torque sensor' |
| Physical boundary | Hardware components included | 'EPS ECU, PMSM motor, torque sensor, column angle sensor, power supply' |
| Legal/regulatory constraints | Standards and regulations applicable | 'ECE R79 (steering), ISO 26262, ISO 13849 (for external components)' |
| Known hazards | Pre-identified hazards from experience | 'Loss of steering assistance, unintended steering torque' |
| Prior incidents | Field data, recalls, FMEA from similar items | 'Reference to prior EPS FMEA; 3 field incidents in prior generation' |
Item Definition: ISO 26262 Part 3 Clause 5
Operational Scenarios for HARA
| Scenario | Driving Condition | Relevance to Safety Analysis |
|---|---|---|
| Highway cruise | v > 100 km/h; motorway; dense traffic | High severity if function lost (S3); high exposure (E4) |
| City low-speed | v < 30 km/h; urban stop-go | Lower severity (S1-S2); high exposure (E4) |
| Parking | v ≈ 0; manoeuvring | Low severity; very high exposure |
| Motorway entry/exit | Speed change 0–130 km/h; lane change | Relevant for adaptive cruise, lane keep |
| Emergency manoeuvre | Hard braking, swerving | Highest controllability demand (C3) |
| Slippery road (ice/wet) | Reduced tyre friction | Lower controllability — driver cannot correct |
| Night driving | Reduced visibility | Relevant for camera-based ADAS |
| Vehicle empty vs loaded | Mass affects braking distance | Relevant for AEB timing calibration |
Item Boundary Definition Template
Markdownitem_boundary.md
# Item Boundary: Forward Collision Avoidance Braking (FCAB)
## Elements INSIDE the Item
| Element | Type | Description |
|-------------------------|-------------|--------------------------------------|
| FCAB Domain Controller | Hardware+SW | Main ECU: perception, decision, actuation |
| Front Radar Sensor | Hardware+SW | 77 GHz; provides object list via CAN |
| Front Camera Module | Hardware+SW | Provides object/lane data via Ethernet |
| Wiring harness (FCAB) | Hardware | Power + communication within item |
## Elements OUTSIDE the Item (external interfaces)
| External Element | Interface | Data / Signal |
|-------------------------|-------------|--------------------------------------|
| Brake System ECU | CAN (ASIL-D)| FCAB sends: emergency_brake_request |
| HMI / Instrument Cluster| CAN | FCAB sends: fcw_warning_active |
| Body CAN bus | CAN | FCAB receives: vehicle_speed, yaw_rate|
| Power supply module | 12V hardwired| FCAB ECU power; under/over-voltage monitored |
| GNSS module | Ethernet | Position (not safety-critical path) |
## Exclusions (explicitly NOT part of this item)
- Brake hydraulics and actuators (part of Brake System Item)
- Driver assistance arbitration (separate ADAS arbitration item)
- Camera thermal management (body control item)
## Operating Environment
- Temperature: -40°C to +85°C ambient; -40°C to +125°C ECU junction
- Supply voltage: 9V–16V (normal); 6V–32V (transient per ISO 7637)
- Vibration: per ISO 16750-3 (road vehicle category B)Summary
The item definition is the foundational document for the entire safety case — every subsequent safety analysis refers back to it. The most common item definition error is an incomplete or ambiguous boundary: if the boundary between the FCAB item and the Brake System item is not precisely defined, then neither team knows who is responsible for the ASIL-D brake request interface. Each external interface at the item boundary must be explicitly specified with its data content, protocol, ASIL level, and the assumption about the external element's behaviour. These are the basis for the Hardware-Software Interface (HSI) specification developed later in the system lifecycle.
🔬 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.