MBSE Flagship Programme

Model-Based Systems Engineering and SysML v2

Use MBSE and SysML v2 to create connected system models, traceable decisions and a stronger digital engineering thread.

Move from document-centred engineering to an integrated model-based way of working.

Model-Based Systems Engineering and SysML v2 develops practical capability to organise system information as connected models rather than disconnected documents.

Participants learn MBSE planning, model purpose and scope, SysML v2 concepts, requirements, behaviour, structure, interfaces, analysis, verification relationships and model governance. The course also addresses transition considerations for organisations moving from established SysML v1 practices.

The emphasis is on useful modelling decisions, traceability, collaboration and lifecycle evidence—not on memorising notation in isolation.

What participants will be able to do.

By the end of the course, participants should be able to:

  • Explain MBSE principles, benefits, limitations and organisational implications.
  • Define an MBSE strategy including model purpose, scope, viewpoints, governance and stakeholders.
  • Use core SysML v2 concepts to represent system requirements, behaviour and structure.
  • Model relationships, interfaces, allocations and constraints with clear semantic intent.
  • Establish traceability across needs, requirements, architecture, analysis and verification.
  • Use model queries, views and analysis relationships to support decision-making.
  • Plan model configuration, reviews, quality checks and collaborative working practices.
  • Identify practical migration and adoption considerations for SysML v2 and the wider digital engineering environment.

Designed for professionals who contribute to complex-system decisions and delivery.

  • Systems engineers and systems architects.
  • Modelling specialists and digital engineering practitioners.
  • Requirements, integration and verification professionals working in model-based environments.
  • Technical leads and engineering managers sponsoring MBSE adoption.
  • Organisations transitioning from document-centric or SysML v1 practices.

Professionally relevant and application-focused.

Participants should understand basic systems engineering concepts. Previous SysML experience is helpful but not mandatory; exercises focus on concepts and practical modelling logic.

A five-module systems engineering learning journey.

The sequence develops understanding, application and practical engineering outputs progressively across five connected Modules.

1

Module 1

MBSE Strategy, Model Purpose and Digital Thread

  • Document-centric versus model-based engineering
  • Model purpose, scope, stakeholders and use cases
  • Viewpoints, model governance and information architecture
  • Digital thread, traceability and collaboration
2

Module 2

SysML v2 Foundations and System Definition

  • SysML v2 language concepts and semantic modelling
  • Packages, parts, definitions/usages and relationships
  • Needs, requirements and requirement relationships
  • Views and stakeholder-focused representations
3

Module 3

Behaviour, Structure, Interfaces and Constraints

  • Activities, actions and behavioural flows
  • Structural decomposition and part relationships
  • Interfaces, ports, connections and exchanges
  • Constraints, quantities and parametric reasoning
4

Module 4

Analysis, Verification and Traceability

  • Model-based trade studies and analysis links
  • Verification cases and requirement satisfaction evidence
  • Allocations, dependencies and end-to-end traceability
  • Queries, views and decision-support information
5

Module 5

Model Governance, Quality and Adoption

  • Model configuration and change control
  • Model quality, reviews and conventions
  • SysML v1-to-v2 transition considerations
  • MBSE implementation roadmap and integrated case review

Apply engineering concepts—not simply remember terminology.

Plan

Define why the model exists

Set model purpose, scope, viewpoints and governance before creating content.

Model

Represent the system coherently

Build connected requirements, behaviour, structure and interface information.

Trace

Create a digital thread

Link decisions and evidence across system-definition and verification activities.

Review

Assure model quality

Use conventions, configuration and technical reviews to maintain model integrity.

Adopt

Plan organisational transition

Identify practical steps for MBSE and SysML v2 capability development.

Demonstrate participation, application and professional judgement.

  • Participate in guided modelling and model-review exercises.
  • Develop the principal requirements, behaviour, structure and traceability views.
  • Complete an integrated model-based decision exercise.
  • Produce an MBSE workplace adoption/action plan.

Leave with practical systems engineering artefacts.

  • MBSE purpose and scope statement.
  • Model organisation and viewpoint plan.
  • SysML v2 requirements model.
  • Behaviour, structure and interface model views.
  • Traceability/verification relationship map.
  • Model governance and adoption roadmap.

Choose the format that fits your people and engineering environment.

Instructor-led

Live Classroom

Face-to-face delivery with facilitated discussion, system cases, engineering workshops, technical reviews and immediate feedback.

Instructor-led

Live Virtual Classroom

Interactive online delivery using collaborative workspaces, modelling activities, breakout analysis and guided application.

Flexible

Blended Learning

A structured combination of preparation, live sessions, applied assignments, engineering artefacts and follow-up application.

Organisation-specific

Corporate and In-Company

Tailored delivery aligned with organisational lifecycle processes, standards, systems, engineering roles, models and capability priorities.

Course information and participation.

Which SysML version does the course address?

The course focuses on SysML v2 and current model-based systems engineering practice, while recognising that many organisations are transitioning from SysML v1 environments.

Is SysML v2 an adopted standard?

Yes. OMG formally adopted SysML v2.0 in 2025. The course focuses on practical use and may be updated as tools and organisational adoption practices continue to mature.

Do I need a specific modelling tool?

No. The course is designed around language and engineering concepts. Tool-specific corporate delivery can be arranged where feasible.

Do I need previous SysML experience?

No, although familiarity with systems engineering helps. Participants with SysML v1 experience will also benefit from explicit transition discussion.

Can this support an organisational MBSE transformation?

Yes. Corporate delivery can add model-governance, adoption and roadmap workshops aligned with the organisation’s toolchain and engineering maturity.

Build practical MBSE capability and prepare your engineering environment for SysML v2.

Discuss public delivery, a corporate cohort or a tailored programme aligned with your organisation’s systems, lifecycle environment and engineering capability priorities.