Jack, my impression of code testing is that it allows the code to be verified correct before the system is tested in the real world, where another whole set of "bugs" come to light, such as timing, impedance problems, differences between vendor spec sheets and actual chip operation, power supply stability, heat problems, RFI susceptibility and FCC compliance, etc. Is this a fair statement?
I believe in integration testing - which is the real-world stuff you mention - from day 1. There just isn't much to integrate at first, but as time goes on we've generally done a good job stressing the system.
Truchard will be presented the award at the 2014 Golden Mousetrap Awards ceremony during the co-located events Pacific Design & Manufacturing, MD&M West, WestPack, PLASTEC West, Electronics West, ATX West, and AeroCon.
In a bid to boost the viability of lithium-based electric car batteries, a team at Lawrence Berkeley National Laboratory has developed a chemistry that could possibly double an EV’s driving range while cutting its battery cost in half.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This discussion will examine what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.