Challenges in the three-tier development structure

In the past, an electronic control unit (ECU) realized one or more functions with very little interoperability towards other ECUs . An OEM usually outsourced the ECU development to exactly one supplier with full warranty and liability. Today, in addition to classic ECUs, vehicles have high-performance computers that together implement complex functions, such as Plug and Charge, driver assistance, connect and infotainment functions. A complex function is realized by a chain of software components on a number of ECUs, which leads to three development layers: i) Functions ii) ECU/Hardware with basic software and iii) Software Components The development challenges arise from the high complexity that results from multi-matrix organizations which is needed to develop the so called End-to-End (E2E) Architecture. Which proven and new quality methods can be used to master the challenges to release the E2E Architecture according standards? Which methods are efficient or less valuable or even obsolete?

Short biography

Achim Hoenow is the Solution Train Quality Manager for CARIAD’s electronic platform of the Premium Platform Electric (PPE) and Premium Platform Combustion (PPC), which was successfully launched in 2024. In his position he is incorporating with CARIAD’s project management, quality departments of Audi and Porsche and CARIAD quality experts. In his previous position Achim lead the Software Supplier Quality Management department at Continental with the responsibility of assessing and improving worldwide software and firmware suppliers. He is Automotive SPICE principal assessor, has executed much more than 100 Automotive SPICE assessments and was several years member of the working group 13 Automotive SPICE. Achim Hoenow is a graduated computer scientist with more than 25 years of experience in development, as team and department leader and quality management.