Skip to main content
Reference · 100+ techniques · ASIL A to D

Which method does your ASIL require?

A curated, searchable reference of 100+ safety techniques aligned with ISO 26262: each with our practitioner interpretation of ASIL applicability, practical inputs and outputs, and automotive examples. Find the right technique in seconds instead of hours of cross-referencing.

See Expert PlanSee what’s covered
Software unit verificationSample entry
MethodABCD
Requirements-based testing++++++++
Walk-through (peer review)+++oo
Inspection+++++++
Static code analysis+++++++
Fault injection testing++++++
MC/DC structural coverageo++++
++ highly recommended · + recommended · o no recommendation. Our practitioner interpretation, not a reproduction of the standard.

How ASIL tailoring works

ISO 26262 does not prescribe one fixed process. For each development activity it lists candidate methods, and how strongly a method is expected depends on the ASIL of the safety requirement: what is optional at ASIL A can be highly recommended at ASIL D. Choosing a lower-rated alternative is possible, but must be justified in your safety argumentation. That is why a unified view of methods and their ASIL applicability is the fastest way to plan verification and justify technique choices in a safety case.

Sound familiar?

You spend hours searching through the standard trying to understand which techniques apply to your ASIL

Different parts describe methods in different formats, making it hard to get a unified view

You need to justify technique choices in your safety case but lack practical interpretation of the requirements

Mapping safety engineering techniques to your actual development activities feels like guesswork

What you get instead

Over 100 techniques organized in one searchable reference with ASIL A to D applicability guidance

Filter by topic, keyword, ASIL, or method category and find what you need in seconds

Each technique with our detailed explanation, practical inputs/outputs, and integration guidance

Original applicability summaries you can use to support your safety case documentation

What’s inside · by discipline

The techniques, by name

A sample of the technique families in the database. Every entry gets its own explanation, ASIL applicability interpretation, inputs and outputs, and examples.

Safety analysis

Part 9
  • FMEA
  • FTA
  • FMEDA
  • STPA
  • Dependent failure analysis (DFA)
  • Markov analysis
  • HAZOP
  • Common-cause analysis

Software development

Part 6
  • Coding guidelines (MISRA-style)
  • Static code analysis
  • Control flow analysis
  • Data flow analysis
  • Unit testing
  • Back-to-back testing
  • Structural coverage (statement, branch, MC/DC)
  • Resource usage evaluation

Hardware development

Part 5
  • Hardware architectural metrics (SPFM, LFM)
  • PMHF evaluation
  • Diagnostic coverage evaluation
  • Safety mechanism evaluation
  • Fault injection
  • Derating and stress analysis

System development

Part 4
  • Requirements-based testing
  • Hardware-in-the-loop testing
  • Environmental testing
  • Long-term and stress testing
  • User and misuse testing

Verification and reviews

Part 8
  • Walk-through
  • Inspection
  • Semi-formal verification
  • Formal verification
  • Simulation
  • Prototyping

Management and concept

Part 2-3
  • HARA techniques
  • Safety culture evaluation
  • Confirmation reviews
  • Functional safety audits
  • Field monitoring

Plus production and operation measures, supporting-process techniques, and semiconductor-specific guidance: over 100 entries in total, expanding monthly.

Anatomy of an entry

Every method explained in detail

Not just a list of names. Each technique comes with our original educational content, practical guidance, and real-world examples you can apply directly.

Example: FMEA

ABCD

Relevant for hardware and system-level safety analysis

What it is

Systematic technique to identify potential failure modes and their effects on system behavior

When to use

During hardware and system design, before design freeze

Inputs needed

Block diagrams, interface definitions, operating conditions

Outputs

Failure mode catalog, severity rankings, detection measures, recommended actions

What every method page includes

Our plain-language explanation of what the technique is and why it matters

Practical step-by-step application guidance with typical inputs and outputs

Our interpretation of ASIL applicability based on industry best practices

How it connects with related techniques in your safety workflow

Original automotive examples from powertrain, chassis, and ADAS domains

Topics covered by discipline

2Management8+
3Concept12+
4System15+
5Hardware18+
6Software25+
7Production6+
8Supporting10+
9ASIL Analysis10+
10Guidelines8+

Frequently Asked Questions

Common questions about the methods and measures database

It is an original educational reference built by functional safety practitioners. We compiled and organized the safety engineering techniques commonly used in ISO 26262 projects, added our own interpretations of ASIL applicability, practical guidance, and real-world examples to help engineers navigate compliance more efficiently. This is not a reproduction of the standard itself.
They follow the notation used across the industry for method applicability: "++" means the technique is highly recommended for that ASIL, "+" means it is recommended, and "o" means there is no recommendation for or against it. Our tables present our practitioner interpretation of these ratings for each technique at ASIL A, B, C, and D.
The guide covers widely recognized safety engineering techniques used across the industry: safety analysis methods (FMEA, FTA, FMEDA, STPA, DFA, Markov analysis, HAZOP), verification and validation approaches (reviews, inspections, testing strategies, structural coverage), hardware safety techniques (architectural metrics, diagnostic coverage, fault injection), and software development practices (coding guidelines, static analysis, control and data flow analysis).
For each technique, we provide our interpretation of how it maps to different ASILs (A through D) based on industry best practices and the general framework of ISO 26262. The guidance helps you understand which techniques are typically expected at each integrity level for your projects.
The reference covers all major functional safety disciplines: safety management, concept phase, system-level development, hardware engineering, software engineering, production and operations, supporting processes, and safety analysis. Each area is organized with its own section.
Yes. This reference guide is an educational companion, not a replacement for the official ISO 26262 standard. We provide interpretive guidance, practical examples, and our own structured summaries to help you work more effectively, but the official standard from ISO remains the authoritative source.

Stop guessing which methods your ASIL requires

The Methods & Measures database is available on the Expert plan. Not sure yet? Start free and explore the platform first.

The free plan includes a full concept guide, 3 work product templates, 1 guided process, the Markov simulator, and 5 practice exams per month. No credit card required.

See Expert PlanStart Free