V-Model: Integration Strategy — Big-Bang vs Incremental and the Stub/Driver Problem

Date
2026-09-14
Location
Online
Host
Zach L

About this event

A live 30-minute expert session on Integration Strategy — Big-Bang vs Incremental and the Stub/Driver Problem (V-Model — The V-Model & Safety Lifecycle). What We'll Cover: What integration testing is and why it is the most-skipped rung on the right side of the V Building an integration strategy step by step: dependency ordering, stub and driver design, and interface test selection How integration levels map to ISO 26262-6 and IEC 61508-3 integration clauses and the integration test reports produced Common mistakes: big-bang integration under schedule pressure, untested stubs, and interface tests that never exercise error paths The interface coverage and integration-order rationale an assessor looks for in integration evidence Related topics: integration testing · integration strategy · stubs and drivers · bottom up integration · interface testing · big bang integration · continuous integration · integration test report · dependency ordering · interface error handling · software integration · hardware software integration · integration coverage · call interface verification Critical Systems Analysis provides embedded functional safety consulting for V-Model — The V-Model & Safety Lifecycle. Learn more: https://criticalsystemsanalysis.com Partner with us: https://meetings.hubspot.com/benjamin-twombly/strategic-partnerships

Topics

Registration

View event page

About Functional Safety Foundations

This online session delivers expert-led instruction on the regulatory landscape and implementation approach for Functional Safety Foundations.

The cross-sector fundamentals underlying every functional safety standard: risk as severity × likelihood, the safety function concept, integrity levels, the safety lifecycle, and the split between random and systematic failures.

What it regulates

Shared vocabulary and reasoning: hazard → risk → risk reduction allocation → safety requirement → verified implementation → maintained integrity in operation.

Who must comply

Everyone entering the field — the conceptual base of the entire catalog.

Key requirements of Functional Safety Foundations

  • Hazard and risk fundamentals
  • Safety function anatomy: sensor-logic-actuator with defined safe state
  • Integrity ladders (SIL/PL/ASIL/DAL) as risk-reduction currencies
  • Random vs systematic failure treatment
  • Lifecycle and management of functional safety incl. competence

Key concepts: Functional Safety Foundations

Functional safety management
Planning, competence, documentation and assessment wrapped around technical work.
Random vs systematic
Hardware wear-out/chance failures quantified statistically versus design/process errors controlled by rigor.
Risk reduction allocation
Distributing required risk reduction among mechanical design, safeguards, control functions and procedures.
Safe state
The defined condition a function drives the equipment to on demand or fault.

Frequently asked questions: Functional Safety Foundations

Why can't testing alone prove safety?

Rare-event targets (like 1e-7/h) are unverifiable by test duration, and systematic errors evade random testing — hence the standards' dual machinery of quantified hardware analysis plus process rigor and independent assessment.

Standard information based on the published text of Functional Safety Foundations. Event content is provided by the host. For authoritative guidance, consult the official standard body.