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:
Revision 6 - August 2015 that each guidance followed be identified. Once the RAI is answered, then the reviewer can determine the acceptability of the defined process, and proceed with the review. The acceptance criteria are subdivided into three areas: Subsection B.3.1, planning; Subsection B.3.2, implementation; and Subsection B.3.3, design outputs. B.3.1 Acceptance Criteria for Planning This subsection addresses acceptance criteria for planning activities. The acceptance criteria address specific software development planning activities and products. These products, when found to be acceptable, provide the reviewer with additional criteria for reviewing the processes and products of subsequent life cycle activities, as discussed in Subsections B.3.2 and B.3.3 below. Safety system development is a complex set of activities implemented by various organizational entities. The plans described in this BTP are one representation of the required activities in terms of coherent and cohesive views, with defined inter-relationships, to be implemented by defined organizational entities. For example, it is understood that the software verification and validation plan (SVVP) defines all of the activities performed by the software verification and validation team (SVVT), and no activities that will be performed by another team. However, a Test Plan (TP) may describe all of the testing activities, even if portions are performed by different groups. Other sets of plans are permissible so long as each plan descries a coherent and cohesive view of the activities to be performed. Plans may be organized in a layered fashion such that a higher level plan is implemented by lower level plans. For example, the TP could be a higher level plan that would be implemented by lower level plans, specific to particular teams (i.e., the SVVP includes the testing activities performed by the SVVT, and the software development plan includes the testing activities performed by the software