The December 2022 issue of IEEE Spectrum is here!

Close bar

US National Highway Traffic Safety Administration Has No EEs or SW Engineers Working For It

Lacks Expertise to Investigate Software-Related Safety Issues Claims Congressional Committee

2 min read
US National Highway Traffic Safety Administration Has No EEs or SW Engineers Working For It

The Congressional hearings focusing on sudden unintended acceleration in Toyota vehicles are set to begin today by the US House Committee on Energy and Commerce and the US House Committee on Oversight and Government Reform tomorrow.  It will not likely be a fun day for Toyota executives nor for those at the US Department of Transportation.

In a letter dated yesterday by the Chairman of the House Committee on Energy and Commerce Henry A. Waxman to Secretary of U. S. Department of Transportation Ray LaHood, Chairman Waxman asked Secretary LaHood how could the US National Highway Traffic Safety Administration (NHTSA) possibly investigate electronic or software related defects in vehicles when it has no electrical engineers or software engineers on its staff of 635?

That's a good question.

NHTSA told the Energy and Commerce staff  "they have the authority to contract for such services as needed" but apparently they have not done so, the Committee letter claims.

[Update: In testimony in front of the Oversight and Government Reform Committee, Secretary LaHood said that there are two EEs on NHTSA's staff of 125 engineers. He made no mention of software engineers.]

The Energy and Commerce Committee also sent a letter to Toyota asking why it was saying publicly that the unintended acceleration problem was fixed and that it wasn't caused by vehicle electronics when the company was also privately telling its staff that; (a) "sticky pedals" were not the cause, and; (b) causes of unintentional vehicle acceleration were "multiple" and "hard to identify."

Energy and Commerce Committee members may also ask Toyota about a story yesterday appearing on ABC News. In the story, Professor David Gilbert of Southern Illinois University showed, "A flaw in the design of Toyota's electronic acceleration system prevents the car's onboard computer from detecting and stopping certain short circuits that can trigger sudden speed surges ..." 

"As a result, Gilbert told ABC News, the Toyota computers will not record an error code, nor will they activate the 'fail safe' system designed to shutdown the power and put the car in the 'limp home' mode."

You can watch the video of the demonstration here. You judge for yourself whether what the professor showed was a "flaw" or not.

According to recent public statements by Toyota, one might conclude that this should not be able to happen, however.

As I said, it will not be a fun day for Toyota. I'll let you know what happens.

The Conversation (0)

Why Functional Programming Should Be the Future of Software Development

It’s hard to learn, but your code will produce fewer nasty surprises

11 min read
Vertical
A plate of spaghetti made from code
Shira Inbar
DarkBlue1

You’d expectthe longest and most costly phase in the lifecycle of a software product to be the initial development of the system, when all those great features are first imagined and then created. In fact, the hardest part comes later, during the maintenance phase. That’s when programmers pay the price for the shortcuts they took during development.

So why did they take shortcuts? Maybe they didn’t realize that they were cutting any corners. Only when their code was deployed and exercised by a lot of users did its hidden flaws come to light. And maybe the developers were rushed. Time-to-market pressures would almost guarantee that their software will contain more bugs than it would otherwise.

Keep Reading ↓Show less
{"imageShortcodeIds":["31996907"]}