ISO 26262-6:2018
(Main)Road vehicles — Functional safety — Part 6: Product development at the software level
Road vehicles — Functional safety — Part 6: Product development at the software level
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.
Véhicules routiers — Sécurité fonctionnelle — Partie 6: Développement du produit au niveau du logiciel
General Information
Relations
Standards Content (Sample)
INTERNATIONAL ISO
STANDARD 26262-6
Second edition
2018-12
Road vehicles — Functional safety —
Part 6:
Product development at the software
level
Véhicules routiers — Sécurité fonctionnelle —
Partie 6: Développement du produit au niveau du logiciel
Reference number
©
ISO 2018
© ISO 2018
All rights reserved. Unless otherwise specified, or required in the context of its implementation, no part of this publication may
be reproduced or utilized otherwise in any form or by any means, electronic or mechanical, including photocopying, or posting
on the internet or an intranet, without prior written permission. Permission can be requested from either ISO at the address
below or ISO’s member body in the country of the requester.
ISO copyright office
CP 401 • Ch. de Blandonnet 8
CH-1214 Vernier, Geneva
Phone: +41 22 749 01 11
Fax: +41 22 749 09 47
Email: copyright@iso.org
Website: www.iso.org
Published in Switzerland
ii © ISO 2018 – All rights reserved
Contents Page
Foreword .v
Introduction .vii
1 Scope . 1
2 Normative references . 2
3 Terms and definitions . 2
4 Requirements for compliance . 2
4.1 Purpose . 2
4.2 General requirements . 2
4.3 Interpretations of tables . 3
4.4 ASIL-dependent requirements and recommendations . 3
4.5 Adaptation for motorcycles . 4
4.6 Adaptation for trucks, buses, trailers and semi-trailers. 4
5 General topics for the product development at the software level .4
5.1 Objectives. 4
5.2 General . 4
5.3 Inputs to this clause . 5
5.3.1 Prerequisites . 5
5.3.2 Further supporting information . 5
5.4 Requirements and recommendations . 5
5.5 Work products . 7
6 Specification of software safety requirements . 7
6.1 Objectives. 7
6.2 General . 8
6.3 Inputs to this clause . 8
6.3.1 Prerequisites . 8
6.3.2 Further supporting information . 8
6.4 Requirements and recommendations . 8
6.5 Work products .10
7 Software architectural design .10
7.1 Objectives.10
7.2 General .10
7.3 Inputs to this clause .10
7.3.1 Prerequisites .10
7.3.2 Further supporting information .10
7.4 Requirements and recommendations .11
7.5 Work products .16
8 Software unit design and implementation .16
8.1 Objectives.16
8.2 General .17
8.3 Inputs to this clause .17
8.3.1 Prerequisites .17
8.3.2 Further supporting information .17
8.4 Requirements and recommendations .17
8.5 Work products .19
9 Software unit verification .19
9.1 Objectives.19
9.2 General .19
9.3 Inputs to this clause .20
9.3.1 Prerequisites .20
9.3.2 Further supporting information .20
9.4 Requirements and recommendations .20
9.5 Work products .24
10 Software integration and verification .24
10.1 Objectives.24
10.2 General .24
10.3 Inputs to this clause .24
10.3.1 Prerequisites .24
10.3.2 Further supporting information .25
10.4 Requirements and recommendations .25
10.5 Work products .28
11 Testing of the embedded software .28
11.1 Objective .28
11.2 General .28
11.3 Inputs to this clause .28
11.3.1 Prerequisites .28
11.3.2 Further supporting information .28
11.4 Requirements and recommendations .29
11.5 Work products .30
Annex A (informative) Overview of and workflow of management of product development
at the software level .31
Annex B (informative) Model-based development approaches .36
Annex C (normative) Software configuration.
...
Questions, Comments and Discussion
Ask us and Technical Secretary will try to provide an answer. You can facilitate discussion about the standard in here.