Document: NRC Regulatory Guide
Document ID: c6321e39-3d1b-40a6-ace3-8c6a0c54e2cd
Document Type: regulatory_guide
Title: Developing Software Life Cycle Processes for Digital Computer Software Used in Safety Systems of Nuclear Power Plants + HISTORY - HISTORY 08/2012 – DG-1210 , Proposed Revision 1 08/1996 – DG-1059 , Proposed Revision 0 (Rev. 1)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML1031/ML103120727.pdf
Revision Date: 2023-06
Chapter: 
Section ID: RG-1.173
CFR Part: 
CFR Title: 

Content:
gn, purchasing, installation, testing, operation, maintenance, or modification, that affect the safety-related functions of such systems and components. DG-1210, Page 2 In 10 CFR 50.55a(a)(1), the NRC requires, in part, that systems and components be designed, fabricated, erected, tested, and inspected to quality standards commensurate with the safety function to be performed. The regulations in 10 CFR 50.55a(h)(1), the NRC requires that reactor protection and safety systems satisfy the criteria in Institute of Electrical and Electronics Engineers (IEEE) Standard (Std.) 603- 1991, “IEEE Standard Criteria for Safety Systems for Nuclear Power Generation Stations,” issued 1991 (including a correction sheet dated January 30, 1995) (Ref. 2), or the requirements in IEEE Std. 279, “Criteria for Protection Systems for Nuclear Power Generating Stations,” issued 1971 (Ref. 3). These criteria shall be part of the evaluation of the recognized quality codes and standards selected for their applicability, adequacy and sufficiency and shall be supplemented or modified as needed to assure the production of a quality product that will perform the required safety function. The guidance on the safety systems equipment employing digital computer software or firmware requires quality standards in the use of the project life cycle process. This regulatory guide endorses the guidance in IEEE Std. 1074-2006, “IEEE Standard for Developing a Software Project Life Cycle Process,” issued 2006 (Ref. 4), with the exceptions stated in the regulatory positions, as an method acceptable to the NRC staff for complying with NRC regulations to promote high functional reliability and design quality in software used in safety systems.1 In particular, the method is consistent with the previously cited GDC in Appendix A to 10 CFR Part 50 and the criteria for quality assurance programs in Appendix B to 10 CFR Part 50 as they apply to software development processes. The criteria of Appendices A