2008 11th International Biennial Baltic Electronics Conference 2008
DOI: 10.1109/bec.2008.4657515
|View full text |Cite
|
Sign up to set email alerts
|

High-level decision diagram manipulations for code coverage analysis

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2009
2009
2015
2015

Publication Types

Select...
2
2
1

Relationship

0
5

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 5 publications
0
3
0
Order By: Relevance
“…The experiment benchmarks several designs from ITC'99 benchmarks family [ 23 ] and a design gcd which is an implementation of the greatest common devisor. Figure 9 shows comparison results obtained in [ 10 ] with the proposed methodology, based on different HLDD representations and coverage analysis, achieved by a commercial state-of-the-art HDL simulation tool from a major CAD vendor using the same sets of stimuli.…”
Section: Resultsmentioning
confidence: 99%
“…The experiment benchmarks several designs from ITC'99 benchmarks family [ 23 ] and a design gcd which is an implementation of the greatest common devisor. Figure 9 shows comparison results obtained in [ 10 ] with the proposed methodology, based on different HLDD representations and coverage analysis, achieved by a commercial state-of-the-art HDL simulation tool from a major CAD vendor using the same sets of stimuli.…”
Section: Resultsmentioning
confidence: 99%
“…A comparison between the existing high level decision diagram (HLDD) based model [20] and the proposed model on the statement and branch coverage metrics is provided in the Table VII. In all the cases, experiments are run on a Computer with AMD Phenom(tm) II X3710 Processor, 2.5 GHz, 4.0 GB of RAM, Windows XP Professional Service Pack 2. The test patterns are generated using SMT solver and executed for the custom-built circuits on the Xilinx version 10.1 simulator.…”
Section: Resultsmentioning
confidence: 99%
“…In this paper, five fundamental code coverage metrics: statement, condition, branch, path, and expression [17] are included. Recent works [18], [19], [20], [21], [22], [23], [24] have addressed design verification with a number of code coverage metrics. Though the approaches defined and analyzed code coverage metrics well to measure the quality of test benches (stimuli) but does not guarantee full confidence in correctness with respect to specification of a DUT.…”
Section: Introductionmentioning
confidence: 99%