Mentor Coverage Cookbook - Testplan

The cookbook explains that the Testplan is a “subset” of design functionality which has been chosen to be verified. Therefore, it could stand that upon reaching coverage closure, there are some features which have not been verified. agree/disagree?

Is there a separate list of requirements used by the designer/implementer that represents 100% the features of the DUT?

Where I’m going with this is… trying to determine if the designer/implementer is working off the verification engineer’s Testplan, or a seperate document entirely.

In reply to bmorris:

I do not agree the testplan is a subset of design functionality. A testplan is a seperate document in a special format which defines the architecture of the verification environment and a list of verification requirements elaborated from the design requirments. Additionally it contains defines links between the verification reqs and the coverage model (functional and code), directives and scoreboard results. I’m using typically an Excel-sheet which summarizes all design and verification requirements as well as the links I mentioned above. This format can be read by the simulator and describes the verification objectives. After each simualtion run you can evaluate against the plan, indicating the verification progress.

In reply to chr_sue:

I like how you describe it as “verification requirements elaborated from the design requirements”. This was mindset I was leaning towards.

When they describe it as a subset of design functionality, I believe they are referring to the fact that you could always add more verification requirements; you cannot verify everything for any non-simple design.

thanks for the response.

In reply to bmorris:

To get a more detailed figure you can download an example plan from here

In reply to chr_sue:

found it. thanks.