A Day in the Life of a Verification Requirement

Abstract

AbstractOne measure of the quality of a product requirement is that it be verifiable. Verifiability assessment is one of the exit criteria for the Systems Requirements Review and is necessary for requirement validity. Nomination of one or more verification methods (examination, analysis, demonstration or test) is often taken as the sole evidence of verifiability. A completed Verification Cross Reference Matrix is frequently considered as the final verifiability assessment and responsibility for the remainder of the verification effort is transferred to the test and evaluation and other implementing communities for completion.Lessons learned from many Programs have shown that a more robust application of systems engineering should include the requirements engineers (with detailed knowledge of product requirement intent) working with the verification implementing organizations as the best combination to define the verification requirements. Such definition should include statement of the verification objectives, success criteria and environment. Including this information in the “Quality Assurance” section of the requirements document allows for buy‐in by the customer well in advance of implementing the verification activities. This information is used by verification personnel to generate one or more verification plans and to develop the detailed verification program. Verification requirements are planned into verification events which are executed using the proper system elements and environments. These verification requirements are key to establishing long lead verification facilities, tools and laboratories. Early definition of these requirements helps prevent facility re‐designs and verification re‐plans that can cause expensive delays. Finally, verification data analysis is performed, and the information compiled into verification reports certifying system product requirements compliance. This robust verification approach will provide proof of requirements satisfaction, leading to systems that meet the customers' needs at a lower life‐cycle cost.This paper is written to explore the value of well‐crafted verification requirements developed early in the Program. A “Day in the Life of a Verification Requirement” shows the interaction and benefits of verification requirements to the verification execution teams. The reader will be offered a lifecycle description of the verification requirement from conception to certification.