BS ISO 26262-6:2018
$198.66
Road vehicles. Functional safety – Product development at the software level
Published By | Publication Date | Number of Pages |
BSI | 2018 | 66 |
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 product development at the software level for automotive applications, including the following:
-
general topics for product development at the software level;
-
specification of the software safety requirements;
-
software architectural design;
-
software unit design and implementation;
-
software unit verification;
-
software integration and verification; and
-
testing of the embedded software.
It also specifies requirements associated with the use of configurable software.
Annex A provides an overview on objectives, prerequisites and work products of this document.
PDF Catalog
PDF Pages | PDF Title |
---|---|
2 | National foreword |
7 | Foreword |
9 | Introduction |
11 | 1 Scope |
12 | 2 Normative references 3 Terms and definitions 4 Requirements for compliance 4.1 Purpose 4.2 General requirements |
13 | 4.3 Interpretations of tables 4.4 ASIL-dependent requirements and recommendations |
14 | 4.5 Adaptation for motorcycles 4.6 Adaptation for trucks, buses, trailers and semi-trailers 5 General topics for the product development at the software level 5.1 Objectives 5.2 General |
15 | 5.3 Inputs to this clause 5.3.1 Prerequisites 5.3.2 Further supporting information 5.4 Requirements and recommendations |
17 | 5.5 Work products 6 Specification of software safety requirements 6.1 Objectives |
18 | 6.2 General 6.3 Inputs to this clause 6.3.1 Prerequisites 6.3.2 Further supporting information 6.4 Requirements and recommendations |
20 | 6.5 Work products 7 Software architectural design 7.1 Objectives 7.2 General 7.3 Inputs to this clause 7.3.1 Prerequisites |
21 | 7.3.2 Further supporting information 7.4 Requirements and recommendations |
26 | 7.5 Work products |
27 | 8 Software unit design and implementation 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 |
29 | 8.5 Work products 9 Software unit verification 9.1 Objectives |
30 | 9.2 General 9.3 Inputs to this clause 9.3.1 Prerequisites 9.3.2 Further supporting information 9.4 Requirements and recommendations |
34 | 9.5 Work products 10 Software integration and verification 10.1 Objectives 10.2 General 10.3 Inputs to this clause 10.3.1 Prerequisites |
35 | 10.3.2 Further supporting information 10.4 Requirements and recommendations |
38 | 10.5 Work products 11 Testing of the embedded software 11.1 Objective 11.2 General 11.3 Inputs to this clause 11.3.1 Prerequisites 11.3.2 Further supporting information |
39 | 11.4 Requirements and recommendations |
40 | 11.5 Work products |
41 | Annex A (informative) Overview of and workflow of management of product development at the software level |
44 | Annex B (informative) Model-based development approaches |
48 | Annex C (normative) Software configuration |
54 | Annex D (informative) Freedom from interference between software elements |
56 | Annex E (informative) Application of safety analyses and analyses of dependent failures at the software architectural level |
65 | Bibliography |