January 1, 0001
Automation in Automotive
Builds on dedicated machine need some process improvement but ensure a reliable and reprucible state. Like this artifacts are created in a compliant way. It is important to use it in the right way to not wait for builds to finish.
Integration processes (espacially if there are more than 1 party involved) are very complex and error prone. Automated and simplyfied as well as proberly documented process reduce risk significantly.
Testing processes needed to be refined. Manual test are necessary but should only be used if no automation is possible. To have a reliable way of testing the whole software stack it should be automated and generalized as much as possible.
Basically all the steps can be mapped directly - without configure & monitor, which is of course only applicable if there is access to the “production environment”. Maybe if the future brings connected cars we may rethink that. So in theory we should be able to use DevOps methods. The quite complex planning, analysis & testing phases stretch the sprints so 2 week cycles are not really possible. Testing can not be done in an completely automated way since each release needs to be tested in a special environment and / or in cars. So one approach is a 2 week development phase with a 2 week testing phase including a code freeze supporting this.
V-Model is ok -> just execute it faster -> sprints!
Another obversation we made is that modern software engineering practises like Test Drive Development are quite hard to use in this environment.
Version handling not handled.
Learn more on our Whitepaper (Link)