A Multi Pradigm Verifiation Flow dave whipps Home Page多范例verifiation流戴夫惠普的主页.docVIP

下载本文档

4
0
约3.38万字
约 15页
2018-06-19 发布于福建
举报
版权申诉

A Multi Pradigm Verifiation Flow dave whipps Home Page多范例verifiation流戴夫惠普的主页.doc

1、有哪些信誉好的足球投注网站（book118）网站文档一经付费（服务费），不意味着购买了该文档的版权，仅供个人/单位学习、研究之用，不得用于商业用途，未经授权，严禁复制、发行、汇编、翻译或者网络传播等，侵权必究。。
2、本站所有内容均由合作方或网友上传，本站不对文档的完整性、权威性及其观点立场正确性做任何保证或承诺！文档内容仅供研究参考，付费前请自行鉴别。如您付费，意味着您自己接受本站规则且自行承担风险，本站不退款、不进行额外附加服务；查看《如何避免下载的几个坑》。如果您已付费下载过本站文档，您可以点击这里二次下载。
3、如文档侵犯商业秘密、侵犯著作权、侵犯人身权等，请点击“版权申诉”（推荐），也可以打举报电话：400-050-0827(电话支持时间：9:00-18:30)。
4、该文档为VIP文档，如果想要下载，成为VIP会员后，下载免费。
5、成为VIP后，下载本文档将扣除1次下载权益。下载后，不支持退款、换文档。如有疑问请联系我们。
6、成为VIP后，您将拥有八大权益，权益包括：VIP文档下载权益、阅读免打扰、文档格式转换、高级专利检索、专属身份标志、高级客服、多端互通、版权登记。
7、VIP文档为合作方或网友上传，每下载1次，网站将根据用户上传文档的质量评分、类型等，对文档贡献者给予高额补贴、流量扶持。如果你也想贡献VIP文档。上传文档

A Multi Pradigm Verifiation Flow dave whipps Home Page多范例verifiation流戴夫惠普的主页

DesignCon 2006 A Multi Paradigm Verification Flow Dave Whipp, NVIDIA /dv Abstract In a complex chip, many teams contribute blocks to the final result. Different blocks may have different verification needs: some of these differences are due to the technical nature of the blocks themselves; others derive from legacy constraints, and even the desire to experiment with a new approach or tool. This paper discusses a flow that melds together these competing needs. Author(s) Biography Dave Whipp is a Verification Architect at NVIDIA. He has 13 years of verification experience since graduating from UMIST (Manchester, UK) in 1992. Since then he has written several papers focusing on modeling techniques for verification, and is recently a contributing author to the IEC book, “The Functional Verification of Electronic Systems” (1). He currently lives in Santa Clara, CA. The User Interface to Verification A common role of the verification engineer is to create the infrastructure for running tests. This infrastructure supports the patterns of testing that are required for the project. This set of patterns, and the manner in which they are supported, is the “Verification Flow”. I like to think of this flow as being the user interface to verification. I use the term “User Interface” in a broad sense. In addition to interactive human users, I also consider scripts (and script writers) that need to interact with the flow. When I think about human users, I consider not just engineers using their favorite CLI or GUI, but also managers who may prefer a simple web-based status view. When constructing a verification flow, it is all too easy to succumb to the desire for simplicity. If we define only one way to do things then our user interface design becomes much simpler than if we must support a diverse set of users with competing requirements. I explore the reasons why the simple approach breaks down as the scope of the verification challenge increases. Once we decide that we need t