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:
e conformance is acceptable, if conformance was achieved, and finally if the system is safe. For example, an ambiguous claim like “the software life cycle processes were developed consistent with RG 1.173,” does not actually identify which parts of the guidance in the RG were followed, and therefore the acceptability of the process is not clear. In order to determine BTP 7.14-12 Revision 6 - August 2016 the level of conformance, the reviewer should ask, in a request for additional information (RAI), 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