• Skip to main content
  • Skip to search
  • Skip to footer
Cadence Home
  • This search text may be transcribed, used, stored, or accessed by our third-party service providers per our Cookie Policy and Privacy Policy.

  1. Community Forums
  2. Functional Verification
  3. In what aspects is verification different from design?

Stats

  • Locked Locked
  • Replies 8
  • Subscribers 64
  • Views 15865
  • Members are here 0
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

In what aspects is verification different from design?

archive
archive over 19 years ago

Hi,
            I will be co-moderating this board together with Stylianos, a formal introduction will come sometime later.
 
            It appears to me that recently there has been a significant interest in designing new methods for verification planning. Classic methods of planning have been known to result in late releases (in some projects multiple months late) and unpredictable quality.
 
            I believe this forum could become a catalyst to understanding the underlying problem we are trying to solve, and to both discuss and shape the solutions that are taking form.
 
            To trigger some discussion, I want to pose a simple question: In what ways is Verification different from Design? (ways which might affect planning)
 
            I believe if we clarify this question, we can better understand why some of the classic methods fail with verification.
 
            Looking forward to your responses,
 
                                                            Akiva


Originally posted in cdnusers.org by Akiva
  • Cancel
Parents
  • archive
    archive over 19 years ago

    [ Previous post ran into formatting issues... ]

    Maybe some core differences are also cultural?

    If a project succeeds, the designer did a great job.
    If a projects fails, the verifier did a lousy job.

    Why then? Well, since we all want the design to succeed, verifiers are really going up against team spirit, aren't they? When a block is "done", they are the ones that make us go back to the drawing board and do it again. They are the ones that make us give management bad news when the week before we reported things were going great. And they are the ones that will never give us a straight answer! (does it work, are you done, when will you be done, what more do you need in order to be sure, etc...) ;-)

    At the end of the day, all too often verification engineers are the "bad guys". So maybe planning can be an effective way not only to predict, organize and manage the project, but also to help prevent those poor verification guys from getting all that bad vibe :-)

    PS: Feel free to substitute the <..> fields for your favorite metric of success...


    Originally posted in cdnusers.org by stelix
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Reply
  • archive
    archive over 19 years ago

    [ Previous post ran into formatting issues... ]

    Maybe some core differences are also cultural?

    If a project succeeds, the designer did a great job.
    If a projects fails, the verifier did a lousy job.

    Why then? Well, since we all want the design to succeed, verifiers are really going up against team spirit, aren't they? When a block is "done", they are the ones that make us go back to the drawing board and do it again. They are the ones that make us give management bad news when the week before we reported things were going great. And they are the ones that will never give us a straight answer! (does it work, are you done, when will you be done, what more do you need in order to be sure, etc...) ;-)

    At the end of the day, all too often verification engineers are the "bad guys". So maybe planning can be an effective way not only to predict, organize and manage the project, but also to help prevent those poor verification guys from getting all that bad vibe :-)

    PS: Feel free to substitute the <..> fields for your favorite metric of success...


    Originally posted in cdnusers.org by stelix
    • Cancel
    • Vote Up 0 Vote Down
    • Cancel
Children
No Data

Community Guidelines

The Cadence Design Communities support Cadence users and technologists interacting to exchange ideas, news, technical information, and best practices to solve problems and get the most from Cadence technology. The community is open to everyone, and to provide the most value, we require participants to follow our Community Guidelines that facilitate a quality exchange of ideas and information. By accessing, contributing, using or downloading any materials from the site, you agree to be bound by the full Community Guidelines.

© 2025 Cadence Design Systems, Inc. All Rights Reserved.

  • Terms of Use
  • Privacy
  • Cookie Policy
  • US Trademarks
  • Do Not Sell or Share My Personal Information