SDV
Initialism of software-defined vehicle / software-driven vehicle.
SDV: a car that's really a computer on wheels
An SDV is a vehicle where software controls most of the critical systems, not mechanical linkages or hardwired electronics. Instead of a direct connection between the accelerator pedal and the engine throttle, for instance, the pedal sends a signal to a computer module that then commands the engine. The same applies to braking, steering, suspension adjustment, and transmission logic. This shift moves the vehicle's behavior from fixed hardware response to programmable, updateable logic running on onboard computers.
The architecture relies on a central computing platform, often called a domain controller or central gateway, that collates sensor data and executes control algorithms. Engine control units, brake control modules, transmission controllers, and body electronics no longer operate in isolation; they communicate via CAN bus, Ethernet, or proprietary networks. A single software stack can coordinate throttle response, traction control, stability management, and even autonomous driving features without changing the underlying mechanical hardware.
Implementation and the role of over-the-air updates
Automakers use SDV architecture to enable over-the-air (OTA) updates, where new firmware can be pushed to the vehicle without a visit to a service bay. A fix for an engine calibration issue, a refinement to shift logic, or a new driver assistance feature can reach thousands of vehicles simultaneously. This has transformed vehicle maintenance and feature deployment, though it has also introduced cybersecurity challenges that didn't exist when logic lived in unchangeable hardware.
The term gained prominence after 2020 as legacy manufacturers responded to Tesla's software-centric model and as regulatory pressure for connected diagnostics increased. Most new platforms from major OEMs now use some SDV principles, though the degree varies: some vehicles retain mechanical fallbacks for critical safety systems, while others depend entirely on electronic control. The transition creates complexity during development; testing must cover not just hardware failure modes but also software edge cases and network latency.
SDV architecture also enables data collection at scale. Sensors feed continuous information back to manufacturers, revealing real-world usage patterns, component degradation, and potential safety issues. This data informs future designs and can trigger recalls or updates before failures occur. The trade-off is that vehicles become dependent on cloud connectivity and ongoing software support; a manufacturer that ceases support for a model may leave owners with vehicles that cannot be serviced or updated, raising questions about long-term ownership and obsolescence.