Automotive Functional Safety

ISO 26262

Certified evidence, mapped directly onto BTC TestStack workflows.

The problem

Selecting the right methods and tools gets harder as systems grow more complex.

ISO 26262 has become the de facto standard for safety-critical automotive software — with function classification by ASIL and state-of-the-art methods for development and testing. Shortened development cycles make it harder to select appropriate methods and tools, and harder still to prove your toolchain supports the safety goals.

Part 6

Product development at the software level.

Part 6 of ISO 26262 outlines the detailed procedures required for validating, verifying and confirming the safety of software systems in automotive contexts, with methodologies for systematic evaluation of software designs and architectures. Key aspects include requirements-based testing — ensuring every function is tested for its intended output — and code coverage, checking that every part of the code has been executed in tests.

Tool qualification is another essential element, ensuring the tools used in the development process support the safety goals — alongside traceability of requirements, from their origin through to the implemented code and tests.

BTC TestStack

Which ISO 26262 requirements does it cover?

BTC TestStack is a certified environment addressing requirements across ISO 26262 Part 6 for software verification and validation:

Requirements-based test

Tight integration with dSPACE TargetLink, MathWorks Simulink/Embedded Coder, IBM DOORS, Siemens Polarion or PTC Integrity makes BTC TestStack the tool for ISO-26262-compliant requirements-based testing on model and code level.

Requirements-based Testing
Interface test

Built-in domain checks address the ISO 26262 recommendations on interface test, boundary value analysis and equivalence classes, with automatic test generation to reach every test goal — or a formal proof that one is unreachable.

Code coverage analysis

Automatically calculated and updated in the background every time a test case changes — including Modified Condition/Decision Coverage (MC/DC), required at ASIL C/D.

Code Coverage Analysis
Resource usage evaluation

Processor-in-the-loop environments let you execute code on the target platform and measure resource usage directly.

Back-to-back test

Highly recommended by ISO 26262 — managed automatically, with 100% completeness and 0% manual effort.

Back-to-Back Test
Formal verification

A unique model-checking technology gives mathematical proof that a given requirement cannot be violated by your software.

Formal Verification
Semi-formal & formal specification

Transforms safety requirements into a clear, unambiguous, machine-readable representation.

Formal Specification
Coverage as evidence

Coverage that counts as proof, not estimate.

01

MC/DC as a first-class goal

Modified Condition/Decision Coverage — required at ASIL C/D — is a first-class structural coverage goal in BTC TestStack's stimuli vector generation, not an afterthought bolted on top.

02

Unreachable proofs are formal evidence

When the CV engine's model checking proves a coverage goal unreachable, that proof counts toward the coverage objective under ISO 26262 — a complete positive result, not a gap to explain away.

03

Traceability across the toolchain

Test results link back to scopes, stimuli vectors, and — where applicable — requirements, visible directly inside connected ALM/PLM systems like IBM DOORS, Siemens Polarion or codeBeamer.

Certified

BTC TestStack

is ISO 26262 certified

The certificate addresses functional-safety standards across multiple industries:

ISO 26262
Automotive
IEC 61508-3:2010
Industrial / cross-industry functional safety
ISO 25119
Agricultural & forestry machinery
IEC 62304
Medical device software
EN 50716
Railway / rail applications

For ISO 26262, BTC TestStack is certified with the highest Tool Confidence Level (TCL), valid for all ASIL levels including ASIL D. We provide the certificate and report to customers free of charge on request — removing most tool-qualification effort on the customer side.

Get started

Talk to our engineering team.

Tell us where your engineering problem actually is. We'll tell you whether an evaluation license, a workshop, or a conversation is the right next step.