Purpose:

Ensure that selected work products meet their specified requirements.

Objective:

Establishes organizational expectations to ensure that the acquirer’s selected work products meet specified requirements.

Description:

Acquisition verification addresses whether the acquirer’s work products properly reflect specified requirements.

Verification is inherently an incremental process because it occurs throughout the acquisition of the product or service, beginning with the verification of requirements and plans, progressing through the verification of evolving work products, and culminating in the verification of the completed product.

Acquisition Verification is built on each other in the following way:

• • The Select Work Products for Verification specific practice enables the identification of work products to be verified, methods to be used to perform the verification, and documented requirements to be satisfied by each selected work product.
  • The Establish the Verification Environment-specific practice enables the selection or creation of the environment to be used to carry out the verification.
  • The Establish Verification Procedures and Criteria specific practices enable the development of verification procedures and criteria that are aligned with selected work products, requirements, methods, and characteristics of the verification environment.
  • The Prepare for Peer Reviews, Conduct Peer Reviews, and Analyze Peer Review Data-specific practices enable the conduct of peer reviews, an important type of verification that is a proven mechanism for effective defect removal.
  • The Perform Verification-specific practice enables the conduct of verification according to established methods, procedures, and criteria.
  • The Analyze Verification Results specific practice enables analysis of verification results against established criteria.

Entrance Criteria:

• Work products are self-verified by the Owner (spell/grammar check, adherence to standards, templates, or clean compile in case of source code).
• Supporting documents and references used as basis or references to produce the work product are identified and made easily accessible for Reviewers.
• Reviewers and Moderators are trained in Conducting Peer Reviews as per IO’s Guidelines.
• Work products are self-verified by the Owner (spell/grammar check, adherence to standards, templates, or clean compile in case of source code).
• Supporting documents and references used as basis or references to produce the work product are identified and made easily accessible for Reviewers
• Reviewers and Moderators are trained in Conducting Peer Reviews as per IO’s Guidelines

Exit Criteria:

• Lists of Work Products Selected for Verification
• Verification Methods for each Selected Work Product
• Verification Environment
• Verification Procedures
• Verification Criteria
• Identified defects for the work product are logged in Review Log.
• Review Log archived as per Project Data Management Process
• The identified defects for the work product are fixed and verified if necessary before obtaining approval from the work product owner.
• Identified defects for the work product are logged in Review Log.
• Review Log archived as per Project Data Management Process
• The identified defects for the work product are fixed and verified if necessary before obtaining approval from the work product owner.

Process and Procedures:

• Prepare for Verification
• Perform Peer Reviews
• Verify Selected Work Products

Tailoring Guidelines:

• None

Process Verification Record(s):

• E-mail communicating the Review Schedule
  • Stored By: Facilitator
• Review Log(s)
  • Stored By: Facilitator
• Peer Review Summary Report
  • Stored By: Facilitator
• E-mail communicating the Review Schedule
  • Stored By: Facilitator
• Review Log(s)
  • Stored By: Facilitator
• Peer Review Summary Report
  • Stored By: Facilitator

= = = 

• Lists of work products selected for verification
  • Stored By: <?>
• Verification methods for each selected work product
  • Stored By: <?>
• Verification environment
  • Stored By: <?>
• Verification procedures
  • Stored By: <?>
• Verification criteria
  • Stored By: <?>

= =  =

Measure(s):

• Number of defects detected by each defect severity
  • Maintained By: Facilitator
  • Submitted By: Facilitator
  • Frequency of Submission: Reported at the end of the Peer Review and throughout the Peer Review Summary Report
• Number of modifications by defect severity
  • Maintained By: Work Product Owner
  • Submitted By: Work Product Owner
  • Frequency of Submission: Recorded at the end of each review
• Actual time spent on review
  • Maintained By: Work Product Owner
  • Submitted By: Work Product Owner
  • Frequency of Submission: Recorded at the end of each review
• Number of defects detected by each defect severity
  • Maintained By: Facilitator
  • Submitted By: Facilitator
  • Frequency of Submission: Reported at the end of the Peer Review and throughout the Peer Review Summary Report

= = = 

• Identify work products for verification.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Identify requirements to be satisfied by each selected work product.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Identify verification methods available for use.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Define verification methods to be used for each selected work product.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Submit for integration with the project plan the identification of work products to be verified, the requirements to be satisfied, and the methods to be used.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Identify verification environment requirements.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Identify verification resources that are available for reuse or modification.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Identify verification equipment and tools.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Acquire verification support equipment and an environment (e.g., test equipment, software).
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• As necessary, generate a set of comprehensive, integrated verification procedures for work and commercial off-the-shelf products.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Develop and refine verification criteria as necessary.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Identify the expected results, tolerances allowed, and other criteria for satisfying the requirements.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>
• Identify equipment and environmental components needed to support verification.
  • Maintained By: <?>
  • Submitted By: <?>
  • Frequency of Submission: <?>

References:

• CMMI^® for Development, Version 1.3, Software Engineering Process Management Program, November 2010
• CMMI^® for Acquisition, Version 1.3, Software Engineering Process Management Program, November 2010
• CMMI^® for Services, Version 1.3, Software Engineering Process Management Program, November 2010