The need for verification management
Ilana Golan, Cadence Design Systems
(06/05/2006 9:00 AM EDT), EE Times
Project management and automation are quickly becoming the most critical elements of the design and verification process. The key ingredients are good specification development and metric-based checkpoints. The ability to "begin with the end in mind" allows for optimal resource usage, much higher design quality and realistic schedule estimates for customers.
Today's design and verification flows often miss cross-functional problems. The flows tend to focus primarily on individual tasks, engine performance or languages, rather than on defining the entire verification challenge or team interdependencies. In fact, most verification plans are merely a set of incomplete discussion notes that atrophy as the project moves forward.
Good management of the design and verification process starts with specific goals that focus on what needs to be verified. Using those guidelines, an experienced verification team can develop and implement a plan that includes everything. Stakeholders can capture and review the verification plan to drive the design safely and smoothly to closure.
Successful verification management requires good analysis of the specification, an awareness of the scope of the job at hand, and a firm decision on what coverage models and metrics to track. Here are some of the basic do's and don'ts to keep in mind.
(06/05/2006 9:00 AM EDT), EE Times
Project management and automation are quickly becoming the most critical elements of the design and verification process. The key ingredients are good specification development and metric-based checkpoints. The ability to "begin with the end in mind" allows for optimal resource usage, much higher design quality and realistic schedule estimates for customers.
Today's design and verification flows often miss cross-functional problems. The flows tend to focus primarily on individual tasks, engine performance or languages, rather than on defining the entire verification challenge or team interdependencies. In fact, most verification plans are merely a set of incomplete discussion notes that atrophy as the project moves forward.
Good management of the design and verification process starts with specific goals that focus on what needs to be verified. Using those guidelines, an experienced verification team can develop and implement a plan that includes everything. Stakeholders can capture and review the verification plan to drive the design safely and smoothly to closure.
Successful verification management requires good analysis of the specification, an awareness of the scope of the job at hand, and a firm decision on what coverage models and metrics to track. Here are some of the basic do's and don'ts to keep in mind.
To read the full article, click here
Related Semiconductor IP
- Peripheral Sensor Interface (PSI5) Host Controller
- Link Acceleration Unit
- 64-bit, RISC-V, ultra-high performance processors
- 64-bit, RISC-V, performance and data computation processors
- 32-bit, RISC-V, deeply embedded processors
Related Articles
- Verification and Validation (V&V)-in-the-Loop for RISC-V Design: The Holistic Vision of BZL
- Efficient methodology for design and verification of Memory ECC error management logic in safety critical SoCs
- IC design: A short primer on the formal methods-based verification
- Handling the Challenges of Building HPC Systems We Need
Latest Articles
- Croc: Training the Next Generation Chip Designers on Domain-Specific End-to-End Open Source Silicon
- Design and Development of a Neuromorphic Silicon Suite: PVT Sensing, Stochastic LIF Inference, On-Chip STDP Learning, and Crossbar Programming
- LLM4RTL: Tool-Assisted LLM for RTL Generation
- Towards Delta Aware Training: Efficient DNN Weight Storage for Resource-Constrained FPGAs
- CHERI-D: Secure and efficient inline object ID for CHERI temporal memory safety