Document: NUREG-0800
Document ID: be3ce44f-6784-4f40-baef-12c96ec1ff96
Document Type: srp
Title: provides additional guidance on digital data communications systems.
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML0706/ML070670183.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7.9
CFR Part: 
CFR Title: 

Content:
tailed design element to the specific inspections, analyses, or tests that will be used to confirm that the element has been correctly implemented. Verifiability means that it is possible to construct specific analyses, reviews, and tests to verify that the code correctly implements the detailed design. B.3.3.4.3 Review Guidance for CL In addition to the above, the CL should have sufficient comments and annotations that the intent of the code developer is clear. This is not only so the reviewer can understand and follow the code, but also so future modifications of the code are facilitated. Undocumented code should not be accepted as suitable for use in safety-related systems in nuclear power plants. The documentation should be sufficient 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. BTP 7.14-61 Revision 5 - March 2007 B.3.3.5 Integration Activities - System Build Documents (SBDs) 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