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:
an be done via a version number or attached change date. Changes to baselines and to configuration items under change control should be recorded approved and tracked. If the change is due to a problem report, traceability should exist between the problem report and the change. Software changes should be traced to their point of origin, and the software processes affected by the change should be repeated from the point of change to the point of discovery. Proposed changes should be reviewed by the CCB for their impact on system safety. Status accounting should take place for each set of life cycle activities prior to the completion of those activities. The status accounting should document configuration item identifications, baselines, problem report status, change history and release status. The configuration management organization should audit life cycle activities to confirm that configuration management procedures were carried out in the life cycle process implementation. B.3.2.4 Acceptance Criteria for Testing Activities RG 1.152, “Criteria for Use of Computers in Safety Systems of Nuclear Power Plants,” which endorses IEEE Std 7-4.3.2, “IEEE Standard Criteria for Digital Computers in Safety Systems of Nuclear Power Generating Stations,” with a few noted exceptions, identifies an acceptable methods for satisfying computer system qualification testing requirements (See: IEEE Std 7- 4.3.2 Clause 5.4.1, “Computer System Testing”). RG 1.168, Section C.7.b, “Regression Analysis and Testing,” and C.7.d, “Test Evaluation,” contain guidance related to testing activities. RG 1.170, “Software Test Documentation for Digital Computer Software Used in Safety Systems of Nuclear Power Plants,” endorses IEEE Std 829, “IEEE Standard for Software Test Documentation,” with a few noted exceptions, identifies an acceptable method for satisfying test documentation requirements. RG 1.171, “Software Unit Testing for Digital Computer Software Used in