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:
fficient for a qualified software engineer to understand. If the reviewer does not have enough experience in this particular language or with the software tool being used, the reviewer may require the assistance of other NRC personnel or independent contractor personnel to make this determination. B.3.3.5 Integration Activities - System Build Documents (SBDs) BTP 7.14-58 Draft Revision 6 - August 2015 NUREG/CR-6101, Section 3.5.1, “System Build Documents,” and Section 4.5.1, “System Build Documents,” contain relevant guidance. One or more system build documents should be produced. The build documents should include all of the functional and software development process characteristics listed below. B.3.3.5.1 Functional Characteristics of SBDs For each of the functional characteristics, the requirements imposed on the build documents for that characteristic should be satisfied. Functional characteristics addressed by the build documents should include robustness, safety, and security. Robustness means that the software build documents specify methods to detect incorrectly built software releases. The software build documents should identify all errors and anomalies discovered during software build activities. Safety means that the software build activity introduces no new hazards into the safety system. Security means that the software build activity does not introduces unintended changes into the safety system software per RG 1.152. B.3.3.5.2 Process Characteristics of SBDs The system build documents should exhibit each of the following software development process characteristics: completeness, consistency, correctness, style, traceability, and verifiability. Completeness means that all build procedures are fully specified. The software build documents should include all required software units, including code and data, that are part of the build. Consistency means that the software build documents are consistent with the software specifications, as