| Type | When Used | Approval Level |
|---|---|---|
| Permitted exception | Standard itself allows exception in specific context | Engineer; document rationale |
| Project deviation | Project decision to deviate from required rule | Safety Manager + Technical Lead |
| Local deviation | Single specific occurrence with unique justification | Engineer; reviewed in code review |
| Category deviation | Entire category of rule violated for valid architectural reason | Safety Manager; architectural review |
Deviation Types
Deviation Form Template
YAMLdeviation_form.yaml
# MISRA C:2012 Deviation Record
deviation:
id: DEV-2025-001
rule: "Rule 11.3"
rule_text: "A cast shall not be performed between a pointer to object
type and a pointer to a different object type"
category: required
location:
file: "src/Can_Driver.c"
lines: [142, 156, 203]
violation_description: |
CAN frame data accessed as uint8_t* from void* payload pointer.
Required by AUTOSAR CanIf API definition (const void* parameter).
justification: |
1. The void* pointer originates from a uint8_t array (Can_Frame.data[]).
2. uint8_t has alignment requirement of 1 byte; no alignment UB.
3. Strict aliasing: uint8_t is permitted to alias any type (C11 6.5p7).
4. Cast is bounded: only sizeof(Can_Frame.data) bytes accessed.
5. Pattern reviewed by Safety Manager; no defect possible.
alternatives_considered: |
memcpy() alternative considered but rejected: requires additional
buffer copy; performance impact in 1ms CAN receive task unacceptable.
approval:
approver: "J. Schmidt (Safety Manager)"
date: "2025-01-20"
review_record: "DR-2025-CAN-001"Summary
The deviation form is the document that converts an unmanaged MISRA violation into a managed and auditable decision. ASPICE assessors distinguish between "violations that were not noticed" and "deviations that were analysed, justified, and approved" -- only the latter is acceptable. The quality of the justification section is the key differentiator: a justification that simply says "required by architecture" is weak; a justification that explains why the specific code pattern is safe despite violating the rule (alignment correctness, bounds checking, specific C standard provision) demonstrates that the deviation was genuinely analysed rather than rubber-stamped.
🔬 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.