2 Normative references
The terms in the following documents are incorporated into this section by reference in this section of GB T 20438. All subsequent amendments (excluding errata) or revisions of dated references do not apply to this Section, however, parties to agreements under this Part are encouraged to investigate the possibility of using the most recent versions of these documents. For undated references, the most recent version of the document applies to this section.
gb/t 20438.2-2006 Electrical and Electronic Functional Safety of Programmable Electronic Safety Related Systems Part 2: Requirements for Electrical and Electronic Programmable Electronic Safety Related Systems (IEC 61508-2;2000,idt)
gb/t 20438.3-2006 Electrical and Electronic Functional Safety of Programmable Electronic Safety-Related Systems Part 3;Software requirements (IEC 61508-3:1998, IDT).
gb/t 20438.4-2006 Electrical Electronics Functional Safety of Programmable Electronic Safety-Related Systems Part 4: Definitions and Abbreviations (IEC 61508-4:1998, IDT).
gb/t 20438.5-2006 Electrical Electronics Functional Safety of Programmable Electronic Safety-Related Systems Part 5: Examples of Methods for Determining Safety Integrity Levels (IEC 61508-5:1998, IDT).
gb/t 20438.6-2006 Electrical Electronics Functional Safety of Programmable Electronic Safety-Related Systems Part 6: GB T 204382 and GBT 201383 Application Note (IEC 61508-6:2000, IDT).
gb/t 20438.7--2006 Electrical Electronics Functional Safety of Programmable Electronic Safety Related Systems Part 7: Overview of Techniques and Measures (IEC 61508-7.)2000 idt)
ISO IEC Guideline 51:1990 Safety Aspects Guidelines for introducing safety clauses in standards.
IEC Guideline 104:1997 Preparation of safety publications and application of basic safety publications and classified publications.
3 Definitions and Abbreviations
This part uses GB T 20438Definitions and abbreviations specified in 2006-2006.
4 Conformity with GB T 20438
4.1 To meet the requirements of GB T 20438, it must be demonstrated that all requirements made comply with the provisions of GB T 20438 (e.g., Safety Integrity Level) and that the requirements of the various chapters and spare strips have been met.
Note: In general, it is not possible to select a single parameter to determine the degree to which a requirement is met (degree of rigor), but rather on the basis of a number of factors related to the overall security life cycle, the security life cycle or the phases and activities of the software security life cycle, which are:
Consequences and risk reduction.
Hazardous nature;Safety Integrity Level;
Implement the type of technology;
System size;The number of teams involved;
Physical distribution;The degree of novelty of the design.
4.2 GB T 20438 specifies the requirements for safety-related systems in E E PE to meet the full range of complexities associated with such systems. But for simple E e PE safety-related systems (see GB T 20438.)42006 of 34.4) If there is a reliable field experience that can provide the necessary confidence to achieve the required safety integrity, there are several options:
Implementation of GB T 20438 in the relevant application field standards1~gb/t 20438.7. Some of the requirements may be unnecessary, and it is acceptable not to meet them.
If there is no standard in the relevant area, GB T 20438 can be applied directly, and if there is reason to believe that some of the requirements in GB T 20438 are unnecessary, it is acceptable not to meet them.
4.3 The national standard for the application of safety-related systems in the E E PE developed in accordance with the GB T 20438 framework will contain the requirements in ISO IEC Guideline 51 and 1EC Guideline 104.