Proceedings of ASP-DAC/VLSI Design 2002. 7th Asia and South Pacific Design Automation Conference and 15h International Conferen
DOI: 10.1109/aspdac.2002.994973
|View full text |Cite
|
Sign up to set email alerts
|

Property-specific testbench generation for guided simulation

Abstract: Abstract

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
12
0

Publication Types

Select...
3
2
2

Relationship

0
7

Authors

Journals

citations
Cited by 12 publications
(12 citation statements)
references
References 12 publications
0
12
0
Order By: Relevance
“…Two markings are consequently valid considering the input and output observed so far. This is reflected in that curmarkings will contain both markings, as shown in Equation (16). (16) The next input comes after 20 time units, when a new token appears in p, this time with the value 5.…”
Section: If the Transition Does Not Results In The Desired Output Thementioning
confidence: 99%
See 1 more Smart Citation
“…Two markings are consequently valid considering the input and output observed so far. This is reflected in that curmarkings will contain both markings, as shown in Equation (16). (16) The next input comes after 20 time units, when a new token appears in p, this time with the value 5.…”
Section: If the Transition Does Not Results In The Desired Output Thementioning
confidence: 99%
“…Gupta et al [16] apply formal methods to automatically generate a testbench for guided simulation given a model under veri-fication and a CTL property. As a result of their approach, they obtain a testbench which generates stimuli for a subsequent simulation.…”
Section: Introductionmentioning
confidence: 99%
“…The works proposed in [2,14] have combined formal verification techniques with simulation for functional verification. The methodology proposed in [14] extracts an abstract model of the design for the purpose of functional validation.…”
Section: Related Workmentioning
confidence: 99%
“…A typical coverage metric is branch coverage, but there are more code coverage metrics, such as lines, blocks, branches, expressions, paths, and boundary-path. Other techniques (Fallah, 1998); (Gupta, 2002); (Ugarte, 2011) do not depend on the engineer, thus they can be more easily automated. They are also simpler, and provide a first quality metric of the input set.…”
Section: Stimuli Generationmentioning
confidence: 99%