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
6.–10. rezultāts no 84.
21. lappuse
... drive down the number of required verification engineers. Other factors such as business pressure will alter the equation. For example, a small company in a highly competitive market such as network processors must get their new ...
... drive down the number of required verification engineers. Other factors such as business pressure will alter the equation. For example, a small company in a highly competitive market such as network processors must get their new ...
26. lappuse
... drive requirements on the software procurement team or on internal software development teams (Chapters 5, 6). s Completion criteria—define the measurements that indicate that verification is complete (Chapter 13). s Resources (people ...
... drive requirements on the software procurement team or on internal software development teams (Chapters 5, 6). s Completion criteria—define the measurements that indicate that verification is complete (Chapter 13). s Resources (people ...
28. lappuse
... drive different input scenarios each time the team runs the test. The second reason is that the team must repeat all tests after fixes have been applied to the design. The failure occurrence rate drops as the verification cycle reaches ...
... drive different input scenarios each time the team runs the test. The second reason is that the team must repeat all tests after fixes have been applied to the design. The failure occurrence rate drops as the verification cycle reaches ...
31. lappuse
... drive to maintain a schedule overshadows quality. However, in the end, both schedule and quality suffer when the ... driving stimulus and checking for bugs are the pillars of functional verification. The foundation under these two ...
... drive to maintain a schedule overshadows quality. However, in the end, both schedule and quality suffer when the ... driving stimulus and checking for bugs are the pillars of functional verification. The foundation under these two ...
35. lappuse
... driving stimuli and detecting errors is vital to verification. With driving stimuli and detecting errors as the underlying requirement, it is useful to understand the roots of today's verification methodologies. Early verification ...
... driving stimuli and detecting errors is vital to verification. With driving stimuli and detecting errors as the underlying requirement, it is useful to understand the roots of today's verification methodologies. Early verification ...
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 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 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 test bench components tion transaction unit update valid verifica verification components verification cycle verification engineer verification environment verification plan verification team Verilog VHDL