Master'sAutonomous, ADAS & Software-Defined Vehicle Applications open

Master’s in SDV Platforms & Middleware Engineering

Online master's programme of 1,900 hours in SDV platform and middleware engineering, structured in 12 modules covering E/E architectures, service-oriented middleware, AUTOSAR Classic and Adaptive, operating systems and virtualisation, vehicle APIs, DevOps, OTA updates and security under ISO 26262, ISO/SAE 21434 and UN ECE R155, with an assigned technical tutor.

Duration1900 h
ModeOnline
LanguageEnglish
Start datesSet by the faculty
AwardSEIUM Institute diploma
Virtual lab · try it before you enrol

Take the controls.

Run a real engineering trade-off from this field. Move the sliders, watch the model react in real time and beat the challenge.

SIM · LIVE ●
Learning outcomes

What you will be able to do

01

Analyse the evolution towards the software-defined vehicle.

02

Design zonal and centralised E/E architectures.

03

Implement service-oriented middleware.

04

Configure operating systems and virtualisation in the vehicle.

05

Design vehicle abstraction APIs.

06

Apply DevOps practices and OTA updates.

07

Develop a complete SDV platform project.

Profile

Who it's for

  • Vehicle software architects moving towards centralised, service-oriented platforms.
  • Middleware engineers working with SOME/IP, DDS or AUTOSAR Adaptive.
  • Embedded platform engineers dealing with SoCs, hypervisors and automotive Linux.
  • Automotive DevOps engineers building pipelines and virtual ECUs.
  • Software integration engineers responsible for complex vehicle software stacks.
  • SDV product managers who need a solid technical foundation.
  • Engineering or science graduates aiming to enter the automotive sector.
Standards & tools

What you'll work with

  • ISO 26262 (functional safety of road vehicles)
  • ISO/SAE 21434 (road vehicle cybersecurity engineering)
  • UN ECE R155 (cybersecurity management system)
  • UN ECE R156 (software update management system)
  • AUTOSAR Adaptive Platform (service-oriented automotive software architecture)
  • ISO 24089 (software update engineering)
  • IEEE 802.1Q (VLANs and Ethernet traffic shaping)
  • OMG DDS (Data Distribution Service)
  • Eclipse Kuksa
  • vsomeip
  • Yocto Project
  • Docker
  • Vector DaVinci
Syllabus

12 modules · 1900 h

  1. 1.1The software-defined vehicle concept
  2. 1.2Evolution of E/E architectures
  3. 1.3From distributed ECUs to central computing
  4. 1.4Zonal architectures and wiring
  5. 1.5Separation of hardware and software
  6. 1.6Functions as a service
  7. 1.7SDV business models
  8. 1.8Manufacturers' strategies
  9. 1.9Organisational challenges of the transformation
  10. 1.10Case study: analysis of a commercial SDV architecture
  1. 2.1Functional domains of the vehicle
  2. 2.2Domain controllers
  3. 2.3Zonal input/output controllers
  4. 2.4High-performance central computer
  5. 2.5Automotive Ethernet networks
  6. 2.6CAN FD and CAN XL
  7. 2.7Zonal power distribution
  8. 2.8Wiring architecture
  9. 2.9Service-oriented design
  10. 2.10Lab: zonal architecture design
  1. 3.1Service-oriented architecture (SOA)
  2. 3.2The SOME/IP and SOME/IP-SD protocols
  3. 3.3Service discovery
  4. 3.4Data Distribution Service
  5. 3.5Publish-subscribe communication
  6. 3.6Data serialisation
  7. 3.7Quality of service in middleware
  8. 3.8Zero-copy middleware with shared memory
  9. 3.9Interoperability between middlewares
  10. 3.10Practical exercise: SOME/IP service with vsomeip
  1. 4.1AUTOSAR Classic and its architecture
  2. 4.2AUTOSAR Adaptive Platform
  3. 4.3ara platform services
  4. 4.4Execution and state management
  5. 4.5Communication between applications with ara::com
  6. 4.6Methodology and manifests
  7. 4.7Coexistence of Classic and Adaptive
  8. 4.8Configuration tools
  9. 4.9Licensing and suppliers
  10. 4.10Workshop: basic Adaptive application
  1. 5.1Automotive Linux
  2. 5.2QNX and POSIX systems
  3. 5.3Real-time operating systems
  4. 5.4Type 1 hypervisors
  5. 5.5Containers in the vehicle
  6. 5.6Resource partitioning
  7. 5.7Mixed criticality on a single SoC
  8. 5.8Android Automotive in infotainment
  9. 5.9Fast system boot
  10. 5.10Lab: containers in Yocto
  1. 6.1Automotive SoCs
  2. 6.2CPUs, GPUs and accelerators
  3. 6.3Memory architectures
  4. 6.4Bandwidth and interconnect
  5. 6.5Thermal and power management
  6. 6.6Component qualification
  7. 6.7NVIDIA, Qualcomm and Renesas platforms
  8. 6.8Platform scalability
  9. 6.9Hardware costs
  10. 6.10Practical exercise: sizing a central platform
  1. 7.1Hardware abstraction layer
  2. 7.2Vehicle Signal Specification (VSS)
  3. 7.3COVESA APIs
  4. 7.4Kuksa and signal servers
  5. 7.5APIs for third-party applications
  6. 7.6Permission management
  7. 7.7API versioning
  8. 7.8Vehicle data models
  9. 7.9Open SDV standards
  10. 7.10Workshop: VSS service with Kuksa
  1. 8.1Continuous integration and delivery
  2. 8.2Pipelines for vehicle software
  3. 8.3Automated testing at several levels
  4. 8.4ECU virtualisation
  5. 8.5Software digital twins
  6. 8.6Variant management
  7. 8.7Version control at scale
  8. 8.8Software bill of materials
  9. 8.9DORA delivery metrics
  10. 8.10Lab: CI pipeline with a virtual ECU
  1. 9.1Full and differential OTA updates
  2. 9.2SUMS under R156
  3. 9.3A/B partition architectures
  4. 9.4Rollback and recovery
  5. 9.5Management of update campaigns
  6. 9.6Dependencies and compatibility
  7. 9.7Software lifecycle
  8. 9.8Long-term maintenance
  9. 9.9Features on demand
  10. 9.10Practical exercise: A/B update with RAUC
  1. 10.1ISO 26262 in SDV platforms
  2. 10.2Criticality separation
  3. 10.3Cybersecurity under ISO/SAE 21434
  4. 10.4Regulation R155 and the CSMS
  5. 10.5Secure boot and root of trust
  6. 10.6Secure communication with SecOC
  7. 10.7Intrusion detection
  8. 10.8Vulnerability management
  9. 10.9Third-party security
  10. 10.10Case study: TARA of a central platform
  1. 11.1Eclipse SDV community projects
  2. 11.2The SOAFEE initiative for cloud-native workloads
  3. 11.3The COVESA alliance and its specifications
  4. 11.4AUTOSAR and its evolution
  5. 11.5Open-source projects
  6. 11.6Collaboration between OEMs and technology companies
  7. 11.7Free software licences
  8. 11.8Governance of open projects
  9. 11.9Ecosystem trends
  10. 11.10Workshop: prototype with Eclipse Velocitas
  1. 12.1Definition of platform requirements
  2. 12.2E/E architecture design
  3. 12.3Middleware selection
  4. 12.4Software stack design
  5. 12.5Update strategy
  6. 12.6Security analysis
  7. 12.7Functional prototype on a virtual ECU
  8. 12.8Conclusions and roadmap
  9. 12.9Thesis report
  10. 12.10Master's Thesis: defence before a panel
Methodology, software & labs

How you'll learn

Training is 100% online on the SEIUM campus, with downloadable material, recorded classes and an assigned technical tutor. There are no fixed timetables: you progress at your own pace within the intake, so the programme can be combined with work.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is Eclipse Kuksa, vsomeip, Yocto Project, Docker and Vector DaVinci, in free, academic or evaluation versions. Exercises are based on real procedures for prototyping services on virtual ECUs, continuous integration testing and OTA update trials. Assessment is continuous by module, plus the final Master's Thesis.

Standards covered: ISO 26262, ISO/SAE 21434, UN ECE R155, UN ECE R156, AUTOSAR Adaptive Platform, ISO 24089, IEEE 802.1Q, OMG DDS.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of ISO 26262, ISO/SAE 21434 and UN ECE R155 applied to real cases, not as a theoretical annex.
Industry software:Eclipse Kuksa, vsomeip, Yocto Project, Docker and Vector DaVinci, in free, academic or evaluation versions.
Master's Thesis with defence:A complete SDV platform project, from E/E architecture and middleware selection to the software stack, update strategy, security analysis and a functional prototype on a virtual ECU, defended before a panel.
Flexible format:100% online, no fixed timetables, compatible with full-time work.
Capstone project

Build it end to end

Your final project follows the real engineering workflow, step by step, reviewed by your tutor.

Define platform requirements
Set out the functional, performance and safety requirements of the SDV platform.
Design the E/E architecture
Lay out zonal controllers, the central computer and the in-vehicle network.
Build the software stack
Select the middleware and design the stack with operating systems, virtualisation and vehicle APIs.
Plan updates and security
Define the OTA strategy under R156 and carry out a TARA of the platform.
Master's Thesis
Develop a functional prototype on a virtual ECU with conclusions and roadmap, defended before a panel.
Career opportunities

Where this takes you

Vehicle Software ArchitectMiddleware EngineerEmbedded Platform EngineerAutomotive DevOps EngineerSoftware Integration EngineerSDV Product Manager
Admissions & scholarships

Requirements

  • A university degree in engineering, science or architecture, or equivalent demonstrable professional experience.
  • An internet connection and a computer capable of running the programme's software.
  • English sufficient to read technical standards.

Ready to start?

Send your application today. Our admissions team replies within 72 hours with your study plan and funding options.

FAQ

Frequently asked questions

The programme totals 1,900 hours over 12–14 months. You set your own pace within each intake, and your tutor helps you plan the workload around your job.

You work with Eclipse Kuksa, vsomeip, Yocto Project, Docker and Vector DaVinci, using free, academic or evaluation versions. Your tutor indicates the free alternative wherever one exists.

A SEIUM Institute diploma, awarded on passing the continuous assessment and the Master's Thesis. It is SEIUM's own qualification, not an official state degree; its recognition depends on the programme completed and the regulations of each country.

Yes. Modules passed in a course or postgraduate diploma in the same area are recognised in the higher programme. Ask about the recognition policy when you enrol.

A university degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the programme's software and English sufficient to read technical standards.

Start dates are set by SEIUM's faculty for each intake. Our admissions team will confirm the next available date when you apply.

Master’s in SDV Platforms & Middleware EngineeringEnrol
Scroll to Top
SEIUM – Institute of Advanced Engineering
Privacy Overview

This website uses cookies so that we can provide you with the best user experience possible. Cookie information is stored in your browser and performs functions such as recognising you when you return to our website and helping our team to understand which sections of the website you find most interesting and useful.