
At the end of the session, attendees should be able to:
> Summarize the overall goals and purpose of ISO 26262 Part 2
> Identify safety management responsibilities for managers
> Discuss safety culture
> For each clause of ISO 26262 Part 2:
* Compare the objectives
* Identify the responsible parties
* Analyze applicable processes
* Cite required documentation
At the end of the session, attendees should be able to:
> Summarize the overall goals and purpose of ISO 26262 Part 3
> Clarify the steps of Clause 5 – Item Definition
> Identify and classify a hazardous event
> Discuss Functional Safety Requirements and their role in Part 3
> Analyze the role of System Architectural Design
> Explain the steps to verify the Functional Safety Concept
> Define Functional Safety Concept States
At the end of the session, attendees should be able to:
> Describe the life cycle and activities of ISO 26262 Part 4
> Define the work products required by ISO 26262 Part 4
> Analyze the scope of systems development
> Cite the definition of basic terms used in Part 4
> Specify method selection to support FS Part 4 activities
> Examine the impact on of Part 4 on product development
> Identify ISO 26262 Part 4 compliance requirements
At the end of the session, attendees should be able to:
> Identify Safety Goal thresholds
> Define fault types
> Describe how to calculate fault metrics
> Explain the two methods of evaluating safety goal violation
> Examine failure rate classes
> Analyze integration testing requirements
At the end of the session, attendees should be able to:
> Discuss important strategy planning actions
> Identify critical steps in software architecture design practices
> Explain the concept and purpose of software partitioning
> Examine the specification and verification of software safety requirements
> Determine best practices for choosing testing methods
> Explain software integration
> Analyze the role of ISO 26262 Part 8 with Part 6 processes
At the end of this session, attendees should be able to:
> How to Develop and maintain a production process for safety-related elements or items
> How to Achieve functional safety during the production process
At the end of the session, attendees should be able to:
> Give a broad overview of Part 8 goals
> Describe the role of the Distributed Interface Agreement
> Identify overall safety management requirements
> Define factors affecting verification
> Explain the relationship between Part 8 and the Concept and Development Phases
> Analyze hardware and software qualification
> Define proven in-use arguments
At the end of the session, attendees should be able to:
> Describe ASIL decomposition rules
> Discuss the two ASIL decomposition methods
> Identify different ASIL decomposition schemes
> Examine strategies for resolving failures
> Analyze dependent failure types
> Explain failure evaluation
Functional Safety case
A number of components of a car are safety-critical like Electronic Steering System, Anti-lock Braking System, Air-bags, electronic stability control, and more. By safety-critical, we mean that the failure of these components can risk the driver or the passengers’ life. ISO26262 is a standard that defines a framework to implement safety practices during the design, development, and testing of all the critical electrical and electronic components of a road vehicle. This standard has been derived from IEC61508. ISO26262 standard comprises a set of steps that regulate the product lifecycle at the software and the hardware level. ISO26262 provides an extensive set of recommendations for automotive product development, right from the conceptualization to the decommissioning stage. With the introduction of electronic control units to automotive vehicles, system complexity has increased. With this change in complexity, new standards have been created to ensure safety at the system level for these vehicles. Furthermore, vehicles have become increasingly complex with the push for electrification of automotive vehicles, which has resulted in the creation of hybrid electric and battery electric vehicles. ASIL (Automotive Safety Integrity Level) is the notation for software or hardware component that signifies its safety-criticality. ASIL A, ASIL B, ASIL C, and ASIL D. ASIL A indicates the least critical level and D indicates the most critical level. There are three factors that determine the ASIL of software or hardware- the probability of exposure, controllability by the driver, and the severity of the outcome if a fault occurs. ASIL A is almost equivalent to QM level, therefore, ASIL B is usually the minimum requirement, in order to make your product compliant with ISO 26262 Standard for Functional Safety. ASIL is determined at the beginning of the automotive software development with the help of HARA. However, it can be done post the development also but is not recommended. Based on the ASIL rating, safety processes and testing regulations are followed- strictest for D and flexible for A.
This Course makes you learn on these below objectives:
1. Functional Safety Basics and ASIL determination
2. Functional Safety Introduction
3. Functional Safety Management
4. Functional Safety Concept
5. Product Development at System Level
6. Product Development at Hardware Level
7. Product Development at Software Level
8. Functional Safety Management (Production, Operation, Service, and Decommissioning)
9. Functional Safety Support Process
10. ASIL Oriented and Safety Oriented Analysis
Students kindly observe this is Expert Level training. For Beginner's level, I made another training session.