# Part C: Building Blocks

In this section, we explore the foundational components that enable Software-Defined Vehicles (SDVs) to transform the automotive industry. At the heart of this transformation lies the intricate interdependency between the Electrical/Electronic (E/E) Architecture and SDV.

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

E/E Architecture serves as the bridge connecting the mechanical systems of the vehicle, its power distribution network, and connectivity infrastructure with the software layers. It ensures that these traditionally hardware-dominated domains can support the dynamic, real-time demands of modern automotive software systems.&#x20;

Meanwhile, SDVs build on this foundation by introducing software-enabled vehicle experiences, creating a seamless blend of hardware capabilities and advanced digital services. Together, E/E Architecture and SDVs form the backbone of the next generation of connected, intelligent vehicles.

In this chapter, we delve into the key building blocks of software-defined vehicles (SDVs), exploring the critical integration of modern E/E architectures, such as domain-centralized and zonal high-performance computing (HPC) systems, with SDV-enabling technologies. These include service-oriented architectures (SOA), container runtimes, vehicle APIs, functional safety measures, over-the-air (OTA) updates, and the transformative potential of vehicle app stores—all built on robust modern tech stacks.

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


---

# 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.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.