Document: NUREG-0800
Document ID: f1629507-6318-4e71-94a6-9d6664ba96a3
Document Type: srp
Title: of the plant safety analysis report (SAR).  Although NRC did not endorse the annexes of
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML0706/ML070660327.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7.6
CFR Part: 
CFR Title: 

Content:
d address the following: i. Identification and control of all software designs and code ii. Identification and control of all software design functional data (e.g., data templates and data bases) iii. Identification and control of all software design interfaces iv. Control of all software design changes v. Control of software documentation (user, operating, and maintenance documentation) vi. Control of software vendor development activities for the supplied safety system software vii. Control and retrieval of qualification information associated with software designs and code viii. Software configuration audits ix. Status accounting. Some of these functions or documents may be performed or controlled by other quality assurance activities. In this case, the software configuration management plan should describe the division of responsibility. A software baseline should be established at appropriate points in the software life cycle process to synchronize engineering and documentation activities. Approved changes that are created subsequent to a baseline should be added to the baseline. The labeling of the software for configuration control should include unique identification of each configuration item, and revision and/or date time stamps for each configuration item. This labeling should be unambiguous, and clearly identify this particular product and version from all others. Changes to the software/firmware should be formally documented and approved consistent with the software configuration management plan. The documentation should include the reason for the change, identification of the affected software/firmware, and the impact of the change on the system. Additionally, the documentation should include the plan for implementing the change in the system (e.g., immediately implementing the change, or scheduling the change for a future version). There may be two different software configuration management programs to evaluate, that being used by the software vendor