Dissecting SysML V2 Webinar

Don't feel like reading? Watch the recording!

This blog investigates the intricacies of SysML V2, its evolution from SysML V1, the introduction of KerML, and the promising roadmap ahead. Let's learn more about this advanced modeling language, understanding its purpose, key features, and potential applications.

Background and Evolution

SysML V2, a modeling language born out of the Systems Engineering Domain Special Interest Group, traces its roots back to SysML V1 in 2006. As industry needs grew, highlighting both strengths and weaknesses, the SysML V2 journey began. Over 200 individuals from 80 organizations formed the SysML V2 Submission Team (SST), responding to the Object Management Group (OMG) requests for proposals (RFPs) in 2017 and 2018. This laid the foundation for the development of SysML V2, aiming to enhance precision, expressiveness, and usability.

The Role of KerML

KerML, short for Kernel Modeling Language, plays a crucial role in SysML V2. Developed by the SST, Caramel is comprised of three layers: Root, Core, and Kernel. It provides a foundation for SysML V2, offering essential modeling capabilities like classes, data types, and behaviors. This structured approach allows for a usage-oriented modeling technique, setting the stage for the evolution of SysML V2.

Unpacking SysML V2

SysML V2 stands as a general-purpose modeling language, designed for system engineering approaches. The language aims to improve precision, consistency, usability, interoperability, and extensibility. It introduces a textual and graphical notation, offering flexibility and freedom in diagram creation. SysML V2 builds on the strengths of its predecessor, addressing shortfalls and embracing domain-specific concepts through its Systems layer.

Navigating the Textual Notation

Diving into the textual notation of SysML V2, we encounter concepts such as packages, parts, imports, definitions, usages, and specializations. The language introduces features like subsetting, redefines, and variability, providing a comprehensive toolset for effective modeling. However, challenges arise in visualizing the textual notation, calling for a balance between expressiveness and ease of use.

A Glimpse of Actions and Constraints

SysML V2 brings forth the concept of actions, revealing occurrences over time with coordination capabilities. The inclusion of control nodes, merge nodes, decision nodes, and structured control actions enhances the modeling potential. Constraints and requirements find a new hierarchy, offering a robust framework for specifying stakeholder-imposed constraints and validating system designs.

Challenges and Hope for the Future

While SysML V2 promises advancements, challenges persist. The learning curve, especially with the introduction of both textual and graphical notations, demands time and effort. The complexity of the language, reflected in its over 700-page specification, may pose hurdles in widespread adoption. The textual notation, though powerful, requires careful consideration to strike a balance between expressiveness and user-friendly visualization.

A Bridge: Lifecycle Modeling Language (LML)

For those seeking an alternative, the Lifecycle Modeling Language (LML) emerges as a solution. With a smaller set of entities, LML maintains simplicity while addressing the challenges of system modeling. Tools like Innoslate leverage LML to provide a cloud-based, full-lifecycle software solution, offering support for model-based system engineering, requirements management, and more.

Conclusion

As we navigate the evolving landscape of SysML V2, its potential applications, and the challenges it presents, the community eagerly awaits the unfolding chapters. The combination of textual and graphical notations, along with the introduction of API and services, opens new possibilities for system modeling.

The coming years will witness the convergence of innovative tools, improved learning resources, and the maturation of SysML V2 as a standard in the field of model-based system engineering.