News for hackers. Stuff that matters.
Re:The Engineer’s Lament by sjg007 on Monday April 27, 2015 @06:10PM (#9449409)
There was a court case later that investigated the firmware of the drive by wire throttle control system software. Basically, design choices in the software implementation couldn't rule out the software as the source of unintended acceleration. All bets are off after stack overflow and continued execution.

Also the "brake override" wasn't a feature included at all which one could argue should have been part of the design.

In fact, software for car control systems should go through the same rigorous testing, documentation, control etc... (similar to what is required for FDA medical devices).

More: http://www.edn.com/design/automotive/4423428/Toyota-s-killer...

Re:The Engineer’s Lament by vilhelm_s on Monday April 27, 2015 @08:16PM (#9449904)
The court case showed that the throttle control programming was shoddy in various ways, but I don't think they demonstrated any observably buggy behavior, let alone any proof that software faults were behind any particular accident.

I think it's also quite possible that there never were any abnormal unintended accelerations, but the media debacle caused people to carefully investigate the cars, at which point they discovered that the programming was bad.

Re:The Engineer’s Lament by pnathan on Tuesday April 28, 2015 @07:12PM (#9455661)
They actually demonstrated buggy behaviour, as well as the number of paths that could lead to that behaviour (very large).
Re:The Engineer’s Lament by ArkyBeagle on Monday April 27, 2015 @06:46PM (#9449583)
It's hard to say whether it should or not. Something like that, sure. Perhaps not exactly the same thing.
Re:The Engineer’s Lament by kijin on Tuesday April 28, 2015 @02:18AM (#9450744)
> similar to what is required for FDA medical devices

Given how often we hear about gaping security holes in all sorts of medical devices, that doesn't seem like a particularly high standard.

Does anyone know whether Boeing and Airbus have higher standards for software quality?

Re:The Engineer’s Lament by EpicEng on Tuesday April 28, 2015 @03:38AM (#9450906)
Well, I've spent the last decade designing FDA cleared systems (class I and class III), and I can tell you that it is. That doesn't mean that mistakes aren't made, and it doesn't mean that you can't outright lie in documentation. There's no way the FDA could catch that short of replicating all of your V&V.

However, most of us aren't trying to cheat, and I can tell you that the amount of engineering rigor that goes into a medical device is leagues beyond what most software devs have ever been a part of. At my company we don't hire "developers"; we hire engineers who have programming in their toolbox.

Medical software screwups are high profile. You don't hear about every bug that the next "disruptive startup" lets into the wild.