Making Verification Methodology and Tool Decisions
This is the second of a three parts series. Part 1 can be found here
Are you itching to try a new methodology or technology to enhance your existing processes? Are you certain that management will resist change? Read on and learn how to use the new field of metric-driven engineering to objectively justify your decisions using automatically gathered data.
It happens all the time in engineering. A new process or methodology comes along. It looks attractive, your gut tells you this is the way to go, but adopting it requires one the big three 'scary' things:
- Risk (We've never done this before, will it work?)
- Cultural change (You want my designers to write assertions?)
- Spending money (Are you sure that tool will pay for itself?)
|
Cadence Hot IP
Related Articles
- Formal-based methodology cuts digital design IP verification time
- Methodology Independent Exhaustive Constraint Solver for Random Verification and Regression Generation
- Efficient methodology for design and verification of Memory ECC error management logic in safety critical SoCs
- Metric Driven Verification of Reconfigurable Memory Controller IPs Using UVM Methodology for Improved Verification Effectiveness and Reusability
- Efficient methodology for verification of Dynamic Frequency Scaling of clocks in SoC
New Articles
- From a Lossless (~1.5:1) Compression Algorithm for Llama2 7B Weights to Variable Precision, Variable Range, Compressed Numeric Data Types for CNNs and LLMs
- Embracing a More Secure Era with TLS 1.3
- New PCIe Gen6 CXL3.0 retimer: a small chip for big next-gen AI
- Maximizing ESD protection for automotive Ethernet applications
Most Popular
E-mail This Article | Printer-Friendly Page |