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:
should exist to track and report resource expenditures. Sufficient resources should exist to carry out the defined tasks. The plan should ensure that quality assurance budgets, safety budgets, and V&V budgets not be subject to expropriation by the software development organization, in order to maintain financial independence of these assurance activities. Methods/tools requires a description of the means used to manage the project. The plan should identify the methods, techniques and tools required to carry out the project management, including office equipment, computer hardware, and computer software. Personnel requires a specification of the numbers, qualifications, training and types of personnel required to conduct the project. Personnel resources for each project phase should be listed. Safety and V&V personnel should be competent in software engineering in order to ensure that software safety and software V&V are effectively implemented. b. Software Development Plan The software development plan describes the plan for technical project development. It may be part of a general company software management plan, may be project specific, or may be split among various management plans. The software development plan should exhibit the management, implementation and resource characteristics listed below. Management Characteristics The management characteristics that the software development plan should exhibit include purpose, organization, oversight, and risks. Purpose requires a description of the objectives of each life cycle phase and its context within the overall project. Organization describes the software life cycle that will be used in the project. The life cycle should include uniquely identifiable development, verification and support processes with well-defined inputs Rev. 4 — June 1997 Appendix 7-A BTP HICB-14-12 and outputs. The life cycle model should be documented in the plan. Reg. Guide 1.173, "Development Software Life Cycle Processes for Digital