Document: NUREG-0800
Document ID: fea61ff0-f344-4101-adfb-590e3d9dfafe
Document Type: srp
Title: Draft Revision 6 – August 2015
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1515/ML15159A946.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7
CFR Part: 
CFR Title: 

Content:
other unwanted or undocumented functions or applications. B.3.2.2 Acceptance Criteria for Software Verification and Validation Activities RG 1.168 endorses IEEE Std 1012, “IEEE Standard for Software Versification and Validation,” as providing methods acceptable to the staff for meeting the regulatory requirements as they apply to V&V of safety system software, subject to the exceptions listed. RG 1.168 also endorses IEEE Std 1028, “IEEE Standard for Software Reviews and Audits,” as providing an approach acceptable to the staff for carrying out software reviews, inspections, walk through and audits, subject to the exceptions listed. BTP 7.14-44 Draft Revision 6 - August 2015 Clause 5.3.3, “Verification and Validation,” and Clause 5.3.4, “Independent Verification and Validation (IV&V) requirements,” of IEEE Std 7-4.3.2 which is endorsed by RG 1.152, contain guidance on V&V. The SVVP describes the V&V implementation tasks that are to be carried out. The acceptance criterion for software V&V implementation is that the tasks in the SVVP have been carried out in their entirety. Documentation should exist that shows that the V&V tasks have been successfully accomplished for each life cycle activity group. In particular, the documentation should show that the requirements, design, code, integration, and installation design outputs satisfy the appropriate software development functional and process characteristics (as described in Subsection B.3.3 below). Problems identified by the verification effort should be documented, together with any action items required to mitigate or eliminate each problem. A record should be kept of actions taken in response to the action items and the appropriate CM activities should be performed. As part of the software V&V effort, a traceability analysis should be performed and documented. This traceability analysis documentation should clearly show the linkage between each requirement imposed on the software by the system