ISO 26262-6:2011

Road vehicles — Functional safety — Part 6: Product development at the software level

ISO 26262 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 passenger cars with a maximum gross vehicle mass up to 3 500 kg. ISO 26262 does not address unique E/E systems in special purpose vehicles such as vehicles designed for drivers with disabilities. Systems and their components released for production, or systems and their components already under development prior to the publication date of ISO 26262, are exempted from the scope. For further development or alterations based on systems and their components released for production prior to the publication of ISO 26262, only the modifications will be developed in accordance with ISO 26262. ISO 26262 addresses possible hazards caused by malfunctioning behaviour of E/E safety-related 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 E/E safety-related systems. ISO 26262 does not address the nominal performance of E/E systems, even if dedicated functional performance standards exist for these systems (e.g. active and passive safety systems, brake systems, Adaptive Cruise Control). ISO 26262-6:2011 specifies the requirements for product development at the software level for automotive applications, including the following: requirements for initiation of product development at the software level, specification of the software safety requirements, software architectural design, software unit design and implementation, software unit testing, software integration and testing, and verification of software safety requirements.

Véhicules routiers — Sécurité fonctionnelle — Partie 6: Développement du produit au niveau du logiciel

General Information

• Status: Withdrawn
• Publication Date: 13-Nov-2011
• Withdrawal Date: 13-Nov-2011
• ICS: 43.040.10 - Electrical and electronic equipment
• Technical Committee: ISO/TC 22/SC 32 - Electrical and electronic components and general system aspects
• Drafting Committee: ISO/TC 22/SC 32/WG 8 - Functional safety
• Current Stage: 9599 - Withdrawal of International Standard
• Completion Date: 17-Dec-2018

Relations

• Revised: ISO 26262-6:2018 - Road vehicles — Functional safety — Part 6: Product development at the software level
• Effective Date: 05-Nov-2015

Standards Content (Sample)

INTERNATIONAL ISO
STANDARD 26262-6
First edition
2011-11-15

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 26262-6:2011(E)
©
ISO 2011

---------------------- Page: 1 ----------------------
ISO 26262-6:2011(E)

COPYRIGHT PROTECTED DOCUMENT


©  ISO 2011
All rights reserved. Unless otherwise specified, no part of this publication may be reproduced or utilized in any form or by any means,
electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or
ISO's member body in the country of the requester.
ISO copyright office
Case postale 56  CH-1211 Geneva 20
Tel. + 41 22 749 01 11
Fax + 41 22 749 09 47
E-mail [e-mail]
Web www.iso.org
Published in Switzerland

ii © ISO 2011 – All rights reserved

---------------------- Page: 2 ----------------------
ISO 26262-6:2011(E)
Contents Page
Foreword . v
Introduction . vi
1  Scope . 1
2  Normative references . 2
3  Terms, definitions and abbreviated terms . 2
4  Requirements for compliance . 2
4.1  General requirements . 2
4.2  Interpretations of tables . 2
4.3  ASIL-dependent requirements and recommendations . 3
5  Initiation of product development at the software level . 3
5.1  Objectives . 3
5.2  General . 3
5.3  Inputs to this clause . 4
5.4  Requirements and recommendations . 4
5.5  Work products . 6
6  Specification of software safety requirements. 6
6.1  Objectives . 6
6.2  General . 7
6.3  Inputs to this clause . 7
6.4  Requirements and recommendations . 7
6.5  Work products . 9
7  Software architectural design . 9
7.1  Objectives . 9
7.2  General . 9
7.3  Inputs to this clause . 9
7.4  Requirements and recommendations . 10
7.5  Work products . 15
8  Software unit design and implementation . 15
8.1  Objectives . 15
8.2  General . 15
8.3  Inputs to this clause . 16
8.4  Requirements and recommendations . 16
8.5  Work products . 18
9  Software unit testing . 19
9.1  Objectives . 19
9.2  General . 19
9.3  Inputs to this clause . 19
9.4  Requirements and recommendations . 19
9.5  Work products . 21
10  Software integration and testing . 22
10.1  Objectives . 22
10.2  General . 22
10.3  Inputs to this clause . 22
10.4  Requirements and recommendations . 23
10.5  Work products . 25
11  Verification of software safety requirements . 25
© ISO 2011 – All rights reserved iii

---------------------- Page: 3 ----------------------
ISO 26262-6:2011(E)
11.1  Objectives .25
11.2  General .25
11.3  Inputs to this clause .25
11.4  Requirements and recommendations .26
11.5  Work products .27
Annex A (informative) Overview of and workflow of management of product development at the
software level .28
Annex B (informative) Model-based development .31
Annex C (normative) Software configuration .33
Annex D (informative) Freedom from interference between software elements .38
Bibliography .40

iv © ISO 2011 – All rights reserved

---------------------- Page: 4 ----------------------
ISO 26262-6:2011(E)
Foreword
ISO (the International Organization for Standardization) is a worldwide federation of national standards bodies
(ISO member bodies). The work of preparing International Standards is normally carried out through ISO
technical committees. Each member body interested in a subject for which a technical committee has been
established has the right to be represented on that committee. International organizations, governmental and
non-governmental, in liaison with ISO, also take part in the work. ISO collaborates closely with the
International Electrotechnical Commission (IEC) on all matters of electrotechnical standardization.
International Standards are drafted in accordance with the rules given in the ISO/IEC Directives, Part 2.
The main task of technical committees is to prepare International Standards. Draft International Standards
adopted by the technical committees are circulated to the member bodies for voting. Publication as an
International Standard requires approval by at least 75 % of the member bodies casting a vote.
Attention is drawn to the possibility that some of the elements of this document may be the subject of patent
rights. ISO shall not be held responsible for identifying any or all such patent rights.
ISO 26262-6 was prepared by Technical Committee ISO/TC 22, Road vehicles, Subcommittee SC 3,
Electrical and electronic equipment.
ISO 26262 consists of the following parts, under the general title Road vehicles — Functional safety:
 Part 1: Vocabulary
 Part 2: Management of functional safety
 Part 3: Concept phase
 Part 4: Product development at the system level
 Part 5: Product development at the hardware level
 Part 6: Product development at the software level
 Part 7: Production and operation
 Part 8: Supporting processes
 Part 9: Automotive Safety Integrity Level (ASIL)-oriented and safety-oriented analyses
 Part 10: Guideline on ISO 26262
© ISO 2011 – All rights reserved v

---------------------- Page: 5 ----------------------
ISO 26262-6:2011(E)
Introduction
ISO 26262 is the adaptation of IEC 61508 to comply with needs specific to the application sector of electrical
and/or electronic (E/E) systems within road vehicles.
This adaptation applies to all activities during the safety lifecycle of safety-related systems comprised of
electrical, electronic and software components.
Safety is one of the key issues of future automobile development. New functionalities not only in areas such
as driver assistance, propulsion, in vehicle dynamics control and active and passive safety systems
increasingly touch the domain of system safety engineering. Development and integration of these
functionalities will strengthen the need for safe system development processes and the need to provide
evidence that all reasonable system safety objectives are satisfied.
With the trend of increasing technological complexity, software content and mechatronic implementation, there
are increasing risks from systematic failures and random hardware failures. ISO 26262 includes guidance to
avoid these risks by providing appropriate requirements and processes.
System safety is achieved through a number of safety measures, which are implemented in a variety of
technologies (e.g. mechanical, hydraulic, pneumatic, electrical, electronic, programmable electronic) and
applied at the various levels of the development process. Although ISO 26262 is concerned with functional
safety of E/E systems, it provides a framework within which safety-related systems based on other
technologies can be considered. ISO 26262:
a) provides an automotive safety lifecycle (management, development, production, operation, service,
decommissioning) and supports tailoring the necessary activities during these lifecycle phases;
b) provides an automotive-specific risk-based approach to determine integrity levels [Automotive Safety
Integrity Levels (ASIL)];
c) uses ASILs to specify applicable requirements of ISO 26262 so as to avoid unreasonable residual risk;
d) provides requirements for validation and confirmation measures to ensure a sufficient and acceptable
level of safety being achieved;
e) provides requirements for relations with suppliers.
Functional safety is influenced by the development process (including such activities as requirements
specification, design, implementation, integration, verification, validation and configuration), the production
and service processes and by the management processes.
Safety issues are intertwined with common function-oriented and quality-oriented development activities and
work products. ISO 26262 addresses the safety-related aspects of development activities and work products.
Figure 1 shows the overall structure of this edition of ISO 26262. ISO 26262 is based upon a V-model as a
reference process model for the different phases of product development. Within the figure:
 the shaded “V”s represent the interconnection between ISO 26262-3, ISO 26262-4, ISO 26262-5,
ISO 26262-6 and ISO 26262-7;
 the specific clauses are indicated in the following manner: “m-n”, where “m” represents the number of the
particular part and “n” indicates the number of the clause within that part.
EXAMPLE “2-6” represents Clause 6 of ISO 26262-2.
vi © ISO 2011 – All rights reserved

---------------------- Page: 6 ----------------------
ISO 26262-6:2011(E)

Figure 1 — Overview of ISO 26262

© ISO 2011 – All rights reserved vii

1. Vocabulary
2. Management of functional safety
2-6 Safety management during the concept phase 2-7 Safety management after the item´s release
2-5 Overall safety management
and the product development for production
4. Product development at the system level
3. Concept phase 7. Production and operation
4-5 Initiation of product
4-11 Release for production
3-5 Item definition 7-5 Production
development at the system level
4-10 Functional safety assessment
7-6 Operation, service
3-6 Initiation of the safety lifecycle
4-6 Specification of the technical
(maintenance and repair), and
safety requirements
decommissioning
4-9 Safety validation
3-7 Hazard analysis and risk
assessment
4-7 System design 4-8 Item integration and testing
3-8 Functional safety
concept
5. Product development at the 6. Product development at the
hardware level software level
5-5 Initiation of product 6-5 Initiation of product
development at the hardware level
development at the software level
5-6 Specification of hardware
safety requirements
5-7 Hardware design 6-7 Software architectural design
5-8 Evaluation of the hardware 6-8 Software unit design and
architectural metrics implementation
5-9 Evaluation of the safety goal
6-9 Software unit testing
violations due to random hardware
failures
6-10 Software integration and
5-10 Hardware integration and
testing
testing
6-11 Verification of software safety
requirements
8. Supporting processes
8-5 Interfaces within distributed developments 8-10 Documentation
8-6 Specification and management of safety requirements 8-11 Confidence in the use of software tools
8-7 Configuration management 8-12 Qualification of software components
8-8 Change management 8-13 Qualification of hardware components
8-9 Verification 8-14 Proven in use argument
9. ASIL-oriented and safety-oriented analyses
9-5 Requirements decomposition with respect to ASIL tailoring 9-7 Analysis of dependent failures
9-6 Criteria for coexistence of elements 9-8 Safety analyses
10. Guideline on ISO 26262

---------------------- Page: 7 ----------------------
INTERNATIONAL STANDARD ISO 26262-6:2011(E)

Road vehicles — Functional safety —
Part 6:
Product development at the software level
1 Scope
ISO 26262 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 passenger cars with a maximum gross
vehicle mass up to 3 500 kg. ISO 26262 does not address unique E/E systems in special purpose vehicles
such as vehicles designed for drivers with disabilities.
Systems and their components released for production, or systems and their components already under
development prior to the publication date of ISO 26262, are exempted from the scope. For further
development or alterations based on systems and their components released for production prior to the
publication of ISO 26262, only the modifications will be developed in accordance with ISO 26262.
ISO 26262 addresses possible hazards caused by malfunctioning behaviour of E/E safety-related 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 E/E safety-related systems.
ISO 26262 does not address the nominal performance of E/E systems, even if dedicated functional
performance standards exist for these systems (e.g. active and passive safety systems, brake systems,
Adaptive Cruise Control).
This part of ISO 26262 specifies the requirements for product development at the software level for
automotive applications, including the following:
 requirements for initiation of product development at the software level,
 specification of the software safety requirements,
 software architectural design,
 software unit design and implementation,
 software unit testing,
 software integration and testing, and
 verification of software safety requirements.
© ISO 2011 – All rights reserved 1

---------------------- Page: 8 ----------------------
ISO 26262-6:2011(E)
2 Normative references
The following referenced documents are indispensable for the application of this document. For dated
references, only the edition cited applies. For undated references, the latest edition of the referenced
document (including any amendments) applies.
ISO 26262-1:2011, Road vehicles — Functional safety — Part 1: Vocabulary
ISO 26262-2:2011, Road vehicles — Functional safety — Part 2: Management of functional safety
ISO 26262-4:2011, Road vehicles — Functional safety — Part 4: Product development at the system level
ISO 26262-5:2011, Road vehicles — Functional safety — Part 5: Product development at the hardware level
ISO 26262-8:2011, Road vehicles — Functional safety — Part 8: Supporting processes
ISO 26262-9:2011, Road vehicles — Functional safety — Part 9: Automotive Safety Integrity Level (ASIL)-
oriented and safety-oriented analyses
3 Terms, definitions and abbreviated terms
For the purposes of this document, the terms, definitions and abbreviated terms given in ISO 26262-1:2011
apply.
4 Requirements for compliance
4.1 General requirements
When claiming compliance with ISO 26262, each requirement shall be complied with, unless one of the
following applies:
a) tailoring of the safety activities in accordance with ISO 26262-2 has been planned and shows that the
requirement does not apply, or
b) a rationale is available that the non-compliance is acceptable and the rationale has been assessed in
accordance with ISO 26262-2.
Information marked as a “NOTE” or “EXAMPLE” is only for guidance in understanding, or for clarification of
the associated requirement, and shall not be interpreted as a requirement itself or as complete or exhaustive.
The results of safety activities are given as work products. “Prerequisites” are information which shall be
available as work products of a previous phase. Given that certain requirements of a clause are
ASIL-dependent or may be tailored, certain work products may not be needed as prerequisites.
“Further supporting information” is information that can be considered, but which in some cases is not required
by ISO 26262 as a work product of a previous phase and which may be made available by external sources
that are different from the persons or organizations responsible for the functional safety activities.
4.2 Interpretations of tables
Tables are normative or informative depending on their context. The different methods listed in a table
contribute to the level of confidence in achieving compliance with the corresponding requirement. Each
method in a table is either
a) a consecutive entry (marked by a sequence number in the leftmost column, e.g. 1, 2, 3), or
2 © ISO 2011 – All rights reserved

---------------------- Page: 9 ----------------------
ISO 26262-6:2011(E)
b) an alternative entry (marked by a number followed by a letter in the leftmost column, e.g. 2a, 2b, 2c).
For consecutive entries, all methods shall be applied as recommended in accordance with the ASIL. If
methods other than those listed are to be applied, a rationale shall be given that these fulfil the corresponding
requirement.
For alternative entries, an appropriate combination of methods shall be applied in accordance with the ASIL
indicated, independent of whether they are listed in the table or not. If methods are listed with different
degrees of recommendation for an ASIL, the methods with the higher recommendation should be preferred. A
rationale shall be given that the selected combination of methods complies with the corresponding
requirement.
NOTE A rationale based on the methods listed in the table is sufficient. However, this does not imply a bias for or
against methods not listed in the table.
For each method, the degree of recommendation to use the corresponding method depends on the ASIL and
is categorized as follows:
 “++” indicates that the method is highly recommended for the identified ASIL;
 “+” indicates that the method is recommended for the identified ASIL;
 “o” indicates that the method has no recommendation for or against its usage for the identified ASIL.
4.3 ASIL-dependent requirements and recommendations
The requirements or recommendations of each subclause shall be complied with for ASIL A, B, C and D, if not
stated otherwise. These requirements and recommendations refer to the ASIL of the safety goal. If ASIL
decomposition has been performed at an earlier stage of development, in accordance with ISO 26262-9:2011,
Clause 5, the ASIL resulting from the decomposition shall be complied with.
If an ASIL is given in parentheses in ISO 26262, the corresponding subclause shall be considered as a
recommendation rather than a requirement for this ASIL. This has no link with the parenthesis notation related
to ASIL decomposition.
5 Initiation of product development at the software level
5.1 Objectives
The objective of this sub-phase is to plan and initiate the functional safety activities for the sub-phases of the
software development.
5.2 General
The initiation of the software development is a planning activity, where software development sub-phases and
their supporting processes (see ISO 26262-8 and ISO 26262-9) are determined and planned according to the
extent and complexity of the item development. The software development sub-phases and supporting
processes are initiated by determining the appropriate methods in order to comply with the requirements and
their respective ASIL. The methods are supported by guidelines and tools, which are determined and planned
for each sub-phase and supporting process.
NOTE Tools used for software development can include tools other than software tools.
EXAMPLE Tools used for testing phases.
The planning of the software development includes the coordination with the product development at the
system level (see ISO 26262-4) and the hardware level (see ISO 26262-5).
© ISO 2011 – All rights reserved 3

---------------------- Page: 10 ----------------------
ISO 26262-6:2011(E)
5.3 Inputs to this clause
5.3.1 Prerequisites
The following information shall be available:
 project plan (refined) in accordance with ISO 26262-4:2011, 5.5.1;
 safety plan (refined) in accordance with ISO 26262-4:2011, 5.5.2;
 technical safety concept in accordance with ISO 26262-4:2011, 7.5.1;
 system design specification in accordance with ISO 26262-4:2011, 7.5.2; and
 item integration and testing plan (refined) in accordance with ISO 26262-4:2011, 8.5.1.
5.3.2 Further supporting information
The following information can be considered:
 qualified software tools available (see ISO 26262-8:2011, Clause 11);
 qualified software components available (see ISO 26262-8:2011, Clause 12);
 design and coding guidelines for modelling and programming languages (from external source);
 guidelines for the application of methods (from external source); and
 guidelines for the application of tools (from external source).
5.4 Requirements and recommendations
5.4.1 The activities and the determination of appropriate methods for the product development at the
software level shall be planned.
5.4.2 The tailoring of the lifecycle for product development at the software level shall be performed in
accordance with ISO 26262-2:2011, 6.4.5, and based on the reference phase model given in Figure 2.
5.4.3 If developing configurable software, Annex C shall be applied.
5.4.4 The software development process for the software of an item, including lifecycle phases, methods,
languages and tools, shall be consistent across all the sub-phases of the software lifecycle and be compatible
with the system and hardware development phases, such that the required data can be transformed correctly.
NOTE The sequencing of phases, tasks and activities, including iteration steps, for the software of an item is to
ensure the consistency of the corresponding work products with the product development at the hardware level (see
ISO 26262-5) and the product development at the system level (see ISO 26262-4).
4 © ISO 2011 – All rights reserved

---------------------- Page: 11 ----------------------
ISO 26262-6:2011(E)

NOTE Within the figure, the specific clauses of each part of ISO 26262 are indicated in the following manner: “m-n”,
where “m” represents the number of the part and “n” indicates the number of the clause, e.g. “4.7” represents Clause 7 of
ISO 26262-4.
Figure 2 — Reference phase model for the software development
5.4.5 For each sub-phase of software development, the selection of the following, including guidelines for
their application, shall be carried out:
a) methods; and
b) corresponding tools.
5.4.6 The criteria that shall be considered when selecting a suitable modelling or programming language
are:
a) an unambiguous definition;
EXAMPLE Syntax and semantics of the language.
b) the support for embedded real time software and runtime error handling; and
c) the support for modularity, abstraction and structured constructs.
Criteria that are not sufficiently addressed by the language itself shall be covered by the corresponding
guidelines, or by the development environment.
NOTE 1 The selected programming language (such as ADA, C, C++, Java, Assembler or a graphical modelling
language) supports the topics given in 5.4.7. Programming or modelling guidelines can be used to comply with these
topics.
NOTE 2 Assembly languages can be used for those parts of the software where the use of high-level programming
languages is not appropriate, such as low-level software with interfaces to the hardware, interrupt handlers, or time-critical
algorithms.
© ISO 2011 – All rights reserved 5

---------------------- Page: 12 ----------------------
ISO 26262-6:2011(E)
5.4.7 To support the correctness of the design and implementation, the design and coding guidelines for the
modelling, or programming languages, shall address the topics listed in Table 1.
NOTE 1 Coding guidelines are usually different for different programming languages.
NOTE 2 Coding guidelines can be different for model-based development.
NOTE 3 Existing coding guidelines can be modified for a specific item development.
[3] [4]
EXAMPLE MISRA C and MISRA AC AGC are coding guidelines for the programming language C.
Table 1 — Topics
...