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?