Document: NUREG-0800
Document ID: 4cca74ec-66e0-4765-9c61-cf547e17c308
Document Type: srp
Title: of the plant safety analysis report (SAR).  Although the NRC did not endorse the annexes of
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1601/ML16019A114.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7.6
CFR Part: 
CFR Title: 

Content:
rolled under CM; and that one or both of the following methods should be used to confirm that the software tools are suitable for use: (a) A test tool validation program should be developed to provide confidence that the necessary features of the software tool function as required. (b) The software tool should be used in a manner such that defects not detected by the software tool will be detected by V&V activities. Appendix 7.1-D-6 Revision 1 - August 2016 In addition to the criteria of IEEE Std 603-1991 and IEEE Std 7-4.3.2, SRP BTP 7-14 directs the reviewer to specific features of software development that should be reviewed. SRP BTP 7-14 has the following three objectives: i. To confirm that plans exist that will provide a high-quality software life-cycle process, and that these plans commit to documentation of life-cycle activities that permit the NRC staff to evaluate the quality of the design features upon which the safety determination is based. ii. To verify that implementation of the software life-cycle process meets the criteria expected for high-quality software. iii. To assess the adequacy of the design outputs. All software development life-cycles share certain characteristics. The activities that will be performed can be grouped into a number of categories (termed activity groups in SRP BTP 7-14); the activity groups are common to all life-cycles. Life-cycle activities produce process documents and design outputs that can be reviewed and assessed. The documents to be provided for each life-cycle activity group are shown in Figure 7-A-1 of SRP BTP 7-14. The information to be reviewed is subdivided into three topic areas: software life-cycle process planning; software life-cycle process implementation; and software life-cycle development process outputs. The applicant/licensee need not develop a separate document for each of the topics identified below; however, project documentation should encompass all of the topics. The information documents in the