V-Model: The Left Side Done Right — Architecture Design Verification Before Any Code Exists

Date
2026-12-28
Location
Online
Host
Zach L

About this event

A live 30-minute expert session on The Left Side Done Right — Architecture Design Verification Before Any Code Exists (V-Model — The V-Model & Safety Lifecycle). What We'll Cover: Why architecture verification is a left-side V activity and what it must establish before implementation starts The method step by step: design reviews against requirements, timing and memory budget analysis, and architecture-level FMEA How architecture verification maps to design clauses in IEC 61508-3 and ISO 26262-4/6 and the design verification report produced Common mistakes: architecture documents written after the code, and budgets never re-checked against the built system The requirement-to-architecture trace and budget verification evidence auditors expect at the design gate Related topics: architecture verification · design analysis · timing budgets · resource budgets · architecture fmea · design verification report · design gate · requirement allocation · architecture review · static architecture · freedom from interference · design rationale · memory budgets · architecture trace 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

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.
Functional safety management
Planning, competence, documentation and assessment wrapped around technical work.
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.