We present a coverage analysis that can be used in-based verification. The analysis helps identifying ”forgotten”; scenarios where the property list under analysis not constrain a certain output at a certain point in time. scenarios can then be manually investigated, possibly leading new, previously forgotten properties being added. As there exist cases in which outputs are not supposed to be specified, also provide means for the specificier to annotate properties in to control what cases are supposed to be underconstrained. main differences with earlier proposed similar analyses: The presented analysis is design-independent, and it makes explicit distinction between intentionally and unintentionally behavior.
No takes yet. Share an insight, caveat, or question.
Koen Claessen (2007) studied this question.
Synapse has enriched one closely related paper. Consider it for comparative context: