SysML v2: the future of model-based system engineering
The design and manufacturing of today’s technological systems, both for software and hardware products, involve many engineering domains. This results in teams being larger and the interfaces between the different parts of the system increasing in both number and complexity. The needs and constraints imposed by customers are also becoming increasingly demanding, not only in terms of time and quality, but also for aspects such as modularisation, sustainability and security.
When it comes to system engineering activities, many industries are shifting from the traditional document based approach to model-based system engineering (MBSE). This is because relying on documents is not efficient anymore and can lead to mistakes and outdated information, which in turn results in unexpected costs and time-consuming reworking.
To implement MBSE at company, department or project level, we need to consider the methodology, tools and languages that will be used. One of these languages is Systems Modeling Language: more commonly referred to as SysML. The new version – SysML v2 – that was officially released this summer aims to provide a framework for more robust, integrated and automated digital ecosystems. In this blog series, we’ll cover the main aspects of SysML v2, with examples of how it can be used to support systems modelling. But first we’ll explain why it has been assigned so much importance in recent years and how industry is planning to adopt it.
By Paloma Maestro Redondo, System Engineer and Project Manager
What is SysML v2 and how is it linked to system engineering?
The increase of digitalisation in all the life cycle phases of a system requires advanced methodologies and tools to support the challenges of creating and maintaining system models, as well as their related documentation. In the context of the system engineering domain, the adoption of MBSE in multiple processes is already helping to improve traceability, consistency and requirements management while facilitating data exchanges between different teams at any stage of a project.
SysML has been one of the main standards in the MBSE world, allowing specification of requirements, structure, behaviour, interfaces and traceability across the different parts of a system model. As technologies and engineering systems evolve, teams demand higher automation and more precise semantics to model their products. Therefore, not only do the modelling tools have to be adapted to the new user needs, but the languages also need to be improved to avoid limitations when expressing requirements and architectures.
SysML v2 is the next-generation systems modelling language, designed to address these limitations, enabling the definition of more precise and expressive models. It also provides significant enhancements over the previous version in terms of usability and interoperability. While some of the tools implementing SysML v1 were more software engineering oriented, requiring a steep learning curve, SysML v2 is intended to be easier for system engineers to use. SysML v2 is also more powerful than the previous version, incorporating a highly sophisticated and semantically precise textual language on top of an enhanced graphical notation.
Who will use SysML v2?
SysML v2 will offer greater support for quantitative analysis, variant management, rigorous semantics and integration into digital engineering tool chains. In the context of space engineering, for example, all of these points are highly relevant for mission-critical and safety-critical systems.
It is expected that over the next few years, all members of the MBSE community will shift from SysML v1 to SysML v2, and it will become the main language for most of the projects where modelling is required.
Some of those expected to make use of the new modelling language are:
- System engineers working in the early phases of a project, defining the architecture and requirements, and performing analysis and trade-offs
- Domain engineers (thermal, structure, power, avionics, etc.) who need to connect their subsystem models to system level models
- Teams working on verification and validation activities
- Tool developers, software developers and teams working on system integration and digitalisation
- Project leaders who are committed to achieving greater assurance, traceability and automation throughout life cycles.
SysML v2 governance and roadmap
SysML v2 has been developed by the Object Management Group (OMG), the same international standards organisation responsible for the original SysML, Unified Modeling Language (UML) and other modelling standards. The development started in 2017, when OMG asked industry and the MBSE community to come up with definitions and required features for the next generation modelling language.
The official release was in July 2025, when OMG approved the final adoption of the SysML v2 specification, together with the Kernel Modeling Language (KerML) specification, which provides the semantic and syntactic foundation, and the Systems Modeling Application Programming Interface (API) and Services specification that enables interoperability with other models and tools.
The participating organisations came from a range of industry sectors, with a large aerospace representation. An extensive team of end-users were involved, as well as academia, government representatives and, of course, tool vendors. Different materials, sessions and demonstrations have been provided by OMG to promote SysML v2 and increase public awareness. There have been also several pilot projects and implementations by tool vendors, including open-source tool support, to demonstrate its benefits and allow end-users to test it.
The MBSE community in Europe is also engaging its members by organising workshops, such as the upcoming MBSE 2025 conference, to discuss the transition towards SysML v2 and migration strategies in the industry.
The European Space Agency (ESA) is working on adapting its methodology, the ESA SysML Solution, to the new version of the modelling language, sharing a pilot implementation for SysML v2 with the European space community. In the ground segment domain, ESA is working on the Ground and Space Segment Engineering Framework (GSEF), which is a tailored MBSE web platform to support space missions that will be compliant with SysML v2.
Challenges and considerations
While SysML v2 is more robust and powerful than the previous version,, and as with any evolving standard there is a risk for projects and teams adopting it prematurely. Another challenge to consider is the lack of a certified ecosystem of tools to support the modelling language, especially for integration with domain-specific tools.
Although the learning curve is expected to be less demanding, even users familiar with SysML v1 will need to learn a new textual and graphical syntax, as well as stricter semantics. Moreover, all methodologies and workflows based on SysML v1 will need to evolve to ensure compatibility with the new version. This will also be the case for other domain tools, like the ones used for requirements management, simulation or product line management, since interoperability will be also necessary in that context. While backward compatibility might be provided, legacy models will need to be migrated to SysML v2, preserving semantics and traceability.
Summary
SysML v2 represents a significant advancement for MBSE. Not only does it come with an improved notation and richer and more clear semantics, but also with more rigour, automation and functionalities to support interoperability between models. Consequently, engineers will benefit from a more powerful solution for implementing MBSE in their projects, streamlining key system engineering tasks such as traceability and variant management, while also integrating performance and behaviour parameters into models.
Looking ahead, SysML v2 is set to become the preferred MBSE standard in several industries and domains, facilitating interdisciplinary integration, automated verification and improved connection with digital twins.
In the context of space systems engineering, this means that SysML v2 can serve as the backbone for model-based processes and methodologies, linking mission and system architectures, subsystem modelling, simulation and verification activities, and traceability across supply chains and life cycles.
The adoption of SysML v2 will not only mean a change in language, but also a step forward towards a seamless integration of MBSE into system engineering processes. The European space sector, and ESA in particular, is working hard to test and implement the new version in its projects, and the MBSE community is closely following the latest developments.
Do you want to learn more?
If your team or organisation is interested in MBSE, if you would like to learn more about SysML v2 to implement it in your projects, or if you simply work on the space sector and want to stay up to date with the latest digital developments that will set the course for future missions, follow Starion on LinkedIn to be updated with the new posts in this series. Now is the perfect time to start exploring SysML v2, test out new tools and define transition plans to adopt the new version in your modelling activities.
You can also reach out to our team for guidance and support, and meet our experts at the Model-Based Space Systems and Software Engineering 2025 (MBSE 2025) Workshop that will be held in Vilnius, Lithuania, on 5-7 November, where we will present some of the activities related to MBSE in which Starion is involved.
