How to understand requirements of nuclear and defense welding contracts

This paper presents a basic requirements control plan for contract documentation and software validation and maintenance for nuclear operation. The objective is designing an integrated configuration control plan of both old, new, large or small, critical and noncritical software programs. There are positive advantages to managing a planned requirements program for product delivery or business operations. A requirements baseline like this is preferable to many iterations of design effort in the maintenance of nonbaselined programs, documentation and software. The plan that applies program requirements needs to address different levels of criticality and define matching program requirements for those levels. The plan needs to describe old vs. new requirements and define scope/responsibility that is needed to support the design, development and completion of these program requirements. Presented are management goals, relative costs, quality assurance goals, and program assessment plans. Outlined is a set of program QA requirements and document/software functional requirements for planning of program; also presented are some criteria for criticality assessment to establish levels of contract documentation or software activity. The paper shows two examples of planning work on this configuration control plan. The integrated configuration control requirements plan can be computer based or paper based for activity. It is designed to cover existing or new requirements and to cover either no documentation or all documentation