Document: NUREG-0800
Document ID: fea61ff0-f344-4101-adfb-590e3d9dfafe
Document Type: srp
Title: Draft Revision 6 – August 2015
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1515/ML15159A946.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7
CFR Part: 
CFR Title: 

Content:
Documentation,” with a few noted exceptions, identifies an acceptable method for satisfying test documentation requirements. RG 1.171, “Software Unit Testing for Digital Computer Software Used in Safety Systems of Nuclear Power Plants,” which 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. BTP 7.14-48 Draft Revision 6 - August 2015 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. 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 important to safety system software. Criteria are organized first by life cycle activity group, then by design output, and then by characteristic. Formal or semiformal methods are available for use in preparing some of the design