Difference between revisions of "ISO26262/Home"

From OpenMBD
Jump to: navigation, search
Line 21: Line 21:
  
 
[[ISO26262/Home]]
 
[[ISO26262/Home]]
 
[[ISO26262/Supporting_Processes]]
 
 
[[ISO26262/Useful_Links]]
 
 
[[ISO26262/V-Cycle]]
 
  
 
[[ISO26262/V-Cycle/2-5_Overall_Safety_Management]]
 
[[ISO26262/V-Cycle/2-5_Overall_Safety_Management]]
Line 79: Line 73:
  
 
[[ISO26262/V-Cycle/Vocabulary]]
 
[[ISO26262/V-Cycle/Vocabulary]]
 +
 +
[[ISO26262/Supporting_Processes]]
 +
 +
[[ISO26262/Useful_Links]]

Revision as of 07:19, 3 October 2017


Back to Home

AllLogos.png


Welcome to the ISO26262: Recommended Practice. This is the result of a project which is set up by HAN-Automotive Research, in cooperation with Baesis, BRACE, VSE and e-Traction. At this moment the Concept phase and the Development phase at system level are covered.

This project is made possible by our parters who actively contributed: - Baesis, Functional Safety Expert - BRACE, Functional Safety Expert - VSE, implementing ISO26262 - e-Traction, implementing ISO26262

The purpose of this project is to lower the investment in both time and cost needed to introducte ISO26262 into small and medium sized companies (SME's). In order to reach this goal informed decisions made by our project partners are documented, together with their rationale, to enhance decision making in future projects. Particular challenges in the implementation process of ISO26262 are addressed and the solutions will be explained. Also templates are made to aid in the process of new document creation to save both time and money. These templates are provided with hints and examples. In addition to this two real-life use cases are added to each milestone: the VSE use-case and the e-Traction use-case.


This wiki is set up according to the same structure as the V-Cycle which is also referred to in the ISO26262. (picture below)

V-Cycle.png

ISO26262/Home

ISO26262/V-Cycle/2-5_Overall_Safety_Management

ISO26262/V-Cycle/2-6_Safety_Management_during_the_concept_phase_and_product_development

ISO26262/V-Cycle/2-7_Safety_management_after_the_item's_release_for_production

ISO26262/V-Cycle/2_Management_of_Functional_Safety

ISO26262/V-Cycle/3-5_Item_Definition

ISO26262/V-Cycle/3-6_Initiation_of_the_Safety_Lifecycle

ISO26262/V-Cycle/3-7_Hazard_Analysis_and_Risk_Assessment

ISO26262/V-Cycle/3-8_Functional_Safety_Concept

ISO26262/V-Cycle/3._Concept_Phase

ISO26262/V-Cycle/4-10_Functional_Safety_Assessment

ISO26262/V-Cycle/4-11_Release_for_Production

ISO26262/V-Cycle/4-5_Initiation_of_Product_Development_at_System_Level

ISO26262/V-Cycle/4-6_Specification_of_the_technical_safety_requirements

ISO26262/V-Cycle/4-7_System_Design

ISO26262/V-Cycle/4-8_Item_Integration_and_Testing

ISO26262/V-Cycle/4-9_Safety_Validation

ISO26262/V-Cycle/4._Product_development_at_the_system_level

ISO26262/V-Cycle/5-10_Hardware_Integration_and_Testing

ISO26262/V-Cycle/5-5_Initiation_of_Product_Development_at_the_Hardware_Level

ISO26262/V-Cycle/5-6_Specification_of_Hardware_Safety_Requirements

ISO26262/V-Cycle/5-7_Hardware_Design

ISO26262/V-Cycle/5-8_Evaluation_of_the_Hardware_Architectural_Metrics

ISO26262/V-Cycle/5-9_Evaluation_of_the_Safety_Goal_violations_due_to_Random_Hardware_Failure

ISO26262/V-Cycle/5._Product_development_at_the_hardware_level

ISO26262/V-Cycle/6._Product_development_at_the_software_level

ISO26262/V-Cycle/Vocabulary

ISO26262/Supporting_Processes

ISO26262/Useful_Links