Codeofchina.com is in charge of this English translation. In case of any doubt about the English translation, the Chinese original shall be considered authoritative.
GB/T 34590 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.
This part is Part 6 of GB/T 34590.
This part is developed in accordance with the rules given in GB/T 1.1-2009.
This part has been redrafted and modified in relation to ISO 26262-6:2011 Road Vehicles - Functional Safety - Part 6: Product Development at the Software Level.
There are technical deviations between this part and ISO 26262-6:2011. The technical deviations, together with their justifications, are as follows:
——the application scope of this part is modified from "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 500kg" to "This standard 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";
——in order to adapt to the technical conditions in China, adjustment on technical deviations has been made in "Normative References" of this part, which is mainly reflected in Chapter 2 "Normative References" and detailed as follows:
ISO 26262-1:2011 is replaced with GB/T 34590.1-2017 which is modified in relation to international standard;
ISO 26262-2:2011 is replaced with GB/T 34590.2-2017 which is modified in relation to international standard;
ISO 26262-4:2011 is replaced with GB/T 34590.4-2017 which is modified in relation to international standard;
ISO 26262-5:2011 quoted in ISO 26262-6:2011 is replaced with GB/T 34590.5-2017 which is modified in relation to international standard;
ISO 26262-8:2011 is replaced with GB/T 34590.8-2017 which is modified in relation to international standard;
ISO 26262-9:2011 is replaced with GB/T 34590.9-2017 which is modified in relation to international standard.
The following editorial changes present in this part:
——the introduction and its expression as well as Figure 1 of international standard are modified.
This standard was proposed by and is under the jurisdiction of National Technical Committee on Automobiles of Standardization Administration of China (SAC/TC 114).
Introduction
ISO 26262 is prepared based on IEC 61508 to comply with needs specific to the application sector of electrical and/or electronic (E/E) systems within road vehicles.
GB/T 34590 is modified in relation to ISO 26262, it is applicable 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 safety-related 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. GB/T 34590 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 GB/T 34590 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. GB/T 34590:
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 Automotive Safety Integrity Levels (ASIL);
c) uses ASILs to specify applicable requirements of GB/T 34590 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 as well as the management processes.
Safety issues are intertwined with common function-oriented and quality-oriented development activities and work products. GB/T 34590 addresses the safety-related aspects of development activities and work products.
Figure 1 shows the overall structure of this edition of GB/T 34590. GB/T 34590 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 GB/T 34590.3-2017, GB/T 34590.4-2017, GB/T 34590.5-2017, GB/T 34590.6-2017 and GB/T 34590.7-2017;
——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 chapter within that part.
Example: "2-6" represents Chapter 6 of GB/T 34590.2-2017.
Figure 1 Overview of GB/T 34590-2017
Road Vehicles - Functional Safety - Part 6: Product Development at the Software Level
1 Scope
This part of GB/T 34590 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.
This standard 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.
This standard 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 this standard, are exempted from the scope. For further development or alterations based on systems and their components released for production prior to the publication of this standard, only the modifications will be developed in accordance with this standard.
This standard addresses possible hazards caused by malfunctioning behavior 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 behavior of E/E safety-related systems.
This standard 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 system).
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 (including any amendment) applies to this document.
GB/T 34590.1-2017 Road Vehicles - Functional Safety - Part 1: Vocabulary (ISO 26262-1:2011, MOD)
GB/T 34590.2-2017 Road Vehicles - Functional Safety - Part 2: Management of Functional Safety (ISO 26262-2:2011, MOD)
GB/T 34590.4-2017 Road Vehicles - Functional Safety - Part 4:Product Development at the System Level (ISO 26262-4:2011, MOD)
GB/T 34590.5-2017 Road Vehicles - Functional Safety-Part 5:Product Development at the Hardware Level (ISO 26262-5:2011, MOD)
GB/T 34590.8-2017 Road Vehicles - Functional Safety - Part 8: Supporting Processes (ISO 26262-8:2011, MOD)
GB/T 34590.9-2017 Road Vehicles - Functional Safety - Part 9: Automotive Safety Integrity Level(ASIL)-oriented and Safety-oriented Analyses (ISO 26262-9:2011, MOD)
3 Terms, Definitions and Abbreviations
For the purposes of this document, the terms, definitions and abbreviated terms given in GB/T 34590.1-2017 apply.
4 Requirements
4.1 General Requirements
When claiming compliance with GB/T 34590-2017, each requirement shall be complied with, unless one of the following applies:
a) tailoring of the safety activities in accordance with GB/T 34590.2-2017 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 GB/T 34590.2-2017.
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 GB/T 34590-2017 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
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 fulfill 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 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 GB/T 34590.9-2017, Chapter 5, the ASIL resulting from the decomposition shall be complied with.
If an ASIL is given in parentheses in GB/T 34590-2017, 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 subclause is to plan and initiate the functional safety activities for the subphases of the software development.
5.2 General
The initiation of the software development is a planning activity, where software development subphases and their supporting processes (see GB/T 34590.8-2017 and GB/T 34590.9-2017) are determined and planned according to the extent and complexity of the item development. The software development subphases 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 subphase and supporting process.
Note 1: 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 GB/T 34590.4-2017) and the hardware level (see GB/T 34590.5-2017).
Note 2: Table A.1 in Annex A provides an overview on objectives, prerequisites and work products of the particular phases of production and operation.
Foreword i Introduction iii 1 Scope 2 Normative References 3 Terms, Definitions and Abbreviations 4 Requirements 4.1 General Requirements 4.2 Interpretations of Tables 4.3 ASIL-dependent Requirements and Recommendations 5 Initiation of Product Development at the Software Level 5.1 Objectives 5.2 General 5.3 Inputs to this Chapter 5.4 Requirements and Recommendations 5.5 Work Products 6 Specification of Software Safety Requirements 6.1 Objectives 6.2 General 6.3 Inputs to this Chapter 6.4 Requirements and Recommendations 6.5 Work Products 7 Software Architectural Design 7.1 Objectives 7.2 General 7.3 Inputs to this Chapter 7.4 Requirements and Recommendations 7.5 Work Products 8 Software Unit Design and Implementation 8.1 Objectives 8.2 General 8.3 Inputs to this Chapter 8.4 Requirements and Recommendations 8.5 Work Products 9 Software Unit Testing 9.1 Objectives 9.2 General 9.3 Inputs to this Chapter 9.4 Requirements and Recommendations 9.5 Work Products 10 Software Integration and Testing 10.1 Objectives 10.2 General 10.3 Inputs to this Chapter 10.4 Requirements and Recommendations 10.5 Work Products 11 Verification of Software Safety Requirements 11.1 Objectives 11.2 General 11.3 Inputs to this Chapter 11.4 Requirements and Recommendations 11.5 Work products Annex A (Informative) Overview of and Workflow of Management of Product Development at the Software Level Annex B (Informative) Model-based Development Annex C (Normative) Software Configuration Annex D (Informative) Freedom from Interference between Software Elements Bibliography
道路车辆功能安全 第6部分:产品开发：软件层面 1范围 GB/T 34590的本部分规定了车辆在软件层面产品开发的要求，包括： ——启动软件层面产品开发； ——软件安全要求的定义； ——软件架构设计； ——软件单元设计及实现； ——软件单元测试； ——软件集成和测试;及 ——软件安全要求的验证。 本标准适用于安装在量产乘用车上的包含一个或多个电子电气系统的与安全相关的系统。 本标准不适用于特殊用途车辆上特定的电子电气系统，例如，为残疾驾驶者设计的车辆。 本标准不适用于已经完成生产发布的系统及其组件或在本标准发布日期前开发的系统及其组件。对于在本标准发布前完成生产发布的系统及其组件进行进一步的开发或变更时，仅修改的部分需要按照本标准开发。 本标准针对由电子电气安全相关系统的故障行为而引起的可能的危害，包括这些系统相互作用而引起的可能的危害。本标准不针对与触电、火灾、烟雾、热、辐射、毒性、易燃性、反应性、腐蚀性、能量释放等相关的危害和类似的危害，除非危害是直接由电子电气安全相关系统的故障行为而引起的。 本标准不针对电子电气系统的标称性能，即使这些系统(例如，主动和被动安全系统、制动系统、自适应巡航系统)有专用的功能性能标准。 2规范性引用文件 下列文件对于本文件的应用是必不可少的。凡是注日期的引用文件，仅注日期的版本适用于本文件。凡是不注日期的引用文件，其最新版本(包括所有的修改单)适用于本文件。 GB/T 34590.1-2017 Road vehicles-Functional safety- Part 1:Vocabulary (ISO 26262-1:2011, MOD) GB/T 34590.2-2017 Road vehicles-Functional safety- Part 2:Management of functional safety (ISO 26262-2:2011, MOD) GB/T 34590.4-2017 Road vehicles-Functional safety- Part 4:Product development at the system level (ISO 26262-4:2011, MOD) GB/T 34590.5-2017 Road vehicles-Functional safety-Part 5:Product development at the hardware level (ISO 26262-5:2011, MOD) GB/T 34590.8-2017 Road vehicles-Functional safety- Part 8:Supporting processes (ISO 26262-8:2011, MOD) GB/T 34590.9-2017 Road vehicles-Functional safety-Part 9:Automotive Safety Integrity Level(ASIL)-oriented and safety-oriented analyses (ISO 26262-9:2011, MOD)
图2软件开发参考阶段模型 5.4.5应为软件开发的每个子阶段进行如下选择，包括其应用的指南： a) 方法；及 b) 相应的工具。 5.4.6当选择一种合适的建模语言或编程语言时，应考虑准则： a) 无歧义的定义；示例：语言的语法和语义。 b) 为嵌人式实时软件和运行时错误处理提供的支持;及 c) 为模块化、抽象化和结构化的构建提供的支持。 对于通过语言本身不能充分说明的准则应由相应的指南或开发环境来覆盖。 注1：所选择的编程语言(如ADA、C、C+ +Java、汇编或图形化的建模语言）支持5.4.7中给出的通则。可应用编程指南或建模指南以满足这些通则。 注2：汇编语言可用于那些不适合使用高级语言的软件部分，如与硬件接口的底层软件、中断处理程序、或对时间敏感的算法。 5.4.7为了支持设计和实现的正确性，建模语言或编程语言的设计和编码指南应按照表1所列出的通则。 注1:对不同的编程语言，编码指南通常是不同的。 注2:对基于模型的开发，编码指南可以是不同的。附录B描述了基于模型的开发的概念。 注3:对特定相关项的开发，可对现有编码指南进行修改。 示例：MISRA C[3]和MISRA AC AGC[4]是C语言的编码指南。
