HOME   Cart(1)   Quotation   About-Us Tax PDFs Standard-List
Powered by Google-Search & Google-Books www.ChineseStandard.net Database: 189759 (18 Feb 2024)

GB/T 34590.8-2022 (GB/T34590.8-2022)

Standard IDContents [version]USDSTEP2[PDF] delivered inName of Chinese StandardStatus
GB/T 34590.8-2022English755 Add to Cart 0-9 seconds. Auto-delivery. Road vehicles -- Functional safety -- Part 8: Supporting processes Valid


GB/T 34590.8-2022: PDF in English (GBT 34590.8-2022)

GB/T 34590.8-2022
GB
NATIONAL STANDARD OF THE
PEOPLE’S REPUBLIC OF CHINA
ICS 43.040
CCS T 35
Replacing GB/T 34590.8-2017
Road vehicles - Functional safety - Part 8: Supporting
processes
(ISO 26262-8: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 ... 5
Introduction ... 10
1 Scope ... 14
2 Normative references ... 15
3 Terms and definitions ... 16
4 Requirements ... 17
4.1 Purpose... 17
4.2 General requirements ... 17
4.3 Interpretations of tables ... 17
4.4 ASIL-dependent requirements and recommendations ... 18
4.5 Adaptation for motorcycles ... 18
4.6 Adaptation for goods vehicles, buses, special automobiles, trailers ... 19
5 Interfaces within distributed developments ... 19
5.1 Objectives ... 19
5.2 General ... 19
5.3 Inputs to this clause ... 20
5.4 Requirements and recommendations ... 20
5.5 Work products ... 25
6 Specification and management of safety requirements ... 25
6.1 Objectives ... 25
6.2 General ... 26
6.3 Inputs to this clause ... 27
6.4 Requirements and recommendations ... 27
6.5 Work products ... 32
7 Configuration management ... 32
7.1 Objectives ... 32
7.2 General ... 32
7.3 Inputs to this clause ... 33
7.4 Requirements and recommendations ... 33
7.5 Work products ... 34
8 Change management ... 34
8.1 Objectives ... 34
8.2 General ... 34
8.3 Inputs to this clause ... 34
8.4 Requirements and recommendations ... 35
8.5 Work products ... 37
9 Verification ... 37
9.1 Objectives ... 37
9.2 General ... 37
9.3 Inputs to this clause ... 38
9.4 Requirements and recommendations ... 39
9.5 Work products ... 41
10 Documentation management ... 42
10.1 Objectives ... 42
10.2 General ... 42
10.3 Inputs to this clause ... 42
10.4 Requirements and recommendations ... 43
10.5 Work products ... 44
11 Confidence in the use of software tools ... 44
11.1 Objectives ... 44
11.2 General ... 44
11.3 Inputs to this clause ... 47
11.4 Requirements and recommendations ... 48
11.5 Work products ... 55
12 Qualification of software components ... 56
12.1 Objectives ... 56
12.2 General ... 56
12.3 Inputs to this clause ... 56
12.4 Requirements and recommendations ... 57
12.5 Work products ... 59
13 Evaluation of hardware elements ... 59
13.1 Objectives ... 59
13.2 General ... 60
13.3 Inputs to this clause ... 61
13.4 Requirements and recommendations ... 61
13.5 Work products ... 66
14 Proven in use argument ... 66
14.1 Objectives ... 66
14.2 General ... 67
14.3 Inputs to this clause ... 68
14.4 Requirements and recommendations ... 68
14.5 Work products ... 73
15 Interfacing an application that is out of scope of GB/T 34590 ... 73
15.1 Objectives ... 73
15.2 General ... 73
15.3 Inputs to this clause ... 74
15.4 Requirements and recommendations ... 74
15.5 Work products ... 75
16 Integration of safety-related systems not developed according to GB/T 34590 ... 75
16.1 Objectives ... 75
16.2 General ... 75
16.3 Inputs to this clause ... 75
16.4 Requirements and recommendations ... 76
16.5 Work products ... 77
Annex A (Informative) Overview of and workflow of supporting processes ... 78
Annex B (Informative) Development Interface Agreement (DIA) example ... 84
Bibliography ... 91
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 8 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 serves as a replacement of GB/T 34590.8-2017 Road vehicles - Functional
safety - Part 8: Supporting processes. In comparison with GB/T 34590.8-2017, apart from
structural adjustments and editorial modifications, the main technical changes are as follows:
-- Change the scope of application from “series production passenger cars” to “series
production road vehicles, excluding mopeds” (see Clause 1; Clause 1 of the 2017
edition);
-- Add adaptation for motorcycles (see 4.5);
-- Add adaptation for trucks, buses, trailers and semi-trailers (see 4.6);
-- Change the objectives of interfaces within distributed developments (see 5.1; 5.1 of the
2017 edition);
-- Change the scope of non-application for distributed developments (see 5.4.1; 5.4.1 of
the 2017 edition);
-- Change the contents included in RFQ (see 5.4.2.2; 5.4.2.2 of the 2017 edition);
-- Change the contents included in Development Interface Agreement (see 5.4.3.1; 5.4.3.1
of the 2017 edition);
-- Change the segregation of duties between the customer and the supplier, and the specific
requirements during execution of distributed development; add responsibilities to be
borne by the customer (see 5.4.4; 5.4.4 of the 2017 edition);
-- Change the specification of safety requirements, and add a footnote to Table 1 (see 6.4.1;
6.4.1 of the 2017 edition);
-- Modify the requirements of characteristics for safety requirements (see 6.4.2.4; 6.4.2.4
of the 2017 edition);
-- Modify the general rules for configuration management (see 7.2; 7.2 of the 2017 edition);
-- Modify the requirements for configuration management process (see 7.4.2; 7.4.2 of the
2017 edition);
-- Modify the refining clarification for the documentation of work products in
configuration management (see 7.4.4; 7.4.4 of the 2017 edition);
-- Modify the requirements for the change management process (see 8.4.1.4; 8.4.1.4 of the
2017 edition);
-- Modify the prerequisites for verification (see 9.3.1; 9.3.2 of the 2017 edition);
-- Modify the contents included in the verification planning (see 9.4.1.1; 9.4.1.1 of the
2017 edition);
-- Add the requirements for person of test cases in the verification specification and
execution (see 9.4.2.4);
-- Add the requirements for person of verification in the verification specification and
execution (see 9.4.3.2);
-- Add the requirements for two groups of activities, namely tool usage aspects and tool
qualification aspects, in tool confidence (see 11.2);
-- Remove the contents of confirmation and review in software tool qualification (see
11.4.10 of the 2017 edition);
-- Modify the verification requirements of qualification of a software component (see
12.4.3; 12.4.4 of the 2017 edition);
-- Modify the objectives for evaluation of hardware elements (see 13.1; 13.1 of the 2017
edition);
-- Modify the general rules for requirements and recommendations of the evaluated
hardware elements (see 13.4.1.1; 13.4.1.1 of the 2017 edition);
-- Add the evaluation requirements of class I hardware elements (see 13.4.2);
-- Add the evaluation requirements of class II hardware elements (see 13.4.3);
-- Add the evaluation requirements of class III hardware elements (see 13.4.4);
-- Remove the verification objectives, verification method, verification plan, verification
argumentation, analytical verification, testing verification and verification report for
the evaluation of hardware elements (see 13.4.2 ~ 13.4.8 of the 2017 edition);
-- Add requirements for interfacing an application that is out of scope of GB/T 34590 (see
Clause 15);
-- Add requirements for integration of safety-related systems not developed according to
GB/T 34590 (see Clause 16).
This document has been modified using ISO 26262-8:2018 Road vehicles - Functional safety -
Part 8: Supporting processes.
The technical differences between this document and ISO 26262-8:2018, and the causes for
these differences are as follows:
-- Use the normative reference GB/T 34590.1-2022 to replace ISO 26262-1 (see Clause 3;
Clause 3 of ISO 26262-8), to adapt to the technical conditions in China;
-- Change the description of T&B vehicles from “trucks, buses, trailers and semi-trailers”
to “goods vehicles, buses, special automobiles, trailers” (see 4.6; 4.6 of ISO 26262-
8: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;
This document also makes the following editorial modifications:
-- Adjust the order of paragraphs in Scope;
-- List the normatively referenced GB/T 34590.12-2022 in the list in Clause 2;
-- Remove the terminology database website maintained by ISO and IEC for
standardization in Clause 3 of ISO 26262-8:2018;
-- Remove clause numbers 7.5.1 and 16.5.1 in ISO 26262-8:2018;
-- Correct the number of the note in 9.4.2.2 of ISO 26262-8:2018;
Road vehicles - Functional safety - Part 8: Supporting
processes
1 Scope
This document specifies the requirements for supporting processes, including the
following:
-- interfaces within distributed developments;
-- overall management of safety requirements;
-- configuration management;
-- change management;
-- verification;
-- documentation management;
-- confidence in the use of software tools;
-- qualification of software components;
-- evaluation of hardware elements;
-- proven in use argument;
-- interfacing an application that is out of scope of GB/T 34590; and
-- integration of safety-related systems not developed according to GB/T 34590.
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
this document 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 document. 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. This document 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.
Annex A provides an overview on objectives, prerequisites and work products of this
document.
2 Normative references
The following documents are referred to in the text in such a way that some or all of
their content constitutes requirements of this document. For dated references, only the
version corresponding to that date is applicable to this document; for undated references,
the latest version (including all amendments) is applicable to this document.
GB/T 34590.1-2022, Road vehicles - Functional safety - Part 1: Vocabulary (ISO
26262-1:2018, MOD)
GB/T 34590.2-2022, Road vehicles - Functional safety- Part 2: Management of
functional safety (ISO 26262-2:2018, MOD)
Note: There is no technical difference between the referenced content of GB/T
34590.2-2022 and the referenced content of ISO 26262-2:2018.
GB/T 34590.3-2022, Road vehicles - Functional safety - Part 3: Concept phase (ISO
26262-3:2018, MOD)
Note: There is no technical difference between the referenced content of GB/T
34590.3-2022 and the referenced content of ISO 26262-3:2018.
GB/T 34590.4-2022, Road vehicles - Functional safety - Part 4: Product
development at the system level (ISO 26262-4:2018, MOD)
Note: There is no technical difference between the referenced content of GB/T
34590.4-2022 and the referenced content of ISO 26262-4:2018.
GB/T 34590.5-2022, Road vehicles - Functional safety - Part 5: Product
development at the hardware level (ISO 26262-5:2018, MOD)
Note: There is no technical difference between the referenced content of GB/T
34590.5-2022 and the referenced content of ISO 26262-5:2018.
GB/T 34590.6-2022, Road vehicles - Functional safety - Part 6: Product
development at the software level (ISO 26262-6:2018, MOD)
Note: There is no technical difference between the referenced content of GB/T
34590.6-2022 and the referenced content of ISO 26262-6:2018.
GB/T 34590.7-2022, Road vehicles - Functional safety - Part 7: Production,
operation, service and decommissioning (ISO 26262-7:2018, MOD)
Note: There is no technical difference between the referenced content of GB/T
34590.7-2022 and the referenced content of ISO 26262-7:2018.
GB/T 34590.9-2022, Road vehicles - Functional safety - Part 9: Automotive safety
integrity level (ASIL)-oriented and safety-oriented analyses (ISO 26262-9:2018,
MOD)
Note: There is no technical difference between the referenced content of GB/T
34590.9-2022 and the referenced content of ISO 26262-9:2018.
GB/T 34590.12-2022, Road vehicles - Functional Safety - Part 12: Adaptation for
motorcycles (ISO 26262-12:2018, MOD)
Note: There is no technical difference between the referenced content of GB/T
34590.12-2022 and the referenced content of ISO 26262-12:2018.
3 Terms and definitions
For the purposes of this document, the terms and definitions given in GB/T 34590.1-
2022 apply.
Note 1: A “software tool” can vary from a stand-alone software package to a suite of
software tools integrated into a tool-chain.
Example 1: Commercial tools, open source tools, freeware tools, shareware tools or
tools developed in-house by the user.
To determine the required level of confidence in a software tool used within
development under the conditions mentioned above, the following criteria are evaluated:
-- the possibility that the malfunctioning software tool and its corresponding
erroneous output can introduce or fail to detect errors in a safety-related item or
element being developed; and
-- the confidence in preventing or detecting such errors in its corresponding output.
The tool may pre-exist or be developed upon request, based on the tool user
requirements.
Example 2: Software development tools, requirements management tools, system
design tools, testing tools, static analysis tools, etc.
The confidence in the use of software tools is composed of two groups of activities
which are shown in Figure 3:
a) Tool usage aspects:
-- Evaluation of the software tool usage is based on the tool’s required functions
and properties. The determination of the corresponding Tool Confidence Level
(TCL) is based on analysis classes, Tool Impact (TI), and Tool error Detection
(TD). The determination of TI and TD depends on the development process of
the element developed and/or verified with the tool.
-- Integration of the software tool into the user’s environment according to the
results of the evaluation and qualification (see 11.4.2 and 11.4.3).
Example 3: The tool could need to be integrated with configuration
management tools, authoring tools or compilers.
-- Verify that the tool is working appropriately in the user environment. Check the
validity of the predetermined Tool Confidence Level or qualification (11.4.2)
and if required perform qualification procedures in the user environment.
Example 4: Test of the tool performed in the user environment for
representative use cases.
Example 5: Run the tool validation test suite.
-- Appropriate usage of the tool: operating the tool in the user environment for
......