Howard L. Martin, President, Zocalo Tech
Although Assertion-Based Verification (ABV) has proven to cut debug time in half and has been touted to be a major factor for reducing verification time and cost, wide spread acceptance has never materialized. The key to understanding the problem is the difference in the terms "Using Assertions" and "Assertion Based-Verification."
Most surveys reflect assertion use rather than ABV and the usage is still low, i.e., less than 40%. Designers are more likely to create and add assertions since they are intimately familiar with the intent of the design and many are capable of coding simple 1 or 2 cycle SystemVerilog Assertions (SVAs). Since assertion use is ad hoc and at their discretion, they are added in-line as part of the design file without documentation.
At the system level, useful SVAs typically require a higher level of complexity than at the block level. Temporal properties are the norm and since the verification engineer cannot modify the design files, bind files are required. Creating and managing bind files is a labor intensive task and the SVA language learning curve can be extensive for complex temporal expressions. Using assertions even on an ad hoc basis is sparse at the system level.
The problems that have limited ABV are:
Zocalo Tech products provide the ease of use and productivity required to make ABV a major part of the verification process in the next year. The product set marketed under the name Zazz includes products that can be used stand alone or combined. The combination of these products enables incremental adoption of ABV, while assessing the effectiveness each step along the way.