Document: NUREG-0800
Document ID: fea61ff0-f344-4101-adfb-590e3d9dfafe
Document Type: srp
Title: Draft Revision 6 – August 2015
Source: NUREG-0800
Source URL: https://www.nrc.gov/docs/ML1515/ML15159A946.pdf
Revision Date: 2023-06
Chapter: 7
Section ID: 7
CFR Part: 
CFR Title: 

Content:
l plans, specific to particular teams (i.e., the SVVP includes the testing activities performed by the SVVT, and the software development plan includes the testing activities performed by the software development team, with testing activities being coordinated by the TP). Plans other than those defined in this BTP should still contain all of the required information and meet all of the acceptance criteria in this BTP. Acceptance criteria are divided into three sets: management characteristics, implementation characteristics, and resource characteristics. Each of these is further divided into specific characteristics, as shown in the following table. Not all specific characteristics occur for every plan. Management Implementation Resource Characteristics Characteristics Characteristics Purpose Measurement Budget Organization Procedures Methods/tools Oversight Record keeping Personnel Responsibilities Schedule Standards Risks Security All planning documents should be evaluated for the following process characteristics: consistency, style, traceability, unambiguity and verifiability. Consistency - Each plan should be internally consistent, and the complete set of plans should be mutually consistent. BTP 7.14-12 Draft Revision 6 - August 2015 Style - Plans should be documented so that they can be understood both by the users of the plan and by the reviewers. Traceability - The software management plan should be traceable back to system management planning; the remaining software plans should be traceable back to the software management plan; and the various process implementation documents and the design outputs should be traceable back to the relevant plans. Unambiguous - The set of plans should not be ambiguous. Verifiable - It should be possible to verify that the plans have been followed during the software project. The review and assessment of the quality of the plans provide a means of judging the competency of the development organization and management. It might