Comprehensive Functional Verification: The Complete Industry CycleElsevier, 2005. gada 26. maijs - 704 lappuses One of the biggest challenges in chip and system design is determining whether the hardware works correctly. That is the job of functional verification engineers and they are the audience for this comprehensive text from three top industry professionals.As designs increase in complexity, so has the value of verification engineers within the hardware design team. In fact, the need for skilled verification engineers has grown dramatically--functional verification now consumes between 40 and 70% of a project's labor, and about half its cost. Currently there are very few books on verification for engineers, and none that cover the subject as comprehensively as this text. A key strength of this book is that it describes the entire verification cycle and details each stage. The organization of the book follows the cycle, demonstrating how functional verification engages all aspects of the overall design effort and how individual cycle stages relate to the larger design process. Throughout the text, the authors leverage their 35 plus years experience in functional verification, providing examples and case studies, and focusing on the skills, methods, and tools needed to complete each verification task.
|
No grāmatas satura
1.–5. rezultāts no 80.
xxi. lappuse
... verifying that design. While experience is important for a successful verification effort, so is a core understanding of verification theory, strategy, and available methods. Over the last 20 years, a strong verification team has become ...
... verifying that design. While experience is important for a successful verification effort, so is a core understanding of verification theory, strategy, and available methods. Over the last 20 years, a strong verification team has become ...
12. lappuse
... verification engineers break the problem down into smaller pieces. A typical chip may have 100,000 latches, imbedded arrays, and hundreds of input pins. Rather than verify the entire chip at once, the verification team will carve out ...
... verification engineers break the problem down into smaller pieces. A typical chip may have 100,000 latches, imbedded arrays, and hundreds of input pins. Rather than verify the entire chip at once, the verification team will carve out ...
16. lappuse
... verification and a systems test, can show up in customer environments and cause quality problems. Because verification has such a strong effect on the triple constraints, it is prudent to track verification productivity. The design team ...
... verification and a systems test, can show up in customer environments and cause quality problems. Because verification has such a strong effect on the triple constraints, it is prudent to track verification productivity. The design team ...
18. lappuse
... verification team should find any “easy” or low-quality bugs early in the verification schedule. Throughout the process, the average complexity of the design flaws that the verification team uncovers should grow. Simple bugs found late ...
... verification team should find any “easy” or low-quality bugs early in the verification schedule. Throughout the process, the average complexity of the design flaws that the verification team uncovers should grow. Simple bugs found late ...
20. lappuse
... team measures its success by results in system testing. So how does the development team gauge just how many resources to put into verification? Too ... VERIFICATION 1.4.1 Engineering Costs and the Need for an Independent Verification Team.
... team measures its success by results in system testing. So how does the development team gauge just how many resources to put into verification? Too ... VERIFICATION 1.4.1 Engineering Costs and the Need for an Independent Verification Team.
Saturs
3 | |
SIMULATIONBASED VERIFICATION | 139 |
FORMAL VERIFICATION | 437 |
COMPREHENSIVE VERIFICATION | 537 |
CASE STUDIES | 601 |
VERIFICATION GLOSSARY | 641 |
REFERENCES | 657 |
SUBJECT INDEX | 663 |
Citi izdevumi - Skatīt visu
Comprehensive Functional Verification: The Complete Industry Cycle Bruce Wile,John Goss,Wolfgang Roesner Ierobežota priekšskatīšana - 2005 |
Comprehensive Functional Verification: The Complete Industry Cycle Bruce Wile,John C. Goss,Wolfgang Roesner Priekšskatījums nav pieejams - 2005 |
Bieži izmantoti vārdi un frāzes
abstraction algorithm array assertions behavior blocks Boolean cache Calc1 Calc2 cation Chapter checker checking components chip clock command complete constraints create debug design team design under verification drive error escape analysis event-driven example execution Figure formal verification functional verification FV tools hardware hardware description language ification implementation initial input instruction stream interface language latches level of verification logic memory microprocessor monitor multiple occur on-the-fly opcode OpenVera operand operation output packet parameters performance pipeline port problem processor property specification language protocol queue random re-use reference model regression requires reset scan ring scenarios scoreboard sequence signal simulation engine specification stimulus component structure tape-out test bench tion transaction unit update valid verifica verification components verification cycle verification engineer verification environment verification plan verification team Verilog VHDL