With more and more functionality moving into software, is Munro or anyone else doing anything along these lines with the firmware and software in vehicles? Are manufacturers as interested in evaluating the process and design of their software as they are with the physical pieces of the vehicle? Do copyright and sometimes murky legalities around reverse engineering software prevent the equivalent teardown (disassembly) and analysis of software components?
Despite being known for kaizen processes implemented as Plan -> Do -> Check -> Act or 5 Whys, Toyota's issues with unintended acceleration were partly blamed on flaws and spaghetti code in the RTOS controlling their Electronic Throttle Control System in some models:
That's just one example. There's the CAN bus car hacking via OnStar and more examples out there. Would this kind of analysis help more than say, simply implementing better software development methodologies?
Despite being known for kaizen processes implemented as Plan -> Do -> Check -> Act or 5 Whys, Toyota's issues with unintended acceleration were partly blamed on flaws and spaghetti code in the RTOS controlling their Electronic Throttle Control System in some models:
https://users.ece.cmu.edu/~koopman/pubs/koopman14_toyota_ua_... http://www.safetyresearch.net/blog/articles/toyota-unintende...
That's just one example. There's the CAN bus car hacking via OnStar and more examples out there. Would this kind of analysis help more than say, simply implementing better software development methodologies?