Design Con 2015
Breaking News
Design How-To

Top 10 Tips for Success with Formal Analysis – Part 1

NO RATINGS
More Related Links
View Comments: Newest First | Oldest First | Threaded View
Thomas.Anderson_#4
User Rank
Rookie
re: Top 10 Tips for Success with Formal Analysis – Part 1
Thomas.Anderson_#4   1/23/2012 9:02:44 AM
NO RATINGS
Brian, I do believe that designers have a net savings across the project by adopting assertions because it's so much easier to diagnose bugs found at the block level. However, I have not seen a solid ROI analysis to support this belief. Tom A.

Rale
User Rank
Rookie
re: Top 10 Tips for Success with Formal Analysis – Part 1
Rale   12/22/2011 2:01:51 PM
NO RATINGS
Actually, books about assertions claims about 1-2% of increased code size and small increase of RTL coding phase but substantially shorter verification/debug phase. For sure, assertions can help, but they are not silver bullet.

BrianBailey
User Rank
Blogger
re: Top 10 Tips for Success with Formal Analysis – Part 1
BrianBailey   12/12/2011 3:45:26 PM
NO RATINGS
Tom, you say that adding assertions increases the time required by about 15-20%. What is the ROI in terms of the estimated time saved by having bugs found earlier, or additional bugs found?

Flash Poll
Like Us on Facebook

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)
EE Times on Twitter
EE Times Twitter Feed
Top Comments of the Week