Document: NUREG-0800
Document ID: 0acce825-b76b-42b8-abac-5dd1ef880f21
Document Type: srp
Title: Diversity and
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1601/ML16019A085.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7.9
CFR Part: 
CFR Title: 

Content:
ee has made commitments to software development plans similar to those identified in SRP BTP 7-14, and (3) these plans have been accepted by the NRC staff. Appendix 7.0-A-15 Revision 6 – August 2016 3.5 Review of Functional Requirements for Individual Systems The functional requirements and commitments for each I&C system must be reviewed against the requirements of 10 CFR Part 50, as described in SRP Section 7.1 and the individual SRP sections applicable to the system under review. Certain review topics need to be considered differently for digital systems. These topics are: • equipment qualification, including electromagnetic compatibility • real-time, deterministic performance • on-line and periodic test provisions • communications independence • control of access Figure 7.0-A-7 of this appendix outlines the review of these topics. Detailed regulatory bases, material to be reviewed, acceptance criteria, and review processes for each of these topics are contained in SRP Sections 7.1 and 7.9, “Data Communication Systems,” SRP Appendix 7.1-C, and SRP BTPs 7-17, “Guidance on Self-Test and Surveillance Test Provisions,” and 7-21, “Guidance on Digital Computer Real-Time Performance.” 3.6 Audit of Software Life-Cycle Process Implementation For operating reactors, the licensee’s implementation of life-cycle activities should be audited to confirm that the planned process is being implemented. Figure 7.0-A-8 of this appendix provides an overview of the process for auditing the implementation process. Figure 7.0-A-5 of this appendix identifies the software life-cycle process implementation topics that should be considered as candidates for audit. SRP BTP 7-14, Subsection B.3.2, describes the acceptance criteria for software life-cycle process implementation. The scope and depth of the inspection should be consistent with the extent and complexity of the proposed digital system and the potential safety impact of system failure. For simple, limited,