<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Checks or Functional Coverage (Part II)?</title>
	<atom:link href="http://www.verilab.com/blog/2007/07/checks-or-fcov-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.verilab.com/blog/2007/07/checks-or-fcov-2/</link>
	<description>Verilab</description>
	<pubDate>Tue, 06 Jan 2009 03:59:35 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6.1</generator>
		<item>
		<title>By: Sandeep Gor</title>
		<link>http://www.verilab.com/blog/2007/07/checks-or-fcov-2/#comment-151</link>
		<dc:creator>Sandeep Gor</dc:creator>
		<pubDate>Wed, 12 Dec 2007 06:08:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.verilab.com/blog/2007/07/checks-or-fcov-2/#comment-151</guid>
		<description>Hi David,
I had a pleasur to work with you at Infineon's DVBH project.
By the way, I fully agree with your comment that "checkers are more important than functional coverage". In fact, we need to have coverage points defined for checkers. Cadence have come up with a shareware to measure "check that" and "expect" statment and have them into coverage group. Specman 6.0 supports it.

Once all checkers are developed, we should also have checker coverage grid along with functional coverage grid. Not only this, we should also make sure that each functional coverage point has relevent checker coverage point and each checker coverage point has relevent functional coverage point. This way, we make sure that all stimuli (functional coverage) has corrosponding output checker (checker coverage) in place.

I have posted a small description about it on my blog http://digitalverification.blogspot.com/search/label/Coverage
under heading (100% functional coverage is not enough).

Best Regards,
Sandeep Gor</description>
		<content:encoded><![CDATA[<p>Hi David,<br />
I had a pleasur to work with you at Infineon&#8217;s DVBH project.<br />
By the way, I fully agree with your comment that &#8220;checkers are more important than functional coverage&#8221;. In fact, we need to have coverage points defined for checkers. Cadence have come up with a shareware to measure &#8220;check that&#8221; and &#8220;expect&#8221; statment and have them into coverage group. Specman 6.0 supports it.</p>
<p>Once all checkers are developed, we should also have checker coverage grid along with functional coverage grid. Not only this, we should also make sure that each functional coverage point has relevent checker coverage point and each checker coverage point has relevent functional coverage point. This way, we make sure that all stimuli (functional coverage) has corrosponding output checker (checker coverage) in place.</p>
<p>I have posted a small description about it on my blog <a href="http://digitalverification.blogspot.com/search/label/Coverage" rel="nofollow">http://digitalverification.blogspot.com/search/label/Coverage</a><br />
under heading (100% functional coverage is not enough).</p>
<p>Best Regards,<br />
Sandeep Gor</p>
]]></content:encoded>
	</item>
</channel>
</rss>
