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:
Activity Group,” requires the software life cycle to be “remapped and executed, thereby treating the Maintenance Activity Group as iterations of development.” This process will produce revisions to software executables and configurations that may then be installed according to the installation process. Maintenance activities should conform to the configuration control and verification and validation procedures agreed to under the licensing basis. DG-1210, Page 10 d. System Transitions. The discussion in Section A.1.2.3, “Plan System Transition,” of Annex A to IEEE Std. 1074-2006 states that it is applicable only when an existing system (automated or manual) is being replaced with a new or revised system. However, 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. 5. Tailoring Software Criterion V, “Instructions, Procedures, and Drawings,” of Appendix B to 10 CFR Part 50 requires, in part, that activities affecting quality be prescribed by, and accomplished in, accordance with documented instructions, procedures, or drawings. Section A.4.1.2 of Annex A to IEEE Std. 1074-2006 permits data customer tailoring in the install software activity. Any tailoring of packaged software or data in the database at installation should be consistent with the packaged installation planned information of IEEE Std. 1074-2006. Criterion III requires, in part, that design changes be subject to design control measures commensurate with those applied to the original design. Tailoring that constitutes design changes, including configurations not part of the original system design, is not permitted unless such tailoring is subject to the full range of design and quality assurance measures applicable to the development of safety system software. 6. Annexes IEEE Std. 1074-2006 contains the following six annexes (only