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

Master’s in AUTOSAR Adaptive, ROS 2 and DDS Engineering — Middleware Design, QoS and Discovery

Online master's programme of 1,900 hours in AUTOSAR Adaptive, ROS 2 and DDS engineering, structured in 12 modules covering DDS and its quality-of-service policies, discovery and networking, real-time ROS 2, AUTOSAR Adaptive, middleware design, security, performance and functional safety, 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

Compare middlewares for autonomous vehicles.

02

Configure DDS and its quality-of-service policies.

03

Develop ROS 2 applications with real-time requirements.

04

Implement services in AUTOSAR Adaptive.

05

Design gateways and interfaces between middlewares.

06

Secure middleware against threats.

07

Develop a complete middleware project for autonomous driving.

Profile

Who it's for

  • Middleware engineers working on DDS, SOME/IP or ROS 2 communication layers.
  • Automotive software architects who define communication and service interfaces.
  • ROS 2 engineers aiming to take robotics stacks towards production.
  • AUTOSAR Adaptive engineers expanding into DDS and ROS 2 interoperability.
  • Embedded systems engineers dealing with real-time constraints.
  • Software performance engineers focused on latency, jitter and throughput.
  • Engineering or science graduates aiming to enter the automotive sector.
Standards & tools

What you'll work with

  • AUTOSAR Adaptive Platform (service-oriented automotive software architecture)
  • OMG DDS 1.4 (Data Distribution Service)
  • OMG DDS-RTPS 2.5 (real-time publish-subscribe wire protocol)
  • OMG DDS Security 1.1 (security model for DDS)
  • ISO 26262 (functional safety of road vehicles)
  • ISO/SAE 21434 (road vehicle cybersecurity engineering)
  • AUTOSAR SOME/IP Protocol Specification (scalable service-oriented middleware over IP)
  • AUTOSAR E2E Protocol Specification (end-to-end communication protection)
  • ROS 2
  • Eclipse Cyclone DDS
  • eProsima Fast DDS
  • Eclipse iceoryx
  • vsomeip
Syllabus

12 modules · 1900 h

  1. 1.1Communication requirements in autonomous driving
  2. 1.2Publish-subscribe and service patterns
  3. 1.3Latency, determinism and bandwidth
  4. 1.4Middlewares in industry
  5. 1.5Comparison of AUTOSAR Adaptive, ROS 2 and DDS
  6. 1.6Real time and criticality
  7. 1.7Middleware scalability
  8. 1.8Interoperability between platforms
  9. 1.9Production challenges
  10. 1.10Case study: selecting middleware for a stack
  1. 2.1The OMG DDS specification
  2. 2.2Data-centric data model
  3. 2.3Topics, readers and writers
  4. 2.4Domains and partitions
  5. 2.5The RTPS transport protocol
  6. 2.6IDL language and types
  7. 2.7Fast DDS and Cyclone DDS implementations
  8. 2.8XML profile configuration
  9. 2.9DDS performance
  10. 2.10Lab: DDS application with Cyclone
  1. 3.1Reliability QoS policies
  2. 3.2Durability and persistence
  3. 3.3History and depth
  4. 3.4Deadline and liveliness
  5. 3.5Ownership and redundancy
  6. 3.6Latency budget
  7. 3.7QoS compatibility
  8. 3.8QoS tuning for sensors
  9. 3.9Diagnosing incompatibilities
  10. 3.10Practical exercise: QoS tuning for LiDAR
  1. 4.1Simple Participant Discovery Protocol (SPDP)
  2. 4.2Simple Endpoint Discovery Protocol (SEDP)
  3. 4.3Discovery servers
  4. 4.4Multicast versus unicast
  5. 4.5In-vehicle network configuration
  6. 4.6Discovery in large networks
  7. 4.7Discovery security
  8. 4.8Discovery performance
  9. 4.9Troubleshooting
  10. 4.10Workshop: discovery server in Fast DDS
  1. 5.1ROS 2 architecture
  2. 5.2Nodes, topics and services
  3. 5.3Actions and parameters
  4. 5.4The RMW abstraction layer
  5. 5.5Executors and callbacks
  6. 5.6Node composition
  7. 5.7Lifecycle management
  8. 5.8ros2 command-line tools
  9. 5.9Package ecosystem
  10. 5.10Lab: perception pipeline in ROS 2
  1. 6.1Real-time requirements
  2. 6.2Deterministic and event-driven executors
  3. 6.3Zero-copy communication with loaned memory
  4. 6.4Iceoryx and shared memory
  5. 6.5Thread scheduling
  6. 6.6Latency analysis
  7. 6.7ROS 2 on Linux PREEMPT_RT
  8. 6.8micro-ROS for microcontrollers
  9. 6.9Tracing tools
  10. 6.10Practical exercise: latency measurement with ros2_tracing
  1. 7.1Adaptive Platform architecture
  2. 7.2Functional clusters of the platform
  3. 7.3ara::com and SOME/IP
  4. 7.4ara::com over DDS
  5. 7.5Execution management
  6. 7.6State management
  7. 7.7Persistence and logging
  8. 7.8Application manifests
  9. 7.9Development tools
  10. 7.10Workshop: ara::com service over DDS
  1. 8.1Service interface design
  2. 8.2Data modelling
  3. 8.3Interface versioning
  4. 8.4Partitioning of nodes and processes
  5. 8.5Resource management
  6. 8.6Design patterns
  7. 8.7Integration with legacy systems
  8. 8.8Gateways between middlewares
  9. 8.9Architecture documentation
  10. 8.10Lab: ROS 2 to SOME/IP gateway
  1. 9.1The DDS Security specification and plugins
  2. 9.2Authentication and access control
  3. 9.3Data encryption
  4. 9.4Security in ROS 2 with SROS2
  5. 9.5Security in SOME/IP
  6. 9.6Certificate management
  7. 9.7Performance impact
  8. 9.8Threats to middleware
  9. 9.9ISO/SAE 21434 requirements
  10. 9.10Practical exercise: SROS2 configuration
  1. 10.1Middleware benchmarking
  2. 10.2End-to-end latency
  3. 10.3Throughput and jitter
  4. 10.4CPU and memory usage
  5. 10.5Analysis tools
  6. 10.6Traces and profiles
  7. 10.7Serialisation optimisation
  8. 10.8Bottleneck detection
  9. 10.9Stress testing
  10. 10.10Workshop: benchmark with performance_test
  1. 11.1ISO 26262-certified middleware
  2. 11.2Certifiable Safety DDS implementations
  3. 11.3Freedom from interference requirements
  4. 11.4Communication monitoring
  5. 11.5End-to-end (E2E) protection
  6. 11.6Tool qualification
  7. 11.7Safety argumentation
  8. 11.8Certified middleware suppliers
  9. 11.9Limitations of ROS 2 in production
  10. 11.10Case study: E2E protection over DDS
  1. 12.1Definition of requirements
  2. 12.2Middleware selection
  3. 12.3Interface and QoS design
  4. 12.4Node implementation
  5. 12.5Discovery configuration
  6. 12.6Middleware security
  7. 12.7Performance evaluation
  8. 12.8Conclusions and future work
  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 ROS 2, Eclipse Cyclone DDS, eProsima Fast DDS, Eclipse iceoryx and vsomeip, in free, academic or evaluation versions. Exercises are based on real procedures for measuring end-to-end latency, interoperability testing between middlewares and QoS tuning in sensor pipelines. Assessment is continuous by module, plus the final Master's Thesis.

Standards covered: AUTOSAR Adaptive Platform, OMG DDS 1.4, OMG DDS-RTPS 2.5, OMG DDS Security 1.1, ISO 26262, ISO/SAE 21434, AUTOSAR SOME/IP Protocol Specification, AUTOSAR E2E Protocol Specification.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of AUTOSAR Adaptive Platform, OMG DDS 1.4 and OMG DDS-RTPS 2.5 applied to real cases, not as a theoretical annex.
Industry software:ROS 2, Eclipse Cyclone DDS, eProsima Fast DDS, Eclipse iceoryx and vsomeip, in free, academic or evaluation versions.
Master's Thesis with defence:A complete middleware project for autonomous driving, from middleware selection and interface and QoS design to discovery, security and performance evaluation, 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 requirements and select middleware
Set communication requirements and justify the choice between AUTOSAR Adaptive, ROS 2 and DDS.
Design interfaces and QoS
Model service interfaces and data, and tune QoS policies for each sensor flow.
Implement nodes and discovery
Build the nodes and configure discovery for the in-vehicle network.
Secure the middleware
Apply DDS Security or SROS2 with certificate management and assess the performance impact.
Master's Thesis
Benchmark latency, jitter and throughput of the complete middleware architecture, defended before a panel.
Career opportunities

Where this takes you

Middleware EngineerAutomotive Software ArchitectROS 2 EngineerAUTOSAR Adaptive EngineerEmbedded Systems EngineerSoftware Performance 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.

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 ROS 2, Eclipse Cyclone DDS, eProsima Fast DDS, Eclipse iceoryx and vsomeip, 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 AUTOSAR Adaptive, ROS 2 and DDS Engineering — Middleware Design, QoS and DiscoveryEnrol
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.