Master'sDefense, Military Engineering & Land Systems Applications open

Master’s in Avionics, Mission Systems and Open Architectures (MOSA/CMOSS) Engineering

Online master's programme of 1,900 hours in avionics, mission systems and open architectures (MOSA/CMOSS), structured in 12 modules covering MOSA, IMA avionics architecture, FACE, SOSA and CMOSS, MBSE, mission systems, middleware, cybersecurity, integration and sustainment, 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

Understand the MOSA approach and its contractual framework.

02

Design modular, integrated avionics architectures.

03

Apply the FACE, SOSA and CMOSS standards.

04

Use MBSE to define open architectures.

05

Develop portable software on standard middleware.

06

Integrate cybersecurity into open architectures.

07

Manage sustainment and technology refresh.

Profile

Who it's for

  • Mission systems architects defining open, modular architectures.
  • MBSE engineers modelling avionics and mission systems in SysML.
  • Embedded software engineers building portable software on FACE and DDS.
  • Avionics integration engineers working on IMA and OpenVPX platforms.
  • Embedded cybersecurity engineers securing open architectures.
  • Technology sustainment managers dealing with obsolescence and refresh cycles.
  • Engineering or science graduates aiming to enter the defence aerospace industry.
Standards & tools

What you'll work with

  • FACE Technical Standard (The Open Group)
  • SOSA Technical Standard (The Open Group)
  • ARINC 653 (avionics application software standard interface)
  • ANSI/VITA 65 (OpenVPX)
  • RTCA DO-178C (software considerations in airborne systems certification)
  • RTCA DO-326A (airworthiness security process specification)
  • OMG Data Distribution Service (DDS) (data-centric publish-subscribe middleware)
  • ISO/IEC/IEEE 15288 (system life cycle processes)
  • Cameo Systems Modeler
  • RTI Connext DDS
  • Wind River VxWorks 653
  • IBM DOORS Next
  • Capella
Syllabus

12 modules · 1900 h

  1. 1.1The MOSA concept
  2. 1.2Economic and sustainment drivers
  3. 1.3Vendor lock-in and its mitigation
  4. 1.4Open key interfaces
  5. 1.5Data rights and intellectual property
  6. 1.6US regulations on MOSA
  7. 1.7European open architecture initiatives
  8. 1.8Governance of open standards
  9. 1.9Legal and ethical framework
  10. 1.10Case study: analysis of the key interfaces of a mission system
  1. 2.1Federated architectures
  2. 2.2Integrated modular avionics
  3. 2.3Spatial and temporal partitioning
  4. 2.4ARINC 653
  5. 2.5Deterministic networks: AFDX and TSN
  6. 2.6MIL-STD-1553 buses and their evolution
  7. 2.7Distributed processing
  8. 2.8Reference architectures
  9. 2.9Safety and certification
  10. 2.10Lab: modelling an IMA architecture
  1. 3.1Origin of FACE and its consortium
  2. 3.2Architecture segments
  3. 3.3Transport Services Segment
  4. 3.4Operating system profiles
  5. 3.5FACE data model
  6. 3.6FACE conformance and certification
  7. 3.7Software portability
  8. 3.8Relationship with ARINC 653
  9. 3.9Use cases
  10. 3.10Practical exercise: definition of a FACE data model
  1. 4.1SOSA sensor architecture
  2. 4.2OpenVPX cards and backplanes
  3. 4.3Slot and module profiles
  4. 4.4CMOSS for communications and sensors
  5. 4.5VICTORY in vehicles
  6. 4.6Thermal management of embedded chassis
  7. 4.7Hardware management
  8. 4.8SOSA conformance
  9. 4.9Interoperability between standards
  10. 4.10Case study: module selection for an OpenVPX chassis
  1. 5.1MBSE principles
  2. 5.2The SysML language
  3. 5.3Requirements models
  4. 5.4Logical and physical architectures
  5. 5.5Interface modelling
  6. 5.6Trade-off analysis
  7. 5.7Digital thread
  8. 5.8Reference models for open architectures
  9. 5.9MBSE tools
  10. 5.10Lab: SysML model of a mission system
  1. 6.1Functions of a mission system
  2. 6.2Sensor management
  3. 6.3Data processing
  4. 6.4High-level data fusion
  5. 6.5Communications management
  6. 6.6Displays and HMI
  7. 6.7Data recording and management
  8. 6.8Edge computing
  9. 6.9Artificial intelligence and human oversight
  10. 6.10Practical exercise: functional architecture of a surveillance system
  1. 7.1Real-time operating systems
  2. 7.2Hypervisors and virtualisation
  3. 7.3DDS middleware
  4. 7.4Containers in embedded systems
  5. 7.5Portable software development
  6. 7.6DO-178C certifiable software
  7. 7.7Software reuse
  8. 7.8Continuous integration in defence
  9. 7.9Configuration management
  10. 7.10Lab: DDS communication between components
  1. 8.1Attack surface in open systems
  2. 8.2Aeronautical cybersecurity: DO-326A
  3. 8.3Security by design
  4. 8.4Secure boot and root of trust
  5. 8.5Separation of security domains
  6. 8.6Vulnerability management
  7. 8.7Supply chain protection
  8. 8.8Security certification
  9. 8.9Accreditation requirements
  10. 8.10Workshop: threat analysis of an open architecture
  1. 9.1Incremental integration
  2. 9.2System integration benches
  3. 9.3Verification of conformance with standards
  4. 9.4Interoperability testing
  5. 9.5Airworthiness certification
  6. 9.6Functional safety
  7. 9.7Environmental testing of electronics
  8. 9.8Regression testing
  9. 9.9Non-conformance management
  10. 9.10Practical exercise: integration plan for a new sensor
  1. 10.1Technology refresh cycles
  2. 10.2Electronic obsolescence management
  3. 10.3Technology insertion
  4. 10.4Life-cycle cost
  5. 10.5Business models with open architectures
  6. 10.6Competition in sustainment
  7. 10.7Data rights management
  8. 10.8Supplier ecosystems
  9. 10.9Lessons from programmes
  10. 10.10Case study: business case for an open architecture
  1. 11.1Procurement of open systems
  2. 11.2Interface specifications in contracts
  3. 11.3Intellectual property
  4. 11.4International cooperation
  5. 11.5Software export controls
  6. 11.6European strategic autonomy
  7. 11.7Ethics of automation
  8. 11.8Meaningful human oversight
  9. 11.9Transparency
  10. 11.10Workshop: data rights clauses in a contract
  1. 12.1Definition of the mission system
  2. 12.2Openness requirements
  3. 12.3Reference architecture
  4. 12.4Selection of standards
  5. 12.5MBSE model
  6. 12.6Cybersecurity analysis
  7. 12.7Integration and sustainment plan
  8. 12.8Conclusions
  9. 12.9Master's Thesis 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 each 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 Cameo Systems Modeler, RTI Connext DDS, Wind River VxWorks 653, IBM DOORS Next and Capella, in free, academic or evaluation versions. Testing is studied through real procedures for MBSE modelling of mission architectures, component integration with DDS middleware and verification of conformance with open standards. Assessment is continuous per module plus the final Master's Thesis.

Standards covered: FACE Technical Standard, SOSA Technical Standard, ARINC 653, ANSI/VITA 65, RTCA DO-178C, RTCA DO-326A, OMG Data Distribution Service (DDS), ISO/IEC/IEEE 15288.

Assigned technical tutor:every module ends with a deliverable that your tutor marks individually.
Standards-based learning:guided reading of FACE, SOSA and ARINC 653 applied to real cases, not as a theoretical annex.
Industry software:Cameo Systems Modeler, RTI Connext DDS, Wind River VxWorks 653, IBM DOORS Next and Capella, in free, academic or evaluation versions.
Master's Thesis with defence:An open mission system architecture project covering reference architecture, standards selection, MBSE model, cybersecurity and integration plan, 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.

IMA architecture model
Model an integrated modular avionics architecture with ARINC 653 partitioning.
FACE data model
Define a FACE data model for mission system components.
DDS component integration
Connect software components through DDS middleware.
Open architecture threat analysis
Carry out a threat analysis of an open mission architecture.
Master's Thesis
A complete open mission system architecture with MBSE model, cybersecurity analysis and integration plan, defended before a panel.
Career opportunities

Where this takes you

Mission systems architectMBSE engineerEmbedded software engineerAvionics integration engineerEmbedded cybersecurity engineerTechnology sustainment 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 Cameo Systems Modeler, RTI Connext DDS, Wind River VxWorks 653, IBM DOORS Next and Capella, 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 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 Avionics, Mission Systems and Open Architectures (MOSA/CMOSS) 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.