Document: NRC Regulatory Guide
Document ID: 12dd3f35-6baa-4f6a-8372-84c90ef96a91
Document Type: regulatory_guide
Title: Test Documentation for Digital Computer Software Used in Safety Systems of Nuclear Power Plants + HISTORY - HISTORY 08/2012 – DG-1207 , Proposed Revision 1 08/1996 – DG-1056 , Proposed Revision 0 (Rev. 1)
Source: NRC Regulatory Guide Division 1
Source URL: https://www.nrc.gov/docs/ML0833/ML083370243.pdf
Revision Date: 2023-06
Chapter: 
Section ID: RG-1.170
CFR Part: 
CFR Title: 

Content:
IEEE Std. 829-2008 describes software and system test documentation as a set of individual documents. There are different types and levels of test documentation addressed from Clause 8 through Clause 17, which may be combined or eliminated per Clause 6. For each type of test documentation the licensee must document the software and system test content decisions and rationale at the highest level of testing and the documentation must be signed-off by all designated stakeholders. It is the NRC’s position that in order to claim conformance to the IEE Std. 829-2008, the documentation should be completed prior to implementation. For effective document retention, it is acceptable to combine by incorporating individual documents into larger test documents, provided that it retains the identity of each component document and maintains the proper test planning documentation throughout the life-cycle process for a proper traceability matrix in V&V. However, it is not acceptable to lower the integrity level as suggested in Clause 6.4, “Choose to combine or eliminate documents.” Furthermore, some acceptance test procedures may have an open entry location within the document, appendix or attachment to record the data and testing status. To meet the activity and event entry per Clause 13, “Level Test Log,” an acceptable method for eliminating or combining test documents is to use the procedure and log as the same document (e.g., Factory Acceptance Test Procedures). This is DG-1207, Page 9 also the case when the test log is the appendix or attachment to the test procedure, and where the procedure is repeated many times (e.g., surveillance procedures). 4. System Testing Criterion XI requires that testing demonstrate systems and components will perform satisfactorily in service. Clause 10.2.1 of IEEE Std. 829-2008 describes other features in a given test design and not the specific LTD objective that may be exercised but not identified. The licensee should formally test