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

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
Parents

  • The key question is "What is the definition of success ?", since ASIC design first started designers (and many managers) define success as "Tapeout on time", Verification Engineers define success as "working silicon". and from the Company's perspective the market  may ultimately  define success.  Given exhaustive verification, even at the module level is becoming less and less likely, the definition of success becomes blurred into "to find and fix all the critical bugs that can be reasonably found given the resources available in a timely manner" ... not exactly black and white. Proper planning is the only way to manage a project with such a complex goal with any certainty of achieving a successful outcome.


    Originally posted in cdnusers.org by nick_heaton
Reply

  • The key question is "What is the definition of success ?", since ASIC design first started designers (and many managers) define success as "Tapeout on time", Verification Engineers define success as "working silicon". and from the Company's perspective the market  may ultimately  define success.  Given exhaustive verification, even at the module level is becoming less and less likely, the definition of success becomes blurred into "to find and fix all the critical bugs that can be reasonably found given the resources available in a timely manner" ... not exactly black and white. Proper planning is the only way to manage a project with such a complex goal with any certainty of achieving a successful outcome.


    Originally posted in cdnusers.org by nick_heaton
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.