Document: NUREG-0800
Document ID: debf22b1-f3aa-4c75-a43c-f162d22de1c8
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/ML1515/ML15159A491.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7.6
CFR Part: 
CFR Title: 

Content:
9 of SRP Appendix 7.1-C and RG 1.152. Appendix 7.1-D-19 Draft Revision 2 – August 2015 5.10 Repair (IEEE Std 7-4.3.2, Clause 5.10) Guidance is provided in Subsection 5.10 of SRP Appendix 7.1-C. 5.11 Identification (IEEE Std 7-4.3.2, Clause 5.11) To provide assurance that the required computer system hardware and software are installed in the appropriate system configuration, the following identification requirements specific to software systems should be met: i. Firmware and software identification should be used to ensure the correct software is installed in the correct hardware component. ii. Means should be included in the software for the identification to be retrieved from the firmware using software maintenance tools. iii. Physical identification requirements of the digital computer system hardware shall be in accordance with the identification requirements in IEEE Std 603-1991. iv. The identification should be clear and unambiguous. The identification should include the revision level, and should be traceable to configuration control documentation that identifies the changes made by that revision. Additional guidance on identification is provided in Subsection 5.11 of SRP Appendix 7.1-C. 5.12 Auxiliary Features (IEEE Std 7-4.3.2, Clause 5.12) There is no guidance beyond the requirements of IEEE Std 603-1991. 5.13 Multi-Unit Stations (IEEE Std 7-4.3.2, Clause 5.13) There is no guidance beyond the requirements of IEEE Std 603-1991. 5.14 Human Factors Considerations (IEEE Std 7-4.3.2, Clause 5.14) There is no guidance beyond the requirements of IEEE Std 603-1991. SRP Chapter 18 provides additional guidance. 5.15. Reliability (IEEE Std 7-4.3.2, Clause 5.15) In addition to the requirements of IEEE Std 603-1991, when reliability goals are identified, the proof of meeting the goals should include the software. The method for determining reliability may include combinations of analysis, field experience, or testing. Software error recording and trending may be used