Verification Planning and Requirements

A key activity of any verification effort is to capture a Verification Plan (aka Test Plan or just testplan). This document is not that. The purpose of a verification plan is to identify what features need to be verified; the success criteria of the feature and the coverage metrics for testing the feature. Refer to Verification Planning 101 for a tutorial on how verification planning of CORE-V IP is done.

The Verification Strategy (this document) exists to support the Verification Plan. A trivial example illustrates this point: the CV32E40P verification plan requires that all RV32I instructions be generated and their results checked. In this case, the testbench needs to have these capabilities and its the purpose of the Verification Strategy document to explain how that is done.