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:
o the regulatory guide. In Regulatory Guide 1.170 the “Test Program” in Staff Regulatory Guidance position 1 directs the licensee to use the Master Test Plan (MTP) in IEEE Std. 829-2008, Clause 8, and outlines additional requirements with the associated IEEE Subclauses. The MTP overview provides a method of managing design details for test documentation, while following the life-cycle process and track occurrences and provide corrections to the software as noted in IEEE Std. 829-2008, Clause 14, Anomaly Report. Staff Regulatory Guidance position 2 of Regulatory Guide 1.170 has been expanded to include details on the Master Test Report (MTR) and the sequence of other test documents that could occur during a life-cycle process. Because of the integrity scheme level required, the different sequences of test reports are distilled into the summarization MTR. Staff Regulatory Guidance position 3 also includes details for effective document retention which includes ways to combine or eliminate added documents. The original Staff Regulatory Guidance position 4 in Regulatory Guide 1.170 stated that any given safety system feature is tested formally by a given test design, while other features may be exercised but not identified. With the traceability matrix in Staff Regulatory Guidance position 5 and the expanded test documentation for integrity level 4, there can be multiple sets of design testing or retesting to complete an acceptable safety system or software product. The licensee should formally test all associated features in the safety system and follow the recommended testing activity process outlined under Clause 5 in IEEE Std. 829-2008. As for each specifically planned test, the acceptance criteria requirement is that any testing must show positive results and if an error exists, the documentation must show the corrections and retesting, as any modified software has the potential of introducing new errors. The new Staff Regulatory Guidance position 6,