SysML v2 Textual Notation Cheatsheet

How-to Guides
,
1

Hi!

We’re making available our first SysML v2 Textual Notation Cheatsheet!

This is a quick reference guide that covers the basics of the SysML v2 language, including:

  • Constructs & Expressions: Learn the syntax for comments, definitions, and specializations
  • Requirements & Constraints: See examples for defining and using requirements and constraints.
  • Parts & Connections: Understand how to define and use parts, ports, and connections.
  • Behavior: Get a quick overview of actions and states.
  • Keywords: A table of keywords and their shorthand notations.

It is perfect for quickly looking up syntax and examples.

:rocket: Use it freely and let us know what you think!

SysML Textual Notation Cheatsheet.pdf (201.6 KB)

1 Like
2

Thanks, this is helpful for the community.

I have a few suggestions for improvements:

  1. The cheatsheet would be more usable as a (HTML) web page since users could save the weblink and always access the most recent version of it.
  2. In the “Structure” box (top left corner), “Classification” should be the fist item since it’s most fundamental.
  3. In the “Behavior” box (top left corner), add “Action-based” as the first item since it’s the most important one and better drop “Function-based” and “Sequence-based” since (1) “Functions” are not essential for behavior (in fact, there is a proposal to not consider Functions as behaviors), and (2) SysML v2 behavior modeling is not “Sequence-based” in any sense, but only “Succession-based”.
  4. In “Constructs & Expressions“, add “(Classifier)” after “Definition” and “(Feature)” after “Usage” for indicating the meaning of these new terms.
  5. Switch the 2nd and 3rd columns, since state structure modeling should come before behavior modeling, and move “Actions“ before “Constraints & Requirements“.
  6. The second column should contain “Parts”, “Items”, “Connections”, and if space permits “Ports” and “Interfaces”.

Best regards,
Gerd

1 Like
3

Thanks for the feedback. I will make sure to take these suggestions into account in the next iteration.