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:
ning is understandable, that testing responsibilities have been given to the appropriate personnel, and that adequate provisions are made for retest in the event of failure of the original test. Since modifying software after an error occurs can result in a new error, it is important that the STP require the full set of tests be run after any modification to the software. The reviewer should ensure that since final system testing is considered a V&V test, the STP assigns the responsibility of the definition, test design, and performance to the V&V group. B.3.2 Acceptance Criteria for Implementation This subsection addresses acceptance criteria for implementation activities. The acceptance criteria address specific software life cycle process implementation activities and documentation. These activities and products, when found to be acceptable, provide the reviewer with confidence that the plans have been carried out. BTP 7.14-46 Revision 6 - August 2016 The NRC staff reviewer confirms that the plans have been followed by the software developer. The detailed acceptance criteria are provided by the software developer and evaluated by the NRC staff in its acceptance of the plans. In addition to verifying that plans have been followed, the reviewer should pay particular attention to the areas discussed below. These activities are depicted in Figure 7-A-1 of this BTP as process implementation. B.3.2.1 Acceptance Criteria for Safety Analysis Activities The SSP describes the safety analysis implementation tasks that are to be performed. The acceptance criterion for software safety analysis implementation is that the tasks in that plan have been carried out in their entirety. Documentation exist show that the safety analysis activities have been successfully accomplished for 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