Building expertise today to engineer the innovations of tomorrow 

Day 1 – MBSE Foundation & Structural Modelling

Session 1: Introduction to MBSE and SysML

• Transition from document-centric SE to MBSE

• The role of SysML in INCOSE’s Systems Engineering V-model

• What SysML can (and cannot) do

• SysML vs UML – why SysML is specialized for systems

• Overview of SysML diagram categories (Structure, Behavior, Requirements, Parametric)

Interactive Discussion: MBSE challenges in participants’ current projects

Session 2: Block Definition Diagram (BDD)

• Purpose of BDD

• Defining Blocks, Value Types, Properties

• Relationships:

  • Association

  • Aggregation

  • Composition (whole–part)

  • Generalization (inheritance)

• Hierarchical system decomposition
  
  

Hands-On Exercise:

• Model the structure of a System

• Add parts, subsystems, and relationships
  
  

Session 3: Internal Block Diagram (IBD)

• Purpose of IBD

• Defining ports, connectors, flows

• Modeling internal interactions of a system

• Allocating interfaces
  
  

Hands-On Exercise:

• Create an IBD showing component interactions

Session 4: Packages and Model Organization

• Packages for organizing large models

• Best practices for naming and structuring diagrams

• Example: Breaking down system model into packages

Day 2 – Requirements & Behavioural Modelling (Part 1)

Session 5: Requirements in SysML

• Types of requirements: Stakeholder, System, Derived

• Requirement diagram syntax

• Key relationships: satisfy, derive, refine, verify

• Benefits of traceability

Hands-On Exercise:

• Capture stakeholder needs for the chosen case study

• Link system requirements to blocks (traceability)

Session 6: Use Case Diagrams

• Purpose of Use Cases in SysML

• Identifying actors and system boundaries

• Use case relationships: include, extend, generalization

Hands-On Exercise:

• Model use cases for system

Session 7: Activity Diagrams

• Purpose of Activity Diagrams

• Modelling control flows vs object flows

• Decisions, merges, forks, joins

• Swim lanes for responsibility allocation
  
  

Hands-On Exercise:

• Create an activity flow for a sample use case

Day 2 Deliverables:

• Requirement model with traceability links

• Basic behaviour models: Use Case + Activity diagrams

Day 3 – Behavioural (Part 2) & End-to-End Modelling

Session 8: Sequence Diagrams

• Lifelines, messages, synchronous vs asynchronous calls

• Modelling interactions between system elements

• Example: ATM card authentication sequence

Hands-On Exercise:

• Create a sequence diagram

Session 9: State Machine Diagrams

• Purpose of state machines

• Elements: states, events, transitions, guards, actions

• When to use activity vs state machine

• Example: system operation states

Hands-On Exercise:

• Model a state machine for the sample system

Session 10: Putting It All Together – Mini Project

• Integrating Requirements + Structure + Behaviour

• Ensuring traceability between diagrams

• Demonstrating an end-to-end workflow:

  1. Stakeholder Need → Requirement → Block → Use Case → Behaviour (Activity/Sequence/State)

  2. Cross-checking consistency across diagrams

Group Work Exercise:

• Each team builds a mini SysML model for a chosen case study system

• Present their models to the group