SysML v2 is the next major generation of the Systems Modeling Language, the standard graphical and textual language for model-based systems engineering. Developed under the Object Management Group (OMG), it is a ground-up redesign of SysML v1.x intended to make system models far more precise, consistent, and interoperable.
What's new in SysML v2
- A precise metamodel: SysML v2 has its own formal foundation (KerML) rather than being a UML profile, removing the ambiguity that plagued v1.
- A textual notation: models can be authored as text, not just diagrams, making them diff-able, reviewable in version control, and far easier to manage at scale.
- A standard API and Services layer: a defined REST/Platform API lets tools read and write models interoperably, enabling the digital thread.
- Stronger semantics: clearer rules for structure, behavior, requirements, and analysis reduce misinterpretation between teams and tools.
SysML v2 vs. SysML v1: the key differences
| Aspect | SysML v1.x | SysML v2 |
|---|---|---|
| Foundation | UML profile | Dedicated metamodel (KerML) |
| Notation | Graphical only | Graphical + textual |
| Interoperability | Inconsistent across tools | Standard API for model exchange |
| Precision | Ambiguous in places | Formal, well-defined semantics |
| Version control | Difficult (binary model files) | Text-friendly, diff-able |
For a detailed engineer's-eye view of what changes day to day, see SysML v2 vs SysML v1.6: what changes for systems engineers.
A taste of the textual notation
part def Satellite {
part reactionWheels : ReactionWheel[3];
attribute mass : MassValue;
requirement settlingTimeReq {
doc /* Attitude shall settle within the required time. */
attribute settlingTime : TimeValue;
}
}Expressing models as text like this is one of the biggest practical wins of v2: it brings systems models into the same review, versioning, and automation workflows that software teams already rely on.
Why SysML v2 matters for tool selection
Many legacy MBSE tools were built entirely around SysML v1 and its UML heritage; retrofitting them for v2's new foundation is hard. This is a moment of disruption in the MBSE tool market, and an advantage for modern platforms designed around v2-era concepts from the start.
Dalus embraces the v2 generation of systems modeling, precise, machine-readable, and interoperable, while keeping the experience approachable. See what MBSE is for the broader context.
Frequently asked questions
What is SysML v2?+
SysML v2 is the next-generation Systems Modeling Language standardized by the Object Management Group (OMG). It is a ground-up redesign of SysML v1 with a precise metamodel, a textual notation in addition to diagrams, and a standard API, making model-based systems engineering models more rigorous and interoperable.
How is SysML v2 different from SysML v1?+
SysML v1 was built as a UML profile and was often ambiguous and inconsistent across tools. SysML v2 has its own dedicated metamodel (KerML), supports both graphical and textual notation, defines a standard API for exchanging models between tools, and has more precise semantics.
Does SysML v2 have a textual syntax?+
Yes. A major addition in SysML v2 is a textual notation, so models can be authored as text in addition to diagrams. This makes models diff-able, reviewable in version control, and easier to automate at scale.
Is SysML the same as MBSE?+
No. MBSE is the methodology of engineering with a central system model. SysML is one language used to express those models. SysML v2 is the current generation of that language.
Why does SysML v2 matter for choosing an MBSE tool?+
Many legacy tools were built around SysML v1's UML foundation, which makes adopting v2's new metamodel difficult. Tools designed around the v2 generation of concepts can offer better interoperability and a cleaner path to the digital thread.