How does DFD differentiate from verification or testing?
It’s interesting that phrase “design for debug” actually refers to something quite specific that is in fact related to our new product offering. Over the years we have thought about whether there is a design for debug in the general sense. Our conclusion was no. You pretty much design for everything else and debug needs to pick up the pieces so that you can comprehend what you have done. We didn’t actually coin this term design for debug. It’s a phrase that exists in the realm of silicon debug, another new buzz phrase that’s related to our visibility enhancement line. It turns out to be just a small part of what we are doing in visibility enhancement because VE works across the whole flow. It’s funny because we actually started thinking about visibility enhancement with respect to silicon debug and thus design for debug. Let me just take this hierarchally. Silicon debug is that part of the process where you are trying to figure out whether your actual silicon is working or why it is no
Related Questions
- How long has IQue been on the market? What product testing and verification of data are there?
- What status must a testing organization possess, suitable for ETV Canada verification?
- What status must a testing organization possess, suitable for ETV Canada verification?
- How does DFD differentiate from verification or testing?
- Does ETV Canada conduct verification testing?
- Does ETV Canada conduct verification testing?
