GB/T 34590.6-2022 PDF English
US$695.00 · In stock · Download in 9 secondsGB/T 34590.6-2022: Road vehicles - Functional safety - Part 6: Product development at the software level Delivery: 9 seconds. True-PDF full-copy in English & invoice will be downloaded + auto-delivered via email. See step-by-step procedureStatus: Valid GB/T 34590.6: Evolution and historical versions
| Standard ID | Contents [version] | USD | STEP2 | [PDF] delivery | Name of Chinese Standard | Status |
| GB/T 34590.6-2022 | English | 695 |
Add to Cart
|
0-9 seconds. Auto-delivery
|
Road vehicles - Functional safety - Part 6: Product development at the software level
| Valid |
| GB/T 34590.6-2017 | English | 345 |
Add to Cart
|
0-9 seconds. Auto-delivery
|
Road vehicles -- Functional safety -- Part 6: Product development at the software level
| Obsolete |
Excerpted PDFs (Download full copy in 9 seconds upon purchase)PDF Preview: GB/T 34590.6-2022
GB/T 34590.6-2022: Road vehicles - Functional safety - Part 6: Product development at the software level
---This is an excerpt. Full copy of true-PDF in English version (including equations, symbols, images, flow-chart, tables, and figures etc.), auto-downloaded/delivered in 9 seconds, can be purchased online: https://www.ChineseStandard.net/PDF.aspx/GBT34590.6-2022
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 43.040
CCS T 35
Replacing GB/T 34590.6-2017
Road Vehicles - Functional Safety - Part 6.Product
development at the software level
(ISO 26262-6.2018, MOD)
Issued on. DECEMBER 30, 2022
Implemented on. JULY 1, 2023
Issued by. State Administration for Market Regulation;
Standardization Administration of the People’s Republic of China.
Table of Contents
Foreword... 4
Introduction... 9
1 Scope... 13
2 Normative references... 14
3 Terms and definitions... 15
4 Requirements for compliance... 15
4.1 Purpose... 15
4.2 General requirements... 15
4.3 Interpretations of tables... 16
4.4 ASIL-dependent requirements and recommendations... 17
4.5 Adaptation for motorcycles... 17
4.6 Adaptation for cargo trucks, buses, special vehicles, trailers... 17
5 General topics for the product development at the software level... 17
5.1 Objectives... 17
5.2 General... 18
5.3 Inputs to this clause... 19
5.4 Requirements and recommendations... 19
5.5 Work products... 21
6 Specification of software safety requirements... 21
6.1 Objectives... 21
6.2 General... 22
6.3 Inputs to this clause... 22
6.4 Requirements and recommendations... 22
6.5 Work products... 24
7 Software architectural design... 25
7.1 Objectives... 25
7.2 General... 25
7.3 Inputs to this clause... 25
7.4 Requirements and recommendations... 26
7.5 Work products... 33
8 Software unit design and implementation... 33
8.1 Objectives... 33
8.2 General... 33
8.3 Inputs to this clause... 34
8.4 Requirements and recommendations... 34
8.5 Work products... 36
9 Software unit verification... 37
9.1 Objectives... 37
9.2 General... 37
9.3 Inputs to this clause... 37
9.4 Requirements and recommendations... 38
9.5 Work products... 41
10 Software integration and verification... 41
10.1 Objectives... 41
10.2 General... 42
10.3 Inputs to this clause... 42
10.4 Requirements and recommendations... 43
10.5 Work products... 46
11 Testing of the embedded software... 46
11.1 Objective... 46
11.2 General... 46
11.3 Inputs to this clause... 47
11.4 Requirements and recommendations... 47
11.5 Work products... 49
Annex A (informative) Overview of and workflow of management of product... 50
development at the software level... 50
Annex B (informative) Model-based development approaches... 53
Annex C (normative) Software configuration... 59
Annex D (informative) Freedom from interference between software elements... 65
Annex E (informative) Application of safety analyses and analyses of dependent failures
at the software architectural level... 68
Bibliography... 78
Foreword
This document was drafted in accordance with the rules provided in GB/T 1.1-2020 Directives
for Standardization - Part 1.Rules for the Structure and Drafting of Standardizing Documents.
This document is Part 5 of GB/T 34590 Road Vehicles - Functional Safety. GB/T 34590 has
issued the following parts.
-- 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, Operation, Service and Decommissioning;
-- Part 8.Supporting Processes;
-- Part 9.Automotive Safety Integrity Level (ASIL)-oriented and Safety-oriented Analyses;
-- Part 10.Guideline;
-- Part 11.Guidelines on Applications to Semiconductors;
-- Part 12.Adaptation for Motorcycles.
This document replaces GB/T 34590.6-2017 "Road vehicles - Functional safety - Part 6.
Product development at the software level". Compared with GB/T 34590.6-2017, the main
technical changes in this document are as follows.
- Change the scope of application of the standard from "mass-produced passenger cars" to
"mass-produced road vehicles other than mopeds" (see Chapter 1 of this Edition, Chapter
1 of Edition 2017);
- Add the suitability requirements for motorcycles (see 4.5 of this Edition);
- Add the applicability requirements for cargo trucks, buses, special vehicles and trailers (see
4.6 of this Edition);
- Change the description of the software development process and development environment
requirements (see 5.4.1 of this Edition, 5.4.1 of Edition 2017);
- Change the relevant requirements for design language, modeling language or programming
language (see 5.4.2 and 5.4.3 of this Edition, 5.4.6 and 5.4.7 of Edition 2017);
- Change the work product (see 5.5 of this Edition, 5.5 of Edition 2017);
- Change the description of software safety requirements (see 6.4 of this Edition, 6.4 of
Edition 2017);
- Change the work product (see 6.5 of this Edition, 6.5 of Edition 2017);
- Change the description requirements for software architecture design, including software
architecture design notation requirements (see 7.4.1 and 7.4.2 of this Edition, 7.4.1 and
7.4.2 of Edition 2017);
- Change the requirements for software architecture characteristics, including software
architecture principles (see 7.4.3 of this Edition, 7.4.3 of Edition 2017);
- Change the description of software static and dynamic design requirements (see 7.4.5 of
this Edition, 7.4.5 of Edition 2017);
- Delete the software component classification and development requirements (see 7.4.6 and
7.4.7 of Edition 2017);
- Change the description of software safety analysis requirements (see 7.4.6 and 7.4.7 of this
Edition, 7.4.8 and 7.4.9 of Edition 2017);
- Change the description of the software architecture design verification method (see 7.4.14
of this Edition, 7.4.18 of Edition 2017);
- Change the work product (see 7.5 of this Edition, 7.5 of Edition 2017);
- Add the requirements for software unit design characteristic (see 8.4.3 of this Edition);
- Change the requirements for software unit design notation (see 8.4.3 of this Edition, 8.4.2
of Edition 2017);
- Change the design principles for software unit design and implementation (see 8.4.4 and
8.4.5 of this Edition, 8.4.3 and 8.4.4 of Edition 2017);
- Delete the requirements and verification methods for software unit design and
implementation verification (see 8.4.5 of Edition 2017);
- Change the work product (see 8.5 of this Edition, 8.5 of Edition 2017);
- Delete the requirements for software unit test plan (see 2017 edition 9.4.2);
- Change the software unit verification requirements, including software unit verification
methods (see 9.4.4 of this Edition, 9.4.5 of Edition 2017);
- Change the work product (see 9.5 of this Edition, 9.5 of Edition 2017);
- Delete the requirements for software integration test plan (see 10.4.2 of Edition 2017);
- Change the requirements for software integration verification, including software
integration verification methods (see 10.4.2 of this Edition, 10.4.3 of Edition 2017);
- Change the description of software integration verification coverage requirements (see
10.4.4 and 10.4.5 of this Edition, 10.4.5 and 10.4.6 of Edition 2017);
- Change the work product (see 10.5 of this Edition, 10.5 of Edition 2017);
- Delete the requirements for software security requirements verification plan (see 11.4.1 of
Edition 2017);
- Change the test environment requirements for software testing (see 11.4.1 of this Edition,
11.4.2 and 11.4.3 of Edition 2017);
- Add the requirements for embedded software testing methods (see 11.4.2 of this Edition);
- Add the method requirements for deriving embedded software test cases (see 11.4.3 of this
Edition);
- Change the work product (see 11.5 of this Edition, 11.5 of Edition 2017);
- Add introduction, general applicability of model-based development methods and potential
impact on software life cycle (see B.2.1, B.2.2, B.2.3 of this Edition);
- Add special considerations for sample software development use cases (see B.3 of this
Edition);
- Change the description of the requirements for software configuration (see Annex C of this
Edition, Annex C of Edition 2017);
- Change the description of requirements to avoid interference between software elements
(see Annex D of this Edition, Annex D of Edition 2017).
The revision of this document adopts ISO 26262-6.2018 "Road vehicles - Functional safety -
Part 6.Product development at the software level".
The technical differences between this document and ISO 26262-6.2018 and their reasons are
as follows.
- Change the description of T&B vehicles from "trucks, buses, trailers and semi-trailers" to
"cargo trucks, buses, special vehicles, trailers" (see 4.6 of this Edition, 4.6 of ISO 26262-
6.2018), to be consistent with the vehicle types specified in GB/T 3730.1-2022 "Terms
and definitions of motor vehicles, trailers and combination vehicle -- Part 1.Types".
Attention is drawn to the possibility that some of the elements of this document may be the
subject of patent rights. The issuing authority shall not be held responsible for identifying any
or all such patent rights.
This document was proposed by the Ministry of Industry and Information Technology of the
People's Republic of China.
This document shall be under the jurisdiction of National Technical Committee 114 on Auto of
Standardization Administration of China (SAC/TC 114).
The drafting organizations of this document. China Automotive Technology and Research
Center Co., Ltd., United Automotive Electronics Co., Ltd., Neusoft Reach Automotive
Technology (Shenyang) Co., Ltd., Weilai Automobile (Anhui) Co., Ltd., Huawei Technologies
Co., Ltd., Neusoft Group (Dalian) Co., Ltd., Valeo Automotive Internal Control (Shenzhen) Co.,
Ltd., Bosch Automotive Parts (Suzhou) Co., Ltd., Shanghai Hella Electronics Co., Ltd., Hitachi
Anstemo Automotive Electronics (Shanghai) Co., Ltd., Xingkedi Technology (Taizhou) Co.,
Ltd., Beijing Hua Tedaidai Electric Vehicle Technology Co., Ltd., Suzhou Inovance United
Power System Co., Ltd., Ningde Times New Energy Technology Co., Ltd., SAIC Maxus
Automobile Co., Ltd., Huating (Hefei) Power Technology Co., Ltd., Daimler Greater China
Investment Co., Ltd. Company, Beijing Baowo Automobile Co., Ltd., Hefei Juyi Power System
Co., Ltd., Beijing Baidu Zhixing Technology Co., Ltd., Schaeffler (China) Co., Ltd., BYD Auto
Industry Co., Ltd., SAIC Volkswagen Co., Ltd., Yutong Bus Co., Ltd. Company, Beijing New
Energy Automobile Co., Ltd., Weichai Power Co., Ltd., Nexteer Automotive Systems (Suzhou)
Co., Ltd., Midea Group (Shanghai) Co., Ltd., Beijing Automobile Co., Ltd., Shanghai Weilai
Automobile Co., Ltd., Ai Chi Automobile (Shanghai) Co., Ltd., Zhixing Automotive
Technology (Suzhou) Co., Ltd., Shanghai Jinmai Electronic Technology Co., Ltd., CRRC
Times Electric Vehicle Co., Ltd., ZF Automotive Technology (Shanghai) Co., Ltd., SAIC Motor
Corporation Limited Company Technology Center, Ligao (Shandong) New Energy Technology
Co., Ltd., Honeycomb Energy Technology Co., Ltd., Beijing Horizon Robot Technology
Research and Development Co., Ltd., Youmuyu Information Technology (Shanghai) Co., Ltd.,
China FAW Group Co., Ltd., Great Wall Motors Co., Ltd., Pan Asia Automotive Technology
Center Co., Ltd., Dongfeng Motor Co., Ltd. Dongfeng Nissan Passenger Vehicle Company,
Huizhou Yineng Electronics Co., Ltd., Vitesco Technology Investment (China) Co., Ltd.,
Beijing Jingwei Hengrun Technology Co., Ltd., Geely Automobile Research Institute (Ningbo)
Co., Ltd.
The main drafters of this document. Li Bo, Wang Wenliang, Guo Xiaodong, Ouyang Chaohui,
Fu Yue, Chen Wei, Wei Fang, Gao Jianyong, Liu Xiangchao, Qu Yuanning, Yu Jianye, Xu
Huizhong, Qian Qiuhua, Zhuang Ping, Liu Chang, Han Biao, Shi Ting, Luo Huan, Lu Ming,
Zhao Tianli, Zhang Ci, Huang Jin, Xue Jianbo, Zhang Li, Zhang Lemin, Chen Xin, He
Zhongwei, Wang Jinping, Shao Haihe, Wang Shuangquan, Guo Feifei, Shen Xiaoyong, Zhang
Chan, Zhang Aiqin, Song Weijin, Zhou Dongdong, Li Yong, Li Xinran, Li Hongbo, Bao Wei,
Wang Zhipeng, Yang Hu, Wang Yiqun, Li Haixia, Yan Gang, Shang Shiliang, Wu Yang, Wang
Bin, Fan Yaoguo, Chen Xiaohu, Chen Wei, Li Gang.
Versions of standard substituted by this document are.
- GB/T 34590.6-2017 that was issued in 2017 of the first time.
- This is the first revision.
1 Scope
This document specifies the requirements for product development at the software level for
automotive applications, including the following.
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.
3 Terms and definitions
For the purposes of this document, the terms and definitions defined in GB/T 34590.1-2022
apply.
4 Requirements for compliance
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.
5 General topics for the product development at the software level
The reference phase model for the development of software is given in Figure 2.Details
concerning the treatment of configurable software are provided in Annex C.
6 Specification of software safety requirements
The hardware-software interface specification initiated in GB/T 34590.4-2022, Clause 6,
shall be refined sufficiently to allow for the correct control and usage of the hardware by the
software, and shall describe each safety‑related dependency between hardware and software.
7 Software architectural design
The software architectural design represents the software architectural elements and their
interactions in a hierarchical structure. Static aspects, such as interfaces between the software
components, as well as dynamic aspects, such as process sequences and timing behaviour, are
described.
8 Software unit design and implementation
Based on the software architectural design, the detailed design of the software units is
developed. The detailed design can be represented in the form of a model.
9 Software unit verification
The software unit design and the implemented software units are verified by using an
appropriate combination of verification measures such as reviews, analyses and testing.
In order to verify a single software unit design, both software safety requirements and all non-
safety related requirements are considered. Hence in this sub-phase safety-related and non-
safety-related requirements are handled within one development process.
......
Source: Above contents are excerpted from the full-copy PDF -- translated/reviewed by: www.ChineseStandard.net / Wayne Zheng et al.
Tips & Frequently Asked QuestionsQuestion 1: How long will the true-PDF of English version of GB/T 34590.6-2022 be delivered?Answer: The full copy PDF of English version of GB/T 34590.6-2022 can be downloaded in 9 seconds, and it will also be emailed to you in 9 seconds (double mechanisms to ensure the delivery reliably), with PDF-invoice. Question 2: Can I share the purchased PDF of GB/T 34590.6-2022_English with my colleagues?Answer: Yes. The purchased PDF of GB/T 34590.6-2022_English will be deemed to be sold to your employer/organization who actually paid for it, including your colleagues and your employer's intranet. Question 3: Does the price include tax/VAT?Answer: Yes. Our tax invoice, downloaded/delivered in 9 seconds, includes all tax/VAT and complies with 100+ countries' tax regulations (tax exempted in 100+ countries) -- See Avoidance of Double Taxation Agreements (DTAs): List of DTAs signed between Singapore and 100+ countriesQuestion 4: Do you accept my currency other than USD?Answer: Yes. www.ChineseStandard.us -- GB/T 34590.6-2022 -- Click this link and select your country/currency to pay, the exact amount in your currency will be printed on the invoice. Full PDF will also be downloaded/emailed in 9 seconds. Question 5: Should I purchase the latest version GB/T 34590.6-2022?Answer: Yes. Unless special scenarios such as technical constraints or academic study, you should always prioritize to purchase the latest version GB/T 34590.6-2022 even if the enforcement date is in future. Complying with the latest version means that, by default, it also complies with all the earlier versions, technically. How to buy and download a true PDF of English version of GB/T 34590.6-2022?A step-by-step guide to download PDF of GB/T 34590.6-2022_EnglishStep 1: Visit website https://www.ChineseStandard.net (Pay in USD), or https://www.ChineseStandard.us (Pay in any currencies such as Euro, KRW, JPY, AUD).
Step 2: Search keyword "GB/T 34590.6-2022".
Step 3: Click "Add to Cart". If multiple PDFs are required, repeat steps 2 and 3 to add up to 12 PDFs to cart.
Step 4: Select payment option (Via payment agents Stripe or PayPal).
Step 5: Customize Tax Invoice -- Fill up your email etc.
Step 6: Click "Checkout".
Step 7: Make payment by credit card, PayPal, Google Pay etc. After the payment is completed and in 9 seconds, you will receive 2 emails attached with the purchased PDFs and PDF-invoice, respectively.
Step 8: Optional -- Go to download PDF.
Step 9: Optional -- Click Open/Download PDF to download PDFs and invoice.
See screenshots for above steps: Steps 1~3 Steps 4~6 Step 7 Step 8 Step 9
|