|
|
|
|
|
by jimbomins
1263 days ago
|
|
I've been out of automotive safety critical software (engine, brake, controllers, etc...) but still have friends in it. Proper best practice is still followed by the likes of Toyota, Jaguar and Ford as the ones I've had experience in. That means the coding standards mentioned. Full requirements->design->implementation with functional unit testing, module unit testing and system testing including using simulators. Multiple people doing reviews, strict standards enforcement. Static analysis and code test coverage aiming for 100% path coverage with testing even when I was doing it. With staff typically staying on projects for the full 5 years of development. Ford as one I can speak about with knowledge took seriously the cost of recalls versus catching issues in testing. It's massively cheaper to spend money up front to do full process and catch every bug you can than to cover recall costs to update later not even considering liabilities if anything does go pop. Mistakes of course happen. But they're also rarely working from scratch. It makes working in modern ways horrific seeing the shoddy shit tossed out to meet consumer gadget deadlines. |
|
Then a few years later they got hit again with one of their suppliers: Takata's killing airbags