Breaking News
Design How-To

Hunting that elusive bug

9/28/2010 07:44 AM EDT
42 comments
NO RATINGS
Page 1 / 4 Next >
More Related Links
View Comments: Threaded | Newest First | Oldest First
STS_SK
User Rank
Rookie
re: Hunting that elusive bug
STS_SK   9/29/2010 4:39:41 AM
NO RATINGS
Good reminder of problem faced in SOC integration

MikeLC
User Rank
Rookie
re: Hunting that elusive bug
MikeLC   9/30/2010 8:14:34 AM
NO RATINGS
As a programmer who has done a fair amount of client/server software, it certainly is important for the hardware to be reliable. Keep up the good work.

sharps_eng
User Rank
Rookie
re: Hunting that elusive bug
sharps_eng   10/1/2010 8:02:40 PM
NO RATINGS
Interestingly this article contains 6 or more arguments ended by a 'counsel of despair' typified by 'its so complex you'll never find all the bugs, so why bother?' then describes a brute-force method of testing to try to find said bugs, and _prove_their_absence_(I'll not go there!). Reliable design used to start by designing a core so simple it could be proven to be correct using tools that themselves were simple enough to be proven likewise. Thereafter, this virtuous circle was widened step by step to encompass the entire application, with each proven building block introducing no additional uncertainty save that due to the current layer being developed. But before the impetus had built, or critical mass achieved, commercial forces would often kill the project or force it to market early, and the work done to date would be lost, instead of forming the core of future systems. It would be fascinating to be a code archeologist and unearth some ultra-safe, elegant and incredibly simple systems that have been scrapped without regard to their potential value. Real 'lost knowledge', worthy of a Dan Brown novel (and then some).

WKetel
User Rank
Rookie
re: Hunting that elusive bug
WKetel   11/3/2010 9:38:21 PM
NO RATINGS
This article unintentionally offers another solution, which has two parts, the first being to not make the system so incredibly complex. Don't put all of a cars smart functions on one chip, don't even put them in one module. It is much more likely to be able to understand what code is doing if it is only doing one thing. So coming up with an adequately detailed description of what the system will do is a very good start. The second part of the solution is after a function is selected for a given system, carefully define all of what the function must do, and then make that description be the specification, and, most importantly, avoid feature creep. Both in initial concept creation and as the project is in process, constantly changing and adding is a certified way to add errors.

August Cartoon Caption Winner!
August Cartoon Caption Winner!
"All the King's horses and all the KIng's men gave up on Humpty, so they handed the problem off to Engineering."
5 comments
Top Comments of the Week
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
Flash Poll
Radio
NEXT UPCOMING BROADCAST
How to Cope with a Burpy Comet
October 17, 2pm EDT Friday
EE Times Editorial Director Karen Field interviews Andrea Accomazzo, Flight Director for the Rosetta Spacecraft.