Master'sElectronics, Embedded Systems & Telecom Applications open

Master’s in DevOps for Firmware and Connected Devices

Online master's programme of 1,900 hours in DevOps for firmware and connected devices (CI/CD, HIL farms, release train): 12 modules covering version control, reproducible builds, continuous integration, automated firmware testing, continuous delivery and OTA, supply-chain security, IoT backends, fleet observability, manufacturing provisioning and regulated products, with an assigned technical tutor.

Duration1,900 hours · 12–14 months
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 practices to firmware development.

02

Build reproducible build systems.

03

Automate continuous integration and testing.

04

Implement continuous delivery and OTA updates.

05

Protect the software supply chain.

06

Operate backends and fleets of connected devices.

07

Integrate DevOps into regulated products and manufacturing.

Profile

Who it's for

  • Embedded DevOps engineers.
  • Firmware engineers who want to automate their build, test and release flow.
  • IoT platform engineers.
  • Build and release engineers.
  • Test automation engineers.
  • DevSecOps engineers.
  • Engineering or science graduates seeking to enter industrial IoT.
Standards & tools

What you'll work with

  • Regulation (EU) 2024/2847 (Cyber Resilience Act) (cybersecurity requirements for products with digital elements)
  • ISO/IEC 5962 (SPDX) (software bill of materials format)
  • SLSA v1.0 (supply-chain levels for software artefacts)
  • IEC 62443-4-1 (secure product development lifecycle)
  • Automotive SPICE 4.0 (automotive process assessment model)
  • IEC 62304 (medical device software lifecycle)
  • ETSI EN 303 645 (cybersecurity for consumer IoT)
  • GitLab CI
  • Zephyr RTOS
  • Renode
  • Mender
  • Yocto Project
Syllabus

12 modules

  1. 1.1DevOps principles
  2. 1.2Differences from web DevOps
  3. 1.3Hardware constraints
  4. 1.4Firmware lifecycle
  5. 1.5Culture and collaboration
  6. 1.6DORA metrics
  7. 1.7Maturity of embedded processes
  8. 1.8Ecosystem tools
  9. 1.9Success stories
  10. 1.10Case study: assessing the development flow of a firmware team
  1. 2.1Advanced Git
  2. 2.2Branching strategies
  3. 2.3Monorepo and multirepo
  4. 2.4Submodules and dependency management
  5. 2.5Code reviews
  6. 2.6Conventional Commits
  7. 2.7Binary management with Git LFS
  8. 2.8Project templates
  9. 2.9Hardware configuration management
  10. 2.10Lab: trunk-based workflow for firmware
  1. 3.1CMake and Ninja
  2. 3.2West and Zephyr
  3. 3.3Yocto and BitBake
  4. 3.4Build containers
  5. 3.5Pinned toolchains
  6. 3.6Reproducible builds
  7. 3.7Build caches
  8. 3.8Product variant management
  9. 3.9Artefacts and repositories
  10. 3.10Practical exercise: reproducible build in a container
  1. 4.1Pipelines in GitHub Actions and GitLab CI
  2. 4.2Self-hosted runners
  3. 4.3Static analysis in CI
  4. 4.4Host-based unit testing
  5. 4.5Code coverage
  6. 4.6Quality gates
  7. 4.7Pipeline parallelisation
  8. 4.8Notifications
  9. 4.9Pipeline metrics
  10. 4.10Lab: CI pipeline for a Zephyr project
  1. 5.1Unit testing with Unity and Ceedling
  2. 5.2Hardware mocks
  3. 5.3Emulation with QEMU and Renode
  4. 5.4Integration testing
  5. 5.5Hardware-in-the-loop in CI
  6. 5.6Device farms
  7. 5.7Regression testing
  8. 5.8Performance testing
  9. 5.9Test reliability
  10. 5.10Practical exercise: Renode tests within CI
  1. 6.1Versioning and releases
  2. 6.2Image signing
  3. 6.3OTA updates
  4. 6.4Staged rollout
  5. 6.5Automatic rollback
  6. 6.6Mender, SWUpdate and RAUC
  7. 6.7Fleet management
  8. 6.8Feature flags in firmware
  9. 6.9Deployment to production
  10. 6.10Lab: OTA with Mender
  1. 7.1DevSecOps
  2. 7.2Dependency analysis
  3. 7.3SBOM with SPDX and CycloneDX
  4. 7.4Artefact signing with Sigstore
  5. 7.5Secrets management
  6. 7.6Pipeline protection
  7. 7.7SLSA and provenance
  8. 7.8Vulnerability scanning
  9. 7.9CRA compliance
  10. 7.10Practical exercise: SBOM and signing in the pipeline
  1. 8.1Infrastructure as code
  2. 8.2Cloud IoT platforms
  3. 8.3MQTT brokers
  4. 8.4Device provisioning
  5. 8.5Certificate management
  6. 8.6Kubernetes for IoT services
  7. 8.7Scaling
  8. 8.8Infrastructure costs
  9. 8.9High availability
  10. 8.10Lab: IoT backend with Terraform
  1. 9.1Fleet telemetry
  2. 9.2Remote logs
  3. 9.3Crash reports
  4. 9.4Health metrics
  5. 9.5Dashboards and alerts
  6. 9.6Correlation with releases
  7. 9.7Remote diagnostics
  8. 9.8Data privacy
  9. 9.9Continuous improvement
  10. 9.10Practical exercise: fleet health dashboard
  1. 10.1Programming on the production line
  2. 10.2End-of-line testing
  3. 10.3Injecting identities and keys
  4. 10.4Device traceability
  5. 10.5MES integration
  6. 10.6Production test automation
  7. 10.7Version management in the factory
  8. 10.8Production quality
  9. 10.9Firmware logistics
  10. 10.10Case study: secure provisioning process
  1. 11.1DevOps for medical devices
  2. 11.2DevOps in automotive and ASPICE
  3. 11.3Requirements traceability
  4. 11.4Test evidence
  5. 11.5Controlled change management
  6. 11.6Tool qualification
  7. 11.7Audits
  8. 11.8Automated documentation
  9. 11.9Balancing agility and compliance
  10. 11.10Workshop: pipeline with audit evidence
  1. 12.1Product and team
  2. 12.2Initial assessment
  3. 12.3Pipeline design
  4. 12.4Reproducible build
  5. 12.5Test automation
  6. 12.6OTA delivery
  7. 12.7Delivery chain security
  8. 12.8Metrics and evaluation
  9. 12.9Master's Thesis report
  10. 12.10Master's Thesis: defence before a panel
Methodology, software & labs

How you'll learn

100% online programme on the SEIUM campus, with downloadable material, recorded lectures and an assigned technical tutor. No fixed timetables: you progress at your own pace within each intake, so it fits around your job.

Each module combines theory, guided reading of the original standard and applied exercises. The working software is GitLab CI, Zephyr RTOS, Renode, Mender and the Yocto Project, in free, academic or evaluation versions. Testing is studied on real procedures: automated testing on device farms, staged OTA rollouts and firmware simulation in CI. Assessment is continuous by module, plus the final Master's Thesis.

Standards covered: Regulation (EU) 2024/2847 (Cyber Resilience Act), ISO/IEC 5962 (SPDX), SLSA v1.0, IEC 62443-4-1, Automotive SPICE 4.0, IEC 62304, ETSI EN 303 645.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of the Cyber Resilience Act (Regulation (EU) 2024/2847), ISO/IEC 5962 (SPDX) and SLSA v1.0 applied to real cases, not as a theoretical annex.
Industry software:GitLab CI, Zephyr RTOS, Renode, Mender and Yocto Project, in free, academic or evaluation versions.
Master's Thesis with defence:A complete DevOps pipeline for a firmware product, from reproducible builds and automated testing to OTA delivery and supply-chain security, 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.

Initial assessment
Assess the product and team development flow and design the target pipeline.
Reproducible build and CI
Containerise the build and set up CI with static analysis and quality gates.
Test automation
Automate firmware tests with Renode emulation and hardware-in-the-loop.
OTA and supply-chain security
Deliver signed OTA updates with SBOM and provenance.
Master's Thesis
An end-to-end firmware DevOps pipeline evaluated with delivery metrics, defended before a panel.
Career opportunities

Where this takes you

Embedded DevOps EngineerFirmware EngineerIoT Platform EngineerBuild and Release EngineerTest Automation EngineerDevSecOps Engineer
Admissions & scholarships

Requirements

  • University degree in engineering, science or architecture, or equivalent demonstrable professional experience.
  • 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, Zephyr RTOS, Renode, Mender and Yocto Project, 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 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 DevOps for Firmware and Connected DevicesEnrol
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.