1、raising standards worldwideNO COPYING WITHOUT BSI PERMISSION EXCEPT AS PERMITTED BY COPYRIGHT LAWBSI Standards PublicationBS ISO 26262-6:2011Road vehicles FunctionalsafetyPart 6: Product development at thesoftware levelBS ISO 26262-6:2011 BRITISH STANDARDNational forewordThis British Standard is the
2、 UK implementation of ISO 26262-6:2011.The UK participation in its preparation was entrusted to TechnicalCommittee AUE/16, Electrical and electronic equipment.A list of organizations represented on this committee can beobtained on request to its secretary.This publication does not purport to include
3、 all the necessaryprovisions of a contract. Users are responsible for its correctapplication. BSI 2011ISBN 978 0 580 62308 0ICS 43.040.10Compliance with a British Standard cannot confer immunity fromlegal obligations.This British Standard was published under the authority of theStandards Policy and
4、Strategy Committee on 30 November 2011.Amendments issued since publicationDate Text affectedBS ISO 26262-6:2011Reference numberISO 26262-6:2011(E)ISO 2011INTERNATIONAL STANDARD ISO26262-6First edition2011-11-15Road vehicles Functional safety Part 6: Product development at the software level Vhicules
5、 routiers Scurit fonctionnelle Partie 6: Dveloppement du produit au niveau du logiciel BS ISO 26262-6:2011ISO 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,
6、electronic or mechanical, including photocopying and microfilm, without permission in writing from either ISO at the address below or ISOs 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 copyright
7、iso.org Web www.iso.org Published in Switzerland ii ISO 2011 All rights reservedBS ISO 26262-6:2011ISO 26262-6:2011(E) ISO 2011 All rights reserved iiiContents Page Foreword . v Introduction vi 1 Scope 1 2 Normative references 2 3 Terms, definitions and abbreviated terms 2 4 Requirements for complia
8、nce 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 produc
9、ts . 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 re
10、commendations . 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 c
11、lause 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 . 2
12、5 BS ISO 26262-6:2011ISO 26262-6:2011(E) iv ISO 2011 All rights reserved11.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 softwar
13、e 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 BS ISO 26262-6:2011ISO 26262-6:2011(E) ISO 2011 All rights reserved vForeword ISO (the Internation
14、al 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 e
15、stablished 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 standard
16、ization. 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 vo
17、ting. 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 su
18、ch 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
19、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
20、 safety-oriented analyses Part 10: Guideline on ISO 26262 BS ISO 26262-6:2011ISO 26262-6:2011(E) vi ISO 2011 All rights reservedIntroduction 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 vehi
21、cles. 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, propul
22、sion, 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
23、 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
24、 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. Althou
25、gh 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)
26、 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 re
27、sidual 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 require
28、ments 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
29、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”
30、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 “
31、2-6” represents Clause 6 of ISO 26262-2. BS ISO 26262-6:2011ISO 26262-6:2011(E) ISO 2011 All rights reserved vii3. Concept phase2. Management of functional safety2-5 Overall safetymanagement2-6Safetymanagement during the concept phase and the product development 7. Production and operation6-5Initiat
32、ion of product development at the software level6-7Software architectural design6-8Software unit design and implementation6-9Software unit testing6-10Software integration and testing 6-11 Verification of software safetyrequirements5-5Initiation of product development at the hardware level5-6Specific
33、ation of hardware safetyrequirements5-7Hardware design5-8Evaluation of the hardware architecturalmetrics5-10Hardware integration and testing2-7Safetymanagement after the items release for production3-6 Initiation of the safetylifecycle1. Vocabulary3-5 Item definition3-7 Hazard analysis andrisk asses
34、sment3-8 Functional safetyconcept7-6 Operation, service (maintenance and repair), and decommissioning7-5 Production8. Supporting processes8-5Interfaces within distributed developments8-6Specification and managementof safetyrequirements8-8Change management8-9Verification8-7Configuration management4.
35、Product development at the system level4-5Initiation of product development at the system level4-7System design 4-8Item integration and testing4-9Safetyvalidation4-10Functional safetyassessment4-11Release for production6. Product development at thesoftware level5. Product development at thehardware
36、level5-9Evaluation of the safetygoal violations due to random hardware failures4-6Specification of the technical safetyrequirements9. ASIL-oriented and safety-oriented analyses9-5Requirements decomposition with respect to ASIL tailoring9-6Criteria for coexistence of elements8-10Documentation8-11Conf
37、idence in the use of software tools8-13Qualificationof hardware components8-14Proven in use argument8-12Qualificationof software components9-7Analysis of dependent failures9-8Safetyanalyses10. Guideline on ISO26262Figure 1 Overview of ISO 26262 BS ISO 26262-6:2011BS ISO 26262-6:2011INTERNATIONAL STA
38、NDARD ISO 26262-6:2011(E) ISO 2011 All rights reserved 1Road 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 i
39、n 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 component
40、s 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
41、 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 en
42、ergy 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 sys
43、tems, 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 require
44、ments, software architectural design, software unit design and implementation, software unit testing, software integration and testing, and verification of software safety requirements. BS ISO 26262-6:2011ISO 26262-6:2011(E) 2 ISO 2011 All rights reserved2 Normative references The following referenc
45、ed 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 IS
46、O 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:20
47、11, 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, definitio
48、ns 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
49、 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 p
