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 82.
14. lappuse
... interface to query the behavior of the model to check for results and to flag incorrect behavior. Formal verification, a newer technique, is a great complement to simulation. Rather than verifying possible input sequences and internal ...
... interface to query the behavior of the model to check for results and to flag incorrect behavior. Formal verification, a newer technique, is a great complement to simulation. Rather than verifying possible input sequences and internal ...
20. lappuse
... Interface protocol specifications should come from an independent designer or from master documentation, rather than from the designer whose logic is under test. However, for many reasons, the design team is crucial to. 1.4.1. Engineering.
... Interface protocol specifications should come from an independent designer or from master documentation, rather than from the designer whose logic is under test. However, for many reasons, the design team is crucial to. 1.4.1. Engineering.
21. lappuse
... interface specifications and details on the internals of the design such as queue depth, pipeline length, array sizes, and state machine transitions. This information guides the verification team in creating complete test plans and ...
... interface specifications and details on the internals of the design such as queue depth, pipeline length, array sizes, and state machine transitions. This information guides the verification team in creating complete test plans and ...
38. lappuse
... interfaces and functionality tend to change often. During the design phase, engineers often uncover problems that make ... interface protocols to and from the unit are correct; that is, the neighboring units contained in higher levels ...
... interfaces and functionality tend to change often. During the design phase, engineers often uncover problems that make ... interface protocols to and from the unit are correct; that is, the neighboring units contained in higher levels ...
39. lappuse
... interface and application parameters in which the design team will place the core. Engineers can be very creative ... interface boundaries. The purpose of this verification is to ensure that the units are properly connected and that the ...
... interface and application parameters in which the design team will place the core. Engineers can be very creative ... interface boundaries. The purpose of this verification is to ensure that the units are properly connected and that the ...
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