ISO 26262 Tool Confidence Level - Model-Based Development

ISO 26262 Tool Classification

ISO 26262 Part 8 Clause 11: Software Tool Qualification

Every software tool used in the development of safety-relevant software must be classified and, if required, qualified per ISO 26262 Part 8 Clause 11.

Tool Impact (TI): Could a malfunction of the tool lead to a failure to detect or introduce a fault in the safety-relevant software?

TI1: Tool cannot introduce or fail to detect faults (e.g., text editor, requirement document viewer)
TI2: Tool could fail to detect a fault (e.g., test coverage tool -- misses a gap)
TI3: Tool could introduce faults into the safety-relevant software (e.g., code generator -- generates wrong code)

Tool Error Detection (TD): Are errors in the tool output detected by other means?

TD1: High confidence in error detection (multiple independent checks)
TD2: Medium confidence
TD3: Low confidence (tool output used directly without verification)

TCL = f(TI, TD): Higher TI + lower TD = higher TCL = more qualification work required.

TCL Determination Matrix

TI / TD	TD1	TD2	TD3
TI1	TCL0 (no qualification)	TCL0	TCL0
TI2	TCL1	TCL2	TCL3
TI3	TCL1	TCL2	TCL3

MBD Tool TCL Classification

Tool	TI	TD	TCL	Qualification Required
MATLAB (computation engine)	TI3	TD2	TCL2	Tool qualification report + validation tests
Simulink (model execution)	TI3	TD2	TCL2	Qualification report; MiL/SiL back-to-back provides TD evidence
Embedded Coder (code gen)	TI3	TD2	TCL2	Qualification report; back-to-back MiL/SiL is key TD1 measure
Simulink Design Verifier	TI2	TD2	TCL2	Qualification report; results reviewed by engineer
Model Advisor (MAAB checks)	TI2	TD1	TCL1	Limited qualification; checks reviewed by engineer
Stateflow	TI3	TD2	TCL2	Same as Simulink; part of same qualification

Summary

The Tool Confidence Level framework is ISO 26262's answer to the question: "how much do we trust our development tools?" Embedded Coder has TI3 (could introduce faults - a bug in the code generator could produce wrong C code) and TD2 (medium confidence in detection - the back-to-back MiL/SiL test detects most code generation errors but not all). The result is TCL2, requiring a qualification report. The back-to-back MiL/SiL test is not just a verification activity - it is also a Tool Error Detection measure that raises confidence in the code generator and reduces the qualification effort needed. This is why the MiL/SiL comparison is mandatory in safety-compliant MBD projects, not just good practice.

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