Software-defined vehicles: architecture to application, 1.4 hours
One recorded webinar of about 1 hour 25 minutes, presented over slides, from October 2024. It moves from the SDV definition and its challenges to application examples, the reference architecture, and the open-source Eclipse Velocitas toolchain, then audience questions.
23 chapters · published 4 Oct 2024 · 6,484 views as of 19 Nov 2026 · by Skill-Lync
Free. We ask for your name and phone once before it plays here · or watch on YouTube ↗
Who is this course for?
Embedded, automotive software and E/E engineers and students who want to understand what an SDV is, how its on-board and cloud architecture fits together, and how in-vehicle apps are built.
What will you learn?
- Explain how an SDV differs from a traditional vehicle in coupling of hardware and software, prototype time and variant code
- List the six engineering challenges the speaker names for adopting SDVs
- Describe the move from distributed to domain to zonal E/E architecture with a high performance computer
- Explain why applications are containerized and where hypervisors, middleware and mixed-criticality virtual machines fit
- Trace data from an ECU through a feeder and data broker to a vehicle app in the Velocitas toolchain
- Describe the role of a unified vehicle API such as VSS in letting any developer write vehicle apps
What does each part of the course cover?
7 sections, in watching order. Click a timestamp to jump the player there. The video description has no chapter list, so these chapters and timestamps were written from the video itself.
- 0:0414 min · 4 chapters
What an SDV is and why software and hardware decouple
After housekeeping, the speaker defines an SDV as new functions and software updates through the vehicle's life, built on update and upgrade over the air. Then it compares traditional and SDV development on coupling, development cost, prototype time, time to market, MVP and one code base across variants.
- 14:047 min · 1 chapter
Six engineering challenges
The six challenges the speaker lists for adopting SDVs: software complexity from connected V2X systems, cyber security, standard hardware interfaces and a vehicle abstraction layer, development methodology, functional safety and compliance, and moving legacy AUTOSAR applications into containers.
Chapters
- 14:04The six engineering challenges of adopting SDVs
- 21:109 min · 3 chapters
SDV application examples
Applications are split into domain-specific, cross-domain and ecosystem-based. The examples are a car that adjusts lighting, temperature and music after a workout, a dog mode screen message, EV charge scheduling at off-peak hours with the grid, and a car that offers to post a scenic photo to social media.
- 30:025 min · 1 chapter
The philosophy of an SDV
Eight principles the speaker says a vehicle must meet to count as an SDV: flexibility and adaptability, modularity and reuse, enhanced functionality and customisation, integration and interoperability, cost-efficient upgrades, safety and security by design, user experience, and continuous improvement.
Chapters
- 30:02The philosophy of an SDV: eight principles
- 35:0113 min · 5 chapters
The SDV reference architecture
Walks the architecture with on-board services on the left and the cloud on the right: E/E architecture moving from distributed to domain to zonal with a high performance computer, then SoC, GPOS, hypervisor, middleware, containers, virtual ECUs in the cloud, the founding consortium, and mixed-criticality virtual machines.
- 47:4319 min · 5 chapters
Eclipse Velocitas toolchain for in-vehicle apps
Describes Eclipse Velocitas as an open-source framework for containerized in-vehicle applications. It covers the problems it targets, standard vehicle APIs, and the flow from ECU data feeder through a data broker with gRPC to a vehicle app, then the template, model generator, CI/CD and app container.
Chapters
- 47:43Eclipse Velocitas: the problems it targets and its solution
- 54:49The Velocitas data flow: feeder, data broker and vehicle app
- 59:50Any developer can write a vehicle app: the SDVerse app store
- 1:01:15From app template and model generator to a vehicle app container
- 1:04:08The software-defined car metro map
- 1:06:4919 min · 4 chapters
Audience Q&A
Questions answered cover open-source SDV consortia, edge computing and the high performance computer, whether VSS addresses privacy and security, how containers move apps between vehicles, AUTOSAR inside an SDV, and the open question of OTA reliability. The session closes with a training programme and next steps.
Is the Software-Defined Vehicles (SDVs): From Architecture to Application course really free?
Yes. All 1 h 25 min of it is free on Skill-Lync's YouTube channel, with no payment. To watch it on this page with the chapter guide, leave your name and phone number once; you can also watch it directly on YouTube. It was published on 4 Oct 2024 and had 6,484 views as of 19 Nov 2026. This page adds the chapter guide, a study plan and what to learn next.
How long does the Software-Defined Vehicles (SDVs): From Architecture to Application course take to finish?
The video runs 1 h 25 min across 23 chapters. At one hour a day that is about 2 days; plan roughly twice that if you practise each exercise as you go. The longest section is "Eclipse Velocitas toolchain for in-vehicle apps" (19 min), so give it its own days.
Does the free software-defined vehicles course come with a certificate?
The video description has a "claim your certificate" link, which now opens this page. To ask about a certificate for this course, leave your name and phone number in the form below and a Skill-Lync counsellor will call you back. The paid Skill-Lync courses linked here include a certificate along with mentor-reviewed projects.
What should I learn after this course?
The next step is Introduction to Automotive Embedded Systems and AUTOSAR (₹40,000), then Pre-Graduate Program in Embedded Systems (₹1,50,000). The free course teaches the concepts; the paid Skill-Lync courses add graded projects, mentor feedback and, in the PG programs, placement support.
Do I need to know AUTOSAR before watching an SDV webinar?
The webinar does not set prerequisites. The speaker mentions AUTOSAR Classic, AUTOSAR Adaptive, CAN and ECUs as familiar background and says existing AUTOSAR applications must be containerized, so basic embedded and automotive knowledge helps, but the SDV ideas are introduced from the definition onwards.
What is the difference between a software-defined vehicle and a traditional vehicle?
The speaker says that in a traditional vehicle software and hardware are tightly coupled and released together, whereas in an SDV they are loosely coupled. Software can be developed before hardware exists, a prototype can take hours instead of months, and the same code can serve all car variants.
Are the tools shown in the webinar open source?
The speaker describes Eclipse Velocitas as an open-source framework from the Eclipse SDV Foundation for building containerized in-vehicle applications, and says the code is available to inspect and change. The speaker also notes the toolchain is not an endorsement, only an open example.
Last updated 19 Nov 2026 · Course length, chapters, views and dates from the YouTube video on 19 Nov 2026 · Grow by Skill-Lync: free lessons from every course