Previous Section Next Section

1.4 Summary

Verification methodologies have evolved over the years from a simple HDL task-based methodology to a complete verification automation system. With designs today reaching a few million gates, verification automation systems are now required to maximize productivity of the verification process.

e provides all constructs needed to build an integrated verification automation system in an object oriented manner and an aspect oriented manner. Currently, the Specman Elite tool from Verisity Design supports the e language. Other tools may support e in the future.

e can be used to construct components to do the following functions in a verification environment:

Generation

e automates the generation of stimuli. Input stimuli are generated based on the constraints provided by the verification engineer.

Driving Stimulus

After the test vectors are generated, they must be driven on to the DUT. e provides a simulator interface and the necessary mechanism to drive the DUT.

Collecting Output

After the stimulus is applied to the DUT, output is produced from the DUT. This output must be collected and checked. e provides a simulator interface and the necessary mechanism to receive data from the DUT.

Data Checking

After the output data are received from the DUT, the data must be checked. Data value checks compare the output data values against the expected data. Temporal assertions monitor the functional protocol at important interfaces.

Coverage

Functional coverage results tell the verification engineer if the test plan goals have been met. There are three types of coverage: basic item coverage, transition item coverage, and cross coverage.

Previous Section Next Section