SysML v2 FAQ: What is SysML v2? Who created SysML v2?

What is SysML v2?

SysML v2 is the next evolution of the Systems Modeling Language developed and adopted by the Object Management Group (OMG). It is a major revision of SysML v1.x designed to address long-standing limitations and modernize model-based systems engineering (MBSE).

SysML v2 provides:

• A precise, formally defined semantic foundation
• A modernized and cleaner language architecture
• Both textual and graphical notations
• Improved interoperability across tools
• A standardized Systems Modeling API

Its objective is to enable more rigorous, scalable, and automatable systems engineering practices.

---

How is SysML v2 different from SysML v1.x?

SysML v2 represents a substantial redesign rather than an incremental update. Key differences include:

• A formal semantic foundation independent of diagrams
• A fully standardized textual notation
• A modular, library-based architecture
• Cleaner and more consistent language constructs
• Standard machine-readable representations (MOF, XMI, JSON)
• A normative SysML v1-to-v2 transformation specification
• A standardized Systems Modeling API

Unlike SysML v1.x, which was defined as a UML profile, SysML v2 is built on a dedicated modeling kernel and is no longer dependent on UML.

---

What is KerML and how does it relate to SysML v2?

KerML (Kernel Modeling Language) is the foundational modeling language underlying SysML v2.

KerML defines core modeling concepts such as:

• Types and specialization
• Features and membership
• Relationships and dependencies
• Constraints and expressions
• Structural and behavioral foundations

SysML v2 extends KerML with systems engineering–specific libraries, including requirements modeling, allocations, interfaces, analysis constructs, and other domain capabilities.

This layered architecture improves clarity, extensibility, and precision.

---

Is SysML v2 backward compatible with SysML v1.x?

SysML v2 is not backward compatible at the language level.

However, OMG provides a normative SysML v1-to-v2 Transformation Specification that defines how SysML v1.x models can be transformed into SysML v2 models while preserving modeling intent as much as possible.

Migration may still require review and adaptation due to conceptual and structural differences.

---

Does SysML v2 support graphical modeling?

Yes, SysML v2 supports graphical notation. Diagrams are defined as views of the underlying abstract syntax rather than serving as the semantic source of truth.

In addition, SysML v2 introduces a standardized textual notation that:

• Aligns directly with the formal abstract syntax
• Supports version control and diff/merge workflows
• Enables automation and scripting
• Integrates with modern DevOps pipelines

Textual and graphical representations are complementary and semantically equivalent.

---

Why was a textual syntax introduced?

The textual notation addresses practical workflow limitations experienced with diagram-only modeling.

It enables:

• Unambiguous and precise model definition
• Efficient editing of large models
• Git-based configuration management
• Automated validation and generation
• Continuous integration workflows

This aligns systems engineering practices more closely with modern software engineering methods.

---

What are machine-readable artifacts?

SysML v2 includes standardized machine-readable artifacts to enable tool interoperability and conformance.

These include:

• MOF-based abstract syntax definitions
• XMI representations
• JSON representations
• Standard libraries
• A Systems Modeling API specification

These artifacts allow consistent parsing, validation, model exchange, and tool integration.

---

What is the Systems Modeling API?

The SysML v2 Systems Modeling API defines a standardized way for tools to:

• Access and query model elements
• Navigate relationships
• Create and modify models
• Integrate analysis and external services

This significantly improves interoperability compared to the proprietary integrations typical of SysML v1.x environments.

---

Who should adopt SysML v2?

SysML v2 is intended for:

• Systems engineers practicing MBSE
• Organizations modernizing digital engineering workflows
• Tool vendors building next-generation modeling environments
• Teams planning migration from SysML v1.x
• Academic programs teaching advanced systems modeling

---

Is SysML v2 ready for production use?

SysML v2 has been formally adopted by OMG.

Production readiness depends on:

• Tool implementation maturity
• Workforce training
• Organizational transition planning
• Integration with existing engineering processes

Many vendors are actively implementing and releasing SysML v2 support, and pilot deployments are underway across industries.

---

Will SysML v2 replace SysML v1.x?

SysML v2 is expected to become the primary standard over time.

However:

• SysML v1.x remains widely deployed
• Long-lived programs may continue using v1.x
• Transition will occur gradually across organizations

Consequently, a phased migration strategy is recommended.

---

Where can I download the official SysML v2 specifications?

You can download SysML v2 specifications directly from the OMG web or from the SysML v2 Specifications page of this web.

---

How can I get started?

1. Read the official specifications
   • SysML v2 Specifications page of this web.

2. Explore reference implementations and example models
   • SysML v2 Release Repository (examples and pilot implementation):
   https://github.com/Systems-Modeling/SysML-v2-Release

3. Check out SysML v2 ModSim Tools
   • SysML v2 ModSim tool resources:
   https://sysml.org/sysml-v2/tools/

4. Check out SysML v2 Training Services
   • SysML v2 training resources:
   https://sysml.org/sysml-v2/training/

5. Engage with the SysML v2 community
   • SysML v2 Release discussion group:
   https://groups.google.com/g/sysml-v2-release

6. Start with a SysML v2 pilot project
   • Select a bounded system scope
   • Evaluate SysML v2 toolchain readiness
   • Define SysML v1 -> v2 migration and governance strategy
   • Capture lessons learned before scaling