The cure for overgrown process garden or why engineers have given up with ASPICE.

The useability of development processes in automotive decreased in the past years to a level at which their application and being able to benefit from them are questionable. Such degradation can be attributed to new additions to the processes and introduction of FUSA and Cybersecurity standards. The processes try to keep up with the shift from “plan-implement- test-roll out” to more agile methods. In addition, process departments, in charge of these processes, did not target the engineers as users of these processes, they focused on the compliance of processes and the assessor in the assessment. Due to reasons mentioned above, processes have grown in size and complexity which creates unnecessary overhead and forces the usage of complex tools to handle this overhead. Furthermore, the language of this process is written mostly in the language of the assessor, making them hard to understand for an average engineer. As a result, engineers are annoyed in their daily work and are not as efficient and fast as they could be with a reduced set of sufficient Processes. This has a huge impact on the competitiveness of companies in more and more difficult markets. Against popular belief, the application of AI (LLMS) will not solve the problem as well. On the contrary, it would be automating the complex process in the same non-engineering language and creating documents to serve process overhead that was unnecessary in the first place. The paper presents inefficiencies in current state of the art processes used in automotive and proposes a structured approach which increases the efficiency of automotive software development. It does so by documenting and implementing development processes based on how engineers do their work. In the second step the adjustments that are necessary to ensure compliance of the product with industry standards are made. Such approach produces sufficient, efficient, compact and compliant process definition.