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

Master’s in Software-Defined Vehicle DevOps Engineering

Online master's programme of 1,900 hours in software-defined vehicle DevOps engineering, structured in 12 modules covering code management, continuous integration, continuous virtual testing, delivery to OTA, containers, infrastructure as code, DevSecOps, functional safety compliance and observability (ISO 26262, ISO/SAE 21434, UN ECE R156), 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

Apply DevOps principles to vehicle software development.

02

Design continuous integration pipelines for embedded targets.

03

Automate virtual testing in the pipeline.

04

Implement continuous delivery to OTA systems.

05

Integrate security and SBOM generation into the pipeline.

06

Automate functional safety evidence.

07

Develop a DevOps project for the SDV.

Profile

Who it's for

  • Automotive DevOps engineers modernising vehicle software delivery.
  • Platform engineers building internal developer platforms.
  • Continuous integration engineers working with embedded targets.
  • DevSecOps engineers integrating security into automotive pipelines.
  • SRE engineers applying reliability practices to vehicles in service.
  • Toolchain managers responsible for development tools and processes.
  • Engineering or science graduates seeking 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 R156 (software updates and update management systems)
  • Automotive SPICE 4.0 (automotive software process assessment model)
  • ISO 24089 (road vehicles – software update engineering)
  • SLSA v1.0 (supply-chain levels for software artefacts)
  • SPDX (ISO/IEC 5962) (software bill of materials format)
  • UN ECE R155 (cybersecurity management systems)
  • GitLab CI
  • Bazel
  • Yocto Project
  • Kubernetes
  • Terraform
Syllabus

12 modules · 1900 h

  1. 1.1DevOps principles applied to automotive
  2. 1.2Differences from web DevOps
  3. 1.3Safety and type-approval constraints
  4. 1.4DevOps culture and organisation
  5. 1.5Value stream of vehicle software
  6. 1.6DORA metrics in automotive
  7. 1.7Ecosystem tools
  8. 1.8Cases from leading manufacturers
  9. 1.9Barriers to adoption
  10. 1.10Case study: DevOps maturity assessment
  1. 2.1Monorepo versus multirepo
  2. 2.2Trunk-based branching strategies
  3. 2.3Code reviews and pull requests
  4. 2.4Software dependency management
  5. 2.5Variant management with feature flags
  6. 2.6Integration of supplier software
  7. 2.7Open-source software and licences
  8. 2.8Commit signing and provenance
  9. 2.9Git tools at scale
  10. 2.10Lab: trunk-based workflow with reviews
  1. 3.1Reproducible build pipelines
  2. 3.2Cross-compilation for embedded targets
  3. 3.3Bazel and Yocto build systems
  4. 3.4Distributed build caching
  5. 3.5Static analysis in the pipeline
  6. 3.6Automated unit testing
  7. 3.7Code coverage and thresholds
  8. 3.8Artefact management
  9. 3.9Pipeline parallelisation
  10. 3.10Practical: CI pipeline with Bazel
  1. 4.1Virtual ECUs in the pipeline
  2. 4.2Automated SIL testing
  3. 4.3Scenario simulation in CI
  4. 4.4Service integration testing
  5. 4.5Testing on shared HIL hardware
  6. 4.6Test farms
  7. 4.7Scenario-based regression testing
  8. 4.8Managing flaky tests
  9. 4.9Quality reports
  10. 4.10Workshop: SIL in CI with containers
  1. 5.1Release pipelines for vehicles
  2. 5.2Quality and approval gates
  3. 5.3Software signing and packaging
  4. 5.4Publishing to the OTA backend
  5. 5.5Staged fleet deployments
  6. 5.6Deployment to test fleets
  7. 5.7Rollback and recovery
  8. 5.8Vehicle configuration management
  9. 5.9Release traceability
  10. 5.10Lab: signed release to OTA
  1. 6.1Containers in the vehicle
  2. 6.2Lightweight orchestration at the edge
  3. 6.3Kubernetes in development and the cloud
  4. 6.4Minimal and secure images
  5. 6.5Resource management in containers
  6. 6.6The SOAFEE reference architecture
  7. 6.7Parity between cloud and vehicle
  8. 6.8Image registry
  9. 6.9Container security
  10. 6.10Practical: service deployment on k3s
  1. 7.1Terraform and Ansible tools
  2. 7.2Reproducible development environments
  3. 7.3Dev containers and remote workstations
  4. 7.4Test infrastructure management
  5. 7.5Provisioning of simulation clusters
  6. 7.6Secrets management
  7. 7.7Elastic scaling in the cloud
  8. 7.8Costs and FinOps
  9. 7.9Infrastructure documentation
  10. 7.10Workshop: test environment with Terraform
  1. 8.1Security integrated into the pipeline
  2. 8.2SCA dependency analysis
  3. 8.3SBOM generation
  4. 8.4Vulnerability scanning
  5. 8.5SAST static security analysis
  6. 8.6DAST dynamic testing
  7. 8.7Secrets management in CI
  8. 8.8Artefact provenance with SLSA
  9. 8.9ISO/SAE 21434 requirements
  10. 8.10Lab: SBOM and scanning in CI
  1. 9.1DevOps compatible with ISO 26262
  2. 9.2Evidence automation
  3. 9.3Traceability between requirements and tests
  4. 9.4Qualification of CI tools
  5. 9.5Controlled change management
  6. 9.6Automotive SPICE and agility
  7. 9.7Audits with pipeline data
  8. 9.8Release for type approval
  9. 9.9Documentation management
  10. 9.10Practical: automatic verification evidence
  1. 10.1In-vehicle software telemetry
  2. 10.2Logs, metrics and traces
  3. 10.3OpenTelemetry in automotive
  4. 10.4Monitoring of releases across the fleet
  5. 10.5Incident management
  6. 10.6Blameless post-mortem analysis
  7. 10.7SRE applied to the vehicle
  8. 10.8Service level objectives
  9. 10.9Feedback to development
  10. 10.10Case study: incident after an update
  1. 11.1Platform teams
  2. 11.2Team topologies
  3. 11.3Agile scaling with SAFe and LeSS
  4. 11.4Collaboration with suppliers
  5. 11.5Inner source practices
  6. 11.6Software product management
  7. 11.7Productivity measurement
  8. 11.8Training and culture
  9. 11.9Organisational transformation towards product
  10. 11.10Workshop: design of an internal developer platform
  1. 12.1Assessment of the starting situation
  2. 12.2Design of the toolchain
  3. 12.3Continuous integration pipeline
  4. 12.4Virtual testing strategy
  5. 12.5Delivery pipeline to OTA
  6. 12.6Security integration
  7. 12.7Automation of verification evidence
  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

100% online training 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 each intake, making it compatible with work.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is GitLab CI, Bazel, Yocto Project, Kubernetes and Terraform, in free, academic or evaluation versions. Testing is studied through real procedures: continuous integration with virtual ECUs, SBOM generation and vulnerability scanning, and staged deployments to test fleets. Assessment is continuous for each module, plus the final Master's Thesis.

Standards covered: ISO 26262, ISO/SAE 21434, UN ECE R156, Automotive SPICE 4.0, ISO 24089, SLSA v1.0, SPDX (ISO/IEC 5962), UN ECE R155.

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 R156 applied to real cases, not as a theoretical annex.
Industry software:GitLab CI, Bazel, Yocto Project, Kubernetes and Terraform, in free, academic or evaluation versions.
Master's Thesis with defence:a complete SDV DevOps project, from toolchain design and CI pipeline to virtual testing, delivery to OTA, security integration and automated verification evidence, 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.

CI pipeline for embedded targets
Build a reproducible CI pipeline with Bazel and cross-compilation.
Virtual testing in CI
Run containerised SIL tests with virtual ECUs in the pipeline.
Security in the pipeline
Generate an SBOM and add vulnerability scanning to CI.
Signed delivery to OTA
Produce a signed release and publish it to the OTA backend with staged deployment.
Master's Thesis
A complete SDV DevOps project, from toolchain design and CI pipeline to virtual testing, delivery to OTA, security integration and automated verification evidence, defended before a panel.
Career opportunities

Where this takes you

Automotive DevOps engineerPlatform engineerContinuous integration engineerDevSecOps engineerSRE engineerToolchain 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 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 GitLab CI, Bazel, Yocto Project, Kubernetes and Terraform, 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 degree in engineering, science or architecture (or equivalent professional experience), a computer able to run the 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 Software-Defined Vehicle DevOps 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.