Implementing the SysML v2 standard is a massive engineering challenge. With this 2025.12 release, the SysON team continues to strengthen the foundations. While we haven't reached the end of the road yet, we are hitting key milestones to make modeling more predictable and robust.
Expanded functionality for diagrams
Flexible Displays: Objects could be displayed in different ways on the same diagram: as composed/referenced, in compartments or as border nodes.
We established display rules to optimize and accelerate modeling by given priority to displayed compartments which result from user need. Look at the release notes for more detail on those display rules.
Inherited PortUsages: You have now Inherited PortUsages displayed as graphical border nodes which could be connected to other ports (but not edited or deleted):
The new “View as” menu: lets you showcase elements your way, with complete flexibility like General View, Interconnection View, ActionFlow View or StateTransition View:
Action Parameters: The action parameters are now displayed as border nodes and so could be linked to other parameters using the Binding or Flow connectors.
We fixed an issue where the undo of a diagram object deletion was not restoring the graphical node correctly.
And you can now use the short names in the qualified names in the direct edit of a graphical element or create a Documentation in a Package graphical nodes.
Robustness on Import/Export
We are working hard to make the bridge between text and graphics more reliable. You can now use rational numbers without restrictions and UnaryOperator which are Expression using the operators '+', '-', 'not' or '~' with only one parameter:
package Occurrences {
private import ScalarValues::*;
occurrence def Occurrence1 {
attribute f : Real = 1.0;
attribute g = 3.14;
attribute h = 2.5E-10;
attribute i = .5;
attribute j = 1E+3;
attribute a : Real = -1.0;
attribute b : Integer = -1;
attribute c : Integer = +1;
attribute d : Boolean = not true;
}
}
The textual export now properly exports ConnectionUsages such as in the following model.
Other evolutions make more robust the textual export related to declared short name usage.
Explorer View
Always mindful of hiding complexity, we apply default filtering on Expose element but they can still be displayed when needed:
You will be pleased to see the shortName as part of the label of Elements:
In the Explorer view, no it is possible to create InterconnectionView diagrams from Packages elements.
Different evolutions of library display permit to help you to better handle libraries like imported-by-reference libraries which contain top-level LibraryPackage elements in the User libraries directory or the [read-only] tag for standard and imported-by-reference library:
We continue to tirelessly enhance the visual experience and simplify your modeling workflow. Stay tuned for the next updates, Santa is bringing new gifts for 2026!
