VCRM stands for verification cross reference matrix (VCRM). Basically it’s a method to ensure and direct how to meet Technical Specifications (TS) requirements of a project.
The VCRM is commonly used in a development type projects, prepared by the organization which initiates the project ( the Customer) and is forwarded to the organization which is tasked to execute the project (the Provider) as part of the overall Contract Data Requirement List (CDRLs) in the early stages of the project.
The VCRM is usually discussed and agreed between the Customer and the Provider (especially in a development projects) in advance as it may impose a great burden on the provider with heavy costly tag price for the Customer.
The format:
All the TS requirements are listed one by one in the left column of the table. The requirements are copied from the TS.
Next column shows the source of the requirement from the TS (Clause No, Page etc’)
Methods of verification:
Next, the table will show in what way the TS requirements are to be verified in one or more of the five (5) ways
- Inspection: Verifying the subject requirement is met by performing an inspection on the system. This could be a visual inspection or with the aid of a sensor
- Clarification: Verifying the subject requirement is met by clarifying it with an objective proof or neutral third party statement.
- Analysis: Verifying the subject requirement is met by making an analysis/calculation
- Demonstration: Verifying the subject requirement is met by performing a demo (not on the real system).
- Test: Verifying the subject requirement is met by operating the real system and testing it to the extent that shows the requirement is met.
Test Responsibility: Will identify within the provider structure who is responsible to perform the verification act
Ref: Will identify the verification document or proof Ref No.
The Customer is to fill columns b to h in the table below as a direction to the Provider to allow him planning and pricing the project
