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:
fying computer system qualification testing requirements (See: IEEE Std 7-4.3.2 Clause 5.4.1, “Computer System Testing”). RG 1.168, Section C.7.b, “Regression Analysis and Testing,” and C.7.d, “Test Evaluation,” contain guidance related to testing activities. RG 1.170endorses IEEE Std 829, “IEEE Standard for Software Test Documentation,” with a few noted exceptions, identifies an acceptable method for satisfying test documentation requirements. RG 1.171which endorses ANSI/IEEE Std 1008, “IEEE Standard for Software Unit Testing,” with a few noted exceptions, identifies an acceptable method for satisfying software unit testing requirements. Thorough software testing consists of testing the smallest testable units, and then integrating those units into larger testable units, and testing that integrated unit. This process is repeated until finally the system is tested after installation. There is no generally accepted, precise definition of a unit, module, and system. It is therefore understood that RG 1.171 applies to all testing before integrated system testing. The software development process characteristics listed below should be exhibited by testing activities. Completeness means that all required functionality for all operating modes, including error recovery be tested. BTP 7.14-51 Revision 6 - August 2016 Consistency means that the testing is consistent with the safety system requirements, the safety system design, the SRSs, the SDS, and documented descriptions and known properties of the operational environment within which the safety system will operate. Uniform and consistent terminology, notation, and definitions should be used throughout. Traceability means that a trace exists between the SRS, the SDS, and the test documentation, which shows how each requirement is tested. B.3.3 Acceptance Criteria for Design Outputs This subsection describes the criteria to be used to determine whether the software has each of the characteristics