Learning Objectives

• Tailor the necessary activities to support vehicle safety lifecycle management, development, production, operation, service, and decommissioning.
• Information provided in the class can be used for ISO 26262 implementation.
• Understand functional safety aspects of the entire development process including requirements specification, design, implementation, integration, verification, validation, and configuration.
• Understand the risk-based approach for determining risk classes Automotive Safety Integrity Levels (ASILs).
• Use ASILs for achieving an acceptable residual risk.
• Provide requirements for validation and confirmation measures to ensure a sufficient and acceptable level of safety is being achieved.

Course Outline

Day One

Chapter 1: Introduction and Overview to ISO 26262

• ISO 26262 Purpose, Scope and Framework

Chapter 2: Management of Functional Safety (Part 2)

• Safety Culture
• Project Dependent Safety Management
• Safety Case
• Breakout Exercise 1: Safety Case Outline
• Confirmation Measures

Chapter 3: Production and Operation (Part 7)

Chapter 4: Safety Element out of Context (Part 10)

Chapter 5: Concept Phase (Part 3)

• Item Definition
• Breakout Exercise 2: Item Definition

Day Two

• Chapter 5: Concept Phase (Part 3) (cont’d)
• Hazard Analysis and Risk Assessment (HARA)
• Severity, Exposure and Controllability
• Safety Goals
• Breakout Exercise 3: HARA
• Functional Safety Requirements
• Breakout Exercise 4: Functional Safety Requirements

Chapter 6: ASIL-Oriented and Safety-Oriented Analyses (Part 9)

• Example Scenario
• Safety Analyses in ISO 26262

Chapter 7: System Level Development I (Part 4)

• Technical Safety Concept
• Hardware-Software Interface (HSI)

Day Three

Chapter 8: Hardware Level Development I (Part 5)

• Specification of Hardware Safety Requirements
• Hardware Design
• Evaluation of the Hardware Architectural Metrics
• Breakout Exercise 5: Fault Metrics
• Evaluation of Safety Goal Violations Due to Random Hardware Failures

Chapter 9: Evaluation of Hardware Elements (Part 8)

• Classification of Evaluated Hardware Element
• Hardware Evaluation
• Proven-in-Use Argument

Chapter 10: Hardware Level Development II (Part 5 revisited)

• Initiation of Product Development at the Hardware Level
• Hardware Integration and Verification

Chapter 11: Software Level Development (Part 6)

• General Topics for Product Development at the Software Level
• Specification of Software Safety Requirements

Day Four

• Chapter 11: Software Level Development (Part 6) (cont’d)
• Software Architectural Design
• Breakout Exercise 6: Walkthrough vs. Inspection
• Verification by Review
• Control Flow Analysis and Data Flow Analysis
• Software Unit Design and Implementation
• Software Unit Verification and Testing
• Coverage Metrics
• Software Integration Testing

Chapter 12: System Level Development II (Part 4 revisited)

• Item Integration and Testing
• System Integration and Testing
• Vehicle Level Integration
• Safety Validation
• Functional Safety Assessment
• Release to Production

Chapter 13: Supporting Processes (Part 8)

• Integration of ISO 26262 with ISO 9001 or IATF 16949
• Breakout Exercise 7: Integration with Other Standards

Day Five

• Chapter 13: Supporting Processes (Part 8) (cont’d)
• Distributed Development
• Specification and Management of Safety Requirements
• Configuration Management
• Change Management
• Verification
• Documentation Management System
• Qualification of Software Tools
• Breakout Exercise 8: Confidence in Tools
• Qualification of Software Components
• Evaluation of Hardware Elements
• Proven in Use Argumentation
• Interfacing an Application that is Out of Scope of ISO 26262
• Integration of Safety-Related Systems not Developed According to ISO 26262

Chapter 14: Guideline on Application of ISO 26262 to Semiconductors (Part 11)

Chapter 15: Adaption of ISO 26262 to Motorcycles (Part 12)

Chapter 16: ISO 26262 Implementation Strategy

Optional ISO 26262 Certification Exam – Final 3 hours of Day Five

Level 1

Functional Safety Engineer

Knowledge Requirements:

• 1 week of Functional safety training and candidates must pass a three hour final exam.

Prerequisites:

• At least 3 years of relevant professional experience,

Who Should Attend

Those involved in the design, development, and production of electrical and electronic based vehicle products, including the systems, software and hardware engineers, and managers. Basically, all those responsible for the development and implementation of hardware and software systems in motor vehicles.

Participants should be, or plan to be, actively managing, or involved in, or aware of electrical and/or electronic items, systems, or elements that are incorporated in motor vehicles. Participants should also have the abilities, education, and experience required for the above roles.

Course Materials

Each participant will receive a seminar manual including case studies.

Note: Omnex does not provide copies of standard(s) during training courses, but clients are encouraged to have their own copy.

Pre-Requisite

Participants should be involved in or aware of software and hardware development as it relates to the motor vehicle industry.

Enroll Now