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:
sses 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. 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 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