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:
the breadth or depth of testing and documentation should adhere to the proper activities for a nuclear software safety system product. The licensee or applicant should assign integrity level 4 or the equivalent to software used in nuclear power plant safety systems, as demonstrated by a mapping between its approach and integrity level 4 and defined in IEEE Std. 829-2008. 7. Testing Tasks Clause 5 of IEEE Std. 829-2008 lists the minimum testing tasks for each life-cycle process steps that the applicant or licensee may use for the preparation of the required test plans. Table C.1, “Testing tasks, inputs and outputs” per Annex C of IEEE Std. 829-2008 outlines Clause 5 in a tabular form and amplifies the requirements given in the body of the standard by detailing, for each process, the tasks that the licensee and applicant should carry out, as noted under column names “Testing tasks,” “Inputs” and “Outputs.” For software used in the safety systems of nuclear power plants, applicants and licensees should consider the recommendations in this annex. DG-1207, Page 10 8. Test Tool Documentation Clause 6.3 of IEEE Std. 829-2008 states that there is no need for repetition of test information if completely managed by an automated tool with references for tracing the information. The NRC staff takes exception to this Clause as there are particular cases where electronic validation methods with repetition provide test information easily accessible for the basis of any safety conclusion. This test information should be available within the record management system. The tools used in the development of safety system software should be handled according to IEEE Std. 7-4.3.2-2003, as endorsed by Regulatory Guide 1.152. 9. Secure Analysis IEEE Std. 829-2008, Clause 5 and Table 3 list “Identifying security issues (test)” as a required test effort task in the development life-cycle process and only as a minimum recommended test activity covered in the life-cycle