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:
and guidance for performing a software V&V can be found in Regulatory Guide 1.168 “Verification, Validation, Reviews and Audits for Digital Computers Software Used in Safety Systems of Nuclear Power Plants” (Ref. 9). This revision to Regulatory Guide 1.173 has added a clarification statement to highlight one of the existing planning activities in IEEE Std. 1074-2006. This statement is found under Part C.4.d., “System Transitions” and states all changes to safety systems must be evaluated using the criteria specified in 10 CFR 50.59. If the change is outside the scope of 10 CFR 50.59 then it must be submitted for review as a licensing amendment request. DG-1210, Page 5 Related Guidance In terms of inputs, development, verification or control processes, and outputs, IEEE Std. 1074-2006 describes a set of processes and constituent activities that are commonly accepted as comprising a controlled and well-coordinated software development process. It describes interrelationships among activities by defining the source activities that produce the inputs and the destination activities that receive the outputs. The standard specifies activities that the software will perform and their interrelationships. It does not specify complete acceptance criteria for determining whether the activities themselves are properly designed. Therefore, the standard should be used in conjunction with guidance from other appropriate regulatory guides, standards, and software engineering literature. IEEE Std. 1074-2006 can be used as a basis for developing specific software life-cycle processes that are consistent with regulatory requirements, as applied to software, for controlling and coordinating the design of safety system software. Software development processes are intimately related to system development processes. The system design phase allocates system safety requirements to hardware, software, and human elements. The system integration and testing phases combine and test these