SYSML V2:

WHERE WE ARE AND HOW WE GOT HERE

OMG MEETING
ORLANDO, FLORIDA
JUNE 21, 2023

SANFORD FRIEDENTHAL & ED SEIDEWITZ

CO-LEADS SYSML V2 SUBMISSION TEAM (SST)
 Agenda

❑ Part 1 – S. Friedenthal*
➢ Background
➢ Comparing SysML v2 with SysML v1
➢ Considerations for transitioning from SysML v1 to SysML v2
➢ Summary

❑ Part 2 – E. Seidewitz
➢ SysML v2 Submission Team
➢ Key language design principles
➢ Rational and trade offs for some key language design decisions
➢ Conclusion

* Reference: Friedenthal S., Seidewitz E., "SysML v2: Highlighting the Differences with SysML v1,
Project Performance International (PPI)", Systems Engineering Newsletter, PPI SyEN 123, April 2023
2 https://www.ppi-int.com/systems-engineering-newsjournal/ppi-syen-123/
PART 1
WHERE WE ARE
SANDY FRIEDENTHAL
 SysML v2 Examples
Open-Source Pilot Implementation
❑ Examples of the SysML v2 textual syntax were created using the open-source pilot
implementation that was developed as part of the SysML v2 submission
development effort
❑ The graphical views of the SysML v2 model were created using a prototype
visualization tool integrated with the pilot implementation, based on an open-source
application called Plant UML
➢ Note: Some SysML v2 views created in draw.io application

❑ The quality of the graphical visualization is limited but will be substantially improved
when commercial tools become available

4
BACKGROUND
 The Future of Systems Engineering
is Model-Based

❑ Part of the digital transformation

❑ Full life cycle from SoS to component level
❑ Agile system development including automated workflow and CM of the digital thread
❑ Model patterns and reuse

❑ Facilitates
➢ managing complexity & risk
➢ more rapidly respond to change
➢ reuse and design evolution
➢ reasoning about & analyzing systems Source: INCOSE SE Vision 2035
➢ shared stakeholder understanding
➢ automated documentation & reporting

6
 Systems Modeling Language™ (SysML ®)

Supports the specification, analysis, design, and verification and

validation of complex systems that may include hardware, software,
information, processes, personnel, and facilities

SysML has evolved to address user and vendor needs

v1.0 adopted in 2006; v1.7 adopted 2022

SysML v1 has facilitated awareness and adoption of MBSE

Much has been learned from using SysML v1 for MBSE

SysML v2 is the next generation systems modeling language

intended to address some of the limitations of SysML v1

7
 SysML v2 Status

February 2023 Submitted Alpha Specifications

March 2023 Formed Finalization Task Forces
June 2023 Adopted by OMG Board of Directors
Published Beta Specifications
December 1, 2023 Public Comment Deadline
March 2024 Deliver Finalized Specifications
Establish Revision Task Forces
Mid 2024 Publish Formal Specifications

8
COMPARING SYSML V2
WITH SYSML V1
 SysML v2 Objectives

Increase adoption and effectiveness of MBSE with SysML by enhancing…

➢ Precision and expressiveness of the language
➢ Consistency and integration among language concepts
➢ Interoperability with other engineering models and tools
➢ Usability by model developers and consumers
➢ Extensibility to support domain specific applications
➢ Migration path for SysML v1 users and implementors

10
 Key Elements of SysML v2

❑ New Metamodel that is not constrained by UML

➢ Preserves most of UML modeling capabilities with a focus on systems modeling
➢ Grounded in formal semantics

❑ Robust visualizations based on flexible view & viewpoint specification

➢ Graphical, Tabular, Textual

❑ Standardized API to access the model

11
 SysML v2 Language Capabilities

Requirements
Behavior
- function-based Analysis
- state-based - analysis cases
- sequence-based - expression language
- use cases SysML v2
Structure
Language
- decomposition Verification
- interconnection - verification cases
- classification
View & Viewpoint

12
 Simple Vehicle Model
SysML v2 Textual and Graphical Syntax

13
 Definition and Usage
SysML v2 vs. SysML v1
❑ Reuse concept to define an element once and use it in different contexts
❑ SysML v1 informally introduces the concept of definition and usage (e.g., block and
part property)
➢ It is applied inconsistently across the language (e.g., blocks, activities, requirements)

❑ Definition and usage elements are formally part of SysML v2

➢ Applies to virtually all elements (e.g., attributes, parts, ports, connections, actions, states,
, , , ,…)
➢ Supports consistent pattern of decomposition and specialization

❑ Benefits
➢ Enables effective reuse
➢ Facilitates learning and using the language
➢ Enables automation

14
 Terminology (partial)
SysML v2 vs. SysML v1

SysML v2 SysML v1
part / part def part property / block
attribute / attribute def value property / value type
port / port def proxy port / interface block
action / action def action / activity
state / state def state / state machine
constraint / constraint def constraint property / constraint block
connection / connection def connector / association block
requirement / requirement def requirement
view / view def view

SysML v2 applies a consistent pattern of definition and usage

15
 SysML v1 and v2
Vehicle Block vs Part Decomposition

e a e a

SysML v1 SysML v2
Block Decomposition Part Decomposition
16
 SysML v2 Requirement

❑ Builds on SysML v1 concept of a property-based requirement «requirement group»

vehicleSpecification

❑ A constraint definition that a valid design solution must satisfy that

can include: «requirement»
<1> massReqt:MassRequirement
➢ Identifier doc The actual vehicle mass shall be
less than the required vehicle mass.

➢ Shall statement
➢ Constraint expression that can be evaluated to true or false
constraints
➢ Attributes of the constraint expressions ^require {massActual<=massRequired}
assume {massFluid<=40 [kg]}

➢ Assumed constraint expression must be true for the requirement to

be applicable

A SysML v2 Requirement Can be Evaluated by a Solver as Pass or Fail

17
 SysML v1 Instances vs.
SysML v2 Individuals and Snapshots
SysML v2 distinguishes the concept of an individual from a snapshot of an individual at a point in its
lifetime

SysML v1 SysML v2
18
 SysML v2 Alias and Short Name

alias

short name

19
 Language Extension
SysML v2 vs SysML v1
Library extension mechanism in SysML v2 can automatically combine the capability of
specialization with stereotypes

SysML v1 SysML v2

20
 Simple Vehicle Model

21
 Connecting SysML v2 through the standard API

Systems Modeling API

SysML v2
CM of the Digital Thread
Source: Syndeia with SysML v2
• Structure
• Behavior CAD/CAD Viewer
Source: FreeCAD with SysML v2
• Requirements
• Analysis
• Verification
• View & Viewpoint

Graph Visualization Analysis Solver

Source: Tom Sawyer with SysML v2 Source: Maple with SysML v2

23
 Comparing SysML v2 with SysML v1

✓ Simpler to learn and use ✓ More expressive

➢ Systems engineering concepts designed ➢ Variant modeling
into metamodel versus added-on ➢ Analysis case
➢ Consistent application of definition and ➢ Trade-off analysis
usage pattern
➢ Individuals, snapshots, time slices
➢ More consistent terminology
➢ More robust quantitative properties (e.g., vectors, ..)
➢ Ability to decompose parts, actions,
➢ Simple geometry
➢ More flexible model organization with
package filters ➢ Query/filter expressions
➢ Metadata
✓ More precise
➢ Textual syntax and expression language ✓ More extensible
➢ Formal semantic grounding ➢ Simpler language extension capability
▪ Based on model libraries
➢ Requirements as constraints
✓ More interoperable
➢ Standardized API
24
TRANSITIONING TO
SYSML V2
 SysML v1 to v2 Transition Planning

❑ Integrate transition planning with existing MBSE/DE initiatives

➢ MBSE improvement teams and community of practices

❑ Initiate pilots using the Jupyter environment to begin impact assessment

❑ Initiate tool vendor discussions on roadmap
❑ Prepare incremental plans
➢ MBSE practices ➢ Reference models and reuse repositories
➢ Tool infrastructure ➢ MBSE Community of Practice website
➢ Training ➢ Criteria for project deployment
➢ Metrics
Transition Guidance being developed
by DoD office of DE, Modeling & Simulation

26
 SysML v1 to SysML v2 Transformation

SysML v1 Model SysML v2 XMl SysML v2 Textual Notation

package eVehicleLibrary {
attribute def ElectricEnergy;
attribute def BatteryCapacity :> ScalarValues::Integer;
attribute def Speed :> ScalarValues::Integer;
port def Pow erOutPort { out energy : ElectricEnergy;
}
interface def Pow erInterface {
end supplierPort : Pow erOutPort;
end consumerPort : ~Pow erOutPort;
}
}
package eVehicleDefinitions {
import eVehicleLibrary::*;
part def Wheel {
value size : ScalarValues::Integer;

Source: SST Track 3 Presentation }

part def Battery {

Yves Bernard, Tim Weilkiens }

value capacity : BatteryCapacity;

08 February 2022 }
part def Engine;

27
 SysML v2
Creating a Culture of Model Quality
❑ Transition to SysML v2 provides an opportunity to improve model quality
➢ Bring more rigor to MBSE to ensure model satisfies its intended purpose
➢ Applies if transforming a SysML v1 model or developing a new model

❑ The need for rigor

➢ Consistent high quality training material
➢ Practitioner and instructor certifications
➢ Modeling guidelines, patterns, practices, and metrics
➢ Validation suites and correct by construction
➢ Review processes
➢ Validated reference models
➢ …

28
 SUMMARY

29
 Summary

❑ SysML v1 is based on UML which was originally designed as a software modeling

language
❑ SysML v2 was designed to address the SysML v1limitations and improve MBSE
adoption and effectiveness
➢ New metamodel with both graphical and textual syntax and standardized API to access the
model
➢ More precise, expressive, usable, interoperable, and extensible
➢ Consistent definition and usage pattern enables reuse, usability, and automation

❑ Progress/Plans
➢ Awaiting OMG approval for SysML v2 beta specifications leading to final adopted specification
in 2024
➢ Will continue to evolve specification with domain specific extensions

❑ Organizations should begin SysML v2 transition planning to advance their MBSE

capabilities
➢ Treat as an opportunity to improve model quality

30
 PART 2
HOW WE GOT HERE
ED SEIDEWITZ

31
 Second-System Effect

"The tendency of small, elegant, and successful

systems to be succeeded by over-engineered,
bloated systems, due to inflated expectations
and overconfidence."
https://en.wikipedia.org/wiki/Second-system_effect
http://catb.org/jargon/html/S/second-syste m-effect.html
Fred Brooks, The Mythical Man-Month, Chapter 5

32
SYSML V2 SUBMISSION TEAM
 SysML v2 Submission Team (SST)

SysML v2 Requests for Proposals

Language : December 2017
API and Services : June 2018

SST formed December 2017

Leads: Sandy Friedenthal, Ed Seidewitz

A broad team of end users, vendors,

academics, and government liaisons
Grew to 200+ members from 80+ organizations

Developed submissions to both RFPs

Final submission: February 2023

34
 SST Participating Organizations

▪ Aerospace Corp ▪ Intercax ▪ Qualtech Systems, Inc (QSI) Academia/Research

▪ Airbus ▪ Itemis ▪ Raytheon Tool Vendor
▪ ANSYS medini ▪ Jet Propulsion Lab ▪ Rolls Royce Government Rep
▪ Aras ▪ John Deere ▪ Saab Aeronautics End User
▪ Army Aviation & Missile Center ▪ Kenntnis ▪ SAF Consulting * INCOSE rep *
▪ Army CBRND ▪ KTH Royal Institute of Technology ▪ SAIC
▪ BAE ▪ LieberLieber ▪ Siemens
▪ BigLever Software ▪ Lightstreet Consulting ▪ Sierra Nevada Corporation
▪ Boeing ▪ Lincoln Lab ▪ Simula
▪ U.S. Army DEVCOM Armaments Center ▪ Lockheed Martin ▪ Space Cooperative
▪ CalTech CTME ▪ MathWorks ▪ Sodius Willert
▪ CEA ▪ Maplesoft ▪ System Strategy *
▪ Contact Software ▪ Mercury Systems ▪ Tata Consultancy Services
▪ Defence Science and Technology Group ▪ Mgnite Inc ▪ Thales
▪ DEKonsult ▪ MID ▪ Thematix
▪ Delligatti Associates ▪ MITRE ▪ Tom Sawyer
▪ Draper Lab ▪ ModelAlchemy Consulting ▪ Twingineer
▪ ESTACA ▪ Model Driven Solutions ▪ UFRPE
▪ Ford ▪ Model Foundry ▪ University of Western Switzerland (Rosas
▪ Fraunhofer FOKUS ▪ NIST Center)
▪ General Motors ▪ No Magic/Dassault Systemes ▪ University of Cantabria
▪ George Mason University ▪ OAR ▪ University of Alabama in Huntsville
▪ GfSE ▪ Obeo ▪ University of Detroit Mercy
▪ Georgia Tech/GTRI ▪ OOSE ▪ University of Kaiserslautern / VPE
▪ IBM ▪ Ostfold University College ▪ Vera C. Rubin Observatory
▪ Idaho National Laboratory ▪ Phoenix Integration/ANSYS ▪ Vitech
▪ IncQuery Labs ▪ PTC ▪ 88solutions

35
 SST Incremental Approach
Track 3
Track 2 Profile Dev / Track 4 Track 5 Track 6
Reqts V&V Transformation Metamodel Dev API/Services Dev Pilot Implementation
SysML v2 SysML v2
Language Reqts API/Services Reqts
MagicDraw/TWC MagicDraw/TWC Xtext

Validation Metamodel Textual

Cases Design Notation
Monthly MagicDraw/TWC
baseline
API
MagicDraw/TWC PIM/PSM Tom Sawyer
Jupyter PlantUML
User Profile Design / v1-
Models v2 Transform Graphical
Visualization
Play PostgreSQL

API/Repository
Eclipse
Implementation

Track 1 Pilot
Project Mgmt Implementation
View Generation & Incremental
OpenMBEE /
Spec Production Release
View Editor

36
 SST Milestones

December 2017 SysML v2 RFP issued; SST formed

June 2018 SysML v2 API & Services RFP issued
August 2019
August 2019 Internal Review
Internal Review
August 2020 Initial Submission
February 2021
February 2021 Stakeholder Review
Stakeholder Review
August 2021 1st Revised Submission
November 2021 2nd Revised Submission
September 2022
September 2022 Specification Review
Specification Review(2½
(2½days)
days)
November 2022 3rd Revised Submission
December 2022
2022 Established Change
Established ChangeBoard
Board
February 2023 Final Submission

37
KEY DESIGN PRINCIPLES
 Consistency

For example, consistent pattern of definition and usage

SysML v2 SysML v1
part / part def part property / block
attribute / attribute def value property / value type
port / port def proxy port / interface block
action / action def action / activity
state / state def state / state machine
constraint / constraint def constraint property / constraint block
connection / connection def connector / association block
requirement / requirement def requirement
view / view def view

39
 Unification of Concepts
Feature typing (definition), subsetting and Actions and subactions are related by feature
redefinition are all kinds of specialization. membership, just like parts and subparts.

«part def» «part» «action def»

Vehicle :
«defined by»
vehicle1 Provide Power

«part» «subsets» «part» «action» «part»

wheels [4] front wheels [2] generate torque amplify torque

Object flows are the same as information flows.

«part» «redefines» «part» «action» «part»

lugnuts : Lugnut [*] | lugnuts : Lugnut [4] generate torque amplify torque

40
 Specialization in Context

«part def» «part»

Vehicle : vehicle1

«part»
rear wheels [2]

«part» «part» Features are

wheels [4] front wheels [2] specialized in the
context their owner

«part»
lugnuts : Lugnut [6]
attributes Redefinition can be
different in different
:>> torque = 30 contexts
«part» «part»
lugnuts : Lugnut [*] lugnuts : Lugnut [4]
attributes | attributes Nested features can
be redefined locally
torque :>> torque = 20

41
 Textual and Graphical Notation
➢ There are corresponding textual and graphical notations for each language construct.
➢ There is a comprehensive expression language.
➢ Textual notations can be used consistently on graphical diagrams.

42
DESIGN DECISIONS:
RATIONALE AND TRADE OFFS
 Reified Relationships

«package» «import» «package»

Vehicle Model ISQ

Owning membership

«part def» Rationale

Vehicle All relationships Allows consistent graph-oriented
are reified as navigation across a model
Feature membership model elements.
Trade off
Essentially doubles the number
«part» «part» of model elements needed to
engine driver represent a model

Feature typing
:

«part def» «part def»

44
Engine Person
 Compact Notation

User Conception Actual Meaning

«part» «feature «part»

reference»
engine engine

«feature value» Rationale

Maintains simple user concept, avoids
use of dependency relationships
«subject» without formal semantics.
«satisfy»
Trade off
Simple surface notation hides
underlying complexity, which must be
navigated in a tool or repository.

«requirement» «satisfy «requirement»

engine power requirement» engine power

45
 Semantic Library Models
User Model Library Model

Implied
Vehicle Model relationships Parts

«part def»
Vehicle
«part def»
Part : «part»
parts [*]

Rationale
«part» «part» Provides underlying ontological
semantics in an extensible library.
engine subparts
Trade off
Tools need to account for implied
relationships, even if not
physically added.

46
CONCLUSION
 Conclusion

❑ The SST ran for over 5 years, with no significant conflict, losing no participating
organizations
❑ Pilot implementation was released (almost) every month from November 2018 to
February 2023.
❑ Submitted specifications met their objectives and about 90% of the RFP
requirements.
❑ There is already a SysML v2 user community, and there is great interest in moving
to SysML v2 in the wider MBSE community.

48
 But There are Trade-Offs

❑ SysML v2 is not just a simple evolution from SysML v1

➢ New foundation not based on UML
➢ Reified and implied relationships
➢ Textual in addition to graphical notation

❑ SysML v2 is bigger than SysML v1

➢ New functionality
➢ Extensive model libraries

❑ SysML v2 is not easy to implement

49
 Never he ess…Many Imp emen a ions in Progress!

Dassault/3DS
Cameo

IBM
Rhapsody

PTC
Windchill Modeler

Sparx
Enterprise Architect

Intercax
Syndeia

Siemens
Ansys
50
 SST Public Repositories
Current Release: 2023-02
❑ Monthly release repository
➢ https://github.com/Systems-Modeling/SysML-v2-Release

❑ Release content
➢ Specification documents (for KerML, SysML and API)
➢ Training material for SysML textual notation
➢ Training material for SysML graphical notation
➢ Example models (in textual notation)
➢ Pilot implementation
▪ Installer for Jupyter tooling
▪ Installation site for Eclipse plug-in
➢ Web access to prototype repository via SysML v2 API
➢ Web access to Tom Sawyer visualization tooling

❑ Open-source repositories
➢ https://github.com/Systems-Modeling

❑ Google group for comments and questions

➢ https://groups.google.com/g/SysML-v2-Release
(to request membership, provide name, affiliation and interest)
51
THANK YOU!