The international standard for the functional safety of road vehicles, an adaptation of IEC 61508 to automotive electrical and electronic systems. It defines a safety life cycle and describes the activities required in each of its phases.
The standard provides a specific, risk-based approach to determine risk classes — ASIL, Automotive Safety Integrity Levels — and uses them to specify the safety requirements needed to achieve an acceptable residual risk.
It also sets requirements for the validation and confirmation of the measures taken, to establish that a sufficient level of safety has been achieved, as well as requirements on the relationship with suppliers.
Part 6 (ISO 26262-6) specifies the requirements for product development at the software level.
To assess the completeness of the test cases, ISO 26262 requires structural coverage to be measured. Depending on the target ASIL, statement coverage, branch coverage and/or MC/DC are expected (§ 8.4.5 of ISO 26262-6).
| Test coverage level | ASIL A | ASIL B | ASIL C | ASIL D |
|---|---|---|---|---|
| Statement coverage | ++ | ++ | + | + |
| Branch coverage | + | ++ | ++ | ++ |
| MC/DC (modified condition / decision coverage) | + | + | + | ++ |
++ highly recommended · + recommended.
If the coverage achieved is considered insufficient, the standard requires additional test cases or a rationale. § 9.4.5 also requires the test environment to correspond as closely as possible to the target environment.
Testwell CTC++ meets this requirement directly: it analyzes test coverage on any embedded target, even the smallest.
The structural coverage requirements of the standard, and how to meet them in practice.
Going further
Testwell CTC++: specifications and integrations · Request a free evaluation · Automotive and transportation sector
The video opens in a new tab.
When you come back, try Testwell CTC++ on your own code: a free evaluation, with your compiler and your target, to measure coverage up to MC/DC.
Request a free evaluation →
For Testwell CTC++ 10.x, we provide a certificate from TÜV SÜD Rail GmbH, covering all SIL and ASIL levels of the standards concerned.
As an alternative — and for DO-178C —, a qualification kit (currently available for versions 9.x and earlier) provides the documentation, test cases and procedures to qualify the coverage analyzer for projects based on DO-178C, EN 50128, IEC 61508, IEC 60880 and ISO 26262.
ISO 26262 sets the structural coverage expected by ASIL, up to MC/DC. The animation shows each coverage level and what it checks.
The 13 Testwell CTC++ animations →ISO 26262-6 requires you to define modeling and coding guidelines (table 1): language subset, strong typing, defensive programming, low complexity, naming conventions — MISRA C is cited as an example. Software units are then verified against these guidelines, and static code analysis is among the verification methods proposed by the standard.
TiCS brings together the results of your analyzers — MISRA C/C++ and AUTOSAR C++14 rules, compiler warnings, cyclomatic complexity — in a single dashboard, from the project down to the unit, and tracks them version after version.
TiCS is not a code analyzer: it is an orchestrator and aggregator. It runs your tools (MISRA rule checkers, static analyzers, compilers), gathers their results and presents them in a high-level view, from the project portfolio down to the line of code. Detecting deviations remains the job of these analyzers: it is therefore their qualification that matters for ISO 26262. Several analyzers on the market are certified for this standard; check it for each tool in your configuration, as part of the confidence in the use of software tools (ISO 26262-8, clause 11).
ECUs, cross-compilers, coding rules: TiCS tracks the quality of automotive embedded software like that of any other project. The rules are checked by the analyzers in your configuration.
The 14 TiCS animations →
References, testimonials and uses of Testwell CTC++ in the automotive industry.
DO-178C, EN 50716, IEC 60880, IEC 61508, IEC 62304, IEC 62443, ISO 25119: each standard sets its own requirements.