1.1 This part of GB.T 20438: a) Use should be based on a full understanding of GB/LT 20438.1 and GB/T 20438.2. b) Applicable to any software that forms part of a safety-related system within the scope of GB/T 20438.1 and GB/T 20438.2 or is used to develop safety-related systems. This kind of software is defined as security software. --Security software includes operating systems, system software, software in communication networks, human-machine interface functions, support tools, firmware and applications. --Application programs include high-level languages, low-level language programs and special-purpose programs suitable for limited variable languages (see 3.2.7 of GB/T 20438.4-2006). c) The requirements for software safety functions and software safety integrity levels should be clear. Note 1: If this requirement is already raised as part of electrical/electronic/programmable safety-related systems (see 7.2 of GB/T 20438.2-2006), it does not need to be repeated here. Note 2: Specifying software security functions and software security integrity levels is a repetitive process, see Figure 2 and Figure 6. Note 3: For document structure requirements, see Chapter 5 of GB/T 20438.1-2006 and GB/T 20438.1-2006 Appendix A of. The document structure should take into account company procedures and work realities in the particular application area. d) Establish security life cycle stages and requirements for phases and behaviors in the design and development of security-related software (software security life cycle software modules). These requirements include the application of measures and techniques in software to avoid and control faults and failures, graded according to the safety integrity level. e) Requirements for providing information related to software safety validation to organizations performing electrical/electronic/programmable integration. f) Requirements for the preparation of software-related information and procedures required by users who operate and maintain E/E/PE safety-related systems. g) Requirements for organizations that modify security-related software. h) Put forward requirements for support tools in conjunction with GB/T 20438.1 and GB/T 20438.2, such as design and development tools, language translators, testing and debugging tools, and configuration management tools. 1.2 GB/T 20438.1, GB/T 20438.2, GB/T 20438.3 and GB/T 20438.4 are basic safety standards, although they are not applicable to simple E/E/PE safety-related systems (see 3.4 of GB/T 20438.4-2006 .1), as basic safety standards, because one of the responsibilities of the technical committee is to implement the basic safety standards wherever applicable when drafting its own standards. GB/T 20438 can also be used as an independent standard. 1.3 Figure 1 shows the overall framework of GB/T 20438 and clarifies the role of this part in achieving the functional safety stage of E/E/PE safety-related systems. Appendix A of GB/T 20438.6-2006 describes the application of GB/T 20438.2 and GB/T 20438.3.
IEC 61508-3:1998 history
2010IEC 61508-3:2010 Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 3: Software requirements
1970IEC 61508-3:1998/COR1:1999 Corrigendum 1 - Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 3: Software requirements
1999IEC 61508-3/COR:1999 Functional Safety of Electrical/Electronic/Programmable Electronic Safety-Related Systems - Part 3: Software Requirements (Edition 1.0)
1998IEC 61508-3:1998 Functional safety of electrical/electronic/programmable electronic safety-related systems - Part 3: Software requirements