User:Ricknordin

Model-based Functional Verification

Functional Verification is in need of change. For years, the state of the art technology for scenario generation - the core targeting capabilities for dynamic functional verification testbenches - has been constrained random generation. While this is a step up in automation from directed test generation, it still lacks the targeted nature of a hand written scenario. A revolution in functional verification efficiency and productivity is needed to accompoish the following:

Speed -- Reducing the time required to generate and check tests that verify the design. The time to first test and effectiveness of regression are critical to improving the speed of verificaiton.

The testbench must be able to leverage existing verification components where it makes sense and to easily create new models efficiently from scratch.

Flexibility -- Today's verification environments must be flexible enough to be leveraged into FPGA, Lab and System level verification and validation solutions.

The testbenchh must be able to represent all structure and protocol types in a concise fromat that allows for all possible conditions to be constructed.

Incremental Development -- In most designs, the RTl is ready for verification late, causing the verification team to scramble. Provisions for incremental development and verificaiton allows the design and DV teams to better solve smaller problems.

Coverage -- One of the hardest parts of verificaiton is knowing when it's done. With a visible means of seeing what has been accomplished, the question "Is it done yet?" can be answered with more certainity. There must be a closed loop verification process that is used to define completeness.

Reuse / retarget -- Size and complexity issues are always increasing and the testbench must be able to support reuse - both veritical and horizontal.

This revoloution is Model-Based Functional Verification.