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:
d be described. All variables in the physical environment that the software *Implementation of safety functions should not rely upon a date (calendar time). Actions depending upon calendar time should account for concerns such as those identified with the year 2000 (two-digit 00). BTP 7.14-55 Revision 6 - August 2016 must monitor and control should be fully specified. Functional requirements should describe: how each function is initiated; (2) the input and output variables required of the function; (3) the task sequences, actions, and events required to carry out the function; and (4) the termination conditions and system status at the conclusion of the function. User interfaces should be fully described for each category of user. Consistency means that the contents of the SRS are consistent with the safety system requirements, the safety system design, and documented descriptions and known properties of the operational environment within which the safety system software will operate. Individual requirements should not contradict other requirements. Timing requirements should be consistent with thermo-hydraulic analyses performed in the system safety analysis. Uniform and consistent terminology, notation, and definitions should be used throughout the SRS. Correctness means that the description of actions required of the computer system are free from faults and that no other requirements are stated. The operational environment within which the software will operate should be accurately described. All variables in the physical environment that the software must monitor and control should be properly specified. Functional requirements should accurately describe: (1) how each function is initiated; (2) the input and output variables required of the function; (3) the task sequences, actions and events required to carry out the function; and (4) the termination conditions and system status at the conclusion of the function. Style means that the contents of the SRS are