BS ISO 26262-8:2018
$215.11
Road vehicles. Functional safety – Supporting processes
Published By | Publication Date | Number of Pages |
BSI | 2018 | 72 |
This document is intended to be applied to safety-related systems that include one or more electrical and/or electronic (E/E) systems and that are installed in series production road vehicles, excluding mopeds. This document does not address unique E/E systems in special vehicles such as E/E systems designed for drivers with disabilities.
NOTE Other dedicated application-specific safety standards exist and can complement the ISO 26262 series of standards or vice versa.
Systems and their components released for production, or systems and their components already under development prior to the publication date of this document, are exempted from the scope of this edition. This document addresses alterations to existing systems and their components released for production prior to the publication of this document by tailoring the safety lifecycle depending on the alteration. This document addresses integration of existing systems not developed according to this document and systems developed according to this document by tailoring the safety lifecycle.
This document addresses possible hazards caused by malfunctioning behaviour of safety-related E/E systems, including interaction of these systems. It does not address hazards related to electric shock, fire, smoke, heat, radiation, toxicity, flammability, reactivity, corrosion, release of energy and similar hazards, unless directly caused by malfunctioning behaviour of safety-related E/E systems.
This document describes a framework for functional safety to assist the development of safety-related E/E systems. This framework is intended to be used to integrate functional safety activities into a company-specific development framework. Some requirements have a clear technical focus to implement functional safety into a product; others address the development process and can therefore be seen as process requirements in order to demonstrate the capability of an organization with respect to functional safety.
This document does not address the nominal performance of E/E systems.
This document specifies the requirements for supporting processes, including the following:
-
interfaces within distributed developments;
-
overall management of safety requirements;
-
configuration management;
-
change management;
-
verification;
-
documentation management;
-
confidence in the use of software tools;
-
qualification of software components;
-
evaluation of hardware elements;
-
proven in use argument;
-
interfacing an application that is out of scope of ISO 26262; and
-
integration of safety-related systems not developed according to ISO 26262.
Annex A provides an overview on objectives, prerequisites and work products of this document.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
8 | Foreword |
10 | Introduction |
13 | 1 Scope |
14 | 2 Normative references 3 Terms and definitions 4 Requirements for compliance 4.1 Purpose 4.2 General requirements |
15 | 4.3 Interpretations of tables 4.4 ASIL-dependent requirements and recommendations |
16 | 4.5 Adaptation for motorcycles 4.6 Adaptation for trucks, buses, trailers and semi-trailers 5 Interfaces within distributed developments 5.1 Objectives 5.2 General 5.3 Inputs to this clause 5.3.1 Prerequisites |
17 | 5.3.2 Further supporting information 5.4 Requirements and recommendations 5.4.1 Application of requirements 5.4.2 Supplier selection criteria |
18 | 5.4.3 Initiation and planning of distributed development |
19 | 5.4.4 Execution of distributed development |
20 | 5.4.5 Functional safety assessment activities in a distributed development 5.4.6 Agreement for production, operation, service and decommissioning 5.5 Work products |
21 | 6 Specification and management of safety requirements 6.1 Objectives 6.2 General |
22 | 6.3 Inputs to this clause 6.3.1 Prerequisites 6.3.2 Further supporting information |
23 | 6.4 Requirements and recommendations 6.4.1 Specification of safety requirements 6.4.2 Attributes and characteristics of safety requirements |
25 | 6.4.3 Management of safety requirements |
26 | 6.5 Work products 7 Configuration management 7.1 Objectives 7.2 General |
27 | 7.3 Inputs to this clause 7.3.1 Prerequisites 7.3.2 Further supporting information 7.4 Requirements and recommendations 7.5 Work products |
28 | 8 Change management 8.1 Objectives 8.2 General 8.3 Inputs to this clause 8.3.1 Prerequisites 8.3.2 Further supporting information 8.4 Requirements and recommendations 8.4.1 Planning and initiating change management |
29 | 8.4.2 Change requests 8.4.3 Change request analysis 8.4.4 Change request evaluation |
30 | 8.4.5 Implementing and documenting the change 8.5 Work products 9 Verification 9.1 Objectives 9.2 General |
31 | 9.3 Inputs to this clause 9.3.1 Prerequisites 9.3.2 Further supporting information 9.4 Requirements and recommendations 9.4.1 Verification planning |
32 | 9.4.2 Verification specification |
33 | 9.4.3 Verification execution and evaluation 9.5 Work products |
34 | 10 Documentation management 10.1 Objectives 10.2 General 10.3 Inputs to this clause 10.3.1 Prerequisites 10.3.2 Further supporting information 10.4 Requirements and recommendations |
35 | 10.5 Work products |
36 | 11 Confidence in the use of software tools 11.1 Objectives 11.2 General |
38 | 11.3 Inputs to this clause 11.3.1 Prerequisites 11.3.2 Further supporting information 11.4 Requirements and recommendations 11.4.1 General requirement |
39 | 11.4.2 Validity of predetermined Tool Confidence Level or qualification 11.4.3 Software tool compliance with its evaluation criteria or its qualification 11.4.4 Planning of usage of a software tool |
40 | 11.4.5 Evaluation of a software tool by analysis |
41 | 11.4.6 Qualification of a software tool |
42 | 11.4.7 Increased confidence from use |
43 | 11.4.8 Evaluation of the tool development process |
44 | 11.4.9 Validation of the software tool 11.5 Work products 12 Qualification of software components 12.1 Objectives 12.2 General |
45 | 12.3 Inputs to this clause 12.3.1 Prerequisites 12.3.2 Further supporting information 12.4 Requirements and recommendations 12.4.1 General 12.4.2 Specification of software component qualification |
47 | 12.4.3 Verification of qualification of a software component 12.5 Work products 13 Evaluation of hardware elements 13.1 Objectives |
48 | 13.2 General 13.3 Inputs to this clause 13.3.1 Prerequisites 13.3.2 Further supporting information |
49 | 13.4 Requirements and recommendations 13.4.1 General |
50 | 13.4.2 Evaluation of class I hardware elements 13.4.3 Evaluation of class II hardware elements |
52 | 13.4.4 Evaluation of class III hardware elements 13.5 Work products 14 Proven in use argument 14.1 Objectives |
53 | 14.2 General 14.3 Inputs to this clause 14.3.1 Prerequisites |
54 | 14.3.2 Further supporting information 14.4 Requirements and recommendations 14.4.1 General 14.4.2 Proven in use credit |
55 | 14.4.3 Minimum information on candidate 14.4.4 Analysis of modifications to the candidate 14.4.5 Analysis of field data |
57 | 14.5 Work products |
58 | 15 Interfacing an application that is out of scope of ISO 26262 15.1 Objectives 15.2 General 15.3 Inputs to this clause 15.3.1 Prerequisites 15.3.2 Further supporting information 15.4 Requirements and recommendations |
59 | 15.5 Work products 16 Integration of safety-related systems not developed according to ISO 26262 16.1 Objectives 16.2 General |
60 | 16.3 Inputs to this clause 16.3.1 Prerequisites 16.3.2 Further supporting information 16.4 Requirements and recommendations 16.5 Work products |
61 | Annex A (informative) Overview of and workflow of supporting processes |
65 | Annex B (informative) Development Interface Agreement (DIA) example |
71 | Bibliography |