Document: NRC Regulatory Guide
Document ID: d6326081-f430-476d-8098-4edf00868dd9
Document Type: regulatory_guide
Title: Verification, Validation, Reviews, and Audits for Digital Computer Software Used in Safety Systems of Nuclear Power Plants + HISTORY - HISTORY 08/2012 – DG-1267 , Proposed Revision 2 01/2003 – DG-1123 , Proposed Revision 1 08/1996 – DG-1054 , Proposed Revision 0 (Rev. 2)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML1031/ML103160431.pdf
Revision Date: 2023-06
Chapter: 
Section ID: RG-1.168
CFR Part: 
CFR Title: 

Content:
s that sufficient records be maintained to furnish evidence of activities affecting quality. 6. Tools for Software Development Tools used in the development of safety system software should be handled according to IEEE Std. 7-4.3.2-2003, as endorsed by Regulatory Guide 1.152. However the V&V tasks of witnessing, reviewing, and testing are not required for software tools, provided the software that is produced using the tools is subject to V&V activities that will detect flaws introduced by the tools. If this cannot be demonstrated, the provisions of this regulatory guide are applicable to the development of tools. 7. Verification and Validation Tasks Table 3 of IEEE Std. 1012-2004 lists “optional” V&V tasks. Annex G (which is for information only) to IEEE Std. 1012-2004 further describes these tasks. They are intended to provide a tailoring capability by allowing tasks to be added to the minimum set for safety-related software. The NRC staff takes exception to the “optional” status of some tasks on this list; the staff considers them to be necessary components of acceptable methods for meeting the requirements of Appendices A and B to 10 CFR Part 50 as applied to safety system software, regardless of whether they are performed by the V&V organization. The NRC staff considers the following tasks to be part of the minimum set of V&V activities for safety-related software unless they are (1) incorporated into other V&V tasks in the SVVP or (2) performed outside the software V&V organization as part or all of the duties of some other organization: a. Audits Criterion I of Appendix B defines quality assurance functions as including verification, such as by checking, auditing, and inspecting, that activities affecting safety-related function have been correctly performed. Criterion III requires design control measures for verifying or checking the adequacy of design. Safety system software V&V organizations may employ audits, including functional audits,