# Summary: Building Blocks for Software-Defined Vehicles

In Part C of **SDV 101: Building Blocks**, we explored the foundational elements enabling modern software-defined vehicles (SDVs). At the core of SDVs lies the evolution of **E/E architectures**, which transition from legacy designs into either **domain-centralized architectures** or cutting-edge **zonal architectures** with **high-performance compute (HPC)** capabilities. These advancements provide the structural backbone for SDVs.

<figure><img src="/files/agWg22yPFLwDO3JUt80p" alt=""><figcaption></figcaption></figure>

Building on E/E architectures, SDVs implement **service-oriented architectures (SOAs)** that leverage **container runtimes** and **vehicle APIs** to ensure modularity, scalability, and integration with external ecosystems. Critical to this framework is the focus on **functional safety**, especially when operating in mixed-criticality environments, supported by **modern tech stacks** and industry standards such as **AUTOSAR**, **COVESA VSS**, and **SOAFEE**.

We also examined **over-the-air (OTA) updates**, a critical enabler for dynamic updates of software, AI models, and other digital artifacts, paving the way for continuous innovation. Finally, we looked at the concept of the **Vehicle App Store**, a transformative vision integrating secure environments, controlled API access, and cross-platform services to deliver new digital experiences to automotive customers.

Together, these building blocks represent the future of automotive innovation, where modular architectures, advanced software integration, and seamless updates redefine the vehicle experience.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://www.sdv.guide/sdv101/part-c-building-blocks/summary-building-blocks-for-software-defined-vehicles.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.