AutomotiveCloudWatch

Glossary · Automotive

Software and SDV

78 terms in the Automotive glossary, each with its one-line definition.

78 terms, A to Z

  • A/B Partitioning Keeping two full software copies so a car runs from one while the update is written to the other, with fallback if the new one fails.
  • AI-Defined Vehicle AIDV Vehicle whose main features are driven by AI models that improve through data and updates rather than by hand-written rules.
  • Android Auto Google system that shows apps running on a connected Android phone on the car's screen, wired or wirelessly.
  • Android Automotive OS AAOS Version of Android that runs directly on the car's infotainment computer and can control vehicle features without a phone.
  • Apple CarPlay Apple system that shows iPhone apps on the car's screen, with CarPlay Ultra extending into the instrument cluster.
  • ara::com Programming interface AUTOSAR Adaptive applications use to offer and consume services over the network regardless of transport.
  • Arene Toyota's vehicle software platform, built by Woven by Toyota, giving shared tools and interfaces so features can be reused across models.
  • Atomic Service Small single-purpose software service that wraps one basic vehicle capability behind a standard interface, common in Chinese SOA designs.
  • Automotive Grade Linux AGL Linux Foundation open-source project building one shared Linux platform for infotainment, clusters and telematics.
  • Automotive Linux Use of the Linux operating system in vehicles, mainly for infotainment, telematics, gateways and central computers.
  • AUTOSAR Global partnership of carmakers, suppliers and tool vendors that standardizes how software inside vehicle ECUs is structured.
  • AUTOSAR Adaptive Manifest Configuration files that tell an AUTOSAR Adaptive computer how to start, resource and network each application.
  • AUTOSAR Adaptive Platform AP AUTOSAR standard for high-performance vehicle computers running full operating systems, built around services that can be updated.
  • AUTOSAR Classic Platform CP Original AUTOSAR standard for microcontroller ECUs, configured at build time for predictable timing in brakes, engines and doors.
  • AUTOSAR XML ARXML Standard file format AUTOSAR uses to describe software components, interfaces, ECU settings and network messages for exchange between tools.
  • Basic Software BSW Standard lower layers of an AUTOSAR Classic ECU covering communication, memory, diagnostics, operating system and hardware access.
  • Board Support Package BSP Bundle of drivers, bootloader and configuration needed to run an operating system on a specific board or chip.
  • Bootloader Small program that runs first when an ECU powers on, checks and starts the main software, and allows reprogramming.
  • China Industry Innovation Alliance for the Intelligent and Connected Vehicles CAICV MIIT-guided Chinese alliance that sets roadmaps, group standards and pilots for connected, automated and software-defined vehicles.
  • Cloud-Native Development Building vehicle software with cloud methods such as microservices, containers, virtual ECUs and automated pipelines before hardware exists.
  • Complex Device Driver CDD AUTOSAR Classic module allowed to access hardware directly for tight timing or unusual devices such as injection control.
  • Connected Vehicle Systems Alliance COVESA Nonprofit alliance, formerly GENIVI, that develops open connected-car standards such as the Vehicle Signal Specification.
  • Containerization Packaging an app with its libraries and settings into an isolated container that runs on a shared operating system.
  • Continuous Integration and Continuous Delivery CI/CD Working method in which every code change is automatically built, tested and packaged so problems surface immediately.
  • Delta Update Software update that sends only the changed parts between versions, shrinking downloads and install time.
  • Eclipse Kuksa Kuksa Open-source Eclipse SDV project giving vehicle apps one standard data broker to read and change vehicle signals using COVESA names.
  • Eclipse S-CORE S-CORE Open-source project launched in 2025 to build a shared safety-oriented core software stack for central vehicle computers.
  • Eclipse SDV Eclipse Foundation working group where carmakers, suppliers and tech firms build shared open-source software for software-defined vehicles.
  • Eclipse uProtocol Open-source framework letting software in the vehicle, phones and cloud communicate one consistent way over any underlying transport.
  • ECU State Manager EcuM AUTOSAR Classic module that controls ECU startup, sleep, wake-up and shutdown in the right order.
  • Embedded Rust Using the memory-safe Rust language for ECU and vehicle computer software to remove whole classes of C and C++ bugs.
  • Execution Management AUTOSAR Adaptive function that starts, stops and monitors programs on a vehicle computer and moves it through operating modes.
  • Features on Demand FoD Unlocking or adding car features after purchase through software, as a one-time purchase or a subscription.
  • Firmware Over-the-Air FOTA Over-the-air update of the low-level software in control units such as engine, brake or battery controllers.
  • Functional Cluster Building block of the AUTOSAR Adaptive Platform that provides one defined service such as communication, execution or updates.
  • GB 44496 China's mandatory national standard for vehicle software updates, in force since January 1, 2026.
  • Google Automotive Services GAS Licensed bundle of Google Maps, Google Assistant and Google Play for cars running Android Automotive OS.
  • Hardware Abstraction Layer HAL Software layer that hides specific hardware behind a standard interface so the same software runs on different chips.
  • Hardware-Software Decoupling SDV principle of separating software from its hardware so it can move between chips and be updated independently.
  • Hypervisor Software that splits one processor into isolated virtual machines, each running its own operating system.
  • In-Vehicle App Store Online store from which drivers download apps straight into the car's infotainment system.
  • Japan Automotive Software Platform and Architecture JASPAR Japanese association where automakers and suppliers jointly standardize in-vehicle software, networks and cybersecurity practices.
  • Microcontroller Abstraction Layer MCAL Bottom AUTOSAR Classic layer of drivers giving upper software a standard way to use a chip's built-in hardware.
  • Middleware Software between the operating system and applications that handles how programs find each other and exchange data.
  • Mobility DX Strategy Japan's 2024 METI and MLIT plan to help Japanese automakers compete in SDVs, automated mobility and data use.
  • NVRAM Manager NvM AUTOSAR Classic module that stores data that must survive power-off, such as calibrations and fault records.
  • OSEK/VDX OSEK 1990s German and French standard for small ECU real-time operating systems, communication and network management.
  • OTA Recall Safety recall fixed by an over-the-air software update instead of a dealer visit, still reported as a formal recall.
  • Ouranos Ecosystem METI-led Japanese initiative for trusted cross-industry data sharing, first applied to battery carbon footprint tracing.
  • Over-the-Air Update OTA Updating a car's software wirelessly over cellular or Wi-Fi to fix bugs, close security holes or add features.
  • Port Interface AUTOSAR contract defining what data or services one software component offers to or needs from another.
  • Portable Operating System Interface POSIX IEEE standards family defining common operating system functions so programs move between compliant systems.
  • QNX BlackBerry real-time operating system and platform used in clusters, driver assistance, infotainment and cockpits.
  • Real-Time Operating System RTOS Operating system that guarantees tasks finish within strict time limits, essential for engine, brake and steering control.
  • Rollback Returning an ECU or system to its previous software version when an update fails.
  • Runnable Entity Smallest schedulable piece of code inside an AUTOSAR software component.
  • Runtime Environment RTE Generated AUTOSAR Classic layer that connects software components to each other and to the Basic Software.
  • Scalable Open Architecture for Embedded Edge SOAFEE Arm-led initiative bringing cloud methods such as containers and orchestration into cars running on Arm chips.
  • Service-Oriented Architecture SOA Designing software so each vehicle function is a service with a defined interface that other programs can find and use.
  • Shift-Left Strategy of moving testing and integration earlier in development so mistakes are caught while cheap to fix.
  • Smartphone Projection Running apps on a phone and displaying them on the car's screen, as with CarPlay, Android Auto and Baidu CarLife.
  • Software Bill of Materials SBOM Machine-readable list of every software component, library and version in a product, used for license and vulnerability checks.
  • Software Component SWC AUTOSAR unit of application software with defined ports for the data and services it uses and provides.
  • Software Over-the-Air SOTA Over-the-air update of higher-level software such as infotainment apps, maps or the user interface.
  • Software-Defined Vehicle SDV Vehicle whose features and behavior are set mainly by software that is developed and updated separately from hardware.
  • Specified Modification Permission Japan's rule requiring MLIT approval before a software update changes how cars already on the road work.
  • Update and Configuration Management UCM AUTOSAR Adaptive service that safely installs, updates and removes software on a vehicle computer, with rollback.
  • Update Campaign Planned release of a specific software update to a defined vehicle group, rolled out in waves from the cloud.
  • Vehicle API Standard programming interface for apps to read vehicle data or use functions without knowing the ECUs underneath.
  • Vehicle Digital Twin Virtual copy of a vehicle or vehicle type mirroring its configuration, software versions and often live data.
  • Vehicle Hardware Abstraction Layer VHAL Part of Android Automotive OS that defines vehicle properties and links Android apps to the car's networks and ECUs.
  • Vehicle Information Service Specification VISS Standard web interface for apps and cloud services to read and write vehicle data using VSS names.
  • Vehicle Operating System Carmaker's common software foundation of OS, middleware, cloud services and tools reused across models and branded as an OS.
  • Vehicle Signal Specification VSS Open COVESA data model giving every vehicle signal a standard name in a tree structure.
  • Virtual ECU vECU Software model of an ECU that runs real or near-real production code on a PC or cloud server.
  • Virtual Functional Bus VFB AUTOSAR concept in which all software components talk as if on one perfect shared bus, independent of ECU mapping.
  • Virtual Machine VM Isolated software computer created by a hypervisor that runs its own operating system on shared hardware.
  • Worst-Case Execution Time WCET Longest a piece of code can ever take on a specific processor, used to prove safety tasks meet deadlines.

Full entry for members

Every term has a full entry for members: the plain-words definition, the practitioner note and the typed links between terms.

See membership

ACW Automotive Glossary, edition 2026.11.1. The headword and one line are open to everyone.