Abstract
Automotive manufacturing has undergone a sustained shift in how vehicles are electrically and electronically architected, moving from a distributed arrangement of dozens of largely independent embedded telematics controllers toward a consolidated, software - defined vehicle architecture in which a small number of high - performance zone and central computers host the great majority of vehicle functionality as software. This shift has direct consequences for vehicle manufacturing engineering, affecting how elect rical content is sourced and installed on the assembly line, how software is validated and flashed before a vehicle leaves the plant, how over - the - air updates are planned and deployed after the vehicle reaches a customer, and how a vehicle program's develo pment timeline from concept to start of production is structured. This paper presents an engineering framework for connected - vehicle service evolution that explicitly connects these manufacturing engineering concerns to the underlying architectural transition. The framework characterizes three successive generations of v ehicle electrical and electronic architecture, distributed, domain - based, and zonal or software - defined, and traces how each generation's architectural properties propagate into specific manufacturing engineering requirements, including assembly line stati on design, end - of - line software flashing and calibration procedures, and post - production over - the - air update infrastructure. Drawing on vehicle program and manufacturing data spanning model years 2008 through 2022, this study documents a more than two - fold increase in mean onboard electronic control unit count and nearly a six - fold increase in onboard software volume over this p eriod, alongside a corresponding evolution in assembly line software installation practice from isolated per - controller programming toward consolidated, zone - level software flashing integrated directly into the end - of - line functional test station. Over - the - air update outcome data collected across four successive vehicle platform generations shows first - attempt update success rising from 71 percent on a legacy distributed platform to 97 percent on a zonal software - defined platform, a difference this paper at tributes to architectural consolidation rather than to update tooling improvements alone. The paper further presents a comparative analysis of legacy embedded and software - defined architectures across update agility, scalability, development cost efficiency, feature velocity, hardware reuse, and cybersecurity posture, and examines the relations hip between over - the - air update frequency and software - related warranty claim rates observed across a multi - platform vehicle fleet. The findings support a manufacturing engineering framework in which software platform considerations are integrated into veh icle program planning from the concept phase onward, rather than treated as a downstream integration concern, and the paper concludes with practical guidance for automotive manufacturers planning this transition across future vehicle programs.
Keywords
software - defined vehicle, embedded telematics, vehicle electrical and electronic architecture, automotive manufacturing engineering, over - the - air updates, zonal architecture, domain controllers, vehicle program development, connected - vehicle services.
References
[1] International Organization for Standardization. ISO 26262-1:2018, Road vehicles, Functional safety, Part 1,
Vocabulary. Geneva: ISO, 2018.
[2] International Organization for Standardization. ISO/SAE 21434:2021, Road vehicles, Cybersecurity
engineering. Geneva: ISO, 2021.
[3] SAE International. SAE J3101, Hardware Protected Security for Ground Vehicles. Warrendale, PA: SAE
International, 2020.
[4] AUTOSAR Consortium. Explanation of Adaptive Platform Design, Release R21-11. Munich: AUTOSAR
Development Partnership, 2021.
[5] AUTOSAR Consortium. Specification of Manifest, Adaptive Platform, Release R20-11. Munich:
AUTOSAR Development Partnership, 2020.
[6] Pretschner, A., Broy, M., Kruger, I. H., and Stauner, T. Software Engineering for Automotive Systems, A
Roadmap. Proceedings of the Future of Software Engineering, International Conference on Software
Engineering, Minneapolis, MN, pp. 55 to 71, 2007.
[7] Broy, M. Challenges in Automotive Software Engineering. Proceedings of the 28th International Conference
on Software Engineering, Shanghai, pp. 33 to 42, 2006.
[8] Navet, N. and Simonot-Lion, F. Automotive Embedded Systems Handbook. Boca Raton, FL: CRC Press,
2009.
[9] Staron, M. Automotive Software Architectures, An Introduction. Cham: Springer International Publishing,
2017.
[10] Weber, M. and Weisbrod, J. Requirements Engineering in Automotive Development, Experiences and
Challenges. Proceedings of the IEEE Joint International Conference on Requirements Engineering, Essen,
pp. 331 to 340, 2002.
[11] Hartwich, F., Beck, F., and Nowak, W. CAN FD, The Enhanced Communication System for Series
Production. Proceedings of the International CAN Conference, Nuremberg, pp. 1 to 9, 2012.
[12] Matheus, K. and Konigseder, T. Automotive Ethernet, Second Edition. Cambridge: Cambridge University
Press, 2017.
[13] Burkacky, O., Deichmann, J., Doll, G., and Knochenhauer, C. Rethinking Car Software and Electronics
Architecture. McKinsey and Company Technical Report. New York: McKinsey and Company, 2018.
[14] Deichmann, J., Ebel, E., Heineke, K., Heuss, R., Kellner, M., and Steiner, F. Software-Defined Vehicles,
Capturing Value in the Age of Vehicle Intelligence. McKinsey and Company Technical Report. New
York: McKinsey and Company, 2021.
[15] Bock, F., Siegl, S., Neidig, D., and German, R. Decoupling the Development of Automotive Software and
Hardware, A Model-Based Approach. Proceedings of the IEEE International Conference on Software
Architecture, Hamburg, pp. 101 to 110, 2019.
[16] Boos, D. and Kramer, J. Over-the-Air Programming of Vehicle Systems, State of the Art and Research
Challenges. Proceedings of the IEEE International Conference on Connected Vehicles and Expo,
Shenzhen, pp. 89 to 95, 2015.
Vocabulary. Geneva: ISO, 2018.
[2] International Organization for Standardization. ISO/SAE 21434:2021, Road vehicles, Cybersecurity
engineering. Geneva: ISO, 2021.
[3] SAE International. SAE J3101, Hardware Protected Security for Ground Vehicles. Warrendale, PA: SAE
International, 2020.
[4] AUTOSAR Consortium. Explanation of Adaptive Platform Design, Release R21-11. Munich: AUTOSAR
Development Partnership, 2021.
[5] AUTOSAR Consortium. Specification of Manifest, Adaptive Platform, Release R20-11. Munich:
AUTOSAR Development Partnership, 2020.
[6] Pretschner, A., Broy, M., Kruger, I. H., and Stauner, T. Software Engineering for Automotive Systems, A
Roadmap. Proceedings of the Future of Software Engineering, International Conference on Software
Engineering, Minneapolis, MN, pp. 55 to 71, 2007.
[7] Broy, M. Challenges in Automotive Software Engineering. Proceedings of the 28th International Conference
on Software Engineering, Shanghai, pp. 33 to 42, 2006.
[8] Navet, N. and Simonot-Lion, F. Automotive Embedded Systems Handbook. Boca Raton, FL: CRC Press,
2009.
[9] Staron, M. Automotive Software Architectures, An Introduction. Cham: Springer International Publishing,
2017.
[10] Weber, M. and Weisbrod, J. Requirements Engineering in Automotive Development, Experiences and
Challenges. Proceedings of the IEEE Joint International Conference on Requirements Engineering, Essen,
pp. 331 to 340, 2002.
[11] Hartwich, F., Beck, F., and Nowak, W. CAN FD, The Enhanced Communication System for Series
Production. Proceedings of the International CAN Conference, Nuremberg, pp. 1 to 9, 2012.
[12] Matheus, K. and Konigseder, T. Automotive Ethernet, Second Edition. Cambridge: Cambridge University
Press, 2017.
[13] Burkacky, O., Deichmann, J., Doll, G., and Knochenhauer, C. Rethinking Car Software and Electronics
Architecture. McKinsey and Company Technical Report. New York: McKinsey and Company, 2018.
[14] Deichmann, J., Ebel, E., Heineke, K., Heuss, R., Kellner, M., and Steiner, F. Software-Defined Vehicles,
Capturing Value in the Age of Vehicle Intelligence. McKinsey and Company Technical Report. New
York: McKinsey and Company, 2021.
[15] Bock, F., Siegl, S., Neidig, D., and German, R. Decoupling the Development of Automotive Software and
Hardware, A Model-Based Approach. Proceedings of the IEEE International Conference on Software
Architecture, Hamburg, pp. 101 to 110, 2019.
[16] Boos, D. and Kramer, J. Over-the-Air Programming of Vehicle Systems, State of the Art and Research
Challenges. Proceedings of the IEEE International Conference on Connected Vehicles and Expo,
Shenzhen, pp. 89 to 95, 2015.