If so, your design verification and debugging tools aren't knowledge-based. The knowledge used by the method encompasses design-specific criteria that facilitate fast and accurate graphical views of the design's intent, which is typically buried in the mounds of HDL code. Thus a knowledge system simplifies the verification of ever more complex designs and speeds the time to tape-out. Today's leading-edge design requires a team of design and verification engineers.
Waveforms are no longer enough for efficient design debugging.
Design debugging needs a knowledge-based solution. It's time to say goodbye to tedious hours of surfing uncountable Unix files and using grep to find signal names of which grep has no connectivity knowledge. Knowledge-based tools should serve as the console for all the verification steps in a design flow, regardless of the simulator, language, formal tools, test benches, coverage tools, or static tools used. Currently, the volume of data hides design intent and makes debugging difficult and time-consuming. Verification team members thus lack critical knowledge of the original design intent, inhibiting their understanding of the work they need to accomplish.