ISO 26262 A Complete Guide
You're under pressure. Deadlines are tight. A safety issue surfaces in your automotive software stack, and suddenly, everyone’s asking: “Did we follow ISO 26262 correctly?” You know functional safety isn't optional. But the standard is dense, fragmented, and hard to implement without expert guidance. Missteps could delay launches, fail audits, or worse-jeopardize human lives. This isn’t just about compliance. It’s about confidence. The confidence to walk into any safety review and say: “Yes, our system meets ASIL-D requirements-and here’s the evidence.” ISO 26262 A Complete Guide transforms confusion into clarity. It gives engineers, architects, and technical leads a structured, step-by-step blueprint to mastering functional safety from concept to production-delivering a fully traceable, audit-ready implementation in under 60 days. One lead systems engineer at a global Tier-1 supplier used this methodology to reduce their safety case preparation time by 70%, passing ISO 26262 certification on the first audit with zero critical findings. No guesswork. No outdated templates. Just a proven pathway to safety compliance that scales across projects, teams, and organisational levels. Here’s how this course is structured to help you get there.Course Format & Delivery Details Flexible, Immediate Access - Built for Real-World Demands
This course is self-paced, with on-demand access online. There are no fixed dates, no mandatory sessions, and no time zone constraints. You control your learning journey. Most learners complete the core material in 40–50 hours, with many applying critical components to live projects within the first two weeks. Real results happen fast when the content is practical, structured, and directly applicable. You receive lifetime access to all course materials, including all future updates at no additional cost. As ISO 26262 evolves and new interpretations emerge, your knowledge stays current-automatically. Learn Anywhere, Anytime - Full Compatibility & Continuous Support
The platform is mobile-friendly and accessible 24/7 from any device, anywhere in the world. Whether you're reviewing safety requirements on a tablet between meetings or deep-diving into fault tree analysis from a laptop at home, your progress is always synced. Instructor support is available throughout your journey. Ask targeted questions, receive detailed technical clarification, and get guidance aligned with real automotive development environments-direct from certified functional safety experts with over 15 years of industry experience. Premium Certification - Globally Recognised and Credible
Upon successful completion, you earn a Certificate of Completion issued by The Art of Service-an internationally recognised training provider known for high-calibre professional development in engineering, risk management, and standards compliance. This certificate validates your mastery of ISO 26262 and demonstrates tangible commitment to functional safety. Recruiters at leading OEMs and Tier-1 suppliers recognise The Art of Service credentials during hiring and promotion cycles. No Risk, Full Transparency - Enrol with Complete Confidence
Pricing is straightforward, with no hidden fees. What you see is exactly what you pay-no surprise charges, no recurring subscriptions. We accept all major payment methods, including Visa, Mastercard, and PayPal, ensuring seamless and secure checkout. If you find the course does not meet your expectations, we offer a full satisfaction guarantee: enrol risk-free and request a refund if the material doesn’t deliver immediate value. After enrollment, you'll receive a confirmation email. Your access details will be sent separately once the course materials are fully provisioned-ensuring accurate, reliable delivery every time. This Works Even If...
- You’re new to functional safety but need to ramp up fast for an upcoming vehicle project
- You’ve read parts of the standard but struggle to apply it consistently across system architectures
- Your team lacks a unified approach to hazard analysis and safety case development
- You’re transitioning from another safety standard (like IEC 61508) and need automotive-specific clarity
- Previous training felt too theoretical, with no clear link to implementation or certification readiness
This works because it was designed by lead assessors who’ve conducted hundreds of ISO 26262 audits. They know exactly what separates pass from fail-and they’ve embedded those insights into every module. This isn’t generic knowledge. It’s battle-tested, audit-proven, and engineered for outcomes.
Extensive and Detailed Course Curriculum
Module 1: Foundations of Functional Safety and ISO 26262 Overview - Understanding the purpose and scope of ISO 26262
- Historical context and evolution of automotive functional safety standards
- Key differences between ISO 26262 and other safety standards (IEC 61508, DO-178C)
- Structure of the ISO 26262 series (Parts 1–12)
- The role of functional safety in modern vehicle systems
- Definition of key terms: hazard, risk, fault, failure, event
- Understanding safety goals and their relevance to system design
- Overview of the V-model in automotive development
- The functional safety lifecycle from concept to decommissioning
- Roadmap to certification and compliance validation
- Integration of functional safety with overall product development processes
- Understanding stakeholder responsibilities in safety-critical projects
- Introduction to the safety culture framework
- Regulatory drivers for functional safety in global markets
- How OEMs and suppliers interact under ISO 26262 requirements
Module 2: Hazard Analysis and Risk Assessment (HARA) - Defining operational scenarios and use cases for risk evaluation
- Identifying potential hazards in electrical and electronic systems
- Step-by-step process for conducting a HARA study
- Assigning severity levels (S) to potential harm outcomes
- Assessing exposure probability (E) across driving conditions
- Evaluating controllability (C) by the driver or automated systems
- Combining S, E, C to determine Automotive Safety Integrity Level (ASIL)
- Differentiating between ASIL A, B, C, D and QM classifications
- Dealing with ASIL decomposition and its constraints
- Documenting HARA outputs in a structured safety case
- Managing common cause failures in multi-channel systems
- Techniques for handling uncertain or incomplete data during HARA
- Linking HARA results to system-level safety requirements
- Best practices for reviewing and validating HARA conclusions
- Using real-world incident data to enrich hazard identification
- Integrating autonomous driving scenarios into HARA methodology
Module 3: Functional Safety Concepts and Safety Goals - Deriving safety goals from HARA outputs
- Top-level functional safety requirements definition
- Differentiating between functional and technical safety requirements
- Allocating safety goals to system elements and subsystems
- Handling distributed functionalities across multiple ECUs
- Specification of safety mechanisms and their intended functions
- Incorporating fallback modes and graceful degradation strategies
- Establishing functional safety budgets across subsystems
- Using interface control documents to manage cross-domain interactions
- Defining operational states and transitions for safety monitoring
- Creating a safety envelope for system behaviour under fault conditions
- Integrating cybersecurity considerations into functional safety concepts
- Managing redundancy, diversity, and independence in design
- Validation criteria for functional safety concept approval
- Developing a safety concept traceability matrix
- Common pitfalls in early-phase safety allocation and how to avoid them
Module 4: Technical Safety Requirements and System Design - Refining functional safety requirements into technical specifications
- System architecture design for ASIL-compliant systems
- Partitioning safety requirements across hardware and software domains
- Selecting appropriate microcontrollers and safety-related components
- Designing fail-safe states and error containment regions
- Implementing watchdog timers, memory protection units, and lockstep cores
- Integrating diagnostic coverage metrics into system design
- Ensuring time and space partitioning in complex ECU environments
- Specification of communication protocols (CAN, LIN, Ethernet) with safety extensions
- Signal integrity and noise immunity in safety-critical circuits
- Power supply design considerations for fault tolerance
- Environmental stress screening and robustness validation
- Defining system-level FTTI (Fault Tolerant Time Interval)
- Managing thermal, vibration, and electromagnetic compatibility risks
- Designing for maintainability and serviceability without compromising safety
- Documentation standards for system design description
Module 5: Hardware Development and ASIL Compliance - Requirements for hardware architectural metrics (SPFM, LFM, PMHF)
- Calculating single-point fault metric (SPFM) for component selection
- Computing latent fault metric (LFM) for diagnostic effectiveness
- Probabilistic calculation of hardware failure rate (PMHF)
- Selecting components with documented failure rates (FIT values)
- Applying derating principles for electronic parts
- Using redundancy and diversity to meet ASIL D hardware targets
- Designing for high diagnostic coverage in sensor and actuator interfaces
- Hardware-software interface (HSI) specification and validation
- Implementation of built-in self-test (BIST) routines
- Managing clock supervision and reset circuits
- Ensuring data consistency across dual-core processors
- Static analysis techniques for hardware verification
- Verification through simulation and prototyping
- Compliance checks against ISO 26262-5 requirements
- Reporting hardware metrics in safety case documentation
Module 6: Software Development Lifecycle and ASIL Alignment - Mapping software development phases to the V-model
- Differentiating software safety requirements by ASIL level
- Establishing software safety plans and work product requirements
- Configuration management for safety-related code artifacts
- Version control strategies for traceability and audit readiness
- Change management procedures for safety-critical software
- Code naming conventions and commenting standards for clarity
- Modular software design for testability and reuse
- Static and dynamic memory allocation safety rules
- Error handling and exception management in embedded software
- Scheduling policies and interrupt management for real-time execution
- Ensuring temporal determinism in safety functions
- Software unit design principles (cohesion, coupling, encapsulation)
- Programming language selection and safety coding guidelines (MISRA C, JSF AV)
- Tool qualification for compilers, linkers, and debuggers
- Integration of third-party libraries and commercial software components
Module 7: Software Safety Requirements and Architecture - Deriving software safety requirements from system-level specs
- Architectural patterns for safety-critical software (layered, client-server, event-driven)
- Design of safe state machines and mode management logic
- Specification of inter-process communication with data integrity checks
- Memory management and protection mechanisms (MPU, MMU)
- Secure boot and runtime integrity verification techniques
- Stack overflow detection and prevention strategies
- Watchdog supervision of software tasks and threads
- Use of time-triggered and deadline monitoring for task execution
- Design of fail-operational and fail-safe software behaviours
- Redundant software execution paths for critical functions
- Software-level FTTI calculation and response planning
- Interface definition between safety and non-safety software components
- Isolation techniques for mixed-criticality systems
- Traceability of software requirements to source code and test cases
- Automated generation of software architecture diagrams
Module 8: Software Verification and Validation - Test strategies for ASIL A to D software components
- Unit testing with code coverage targets (statement, branch, MC/DC)
- Integration testing across software modules and hardware interfaces
- System testing in HiL (Hardware-in-the-Loop) environments
- Test case design using equivalence partitioning and boundary value analysis
- Using mutation testing to assess test suite robustness
- Static code analysis using linting and abstract interpretation tools
- Dynamic analysis for runtime errors (null pointers, buffer overflows)
- Model-based testing and test automation frameworks
- Verification of timing constraints and interrupt latencies
- Back-to-back testing from model to executable code
- Requirements-based testing and gap analysis
- Reporting verification results with objective evidence
- Managing test environments and test data configuration
- Regression testing strategies for software updates
- Certification-readiness checklists for software testing
Module 9: Safety Analysis Techniques and Formal Methods - Introduction to qualitative and quantitative safety analysis
- FMEA (Failure Modes and Effects Analysis) application in automotive systems
- FMECA (Failure Modes, Effects and Criticality Analysis) with ASIL weighting
- FTA (Fault Tree Analysis) construction for top-event resolution
- Qualitative and quantitative evaluation of fault trees
- Common cause failure analysis (CCF) using beta factor and alpha factor models
- Dempster-Shafer theory for handling uncertainty in reliability assessment
- Petri nets and Markov models for dynamic system analysis
- Dependability modelling for phased-mission systems
- Sneak circuit analysis for unintended signal paths
- Hazard and operability study (HAZOP) adapted for automotive E/E
- Software FMEA and its integration with system-level analysis
- Applying model checking and theorem proving in critical component verification
- Use of SMT solvers for program correctness proofs
- Formal specification languages (e.g., Z, TLA+) for safety invariants
- Tool-supported analysis workflows and report generation
Module 10: Integration and Testing at System Level - Integration strategy for safety-related subsystems
- Interface testing between safety and non-safety domains
- Signal path validation from sensor input to actuator output
- End-to-end timing verification across distributed systems
- Interoperability testing of multi-vendor components
- Testing fallback and redundant modes under fault injection
- Simulating hardware faults via controlled perturbation (e.g., voltage glitch)
- Software fault injection testing for exception handling
- Environmental stress testing (temperature, EMI, vibration)
- Recovery testing after power cycles and system resets
- Validation of emergency stop and fail-safe deactivation sequences
- Demonstration of compliance with FTTI requirements
- Blind testing scenarios for independent verification
- System-level safety case structuring and argumentation
- Recording objective evidence for certification audits
- Final system verification plan approval process
Module 11: Production, Operation, Service, and Decommissioning - Safety management during series production
- Process validation for automated testing stations
- Field monitoring and in-vehicle diagnostics (OBD, UDS)
- Handling software updates and over-the-air (OTA) safety patches
- Safety implications of remote reprogramming
- Winter/summer release testing for environmental impact
- Customer incident reporting and root cause analysis
- Service manual creation with safety warnings and procedures
- Recall management processes linked to functional safety non-conformances
- Battery system safety in electric vehicles throughout lifecycle
- End-of-life vehicle dismantling and hazardous material handling
- Data retention and deletion policies for safety-related logs
- Post-production safety monitoring and trend analysis
- Updating safety cases based on field experience
- Decommissioning protocols for autonomous driving systems
- Feedback loops from service data to next-gen design improvements
Module 12: Tool Qualification and Confidence Levels - Identifying safety-related tools in the development chain
- Understanding tool impact (TI) and tool error detection (TD) classification
- Tool qualification process for compilers, static analysers, simulators
- Selecting qualified tools from TÜV-certified lists
- Conducting in-house tool qualification using ISO 26262-8 guidelines
- Documenting tool confidence levels (TCL1, TCL2)
- Using equivalence arguments to reuse previously qualified tools
- Managing commercial off-the-shelf (COTS) tool risks
- Version locking and patch management for qualified tools
- Integration of qualification packages into safety case submissions
- Automated traceability tools and their qualification path
- Model-based design toolchain validation
- Script and plugin qualification strategies
- Continuous integration tools in safety workflows
- Audit readiness for tool documentation reviews
- Maintaining tool qualification across software releases
Module 13: Safety Case Development and Certification Readiness - What is a safety case and why it matters for ISO 26262
- Structure of a safety case: claims, arguments, evidence
- Top-level safety claim derivation from project objectives
- Modular argument construction using GSN (Goal Structuring Notation)
- Creating sub-arguments for hardware, software, integration
- Incorporating HARA, FSC, TSC, and V&V results as evidence
- Handling uncertainty in evidence quality and quantity
- Using templates for consistent safety case formatting
- Automating evidence collection from development tools
- Mapping work products to ISO 26262 compliance checklists
- Engaging auditors and assessors early in the process
- Internal review and gap analysis before formal submission
- Preparing for on-site assessments and document requests
- Responding to auditor findings and non-conformance reports
- Finalising certification with notified bodies or independent assessors
- Maintaining safety case updates across product variants
Module 14: Project Management and Functional Safety Monitoring - Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
Module 1: Foundations of Functional Safety and ISO 26262 Overview - Understanding the purpose and scope of ISO 26262
- Historical context and evolution of automotive functional safety standards
- Key differences between ISO 26262 and other safety standards (IEC 61508, DO-178C)
- Structure of the ISO 26262 series (Parts 1–12)
- The role of functional safety in modern vehicle systems
- Definition of key terms: hazard, risk, fault, failure, event
- Understanding safety goals and their relevance to system design
- Overview of the V-model in automotive development
- The functional safety lifecycle from concept to decommissioning
- Roadmap to certification and compliance validation
- Integration of functional safety with overall product development processes
- Understanding stakeholder responsibilities in safety-critical projects
- Introduction to the safety culture framework
- Regulatory drivers for functional safety in global markets
- How OEMs and suppliers interact under ISO 26262 requirements
Module 2: Hazard Analysis and Risk Assessment (HARA) - Defining operational scenarios and use cases for risk evaluation
- Identifying potential hazards in electrical and electronic systems
- Step-by-step process for conducting a HARA study
- Assigning severity levels (S) to potential harm outcomes
- Assessing exposure probability (E) across driving conditions
- Evaluating controllability (C) by the driver or automated systems
- Combining S, E, C to determine Automotive Safety Integrity Level (ASIL)
- Differentiating between ASIL A, B, C, D and QM classifications
- Dealing with ASIL decomposition and its constraints
- Documenting HARA outputs in a structured safety case
- Managing common cause failures in multi-channel systems
- Techniques for handling uncertain or incomplete data during HARA
- Linking HARA results to system-level safety requirements
- Best practices for reviewing and validating HARA conclusions
- Using real-world incident data to enrich hazard identification
- Integrating autonomous driving scenarios into HARA methodology
Module 3: Functional Safety Concepts and Safety Goals - Deriving safety goals from HARA outputs
- Top-level functional safety requirements definition
- Differentiating between functional and technical safety requirements
- Allocating safety goals to system elements and subsystems
- Handling distributed functionalities across multiple ECUs
- Specification of safety mechanisms and their intended functions
- Incorporating fallback modes and graceful degradation strategies
- Establishing functional safety budgets across subsystems
- Using interface control documents to manage cross-domain interactions
- Defining operational states and transitions for safety monitoring
- Creating a safety envelope for system behaviour under fault conditions
- Integrating cybersecurity considerations into functional safety concepts
- Managing redundancy, diversity, and independence in design
- Validation criteria for functional safety concept approval
- Developing a safety concept traceability matrix
- Common pitfalls in early-phase safety allocation and how to avoid them
Module 4: Technical Safety Requirements and System Design - Refining functional safety requirements into technical specifications
- System architecture design for ASIL-compliant systems
- Partitioning safety requirements across hardware and software domains
- Selecting appropriate microcontrollers and safety-related components
- Designing fail-safe states and error containment regions
- Implementing watchdog timers, memory protection units, and lockstep cores
- Integrating diagnostic coverage metrics into system design
- Ensuring time and space partitioning in complex ECU environments
- Specification of communication protocols (CAN, LIN, Ethernet) with safety extensions
- Signal integrity and noise immunity in safety-critical circuits
- Power supply design considerations for fault tolerance
- Environmental stress screening and robustness validation
- Defining system-level FTTI (Fault Tolerant Time Interval)
- Managing thermal, vibration, and electromagnetic compatibility risks
- Designing for maintainability and serviceability without compromising safety
- Documentation standards for system design description
Module 5: Hardware Development and ASIL Compliance - Requirements for hardware architectural metrics (SPFM, LFM, PMHF)
- Calculating single-point fault metric (SPFM) for component selection
- Computing latent fault metric (LFM) for diagnostic effectiveness
- Probabilistic calculation of hardware failure rate (PMHF)
- Selecting components with documented failure rates (FIT values)
- Applying derating principles for electronic parts
- Using redundancy and diversity to meet ASIL D hardware targets
- Designing for high diagnostic coverage in sensor and actuator interfaces
- Hardware-software interface (HSI) specification and validation
- Implementation of built-in self-test (BIST) routines
- Managing clock supervision and reset circuits
- Ensuring data consistency across dual-core processors
- Static analysis techniques for hardware verification
- Verification through simulation and prototyping
- Compliance checks against ISO 26262-5 requirements
- Reporting hardware metrics in safety case documentation
Module 6: Software Development Lifecycle and ASIL Alignment - Mapping software development phases to the V-model
- Differentiating software safety requirements by ASIL level
- Establishing software safety plans and work product requirements
- Configuration management for safety-related code artifacts
- Version control strategies for traceability and audit readiness
- Change management procedures for safety-critical software
- Code naming conventions and commenting standards for clarity
- Modular software design for testability and reuse
- Static and dynamic memory allocation safety rules
- Error handling and exception management in embedded software
- Scheduling policies and interrupt management for real-time execution
- Ensuring temporal determinism in safety functions
- Software unit design principles (cohesion, coupling, encapsulation)
- Programming language selection and safety coding guidelines (MISRA C, JSF AV)
- Tool qualification for compilers, linkers, and debuggers
- Integration of third-party libraries and commercial software components
Module 7: Software Safety Requirements and Architecture - Deriving software safety requirements from system-level specs
- Architectural patterns for safety-critical software (layered, client-server, event-driven)
- Design of safe state machines and mode management logic
- Specification of inter-process communication with data integrity checks
- Memory management and protection mechanisms (MPU, MMU)
- Secure boot and runtime integrity verification techniques
- Stack overflow detection and prevention strategies
- Watchdog supervision of software tasks and threads
- Use of time-triggered and deadline monitoring for task execution
- Design of fail-operational and fail-safe software behaviours
- Redundant software execution paths for critical functions
- Software-level FTTI calculation and response planning
- Interface definition between safety and non-safety software components
- Isolation techniques for mixed-criticality systems
- Traceability of software requirements to source code and test cases
- Automated generation of software architecture diagrams
Module 8: Software Verification and Validation - Test strategies for ASIL A to D software components
- Unit testing with code coverage targets (statement, branch, MC/DC)
- Integration testing across software modules and hardware interfaces
- System testing in HiL (Hardware-in-the-Loop) environments
- Test case design using equivalence partitioning and boundary value analysis
- Using mutation testing to assess test suite robustness
- Static code analysis using linting and abstract interpretation tools
- Dynamic analysis for runtime errors (null pointers, buffer overflows)
- Model-based testing and test automation frameworks
- Verification of timing constraints and interrupt latencies
- Back-to-back testing from model to executable code
- Requirements-based testing and gap analysis
- Reporting verification results with objective evidence
- Managing test environments and test data configuration
- Regression testing strategies for software updates
- Certification-readiness checklists for software testing
Module 9: Safety Analysis Techniques and Formal Methods - Introduction to qualitative and quantitative safety analysis
- FMEA (Failure Modes and Effects Analysis) application in automotive systems
- FMECA (Failure Modes, Effects and Criticality Analysis) with ASIL weighting
- FTA (Fault Tree Analysis) construction for top-event resolution
- Qualitative and quantitative evaluation of fault trees
- Common cause failure analysis (CCF) using beta factor and alpha factor models
- Dempster-Shafer theory for handling uncertainty in reliability assessment
- Petri nets and Markov models for dynamic system analysis
- Dependability modelling for phased-mission systems
- Sneak circuit analysis for unintended signal paths
- Hazard and operability study (HAZOP) adapted for automotive E/E
- Software FMEA and its integration with system-level analysis
- Applying model checking and theorem proving in critical component verification
- Use of SMT solvers for program correctness proofs
- Formal specification languages (e.g., Z, TLA+) for safety invariants
- Tool-supported analysis workflows and report generation
Module 10: Integration and Testing at System Level - Integration strategy for safety-related subsystems
- Interface testing between safety and non-safety domains
- Signal path validation from sensor input to actuator output
- End-to-end timing verification across distributed systems
- Interoperability testing of multi-vendor components
- Testing fallback and redundant modes under fault injection
- Simulating hardware faults via controlled perturbation (e.g., voltage glitch)
- Software fault injection testing for exception handling
- Environmental stress testing (temperature, EMI, vibration)
- Recovery testing after power cycles and system resets
- Validation of emergency stop and fail-safe deactivation sequences
- Demonstration of compliance with FTTI requirements
- Blind testing scenarios for independent verification
- System-level safety case structuring and argumentation
- Recording objective evidence for certification audits
- Final system verification plan approval process
Module 11: Production, Operation, Service, and Decommissioning - Safety management during series production
- Process validation for automated testing stations
- Field monitoring and in-vehicle diagnostics (OBD, UDS)
- Handling software updates and over-the-air (OTA) safety patches
- Safety implications of remote reprogramming
- Winter/summer release testing for environmental impact
- Customer incident reporting and root cause analysis
- Service manual creation with safety warnings and procedures
- Recall management processes linked to functional safety non-conformances
- Battery system safety in electric vehicles throughout lifecycle
- End-of-life vehicle dismantling and hazardous material handling
- Data retention and deletion policies for safety-related logs
- Post-production safety monitoring and trend analysis
- Updating safety cases based on field experience
- Decommissioning protocols for autonomous driving systems
- Feedback loops from service data to next-gen design improvements
Module 12: Tool Qualification and Confidence Levels - Identifying safety-related tools in the development chain
- Understanding tool impact (TI) and tool error detection (TD) classification
- Tool qualification process for compilers, static analysers, simulators
- Selecting qualified tools from TÜV-certified lists
- Conducting in-house tool qualification using ISO 26262-8 guidelines
- Documenting tool confidence levels (TCL1, TCL2)
- Using equivalence arguments to reuse previously qualified tools
- Managing commercial off-the-shelf (COTS) tool risks
- Version locking and patch management for qualified tools
- Integration of qualification packages into safety case submissions
- Automated traceability tools and their qualification path
- Model-based design toolchain validation
- Script and plugin qualification strategies
- Continuous integration tools in safety workflows
- Audit readiness for tool documentation reviews
- Maintaining tool qualification across software releases
Module 13: Safety Case Development and Certification Readiness - What is a safety case and why it matters for ISO 26262
- Structure of a safety case: claims, arguments, evidence
- Top-level safety claim derivation from project objectives
- Modular argument construction using GSN (Goal Structuring Notation)
- Creating sub-arguments for hardware, software, integration
- Incorporating HARA, FSC, TSC, and V&V results as evidence
- Handling uncertainty in evidence quality and quantity
- Using templates for consistent safety case formatting
- Automating evidence collection from development tools
- Mapping work products to ISO 26262 compliance checklists
- Engaging auditors and assessors early in the process
- Internal review and gap analysis before formal submission
- Preparing for on-site assessments and document requests
- Responding to auditor findings and non-conformance reports
- Finalising certification with notified bodies or independent assessors
- Maintaining safety case updates across product variants
Module 14: Project Management and Functional Safety Monitoring - Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
- Defining operational scenarios and use cases for risk evaluation
- Identifying potential hazards in electrical and electronic systems
- Step-by-step process for conducting a HARA study
- Assigning severity levels (S) to potential harm outcomes
- Assessing exposure probability (E) across driving conditions
- Evaluating controllability (C) by the driver or automated systems
- Combining S, E, C to determine Automotive Safety Integrity Level (ASIL)
- Differentiating between ASIL A, B, C, D and QM classifications
- Dealing with ASIL decomposition and its constraints
- Documenting HARA outputs in a structured safety case
- Managing common cause failures in multi-channel systems
- Techniques for handling uncertain or incomplete data during HARA
- Linking HARA results to system-level safety requirements
- Best practices for reviewing and validating HARA conclusions
- Using real-world incident data to enrich hazard identification
- Integrating autonomous driving scenarios into HARA methodology
Module 3: Functional Safety Concepts and Safety Goals - Deriving safety goals from HARA outputs
- Top-level functional safety requirements definition
- Differentiating between functional and technical safety requirements
- Allocating safety goals to system elements and subsystems
- Handling distributed functionalities across multiple ECUs
- Specification of safety mechanisms and their intended functions
- Incorporating fallback modes and graceful degradation strategies
- Establishing functional safety budgets across subsystems
- Using interface control documents to manage cross-domain interactions
- Defining operational states and transitions for safety monitoring
- Creating a safety envelope for system behaviour under fault conditions
- Integrating cybersecurity considerations into functional safety concepts
- Managing redundancy, diversity, and independence in design
- Validation criteria for functional safety concept approval
- Developing a safety concept traceability matrix
- Common pitfalls in early-phase safety allocation and how to avoid them
Module 4: Technical Safety Requirements and System Design - Refining functional safety requirements into technical specifications
- System architecture design for ASIL-compliant systems
- Partitioning safety requirements across hardware and software domains
- Selecting appropriate microcontrollers and safety-related components
- Designing fail-safe states and error containment regions
- Implementing watchdog timers, memory protection units, and lockstep cores
- Integrating diagnostic coverage metrics into system design
- Ensuring time and space partitioning in complex ECU environments
- Specification of communication protocols (CAN, LIN, Ethernet) with safety extensions
- Signal integrity and noise immunity in safety-critical circuits
- Power supply design considerations for fault tolerance
- Environmental stress screening and robustness validation
- Defining system-level FTTI (Fault Tolerant Time Interval)
- Managing thermal, vibration, and electromagnetic compatibility risks
- Designing for maintainability and serviceability without compromising safety
- Documentation standards for system design description
Module 5: Hardware Development and ASIL Compliance - Requirements for hardware architectural metrics (SPFM, LFM, PMHF)
- Calculating single-point fault metric (SPFM) for component selection
- Computing latent fault metric (LFM) for diagnostic effectiveness
- Probabilistic calculation of hardware failure rate (PMHF)
- Selecting components with documented failure rates (FIT values)
- Applying derating principles for electronic parts
- Using redundancy and diversity to meet ASIL D hardware targets
- Designing for high diagnostic coverage in sensor and actuator interfaces
- Hardware-software interface (HSI) specification and validation
- Implementation of built-in self-test (BIST) routines
- Managing clock supervision and reset circuits
- Ensuring data consistency across dual-core processors
- Static analysis techniques for hardware verification
- Verification through simulation and prototyping
- Compliance checks against ISO 26262-5 requirements
- Reporting hardware metrics in safety case documentation
Module 6: Software Development Lifecycle and ASIL Alignment - Mapping software development phases to the V-model
- Differentiating software safety requirements by ASIL level
- Establishing software safety plans and work product requirements
- Configuration management for safety-related code artifacts
- Version control strategies for traceability and audit readiness
- Change management procedures for safety-critical software
- Code naming conventions and commenting standards for clarity
- Modular software design for testability and reuse
- Static and dynamic memory allocation safety rules
- Error handling and exception management in embedded software
- Scheduling policies and interrupt management for real-time execution
- Ensuring temporal determinism in safety functions
- Software unit design principles (cohesion, coupling, encapsulation)
- Programming language selection and safety coding guidelines (MISRA C, JSF AV)
- Tool qualification for compilers, linkers, and debuggers
- Integration of third-party libraries and commercial software components
Module 7: Software Safety Requirements and Architecture - Deriving software safety requirements from system-level specs
- Architectural patterns for safety-critical software (layered, client-server, event-driven)
- Design of safe state machines and mode management logic
- Specification of inter-process communication with data integrity checks
- Memory management and protection mechanisms (MPU, MMU)
- Secure boot and runtime integrity verification techniques
- Stack overflow detection and prevention strategies
- Watchdog supervision of software tasks and threads
- Use of time-triggered and deadline monitoring for task execution
- Design of fail-operational and fail-safe software behaviours
- Redundant software execution paths for critical functions
- Software-level FTTI calculation and response planning
- Interface definition between safety and non-safety software components
- Isolation techniques for mixed-criticality systems
- Traceability of software requirements to source code and test cases
- Automated generation of software architecture diagrams
Module 8: Software Verification and Validation - Test strategies for ASIL A to D software components
- Unit testing with code coverage targets (statement, branch, MC/DC)
- Integration testing across software modules and hardware interfaces
- System testing in HiL (Hardware-in-the-Loop) environments
- Test case design using equivalence partitioning and boundary value analysis
- Using mutation testing to assess test suite robustness
- Static code analysis using linting and abstract interpretation tools
- Dynamic analysis for runtime errors (null pointers, buffer overflows)
- Model-based testing and test automation frameworks
- Verification of timing constraints and interrupt latencies
- Back-to-back testing from model to executable code
- Requirements-based testing and gap analysis
- Reporting verification results with objective evidence
- Managing test environments and test data configuration
- Regression testing strategies for software updates
- Certification-readiness checklists for software testing
Module 9: Safety Analysis Techniques and Formal Methods - Introduction to qualitative and quantitative safety analysis
- FMEA (Failure Modes and Effects Analysis) application in automotive systems
- FMECA (Failure Modes, Effects and Criticality Analysis) with ASIL weighting
- FTA (Fault Tree Analysis) construction for top-event resolution
- Qualitative and quantitative evaluation of fault trees
- Common cause failure analysis (CCF) using beta factor and alpha factor models
- Dempster-Shafer theory for handling uncertainty in reliability assessment
- Petri nets and Markov models for dynamic system analysis
- Dependability modelling for phased-mission systems
- Sneak circuit analysis for unintended signal paths
- Hazard and operability study (HAZOP) adapted for automotive E/E
- Software FMEA and its integration with system-level analysis
- Applying model checking and theorem proving in critical component verification
- Use of SMT solvers for program correctness proofs
- Formal specification languages (e.g., Z, TLA+) for safety invariants
- Tool-supported analysis workflows and report generation
Module 10: Integration and Testing at System Level - Integration strategy for safety-related subsystems
- Interface testing between safety and non-safety domains
- Signal path validation from sensor input to actuator output
- End-to-end timing verification across distributed systems
- Interoperability testing of multi-vendor components
- Testing fallback and redundant modes under fault injection
- Simulating hardware faults via controlled perturbation (e.g., voltage glitch)
- Software fault injection testing for exception handling
- Environmental stress testing (temperature, EMI, vibration)
- Recovery testing after power cycles and system resets
- Validation of emergency stop and fail-safe deactivation sequences
- Demonstration of compliance with FTTI requirements
- Blind testing scenarios for independent verification
- System-level safety case structuring and argumentation
- Recording objective evidence for certification audits
- Final system verification plan approval process
Module 11: Production, Operation, Service, and Decommissioning - Safety management during series production
- Process validation for automated testing stations
- Field monitoring and in-vehicle diagnostics (OBD, UDS)
- Handling software updates and over-the-air (OTA) safety patches
- Safety implications of remote reprogramming
- Winter/summer release testing for environmental impact
- Customer incident reporting and root cause analysis
- Service manual creation with safety warnings and procedures
- Recall management processes linked to functional safety non-conformances
- Battery system safety in electric vehicles throughout lifecycle
- End-of-life vehicle dismantling and hazardous material handling
- Data retention and deletion policies for safety-related logs
- Post-production safety monitoring and trend analysis
- Updating safety cases based on field experience
- Decommissioning protocols for autonomous driving systems
- Feedback loops from service data to next-gen design improvements
Module 12: Tool Qualification and Confidence Levels - Identifying safety-related tools in the development chain
- Understanding tool impact (TI) and tool error detection (TD) classification
- Tool qualification process for compilers, static analysers, simulators
- Selecting qualified tools from TÜV-certified lists
- Conducting in-house tool qualification using ISO 26262-8 guidelines
- Documenting tool confidence levels (TCL1, TCL2)
- Using equivalence arguments to reuse previously qualified tools
- Managing commercial off-the-shelf (COTS) tool risks
- Version locking and patch management for qualified tools
- Integration of qualification packages into safety case submissions
- Automated traceability tools and their qualification path
- Model-based design toolchain validation
- Script and plugin qualification strategies
- Continuous integration tools in safety workflows
- Audit readiness for tool documentation reviews
- Maintaining tool qualification across software releases
Module 13: Safety Case Development and Certification Readiness - What is a safety case and why it matters for ISO 26262
- Structure of a safety case: claims, arguments, evidence
- Top-level safety claim derivation from project objectives
- Modular argument construction using GSN (Goal Structuring Notation)
- Creating sub-arguments for hardware, software, integration
- Incorporating HARA, FSC, TSC, and V&V results as evidence
- Handling uncertainty in evidence quality and quantity
- Using templates for consistent safety case formatting
- Automating evidence collection from development tools
- Mapping work products to ISO 26262 compliance checklists
- Engaging auditors and assessors early in the process
- Internal review and gap analysis before formal submission
- Preparing for on-site assessments and document requests
- Responding to auditor findings and non-conformance reports
- Finalising certification with notified bodies or independent assessors
- Maintaining safety case updates across product variants
Module 14: Project Management and Functional Safety Monitoring - Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
- Refining functional safety requirements into technical specifications
- System architecture design for ASIL-compliant systems
- Partitioning safety requirements across hardware and software domains
- Selecting appropriate microcontrollers and safety-related components
- Designing fail-safe states and error containment regions
- Implementing watchdog timers, memory protection units, and lockstep cores
- Integrating diagnostic coverage metrics into system design
- Ensuring time and space partitioning in complex ECU environments
- Specification of communication protocols (CAN, LIN, Ethernet) with safety extensions
- Signal integrity and noise immunity in safety-critical circuits
- Power supply design considerations for fault tolerance
- Environmental stress screening and robustness validation
- Defining system-level FTTI (Fault Tolerant Time Interval)
- Managing thermal, vibration, and electromagnetic compatibility risks
- Designing for maintainability and serviceability without compromising safety
- Documentation standards for system design description
Module 5: Hardware Development and ASIL Compliance - Requirements for hardware architectural metrics (SPFM, LFM, PMHF)
- Calculating single-point fault metric (SPFM) for component selection
- Computing latent fault metric (LFM) for diagnostic effectiveness
- Probabilistic calculation of hardware failure rate (PMHF)
- Selecting components with documented failure rates (FIT values)
- Applying derating principles for electronic parts
- Using redundancy and diversity to meet ASIL D hardware targets
- Designing for high diagnostic coverage in sensor and actuator interfaces
- Hardware-software interface (HSI) specification and validation
- Implementation of built-in self-test (BIST) routines
- Managing clock supervision and reset circuits
- Ensuring data consistency across dual-core processors
- Static analysis techniques for hardware verification
- Verification through simulation and prototyping
- Compliance checks against ISO 26262-5 requirements
- Reporting hardware metrics in safety case documentation
Module 6: Software Development Lifecycle and ASIL Alignment - Mapping software development phases to the V-model
- Differentiating software safety requirements by ASIL level
- Establishing software safety plans and work product requirements
- Configuration management for safety-related code artifacts
- Version control strategies for traceability and audit readiness
- Change management procedures for safety-critical software
- Code naming conventions and commenting standards for clarity
- Modular software design for testability and reuse
- Static and dynamic memory allocation safety rules
- Error handling and exception management in embedded software
- Scheduling policies and interrupt management for real-time execution
- Ensuring temporal determinism in safety functions
- Software unit design principles (cohesion, coupling, encapsulation)
- Programming language selection and safety coding guidelines (MISRA C, JSF AV)
- Tool qualification for compilers, linkers, and debuggers
- Integration of third-party libraries and commercial software components
Module 7: Software Safety Requirements and Architecture - Deriving software safety requirements from system-level specs
- Architectural patterns for safety-critical software (layered, client-server, event-driven)
- Design of safe state machines and mode management logic
- Specification of inter-process communication with data integrity checks
- Memory management and protection mechanisms (MPU, MMU)
- Secure boot and runtime integrity verification techniques
- Stack overflow detection and prevention strategies
- Watchdog supervision of software tasks and threads
- Use of time-triggered and deadline monitoring for task execution
- Design of fail-operational and fail-safe software behaviours
- Redundant software execution paths for critical functions
- Software-level FTTI calculation and response planning
- Interface definition between safety and non-safety software components
- Isolation techniques for mixed-criticality systems
- Traceability of software requirements to source code and test cases
- Automated generation of software architecture diagrams
Module 8: Software Verification and Validation - Test strategies for ASIL A to D software components
- Unit testing with code coverage targets (statement, branch, MC/DC)
- Integration testing across software modules and hardware interfaces
- System testing in HiL (Hardware-in-the-Loop) environments
- Test case design using equivalence partitioning and boundary value analysis
- Using mutation testing to assess test suite robustness
- Static code analysis using linting and abstract interpretation tools
- Dynamic analysis for runtime errors (null pointers, buffer overflows)
- Model-based testing and test automation frameworks
- Verification of timing constraints and interrupt latencies
- Back-to-back testing from model to executable code
- Requirements-based testing and gap analysis
- Reporting verification results with objective evidence
- Managing test environments and test data configuration
- Regression testing strategies for software updates
- Certification-readiness checklists for software testing
Module 9: Safety Analysis Techniques and Formal Methods - Introduction to qualitative and quantitative safety analysis
- FMEA (Failure Modes and Effects Analysis) application in automotive systems
- FMECA (Failure Modes, Effects and Criticality Analysis) with ASIL weighting
- FTA (Fault Tree Analysis) construction for top-event resolution
- Qualitative and quantitative evaluation of fault trees
- Common cause failure analysis (CCF) using beta factor and alpha factor models
- Dempster-Shafer theory for handling uncertainty in reliability assessment
- Petri nets and Markov models for dynamic system analysis
- Dependability modelling for phased-mission systems
- Sneak circuit analysis for unintended signal paths
- Hazard and operability study (HAZOP) adapted for automotive E/E
- Software FMEA and its integration with system-level analysis
- Applying model checking and theorem proving in critical component verification
- Use of SMT solvers for program correctness proofs
- Formal specification languages (e.g., Z, TLA+) for safety invariants
- Tool-supported analysis workflows and report generation
Module 10: Integration and Testing at System Level - Integration strategy for safety-related subsystems
- Interface testing between safety and non-safety domains
- Signal path validation from sensor input to actuator output
- End-to-end timing verification across distributed systems
- Interoperability testing of multi-vendor components
- Testing fallback and redundant modes under fault injection
- Simulating hardware faults via controlled perturbation (e.g., voltage glitch)
- Software fault injection testing for exception handling
- Environmental stress testing (temperature, EMI, vibration)
- Recovery testing after power cycles and system resets
- Validation of emergency stop and fail-safe deactivation sequences
- Demonstration of compliance with FTTI requirements
- Blind testing scenarios for independent verification
- System-level safety case structuring and argumentation
- Recording objective evidence for certification audits
- Final system verification plan approval process
Module 11: Production, Operation, Service, and Decommissioning - Safety management during series production
- Process validation for automated testing stations
- Field monitoring and in-vehicle diagnostics (OBD, UDS)
- Handling software updates and over-the-air (OTA) safety patches
- Safety implications of remote reprogramming
- Winter/summer release testing for environmental impact
- Customer incident reporting and root cause analysis
- Service manual creation with safety warnings and procedures
- Recall management processes linked to functional safety non-conformances
- Battery system safety in electric vehicles throughout lifecycle
- End-of-life vehicle dismantling and hazardous material handling
- Data retention and deletion policies for safety-related logs
- Post-production safety monitoring and trend analysis
- Updating safety cases based on field experience
- Decommissioning protocols for autonomous driving systems
- Feedback loops from service data to next-gen design improvements
Module 12: Tool Qualification and Confidence Levels - Identifying safety-related tools in the development chain
- Understanding tool impact (TI) and tool error detection (TD) classification
- Tool qualification process for compilers, static analysers, simulators
- Selecting qualified tools from TÜV-certified lists
- Conducting in-house tool qualification using ISO 26262-8 guidelines
- Documenting tool confidence levels (TCL1, TCL2)
- Using equivalence arguments to reuse previously qualified tools
- Managing commercial off-the-shelf (COTS) tool risks
- Version locking and patch management for qualified tools
- Integration of qualification packages into safety case submissions
- Automated traceability tools and their qualification path
- Model-based design toolchain validation
- Script and plugin qualification strategies
- Continuous integration tools in safety workflows
- Audit readiness for tool documentation reviews
- Maintaining tool qualification across software releases
Module 13: Safety Case Development and Certification Readiness - What is a safety case and why it matters for ISO 26262
- Structure of a safety case: claims, arguments, evidence
- Top-level safety claim derivation from project objectives
- Modular argument construction using GSN (Goal Structuring Notation)
- Creating sub-arguments for hardware, software, integration
- Incorporating HARA, FSC, TSC, and V&V results as evidence
- Handling uncertainty in evidence quality and quantity
- Using templates for consistent safety case formatting
- Automating evidence collection from development tools
- Mapping work products to ISO 26262 compliance checklists
- Engaging auditors and assessors early in the process
- Internal review and gap analysis before formal submission
- Preparing for on-site assessments and document requests
- Responding to auditor findings and non-conformance reports
- Finalising certification with notified bodies or independent assessors
- Maintaining safety case updates across product variants
Module 14: Project Management and Functional Safety Monitoring - Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
- Mapping software development phases to the V-model
- Differentiating software safety requirements by ASIL level
- Establishing software safety plans and work product requirements
- Configuration management for safety-related code artifacts
- Version control strategies for traceability and audit readiness
- Change management procedures for safety-critical software
- Code naming conventions and commenting standards for clarity
- Modular software design for testability and reuse
- Static and dynamic memory allocation safety rules
- Error handling and exception management in embedded software
- Scheduling policies and interrupt management for real-time execution
- Ensuring temporal determinism in safety functions
- Software unit design principles (cohesion, coupling, encapsulation)
- Programming language selection and safety coding guidelines (MISRA C, JSF AV)
- Tool qualification for compilers, linkers, and debuggers
- Integration of third-party libraries and commercial software components
Module 7: Software Safety Requirements and Architecture - Deriving software safety requirements from system-level specs
- Architectural patterns for safety-critical software (layered, client-server, event-driven)
- Design of safe state machines and mode management logic
- Specification of inter-process communication with data integrity checks
- Memory management and protection mechanisms (MPU, MMU)
- Secure boot and runtime integrity verification techniques
- Stack overflow detection and prevention strategies
- Watchdog supervision of software tasks and threads
- Use of time-triggered and deadline monitoring for task execution
- Design of fail-operational and fail-safe software behaviours
- Redundant software execution paths for critical functions
- Software-level FTTI calculation and response planning
- Interface definition between safety and non-safety software components
- Isolation techniques for mixed-criticality systems
- Traceability of software requirements to source code and test cases
- Automated generation of software architecture diagrams
Module 8: Software Verification and Validation - Test strategies for ASIL A to D software components
- Unit testing with code coverage targets (statement, branch, MC/DC)
- Integration testing across software modules and hardware interfaces
- System testing in HiL (Hardware-in-the-Loop) environments
- Test case design using equivalence partitioning and boundary value analysis
- Using mutation testing to assess test suite robustness
- Static code analysis using linting and abstract interpretation tools
- Dynamic analysis for runtime errors (null pointers, buffer overflows)
- Model-based testing and test automation frameworks
- Verification of timing constraints and interrupt latencies
- Back-to-back testing from model to executable code
- Requirements-based testing and gap analysis
- Reporting verification results with objective evidence
- Managing test environments and test data configuration
- Regression testing strategies for software updates
- Certification-readiness checklists for software testing
Module 9: Safety Analysis Techniques and Formal Methods - Introduction to qualitative and quantitative safety analysis
- FMEA (Failure Modes and Effects Analysis) application in automotive systems
- FMECA (Failure Modes, Effects and Criticality Analysis) with ASIL weighting
- FTA (Fault Tree Analysis) construction for top-event resolution
- Qualitative and quantitative evaluation of fault trees
- Common cause failure analysis (CCF) using beta factor and alpha factor models
- Dempster-Shafer theory for handling uncertainty in reliability assessment
- Petri nets and Markov models for dynamic system analysis
- Dependability modelling for phased-mission systems
- Sneak circuit analysis for unintended signal paths
- Hazard and operability study (HAZOP) adapted for automotive E/E
- Software FMEA and its integration with system-level analysis
- Applying model checking and theorem proving in critical component verification
- Use of SMT solvers for program correctness proofs
- Formal specification languages (e.g., Z, TLA+) for safety invariants
- Tool-supported analysis workflows and report generation
Module 10: Integration and Testing at System Level - Integration strategy for safety-related subsystems
- Interface testing between safety and non-safety domains
- Signal path validation from sensor input to actuator output
- End-to-end timing verification across distributed systems
- Interoperability testing of multi-vendor components
- Testing fallback and redundant modes under fault injection
- Simulating hardware faults via controlled perturbation (e.g., voltage glitch)
- Software fault injection testing for exception handling
- Environmental stress testing (temperature, EMI, vibration)
- Recovery testing after power cycles and system resets
- Validation of emergency stop and fail-safe deactivation sequences
- Demonstration of compliance with FTTI requirements
- Blind testing scenarios for independent verification
- System-level safety case structuring and argumentation
- Recording objective evidence for certification audits
- Final system verification plan approval process
Module 11: Production, Operation, Service, and Decommissioning - Safety management during series production
- Process validation for automated testing stations
- Field monitoring and in-vehicle diagnostics (OBD, UDS)
- Handling software updates and over-the-air (OTA) safety patches
- Safety implications of remote reprogramming
- Winter/summer release testing for environmental impact
- Customer incident reporting and root cause analysis
- Service manual creation with safety warnings and procedures
- Recall management processes linked to functional safety non-conformances
- Battery system safety in electric vehicles throughout lifecycle
- End-of-life vehicle dismantling and hazardous material handling
- Data retention and deletion policies for safety-related logs
- Post-production safety monitoring and trend analysis
- Updating safety cases based on field experience
- Decommissioning protocols for autonomous driving systems
- Feedback loops from service data to next-gen design improvements
Module 12: Tool Qualification and Confidence Levels - Identifying safety-related tools in the development chain
- Understanding tool impact (TI) and tool error detection (TD) classification
- Tool qualification process for compilers, static analysers, simulators
- Selecting qualified tools from TÜV-certified lists
- Conducting in-house tool qualification using ISO 26262-8 guidelines
- Documenting tool confidence levels (TCL1, TCL2)
- Using equivalence arguments to reuse previously qualified tools
- Managing commercial off-the-shelf (COTS) tool risks
- Version locking and patch management for qualified tools
- Integration of qualification packages into safety case submissions
- Automated traceability tools and their qualification path
- Model-based design toolchain validation
- Script and plugin qualification strategies
- Continuous integration tools in safety workflows
- Audit readiness for tool documentation reviews
- Maintaining tool qualification across software releases
Module 13: Safety Case Development and Certification Readiness - What is a safety case and why it matters for ISO 26262
- Structure of a safety case: claims, arguments, evidence
- Top-level safety claim derivation from project objectives
- Modular argument construction using GSN (Goal Structuring Notation)
- Creating sub-arguments for hardware, software, integration
- Incorporating HARA, FSC, TSC, and V&V results as evidence
- Handling uncertainty in evidence quality and quantity
- Using templates for consistent safety case formatting
- Automating evidence collection from development tools
- Mapping work products to ISO 26262 compliance checklists
- Engaging auditors and assessors early in the process
- Internal review and gap analysis before formal submission
- Preparing for on-site assessments and document requests
- Responding to auditor findings and non-conformance reports
- Finalising certification with notified bodies or independent assessors
- Maintaining safety case updates across product variants
Module 14: Project Management and Functional Safety Monitoring - Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
- Test strategies for ASIL A to D software components
- Unit testing with code coverage targets (statement, branch, MC/DC)
- Integration testing across software modules and hardware interfaces
- System testing in HiL (Hardware-in-the-Loop) environments
- Test case design using equivalence partitioning and boundary value analysis
- Using mutation testing to assess test suite robustness
- Static code analysis using linting and abstract interpretation tools
- Dynamic analysis for runtime errors (null pointers, buffer overflows)
- Model-based testing and test automation frameworks
- Verification of timing constraints and interrupt latencies
- Back-to-back testing from model to executable code
- Requirements-based testing and gap analysis
- Reporting verification results with objective evidence
- Managing test environments and test data configuration
- Regression testing strategies for software updates
- Certification-readiness checklists for software testing
Module 9: Safety Analysis Techniques and Formal Methods - Introduction to qualitative and quantitative safety analysis
- FMEA (Failure Modes and Effects Analysis) application in automotive systems
- FMECA (Failure Modes, Effects and Criticality Analysis) with ASIL weighting
- FTA (Fault Tree Analysis) construction for top-event resolution
- Qualitative and quantitative evaluation of fault trees
- Common cause failure analysis (CCF) using beta factor and alpha factor models
- Dempster-Shafer theory for handling uncertainty in reliability assessment
- Petri nets and Markov models for dynamic system analysis
- Dependability modelling for phased-mission systems
- Sneak circuit analysis for unintended signal paths
- Hazard and operability study (HAZOP) adapted for automotive E/E
- Software FMEA and its integration with system-level analysis
- Applying model checking and theorem proving in critical component verification
- Use of SMT solvers for program correctness proofs
- Formal specification languages (e.g., Z, TLA+) for safety invariants
- Tool-supported analysis workflows and report generation
Module 10: Integration and Testing at System Level - Integration strategy for safety-related subsystems
- Interface testing between safety and non-safety domains
- Signal path validation from sensor input to actuator output
- End-to-end timing verification across distributed systems
- Interoperability testing of multi-vendor components
- Testing fallback and redundant modes under fault injection
- Simulating hardware faults via controlled perturbation (e.g., voltage glitch)
- Software fault injection testing for exception handling
- Environmental stress testing (temperature, EMI, vibration)
- Recovery testing after power cycles and system resets
- Validation of emergency stop and fail-safe deactivation sequences
- Demonstration of compliance with FTTI requirements
- Blind testing scenarios for independent verification
- System-level safety case structuring and argumentation
- Recording objective evidence for certification audits
- Final system verification plan approval process
Module 11: Production, Operation, Service, and Decommissioning - Safety management during series production
- Process validation for automated testing stations
- Field monitoring and in-vehicle diagnostics (OBD, UDS)
- Handling software updates and over-the-air (OTA) safety patches
- Safety implications of remote reprogramming
- Winter/summer release testing for environmental impact
- Customer incident reporting and root cause analysis
- Service manual creation with safety warnings and procedures
- Recall management processes linked to functional safety non-conformances
- Battery system safety in electric vehicles throughout lifecycle
- End-of-life vehicle dismantling and hazardous material handling
- Data retention and deletion policies for safety-related logs
- Post-production safety monitoring and trend analysis
- Updating safety cases based on field experience
- Decommissioning protocols for autonomous driving systems
- Feedback loops from service data to next-gen design improvements
Module 12: Tool Qualification and Confidence Levels - Identifying safety-related tools in the development chain
- Understanding tool impact (TI) and tool error detection (TD) classification
- Tool qualification process for compilers, static analysers, simulators
- Selecting qualified tools from TÜV-certified lists
- Conducting in-house tool qualification using ISO 26262-8 guidelines
- Documenting tool confidence levels (TCL1, TCL2)
- Using equivalence arguments to reuse previously qualified tools
- Managing commercial off-the-shelf (COTS) tool risks
- Version locking and patch management for qualified tools
- Integration of qualification packages into safety case submissions
- Automated traceability tools and their qualification path
- Model-based design toolchain validation
- Script and plugin qualification strategies
- Continuous integration tools in safety workflows
- Audit readiness for tool documentation reviews
- Maintaining tool qualification across software releases
Module 13: Safety Case Development and Certification Readiness - What is a safety case and why it matters for ISO 26262
- Structure of a safety case: claims, arguments, evidence
- Top-level safety claim derivation from project objectives
- Modular argument construction using GSN (Goal Structuring Notation)
- Creating sub-arguments for hardware, software, integration
- Incorporating HARA, FSC, TSC, and V&V results as evidence
- Handling uncertainty in evidence quality and quantity
- Using templates for consistent safety case formatting
- Automating evidence collection from development tools
- Mapping work products to ISO 26262 compliance checklists
- Engaging auditors and assessors early in the process
- Internal review and gap analysis before formal submission
- Preparing for on-site assessments and document requests
- Responding to auditor findings and non-conformance reports
- Finalising certification with notified bodies or independent assessors
- Maintaining safety case updates across product variants
Module 14: Project Management and Functional Safety Monitoring - Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
- Integration strategy for safety-related subsystems
- Interface testing between safety and non-safety domains
- Signal path validation from sensor input to actuator output
- End-to-end timing verification across distributed systems
- Interoperability testing of multi-vendor components
- Testing fallback and redundant modes under fault injection
- Simulating hardware faults via controlled perturbation (e.g., voltage glitch)
- Software fault injection testing for exception handling
- Environmental stress testing (temperature, EMI, vibration)
- Recovery testing after power cycles and system resets
- Validation of emergency stop and fail-safe deactivation sequences
- Demonstration of compliance with FTTI requirements
- Blind testing scenarios for independent verification
- System-level safety case structuring and argumentation
- Recording objective evidence for certification audits
- Final system verification plan approval process
Module 11: Production, Operation, Service, and Decommissioning - Safety management during series production
- Process validation for automated testing stations
- Field monitoring and in-vehicle diagnostics (OBD, UDS)
- Handling software updates and over-the-air (OTA) safety patches
- Safety implications of remote reprogramming
- Winter/summer release testing for environmental impact
- Customer incident reporting and root cause analysis
- Service manual creation with safety warnings and procedures
- Recall management processes linked to functional safety non-conformances
- Battery system safety in electric vehicles throughout lifecycle
- End-of-life vehicle dismantling and hazardous material handling
- Data retention and deletion policies for safety-related logs
- Post-production safety monitoring and trend analysis
- Updating safety cases based on field experience
- Decommissioning protocols for autonomous driving systems
- Feedback loops from service data to next-gen design improvements
Module 12: Tool Qualification and Confidence Levels - Identifying safety-related tools in the development chain
- Understanding tool impact (TI) and tool error detection (TD) classification
- Tool qualification process for compilers, static analysers, simulators
- Selecting qualified tools from TÜV-certified lists
- Conducting in-house tool qualification using ISO 26262-8 guidelines
- Documenting tool confidence levels (TCL1, TCL2)
- Using equivalence arguments to reuse previously qualified tools
- Managing commercial off-the-shelf (COTS) tool risks
- Version locking and patch management for qualified tools
- Integration of qualification packages into safety case submissions
- Automated traceability tools and their qualification path
- Model-based design toolchain validation
- Script and plugin qualification strategies
- Continuous integration tools in safety workflows
- Audit readiness for tool documentation reviews
- Maintaining tool qualification across software releases
Module 13: Safety Case Development and Certification Readiness - What is a safety case and why it matters for ISO 26262
- Structure of a safety case: claims, arguments, evidence
- Top-level safety claim derivation from project objectives
- Modular argument construction using GSN (Goal Structuring Notation)
- Creating sub-arguments for hardware, software, integration
- Incorporating HARA, FSC, TSC, and V&V results as evidence
- Handling uncertainty in evidence quality and quantity
- Using templates for consistent safety case formatting
- Automating evidence collection from development tools
- Mapping work products to ISO 26262 compliance checklists
- Engaging auditors and assessors early in the process
- Internal review and gap analysis before formal submission
- Preparing for on-site assessments and document requests
- Responding to auditor findings and non-conformance reports
- Finalising certification with notified bodies or independent assessors
- Maintaining safety case updates across product variants
Module 14: Project Management and Functional Safety Monitoring - Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
- Identifying safety-related tools in the development chain
- Understanding tool impact (TI) and tool error detection (TD) classification
- Tool qualification process for compilers, static analysers, simulators
- Selecting qualified tools from TÜV-certified lists
- Conducting in-house tool qualification using ISO 26262-8 guidelines
- Documenting tool confidence levels (TCL1, TCL2)
- Using equivalence arguments to reuse previously qualified tools
- Managing commercial off-the-shelf (COTS) tool risks
- Version locking and patch management for qualified tools
- Integration of qualification packages into safety case submissions
- Automated traceability tools and their qualification path
- Model-based design toolchain validation
- Script and plugin qualification strategies
- Continuous integration tools in safety workflows
- Audit readiness for tool documentation reviews
- Maintaining tool qualification across software releases
Module 13: Safety Case Development and Certification Readiness - What is a safety case and why it matters for ISO 26262
- Structure of a safety case: claims, arguments, evidence
- Top-level safety claim derivation from project objectives
- Modular argument construction using GSN (Goal Structuring Notation)
- Creating sub-arguments for hardware, software, integration
- Incorporating HARA, FSC, TSC, and V&V results as evidence
- Handling uncertainty in evidence quality and quantity
- Using templates for consistent safety case formatting
- Automating evidence collection from development tools
- Mapping work products to ISO 26262 compliance checklists
- Engaging auditors and assessors early in the process
- Internal review and gap analysis before formal submission
- Preparing for on-site assessments and document requests
- Responding to auditor findings and non-conformance reports
- Finalising certification with notified bodies or independent assessors
- Maintaining safety case updates across product variants
Module 14: Project Management and Functional Safety Monitoring - Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
- Establishing a functional safety management plan
- Defining roles: Safety Manager, Technical Safety Lead, Assessor
- Creating safety work item breakdowns and schedules
- Tracking safety tasks using milestones and KPIs
- Risk-based prioritization of safety activities
- Conducting safety reviews at key phase gates
- Checklist-driven audits for work product completeness
- Managing supplier safety obligations through contracts
- Reviewing subcontractor deliverables for compliance
- Safety change request (SCR) process and impact analysis
- Configuration audit procedures for safety-relevant items
- Handling late requirement changes without compromising integrity
- Managing parallel development streams for multiple vehicle lines
- Reporting status to executive leadership and oversight committees
- Continuous improvement of safety processes using PDCA
- Lessons learned documentation and knowledge transfer
Module 15: Advanced Topics and Emerging Challenges - Safety for highly automated driving systems (SAE Level 3+)
- Dynamic driving task (DDT) handover and fallback logic
- Scenario-based validation for autonomous functions
- Edge case identification using STPA and hazard libraries
- Safety of the intended functionality (SOTIF) integration
- Differentiating random hardware failures from systematic issues
- Machine learning and neural networks in safety-critical roles
- Assuring neural net behaviour with formal bounds and monitors
- V&V of perception algorithms in ADAS and AD systems
- Cybersecurity interactions with functional safety (ISO/SAE 21434)
- Joint analysis of threats and hazards using THARA
- Secure communication protocols with safety overlays
- Hardware security modules (HSM) and trusted execution environments
- Safety implications of vehicle connectivity (V2X)
- Ethical considerations in autonomous emergency decisions
- Global harmonisation efforts and future editions of ISO 26262
Module 16: Real-World Implementation Projects and Certification - End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
- End-to-end case study: Developing a safety-critical braking ECU
- Applying HARA to regenerative braking and fail-safe operation
- Allocating ASIL D requirements across hydraulic and electric subsystems
- Designing redundant CAN communication paths
- Implementing torque vectoring with fault detection logic
- Creating a complete traceability chain from hazard to code
- Generating qualitative and quantitative hardware metrics
- Developing a full GSN-based safety case
- Preparing documentation for ISO 26262 certification audit
- Passing stage gate reviews with internal assessors
- Submitting work products to an external certification body
- Responding to assessor questions and providing objective evidence
- Obtaining formal certification confirmation
- Leveraging the certification in RFP responses and client presentations
- Reusing components and processes across future vehicle platforms
- Measuring return on investment through reduced audit cycles and faster time to market
