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

Master’s in Dev Platforms Engineering for SDVs — Vehicle-Centric APIs, App Stores, Sandboxing and Permissions

Online master's programme of 1,900 hours in developer platform engineering for SDVs, structured in 12 modules covering vehicle-centric APIs, application frameworks, sandboxing and isolation, permissions and access control, platform security, driver distraction, app stores and distribution, data and privacy under ISO/SAE 21434, UN ECE R155 and UN ECE R156, with an assigned technical tutor.

Duration1900 h
ModeOnline
LanguageEnglish
Start datesSet by the faculty
AwardSEIUM Institute diploma
Enrol now View syllabus Ask an advisor
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

Design vehicle-centric APIs with standard data models.

02

Develop applications on SDV frameworks.

03

Implement sandboxing and isolation mechanisms.

04

Define permission and consent models.

05

Secure the platform against malicious applications.

06

Design application distribution and its governance.

07

Develop a complete SDV developer platform project.

Profile

Who it's for

  • Developer platform architects building ecosystems around the vehicle.
  • Vehicle API engineers designing signal and service interfaces.
  • Application security engineers reviewing and protecting third-party apps.
  • Developer ecosystem managers responsible for portals, SDKs and communities.
  • Connected services product managers shaping app stores and features on demand.
  • Embedded software engineers moving into application platforms.
  • Engineering or science graduates aiming to enter the automotive sector.
Standards & tools

What you'll work with

  • ISO/SAE 21434 (road vehicle cybersecurity engineering)
  • UN ECE R155 (cybersecurity management system)
  • UN ECE R156 (software update management system)
  • Regulation (EU) 2023/2854 (Data Act)
  • Regulation (EU) 2016/679 (GDPR)
  • ISO 26262 (functional safety of road vehicles)
  • ISO 15005 (dialogue management principles for in-vehicle systems)
  • ISO 24089 (software update engineering)
  • Eclipse Kuksa
  • Eclipse Velocitas
  • Android Automotive OS
  • Docker
  • Open Policy Agent
Syllabus

12 modules · 1900 h

  1. 1.1The automotive developer ecosystem
  2. 1.2Third-party applications in the vehicle
  3. 1.3App store models
  4. 1.4Manufacturer and technology company platforms
  5. 1.5Developer experience as a strategy
  6. 1.6Monetisation of features and services
  7. 1.7Success and failure stories
  8. 1.8Security and type-approval requirements
  9. 1.9Differences from the mobile ecosystem
  10. 1.10Case study: analysis of a vehicle app store
  1. 2.1Design of vehicle signal APIs
  2. 2.2The COVESA VSS specification
  3. 2.3Data models and ontologies
  4. 2.4Synchronous and event-driven APIs
  5. 2.5gRPC and REST in the vehicle
  6. 2.6API versioning and compatibility
  7. 2.7Documentation with OpenAPI
  8. 2.8Rate limits and quotas
  9. 2.9API mocks and simulators
  10. 2.10Lab: VSS API with Kuksa Databroker
  1. 3.1Eclipse Velocitas and templates
  2. 3.2Android Automotive and its APIs
  3. 3.3Android Car App Library
  4. 3.4Container-based frameworks
  5. 3.5UI and background applications
  6. 3.6Application lifecycle
  7. 3.7Dependency management
  8. 3.8Internationalisation and accessibility
  9. 3.9Testing of vehicle applications
  10. 3.10Practical exercise: sample Velocitas application
  1. 4.1Application isolation models
  2. 4.2Containers and namespaces
  3. 4.3WebAssembly as an isolated environment
  4. 4.4Virtual machines for third parties
  5. 4.5Resource limiting with cgroups
  6. 4.6Seccomp and system profiles
  7. 4.7Network isolation
  8. 4.8Sandbox escape attacks
  9. 4.9Isolation assessment
  10. 4.10Workshop: containerised application with limits
  1. 5.1Per-signal permission models
  2. 5.2Role-based access control
  3. 5.3User consent
  4. 5.4OAuth 2.0 and access tokens
  5. 5.5Declarative access policies
  6. 5.6Permissions for critical functions
  7. 5.7Access auditing
  8. 5.8Permission revocation
  9. 5.9Designing the consent experience
  10. 5.10Lab: access policies with OPA
  1. 6.1Threat modelling of third parties
  2. 6.2Application signing and verification
  3. 6.3Static and dynamic analysis
  4. 6.4App review in the store
  5. 6.5Detection of malicious behaviour
  6. 6.6Protection of vehicle APIs
  7. 6.7ISO/SAE 21434 requirements
  8. 6.8Vulnerability management
  9. 6.9Incident response across the fleet
  10. 6.10Practical exercise: TARA of a third-party application
  1. 7.1Freedom from interference with critical functions
  2. 7.2Restrictions while driving
  3. 7.3Driver distraction guidelines
  4. 7.4NHTSA visual distraction guidelines
  5. 7.5European HMI principles
  6. 7.6Speed-based feature lockout
  7. 7.7Interface validation
  8. 7.8Type-approval requirements
  9. 7.9Manufacturer liability
  10. 7.10Case study: distraction assessment
  1. 8.1Architecture of a vehicle app store
  2. 8.2Publishing and review process
  3. 8.3OTA distribution of applications
  4. 8.4Compatibility by model and variant
  5. 8.5Licence management
  6. 8.6Payments and subscriptions
  7. 8.7Usage analytics
  8. 8.8Support and updates
  9. 8.9Application withdrawal
  10. 8.10Workshop: application publishing flow
  1. 9.1Vehicle-generated data
  2. 9.2The European Data Act
  3. 9.3Personal data protection under the GDPR
  4. 9.4Anonymisation and pseudonymisation
  5. 9.5Consent management
  6. 9.6Sharing data with third parties
  7. 9.7Data for aftersales services
  8. 9.8Data minimisation
  9. 9.9Transparency towards the user
  10. 9.10Practical exercise: privacy impact assessment
  1. 10.1Development kits and SDKs
  2. 10.2Remote development environments
  3. 10.3Vehicle simulators
  4. 10.4Digital twins for testing
  5. 10.5Continuous integration for applications
  6. 10.6Remote debugging on the vehicle
  7. 10.7Portal and documentation
  8. 10.8Developer community
  9. 10.9Developer experience metrics
  10. 10.10Lab: environment with dev containers
  1. 11.1Revenue-sharing models
  2. 11.2Features on demand
  3. 11.3Developer relations
  4. 11.4Terms of service
  5. 11.5Ecosystem governance
  6. 11.6Competition and regulation
  7. 11.7Cross-brand interoperability
  8. 11.8Platform strategy
  9. 11.9Success indicators
  10. 11.10Case study: an OEM's ecosystem strategy
  1. 12.1Definition of the target ecosystem
  2. 12.2Design of vehicle-centric APIs
  3. 12.3Design of the execution sandbox
  4. 12.4Permission model
  5. 12.5Store architecture
  6. 12.6Security and privacy analysis
  7. 12.7Application prototype
  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, Eclipse Velocitas, Android Automotive OS, Docker and Open Policy Agent, in free, academic or evaluation versions. Exercises are based on real procedures for prototyping applications on vehicle APIs, assessing application isolation and security review of applications. Assessment is continuous by module, plus the final Master's Thesis.

Standards covered: ISO/SAE 21434, UN ECE R155, UN ECE R156, Regulation (EU) 2023/2854 (Data Act), Regulation (EU) 2016/679 (GDPR), ISO 26262, ISO 15005, ISO 24089.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of ISO/SAE 21434, UN ECE R155 and UN ECE R156 applied to real cases, not as a theoretical annex.
Industry software:Eclipse Kuksa, Eclipse Velocitas, Android Automotive OS, Docker and Open Policy Agent, in free, academic or evaluation versions.
Master's Thesis with defence:A complete SDV developer platform project, from vehicle-centric APIs and the execution sandbox to the permission model, store architecture, security and privacy analysis and an application prototype, 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 the target ecosystem
Identify developers, applications and business model for the platform.
Design vehicle-centric APIs
Model the APIs on VSS with versioning and documentation.
Design sandbox and permissions
Specify the execution sandbox and the per-signal permission and consent model.
Architect the store
Define publishing, review and OTA distribution, with a security and privacy analysis.
Master's Thesis
Build an application prototype on the platform and set out the roadmap, defended before a panel.
Career opportunities

Where this takes you

Developer Platform ArchitectVehicle API EngineerApplication Security EngineerDeveloper Ecosystem ManagerConnected Services Product ManagerEmbedded Software Engineer
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.

Apply now Scholarships
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, Eclipse Velocitas, Android Automotive OS, Docker and Open Policy Agent, 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.

Keep exploring

Related programmes

See all in Autonomous, ADAS & Software-Defined Vehicle
Master's6,610 $

Master’s in Reinforcement and Imitation Learning Engineering for Driving

Online master's programme of 1,900 hours in reinforcement and imitation learning engineering for driving, structured in 12 modules covering deep networks for control, imitation learning, inverse…

1900 hOnlineAutonomous, ADAS & Software-Defined Vehicle
Master's6,610 $

Master’s in AI Governance, AI Act & Privacy Engineering in AD

Online master's programme of 1,900 hours in AI governance, AI Act and privacy engineering for autonomous driving, structured in 12 modules covering the EU AI Act,…

1900 hOnlineAutonomous, ADAS & Software-Defined Vehicle
Master's6,610 $

Master’s in AUTOSAR Adaptive, ROS 2 and DDS

Online master's programme of 1,900 hours in AUTOSAR Adaptive, ROS 2 and DDS. 12 modules covering software-defined vehicle architectures, service-oriented middleware, in-vehicle Ethernet and TSN, real-time…

12–14 monthsOnlineAutonomous, ADAS & Software-Defined Vehicle
Master’s in Dev Platforms Engineering for SDVs — Vehicle-Centric APIs, App Stores, Sandboxing and PermissionsEnrol
Related programmes

More in Autonomous, ADAS & Software-Defined Vehicle

Master’s in Product, Regulation & Business EngineeringView programme →Master’s in Runtime Monitoring EngineeringView programme →Master’s in RTOS and Hypervisor Engineering in Automotive — Partitioning, Isolation and Mixed CriticalityView programme →Master’s in Specific Verticals and ODDs EngineeringView programme →Master’s in Human-Vehicle Interaction Engineering at Levels 2–4View programme →Master’s in Automotive RTOS and HypervisorsView programme →

All Autonomous, ADAS & Software-Defined Vehicle programmes → · How to apply · Fees & financing · Scholarships

Scroll to Top
SEIUM – Institute of Advanced Engineering
Powered by  GDPR Cookie Compliance
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.