Second Edition. – Boston: Kluwer Academic Publishers. – 2004. – 405 p. You may have heard that this is a book about verification and now you’re wondering why it’s called Assertion-Based Design, and not Assertion-Based Verification. The answer to that is one of the driving forces in this book: Verification doesn’t happen in a vacuum. Specification has to occur before any form of verification, and as you know, specification occurs very early in the design cycle. Thus, our contention is that assertion specification is one of the integral pieces of a contemporary design cycle. Every design engineer should read this book! Design engineers that add assertions to their design will not only reduce the time needed to complete a design, they will also reduce the number of interruptions from verification engineers to answer questions about design intent and to address verification suite mistakes. Every verification engineer should read this book! The smart verification engineer will assist the design engineer to add assertions to the RTL-design code because the sooner a design engineer understands the usage and benefits of inserting assertions into the design, the more valuable that design engineer will be to the verification effort. These three verification specialists have written a book that will endow the reader with an understanding of the fundamental and important topics needed to comprehend and implement assertion based design. Table of Contents
Assertion Methodology
Specifying RTL Properties
PLI-Based Assertions
Functional Coverage
Assertion Patterns
Assertion Cookbook
Specifying Correct Behavior
Open Verification Library
PSL Property Specification Language
System Verilog Assertions