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:
B.3.3.2.2 Process Characteristics of SAD The software development process characteristics that the SAD should exhibit include completeness, consistency, style, traceability, and verifiability. Completeness means that all the software requirements are satisfied in the architecture. The SAD should address all operating modes specified in the SRS, including initialization, operational, shut-down, maintenance, and test modes. Consistency means that each software architectural element is compatible with the SRS, the hardware architecture, documented descriptions and known properties of the operational and hardware environment, and other software elements. Timing specifications of each software element should be consistent with the specifications of the other elements with which it interacts and with the expected performance of the system as a whole. Uniform and consistent terminology, notation, and definitions should be used. Style means that the contents of the SAD are understandable. The architecture description should conform to the developer's style guide. The architecture specification should contain the rationale for architectural decisions. Traceability means that a two-way trace exists between the requirements in the SRS and the elements in the architecture. A two-way trace should exist between the architectural elements and the detailed design elements. There should be a forward trace from each architectural element to the specific inspections, analyses, or tests that will be used to confirm that the element has been correctly designed. Verifiability means that it is possible to construct specific analyses, reviews, and tests to verify that the architecture satisfies the software requirements. BTP 7.14-57 Revision 5 - March 2007 B.3.3.2.3 Review Guidance for SAD The reviewer should be able to refer to this architecture to understand how the software works, the flow of data, and the deterministic nature of the software. The architecture should be sufficiently