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:
rs are detected are appropriately analyzed, reported, corrected and reassessed. The SVVP should provide procedures for evaluating the risks associated with each project development activity. It should include a procedure for evaluating the effect of proposed software changes on planned reviews and tests. BTP 7.14-39 Revision 6 - August 2016 Anomaly reports should be generated and disseminated. A method should be specified for resolving discrepancies identified during the verification of each V&V task. Procedures should be specified for selecting test cases, and for software review activities. The SVVP should describe V&V reporting requirements. It should require that reports document all V&V activities, including the personnel conducting the activities, procedures and results. This includes review documentation requirements, evaluation criteria, error reporting, and anomaly resolution procedures. V&V reports should summarize the positive practices and findings as well as negative practices and findings. The reports should summarize the actions performed and the methods and tools used. The SVVP should include a description of all required testing plans, specifications, procedures and cases. This includes unit testing, integration (subsystem) testing, system validation testing, installation (acceptance) testing, and the regression testing of modifications. The description should also include test documentation requirements, readiness and evaluation criteria, error reporting, and anomaly resolution procedures. Testing documentation should include test item descriptions, test data, test logs, the identities of testers, types of observations, results and acceptability, and actions taken in connection with any deficiencies. Test case documentation should specify expected results and actual results. RG 1.170, which endorses IEEE Std 829, “IEEE Standard for Software Test Documentation,” describes acceptable methods for documenting test plans, test specifications, test