Document: NUREG-0800
Document ID: c90016c6-e03f-4224-8ff3-87a6f7d3ca42
Document Type: srp
Title: Appendix 7-A
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML0525/ML052500547.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7
CFR Part: 
CFR Title: 

Content:
lem report, traceability should exist between the problem report and the change. Software changes should be traced to their point of origin, and the software processes affected by the change should be repeated from the point of change to the point of discovery. Proposed changes should be reviewed by the CCB for their impact on system safety. Status accounting should take place for each set of life cycle activities prior to the completion of those activities. The status accounting should document configuration item identifications, baselines, problem report status, change history and release status. The configuration management organization should audit life cycle activities to confirm that configuration management procedures were carried out in the life cycle process implementation. 3.3. Acceptance Criteria for Software Life Cycle Process Design Outputs This section 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. Appendix 7-A Rev. 4 — June 1997 BTP HICB-14-29 Formal or semiformal methods are available for use in preparing some of the design outputs described in this section. Section C.3 of Appendix 7.0-A describes the benefits of using such methods and the precautions that should be observed when reviewing design outputs prepared with such methods. Acceptance criteria are divided into two sets: functional characteristics and process characteristics, as shown in the following table. Not all characteristics occur for every design output. Functional Process Characteristics Characteristics Accuracy Completeness Functionality Consistency Reliability Correctness Robustness Style Safety Traceability Security Unambiguity Timing Verifiability a. Requirements Activities & Software Requirements Specification An SRS that exhibits the functional and the software development process