Overview of the reference architecture for software-defined vehicles (SDVs)
Software-defined vehicles are cars that can be updated and customized through their lifetime. Software is the main driver for innovation and differentiation as opposed to physical characteristics such as engine performance. SDVs require a new approach to the design and development of the vehicle software and hardware architecture, as well as the tool processes to manage them.
Microsoft provides two approaches for SDVs:
- Reference architecture for a modern cloud-native SDV software development toolchain that uses Microsoft’s strong developer-centric tooling. The reference architecture covers development, testing, and delivering high quality software.
- An open-source, community-based in-vehicle open source software components and stack contributions as part of the Eclipse Foundation SDV Working Group. These contributions define key components and features to facilitate integration, deployment, and management of various vehicle functions and services.
Current challenges
In the evolving landscape of software-defined vehicles (SDVs), where vehicle functionalities traditionally governed by intertwined hardware and software are now decoupled, virtualized, and steered predominantly by software, several industry challenges emerge:
- Escalating consumer demands: Consumer expectations are undergoing rapid expansion, necessitating the implementation of an ever-increasing array of features primarily through software.
- Dealing with software complexity: The automotive industry has struggled with the increasing complexity of software integration within vehicles for over a decade.
- Adapting to evolving technology: The current technology landscape and development processes weren't originally tailored to accommodate this transformative shift. So, original equipment manufacturers (OEMs) are confronted with substantial development and integration expenses, and delayed start of production (SOP) timelines.