Document: NUREG-0800
Document ID: 4f141c71-35ca-4353-9047-a13efe6d56b7
Document Type: srp
Title: Revision 6 - August 2016
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1601/ML16019A308.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7
CFR Part: 
CFR Title: 

Content:
or each life cycle activity group and that the proposed digital system software is, in fact, safe. In particular, the documentation should show that the system safety requirements have been adequately addressed for each activity group; that no new hazards have been introduced; that the software requirements, design elements, and code elements that can affect safety have been identified; and that all other software requirements, design, and code elements will not adversely affect safety. The safety analysis activities also should include the SDOE risk, and assessing the measures used to ensure that the design products do not contain undocumented code, and 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. 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