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:
nd track purchased items, such as software tools used to make the final product. A qualification procedure should be provided, and a method of tracking tool history, buglists, and errata sheets should enable the applicant/licensee to track which design outputs may be affected by discovered tool or purchased item deficiencies. The plan should describe procedures to control vendors supplying safety system software. Record keeping requires a description of the software CM record keeping requirements. The plan should identify required CM records. Record structures (such as an annotated table of contents) should be provided. Procedures should exist for protecting configuration items. The plan should describe how configuration items will be stored, handled, retained and shipped. A tracking system should exist for managing configuration items, so that the revision history of each configuration item may be retrieved, and so that the latest revision of each configuration item may be easily identified. Procedures should exist for backup and disaster recovery. Rev. 4 — June 1997 Appendix 7-A BTP HICB-14-26 Resource Characteristics The resource characteristics that the software CM plan should exhibit include methods/tools and standards. Methods/tools requires a description of the means that will be used to carry out each CM task. The plan should identify suitable facilities, methods, techniques and tools to facilitate the performance of the CM work. The plan should specify a process for selecting configuration management tools. The hardware and software environment within which the CM tools are to be applied and any necessary controls should be described. Standards requires a list of the international, national, industry and company standards and guidelines to be followed by the software CM organization. 3.2. Acceptance Criteria for Software Life Cycle Process Implementation This section addresses acceptance criteria for implementation activities. The acceptance criteria