 |
| |
Planning for assertion-based verification
Hamilton Carter, Cadence Design Systems
(01/15/2007 9:00 AM EST), EE Times
One concern that is frequently raised when planning design assertions is: "How do we know that we wrote assertions that correspond to all of the behaviors of the device?" In other words, how can it be confirmed that a complete set of checks has been achieved for the features implemented by the design block?
The answer is actually quite simple. Taking a page from software engineering, we'll use an extreme-programming concept. Put concisely, this is an edict that says:
• "No implementation will be performed until a test case exists for the planned implementation."
As implementers determine which features to implement and how to implement them, they first determine how those features will be tested. Only after implementing the test case do they begin implementation of the feature itself.
|
||||||
|
||||||
|
E-mail This Article |
|
|
Printer-Friendly Page |
 | ||
|
|
|
| ||
|
Related Articles
|
|
|
|
|
| ||
|
Related
|
|
|
|
|
| ||
|
Cadence Design Systems, Inc. Hot IPs
|
|
|
|
|
| ||
 |
Latest Articles
|
|
|
PRODUCT HOW-TO: The care and feeding of embedded Linux running on MIPS CPUs
Clock Mesh Variation Robustness: Benefits and Analysis
Rapid debug of serial buses in FPGAs
Embedded Software Architecture Specification Developments in Support of SoC Design and Re-use
Debugging of embedded Linux applications on ARM9/ARM11 processors
| |
| ||
|
Most Popular (Updated Daily)
|
|
|
|
|
| ||
| © 2009 Design And Reuse All Rights Reserved. No portion of this site may be copied, retransmitted, reposted, duplicated or otherwise used without the express written permission of Design And Reuse. Read our privacy guidelines. Contact us. |
 |
|
|