Vehicle software

What Is a Software-Defined Vehicle (SDV)?

A software-defined vehicle shifts important vehicle functions from many isolated hardware modules toward software running on more centralized computing platforms, with features that can evolve through updates.

Simple definition

A software-defined vehicle (SDV) is a vehicle whose functions and user experience are increasingly controlled, updated and expanded through software running on centralized or zonal electronic architectures.

Software-defined vehicle infographic showing central compute, zonal controllers, cockpit systems, ADAS functions and cloud over-the-air updates
An SDV brings more functions into software, central compute, zonal electronics and over-the-air updates.

What makes a vehicle software-defined?

There is no single universal checklist, but the common direction is clear: fewer isolated electronic silos, more centralized or zonal compute, software abstraction, service-oriented architectures, over-the-air updates and a development model that allows functions to evolve after production.

Honda provides a current SDV example

On October 6, 2026, Applied Intuition announced a partnership with Honda to accelerate a centralized, upgradable software-defined vehicle platform for Honda's next-generation vehicle architecture. The work is intended to support Honda's in-house software development across multiple powertrains. On the same day, Nissan and Applied Intuition highlighted AI-defined vehicle development — a useful real-world illustration of how AIDV builds on the SDV foundation.

What is zonal architecture?

Traditional cars can contain many electronic control units distributed by function. Zonal architectures reorganize electronics partly by physical area of the vehicle and connect them to powerful central computers. Volkswagen says its coming zonal SDV architecture will use high-performance modular central computers to manage vehicle functions.

Why automakers want SDVs

  • Reuse software across models and vehicle generations.
  • Deliver updates and new functions after production.
  • Reduce wiring and ECU complexity over time.
  • Coordinate cockpit, connectivity, ADAS and other domains more closely.

Connected-car services may exchange information beyond the vehicle. V2X (vehicle-to-everything) describes communication with compatible vehicles, roadside infrastructure, road users and networks; an SDV describes how vehicle functions are organized and updated through software. The concepts can complement each other, but they are not synonyms.

What SDV does not mean

Calling a car an SDV does not guarantee long software support, bug-free updates or advanced autonomy. The label describes an architectural direction; the quality of implementation, security and lifecycle support still matters.

Sources

CarGlossary note:

Automotive terminology evolves quickly. We separate established standards from manufacturer-specific names and update pages as technologies move into production.