Managing Software Deliverables: A Software Development Management Methodology

The process of determining the correctness of the final product, system, or system component with respect to the user's requirements. Answers the question, Am I building the right product? Compare with verification.

A measure of the relative effort to verify a requirement; a requirement is verifiable only if there is a finite cost-effective process to determine that the software product or system meets the requirement.

The process of determining whether the products of a life cycle phase fulfill the requirements established during the previous phase; answers the question, "Am I building the product right?" Compare to validation.

A formal document that describes the process to verify and validate the requirements. Created during the Planning phase and updated throughout the project.

An initial release or rerelease of a computer software configuration item, associated with a complete compilation or recompilation of the computer software configuration item; sometimes called a build. See build.

A formal document that describes the exact version of a configuration item and its interim changes. It is used to identify the current version; provides a packing list of what is included in the release.

In requirements management, the degree to which requirements are expected to change throughout the Systems Development Life Cycle; opposite of stability.