Legacy development specifications typically organized their verification sections according to activity. In that case, it was necessary to indicate which verification requirements were relevant to each of the design-to requirements, each of which was considered to have been fully verified when all verification requirements indicated in the VCRI were successfully completed. This specification practice resulted in verification sections that clearly described each activity in narrative form.
Most modern specification practices enforce a 1:N relationship between design-to and verification requirements, in which case the VCRM/VCRI concept serves very little purpose.
In many ways, the legacy practice was far superior to the modern one: you could read such a specification and immediately understand the philosophy behind the verification.