Welcome to ISO 26262
This web site details the Tasks, Work Products, Roles and workflows required for the development of safety related work item for a vehicle to be compliant to ISO 26262.
Relationships
Categories
Main Description

This practice content and workflow is an interpretation and reflection of the ISO 26262 standard published in November 2011. It is not intended to replace the standard and it should be used in conjunction with the ISO 26262-2011standard, as the standard is referenced in many places.

The workflow provided in Rational Method Composer is provided to assist you in tracking information that may be important to you in aligning your system and software development processes with tasks from the ISO 26262-2011 standard available from the ISO store.  

The guidance given on these web pages covers the main phases of development from Management of Functional Safety, through the Concept Phase and Product Development at Systems, Hardware and Software level to Production and Operation. The main Supporting processes are also detailed. The ASIL and safety orientated analysis activity may be added at a future time.

 

The tasks detailed on this website (specifically the ISO 26262 tasks) are related to a set of work item templates which are instantiated in an ISO 26262 process template in Rational Team Concert. This allows project managers and team leaders to organize, allocate, control and review the progress of the development of the item. From the users perspective the use of Rational Team Concert with the web template gives guidance in the development of the item and in the use of tools that could help with the development of the item.

As the ISO 26262 process is essentially a V development model and the use and benefits of Model Based approaches are detailed in the standard, extra guidance has been given to support the user in deploying Rational tools for requirements management, model based systems development, embedded software development, testing and integration. The practices detailed in this guidance are generic but they can be adapted to fit with an automotive development process, even down to supporting an AUTOSAR implementation of the software. As further practices are developed more of the ISO 26262 safety lifecycle will be covered with detailed tool guidance.

When starting to look through this web site the user is advised to examine the section detailing the Main Process Flows, this gives an indication of how the work flows and processess work together and are taken directly from ISO 26262. The user can then drill down into the relevant detailed activities. For a more focused view the user is advised to examine the section on the ISO 26262, Main Phases of the Safety Lifecycle, again the upper level flow of activities is directly based on the reference workflows detailed in ISO 26262.

The main process flows cover.

                                           Product development system level

                                           Safety Lifecycle

                                           5 Hardware product development

                                           6 Software product development

The majority of the workflows are divided up into the main phases of the ISO 26262 development lifecycle.

                                            2 Management of functional safety

                                            3 Concept Phase

                                            4. Systems Engineering for product development

                                            5 Hardware product development

                                            6 Software product development

                                            4. Systems Integration and testing

                                            7 Production and Operation

The exceptions are the Management of Functional Safety phase, the Production and Operation phase and the Supporting activity phases. In these phases the clauses within the phase provide the main work item. The System Development phase is split into a Systems Engineering and a System Integration phase to ease the management of the workflows and work items. The prefix numbering of the workitem templates matches to the volume, phase or clause in ISO 26262 that it is related too. 

The work flows for a specific sub-clauses are generic in nature and not specified by ISO 26262, in this instance the work flows were logically derived from experience or from indications and pointers in the ISO 26262 specification. As these detailed flows are generic in nature the author is aware that they may not fit into an organization's process and it is advised that the organization customize these flows to fit their purpose. It should be noted that customization of the main workflows by an organization is effectively tailoring the safety lifecycle and this must be documented and a rationale produced to support the case for this activity, as detailed in ISO 26262, Vol 3 clause 6.

It should be noted that this information is not intended as a replacement for the actual standard. it reflects an understanding of the information in the ISO 26262 standard and should be used as guidance. Many of the tasks detailed in this website provide summary guidance (to prevent infringement of copyright laws and in some case because the guidance cannot be summarised due to its complexity) , where this occurs the user is strongly advised to refer to the standard for more detail.

There are various tables and notations used within the ISO 26262-2011 standard with respect to the tables where methods are related to ASIL levels.

++ The method is highly recommended for this ASIL.

+  The method is recommended for this ASIL.

0 The method has no recommendation for or against its usage for this ASIL.

A number of tables have been summarised in text (to prevent infringement of copyright laws, see below) and where " 0" would have been detailed in the table it has been left out of the summary. It can be assumed that if an ASIL recommendation is not mentioned for a particular method, technique or test then the remaining ASIL has been assigned "0".

Throughout the ISO 26262 documents and in many places in this web document, a statement will appear such as " applicable ASIL to (B), C and D" , the term in paranthese indicates that the corresponding subclause/paragraph shall be read as a recommendation rather than a requirement for this ASIL.

In the tables for ASIL determination the term QM indicates Quality Managed, this means that the functional safety goal assigned this value can be managed using best practices around quality management and does not have an ASIL assigned to it.

For a more detailed understanding of the introduction to ISO 26262 the user is advised to refer to the front matter on any of the ISO 26262 volumes, clauses 1 to 4.

A number of tables and diagrams have been reused from the ISO 26262 standard and have been reproduced with permission from ANSI, where these diagrams and tables are shown the following text will appear at the bottom of the relevant web page:

This table/figure is taken from ISO 26262:2011-[Part of Standard the Table/Figure is From] © ISO 2011 – All rights reserved. Reproduced with the permission of ANSI on behalf of ISO.

Legal Statement

The practice mapping to ISO26262 provided here can be used to help Licensee meet compliance obligations, which may be based on laws, regulations, standards or additional practices. Any directions, suggested usage, or guidance provided by the practice mapping does not constitute legal, accounting, or other professional advice, and Licensee is cautioned to obtain its own legal or other expert counsel. Licensee is solely responsible for ensuring that Licensee and Licensee's activities, applications and systems comply with all applicable laws, regulations, standards and practices. Use of this practice mapping does not guarantee compliance with any law, regulation, standard or additional practice.