| Category | Definition | Deviation Allowed? | Typical Examples |
|---|---|---|---|
| Mandatory | Must be complied with; no deviation permitted under any circumstances | No | Rule 17.2: No recursion; Rule 13.6: No side effects in sizeof |
| Required | Should be complied with; deviation requires formal justification | Yes, with justification | Rule 15.5: Single exit; Rule 10.1-10.8 essential types |
| Advisory | Recommended practice; deviation may be accepted by project | Yes, easier process | Rule 15.4: Only one break per loop; Rule 12.1: Precedence clarity |
Rule Category Definitions
Project Rule Configuration
XMLmisra_config.xml
<!-- MISRA C:2012 project rule configuration -->
<MISRAConfiguration project="SpeedController" asil="ASIL-B">
<!-- All mandatory rules: always enforced -->
<MandatoryRules enforcement="error"/>
<!-- Required rules: enforced as errors for ASIL-B -->
<RequiredRules enforcement="error"/>
<!-- Advisory rules: warnings; deviation easier -->
<AdvisoryRules enforcement="warning"/>
<!-- Project-specific suppressions (with justification) -->
<Suppressions>
<Suppress rule="Rule-15.5" file="Os_Stub.c"
justification="OS stub has multiple returns for test efficiency;
not production code; reviewed and approved 2025-01-10"/>
<Suppress rule="Rule-11.3" file="Can_Stub.c"
justification="CAN frame byte access requires pointer cast;
pattern reviewed; no UB possible with uint8_t* cast"/>
</Suppressions>
<!-- Record deviations for required rules -->
<Deviations>
<Deviation rule="Rule-10.5" count="3"
approver="SafetyManager" date="2025-01-15"
justification="State machine enum-to-integer cast required for
indexed lookup table; bounds checked by assertion"/>
</Deviations>
</MISRAConfiguration>Summary
The mandatory/required/advisory hierarchy is the practical framework that makes MISRA compliance achievable in real projects. Treating all 143 rules as equally mandatory would make compliance impossible in most codebases; the hierarchy allows teams to focus zero-tolerance enforcement on the rules that prevent the most dangerous defects (mandatory and required), while managing advisory rules through the less stringent project configuration process. The key discipline is maintaining a clean deviation register: every suppressed required rule must have a documented justification, an approver, and a date. Suppressions without justification are the most common ASPICE audit finding in static analysis evidence packages.
🔬 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.