Breaking News
Comments
Newest First | Oldest First | Threaded View
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.

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).

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.

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



EE Life
Frankenstein's Fix, Teardowns, Sideshows, Design Contests, Reader Content & More
Max Maxfield

Dr. Duino Diagnostic Shield Deduces Dilemmas in Arduino Shield Stacks
Max Maxfield
13 comments
As you are probably aware, I'm spending a lot of my free time creating Arduino-based projects, such as my Inamorata Prognostication Engine, my BADASS Display, and my Vetinari Clock.

EDN Staff

11 Summer Vacation Spots for Engineers
EDN Staff
20 comments
This collection of places from technology history, museums, and modern marvels is a roadmap for an engineering adventure that will take you around the world. Here are just a few spots ...

Glen Chenier

Engineers Solve Analog/Digital Problem, Invent Creative Expletives
Glen Chenier
15 comments
- An analog engineer and a digital engineer join forces, use their respective skills, and pull a few bunnies out of a hat to troubleshoot a system with which they are completely ...

Larry Desjardin

Engineers Should Study Finance: 5 Reasons Why
Larry Desjardin
46 comments
I'm a big proponent of engineers learning financial basics. Why? Because engineers are making decisions all the time, in multiple ways. Having a good financial understanding guides these ...

Flash Poll
Top Comments of the Week
Like Us on Facebook
EE Times on Twitter
EE Times Twitter Feed

Datasheets.com Parts Search

185 million searchable parts
(please enter a part number or hit search to begin)