Document: NRC Regulatory Guide
Document ID: 3eb179d3-5491-407d-8b0e-eed083d58a17
Document Type: regulatory_guide
Title: Configuration Management Plans for Digital Computer Software Used in Safety Systems of Nuclear Power Plants + HISTORY - HISTORY 08/2012 – DG-1206 , Proposed Revision 1 08/1996 – DG-1055 , Proposed Revision 0 (Rev. 1)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML1032/ML103200044.pdf
Revision Date: 2023-06
Chapter: 
Section ID: RG-1.169
CFR Part: 
CFR Title: 

Content:
procedures applied to other configuration items, and the SCM system should track and report its usage. 5. Corrective Action Criterion XVI requires, in part, that conditions adverse to quality, such as failures, malfunctions, and deficiencies, are identified and that the cause be determined, the condition be corrected, and the entire process be documented. In software development or maintenance activities, the responsibility for these activities is often distributed among several organizations, possibly leading to a fragmented view of the correction process. Clause 3.3.2 of IEEE Std. 828-2005 requires a description of the correction process, including change requests, change evaluation, change approval, change implementation, change verification, and changed-version release. The preliminary steps leading to a change request should also be described, including the responsibility for executing and documenting anomaly reports, problem analyses, and statistical monitoring of software performance. If other documents describe these activities, the descriptions may be included by reference to those documents. DG-1206, Page 8 6. Documentation Clause 3.3.1.1 of IEEE Std. 828-2005 requires, as a minimum, that the SCM plan lists all configuration items to be delivered. This meets the requirements of Criterion VIII with regard to safety system software if all software deliverables are identified and controlled as configuration items. It also meets the requirements of Criteria III, VI, and VII. For safety system software, configuration items or controlled documents should include the following: a. software requirements, designs, and code; b. data files used and called directly or indirectly by software; c. support software used in development (exact versions); d. libraries of software components essential to safety; e. software plans that could affect quality; f. test software requirements, designs, or code used in testing; g. test results used to qualify software; h. analyses