Document: NUREG-0800
Document ID: 4f141c71-35ca-4353-9047-a13efe6d56b7
Document Type: srp
Title: Revision 6 - August 2016
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1601/ML16019A308.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7
CFR Part: 
CFR Title: 

Content:
during the test activity, and any action items required to mitigate or eliminate each problem, be documented. Installation problems and their resolution should be documented. An acceptance test report should be produced describing the execution of the plan and summarizing the results. This report should contain a statement that the plan was successfully executed, and the system is ready for operation. The acceptance test report should demonstrate that the system operates correctly and is identical to the system that was validated during the validation phase. The report should summarize the test results after all problems have been satisfactorily resolved. The report should demonstrate that acceptance testing was executed according to the acceptance test procedure. One of the accepted methods of checking the V&V effort is to perform a “thread audit.” This consists of picking a sample of plant parameters and tracing the software implementation of these parameters from the purchase specification and development of the functional BTP 7.14-48 Revision 6 - August 2016 requirements to the writing and testing of the code. The sample size should be sufficiently large to ensure a representative sample of the requirements and of the software code. This may be as many as 5% of the requirements. The minimum sample size should be determined by statistical significance criteria. This review includes: (1) Reviewing actual sections of the code on a sample basis. Since the reviewer is seldom an expert in a particular language, this may necessitate that the responsible software design engineer walk the reviewer through the code. If the reviewer is unable to follow this explanation, this portion of the thread audit should be delegated to a more experienced staff person or an independent contractor. (2) Examining the various levels of software development documents and comparing them to the code. (3) Examining problem reports and test plans for the selected requirements, and