Technologies / Programming

Systems engineering with SysML and UML 2 — advanced modeling

Three-day SysML and UML 2 training — requirements, structure, behavior and parametric diagrams. Model-Based Systems Engineering (MBSE) in practice. For systems engineers, architects and analysts.

Documents lie — models don’t

A 200-page requirements specification in Word. Nobody reads it in full. Half the requirements contradict each other, but you won’t find out until integration — when a change costs 100x more than at the modeling stage.

SysML (Systems Modeling Language) solves this problem. Instead of documents — models. Instead of text saying “the system must communicate with module X” — a diagram with ports, interfaces and flows that the tool validates automatically. Instead of traceability in Excel — satisfy/verify/derive relationships built into the model.

Who is this training for?

For engineers and architects working on complex systems. Especially when:

You design systems combining hardware and software (embedded, IoT, automotive, aerospace) and need a common language for both teams
Your organization is transitioning to MBSE (Model-Based Systems Engineering) and you need SysML competencies
You have UML experience and want to extend it with requirements, parametric and block diagrams

Three days: from diagrams to a complete model

Day 1: SysML fundamentals and structural diagrams. How SysML differs from UML, what UML cannot do. Requirements diagrams (req) with traceability, block definition diagrams (bdd), internal block diagrams (ibd) — system structure in a single model.

Day 2: Behavior and parameters. Activity, sequence, state machine diagrams — how the system responds to events. Parametric diagrams — modeling physical dependencies (mass, energy, timing) as constraint blocks.

Day 3: MBSE in practice. Traceability from requirements to verification (V-model). Profiles and stereotypes for your domain. Integration with tools (Rhapsody, Cameo, DOORS). Final workshop: complete system model.

SysML in regulated industries

Automotive requires ASPICE and ISO 26262. Aerospace — DO-178C and ARP 4754A. Medtech — IEC 62304. In all these standards, requirements traceability is mandatory. SysML is not “nice to have” — it is a compliance tool.

With over 2,500 trainings in our portfolio and a 4.8/5 rating, EITT is a trusted partner in competency development. Contact us — we’ll tailor the examples to your industry and tools.

Benefits

Model systems in SysML — from requirements (req) through structure (bdd/ibd) to behavior (act/sd/stm)
Apply parametric diagrams to model physical dependencies and constraint blocks
Build traceability from requirements through architecture to verification (V-model)
Distinguish when to use SysML vs UML 2 — and how to combine them
Create profiles and stereotypes tailored to the domain (automotive, aerospace, medtech)
Plan MBSE implementation in your organization — tools, processes, competencies

Who is this training for?

Systems engineers working on complex products (automotive, aerospace, defence, medtech)

Systems architects responsible for hardware-software architecture modeling

Requirements analysts transitioning from text documents to model-based requirements

Engineering project managers who need to understand SysML notation

Software engineers collaborating with systems engineering teams

Professionals preparing to implement MBSE (Model-Based Systems Engineering) in their organization

Prerequisites

Basic knowledge of UML (class, sequence, and use case diagrams)
Experience in systems engineering or architecture design
Familiarity with software or engineering product development processes

Training program

SysML vs UML 2 — what SysML adds to UML, what UML lacks, when to use which
MBSE (Model-Based Systems Engineering) — from documents to models, benefits and implementation challenges
Requirements diagram (req) — modeling requirements, traceability, derive/satisfy/verify relationships
Block definition diagram (bdd) — system structure, blocks, ports, interfaces
Internal block diagram (ibd) — connections between components, data and energy flow
Exercises: modeling requirements and system structure using examples from participants' domains

Activity diagram (act) — process modeling, control and data flows, swimlanes
Sequence diagram (sd) — interactions between components, use case scenarios, timing
State machine diagram (stm) — system states, transitions, guards, actions
Parametric diagram (par) — constraint blocks, modeling equations and physical dependencies
Use case diagram (uc) — actors, scenarios, system boundaries
Exercises: modeling system behavior — from use cases through sequences to state machines

Traceability in SysML — tracking requirements through architecture to verification (V-model)
Profiles and stereotypes — extending SysML for specific domains (automotive, aerospace)
SysML integration with other tools — Rhapsody, Cameo, Enterprise Architect, DOORS
Modeling patterns — how to organize the model, packages, viewpoints, top-down vs bottom-up approach
Final workshop: complete system model from requirements to verification
MBSE implementation plan — how to introduce modeling in your organization step by step

Delivery Methods

Online

Convenience of participating from anywhere
Interactive live sessions with trainer
Materials available for 30 days
No travel costs

On-site

Direct contact with trainer and group
Intensive hands-on workshops
Networking with other participants
Full focus on learning

Training Topics

Frequently asked questions

Do I need to know UML to participate?

Yes — this is an advanced training that assumes familiarity with UML basics (class, sequence, and use case diagrams). SysML extends UML with elements specific to systems engineering — without this foundation it will be difficult to keep up.

What tools are used during the training?

Exercises are conducted using a tool available to participants (e.g. Cameo Systems Modeler or Enterprise Architect). The modeling principles are universal and transfer to any SysML tool.

Which industries benefit from SysML?

Automotive (ASPICE, ISO 26262), aerospace (DO-178C, ARP 4754A), defence, medtech (IEC 62304), telecommunications, energy. Anywhere systems combine hardware, software and processes — and where traceability is required.

What is the format and duration of the training?

The training lasts 3 days (9:00-16:00), available online and on-site. Each day includes modeling exercises on real-world examples.

Will I receive a certificate after the training?

Yes, every participant receives a personalized certificate of completion issued by EITT.