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:
to determine the effectiveness of the program. Description of Change Technical reviews, some audits, and software inspections and walkthroughs focus on the V&V of products of the software development process. Management reviews and other audits are focused on ensuring that planned activities are being accomplished effectively. Reviews and audits are closely associated with V&V activities since technical reviews and audits are frequently conducted by the V&V organization and because the V&V organization normally participates in management reviews. Because DG-1267, Page 4 of this close connection of the V&V activity with reviews and audits, this regulatory guide addresses IEEE Std. 1012-2004 and IEEE Std. 1028-2008 together. The original version of this regulatory guide endorsed IEEE Std. 1012-1998 and IEEE Std. 1028- 1997. This revision endorses the updated versions of the IEEE standards. One of the main IEEE 1028 alterations between versions 2008 and 1998 is the addition of an anomaly ranking and reporting found in Clause 6.8.3. This scheme for reporting anomalies should be considered beneficial and useful to the applicants and licensee, when addressing the anomaly reporting documentation requirements found in IEEE Std. 829-2008, “IEEE Standard for Software and System Test Documentation,” (Ref. 8). The IEEE Std. 1012-2004 revision in comparison to the 1998 version has several new alterations. The first of which is the addition of a conditional independence option in Annex C, Table C.1, and the second is the addition of a new activity called “Security Analysis.” Another noticeable change with the 2004 revision is the recommended use of the software integrity scheme, while the previous version did not require the selection of an integrity level. Regulatory Guide 1.168, Staff Regulatory Guidance item 2 has expanded on the topic of independence and provides clarification for organizational mapping as per IEEE Std. 1012-2004, Annex F. The new concept of