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:
s 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, “Integrity Levels” introduces an integrity scheme level 4, which is maintained throughout the life-cycle testing process despite any risk assessment schemes. For level 4 the breadth, depth of testing, and the associated type of tasks can be found in Annex C, as described in the new Staff Regulatory Guidance position 7, “Testing Tasks.” For example: The Level Interim Test Status Report can be used to maintain a time sequence during the project development and assists in the documentation as an output. As the safety analysis activities are being completed, the output requirements should be adequately addressed so that no hazards have been introduced into the final code prior to the V&V testing. The MTP’s goal is to address and orchestrate all testing and reporting documentation with positive results. As automated tools are used for testing software, the new Staff Regulatory Guidance position 8, “Test Tool Documentation” points out that repetition is sometimes needed. There is a need for making test information easily accessible to the NRC staff and thus improving the timeliness of a safety conclusion. In specific tasks of identifying security issues, the IEEE Std. 829-2008 Std. provides an opportunity to integrate this task within the life-cycle phases, which can be found in Table 3. The secure analysis of any software project is part of the software requirement specification and Annex C of IEEE 829-2008 breaks the inputs down further in system, software, and interface requirements. Regulatory Guide 1.170 outlines that the addition of this task should be considered as early as possible in the life- cycle phases. The NRC further supplements this V&V life-cycle approach by providing secure DG-1207, Page 6 development and operational environment (SDOE)