Tenth IEEE International High-Level Design Validation and Test Workshop, 2005.
DOI: 10.1109/hldvt.2005.1568809
|View full text |Cite
|
Sign up to set email alerts
|

MVP: a mutation-based validation paradigm

Abstract: Abstract-We present a Mutation-based Validation Paradigm (MVP) technology that can handle complete high-level microprocessor implementations and is based on explicit design error modeling, design error simulation, and model-directed test vector generation. We first present a control-based coverage measure that is aimed at exposing design errors that incorrectly set control signal values. We then describe MVP's high-level concurrent design error simulator that can handle various modeled design errors. We then p… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2

Citation Types

0
2
0

Publication Types

Select...
3
1

Relationship

1
3

Authors

Journals

citations
Cited by 4 publications
(2 citation statements)
references
References 20 publications
(18 reference statements)
0
2
0
Order By: Relevance
“…In our previous research [1][5] [6], we have developed the methods that implement MVP (Mutationbased Validation Paradigm), our validation environment for high-level microprocessor implementations. MVP is able to handle complete implementations because it only uses high-level information, and only uses the hardware description language (HDL) information relevant to the set of constraints when identifying all relevant architectural states.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…In our previous research [1][5] [6], we have developed the methods that implement MVP (Mutationbased Validation Paradigm), our validation environment for high-level microprocessor implementations. MVP is able to handle complete implementations because it only uses high-level information, and only uses the hardware description language (HDL) information relevant to the set of constraints when identifying all relevant architectural states.…”
Section: Introductionmentioning
confidence: 99%
“…For our validation paradigm [6], we have created the notion of a prospect state to define an architectural state in terms of a set of constraints. For each constraint, there is a data dependency of its corresponding signal to the set of primary inputs and internal registers, and there is a set of control requirements that allow that data dependency to become active.…”
Section: Introductionmentioning
confidence: 99%