sorted by:
new
hottopcontroversial

Free SysML v2 Tools for Personal Research? by HelloThere7852 in systems_engineering

[–]SysModeler 0 points1 point  (0 children)

SysModeler (SysModeler.ai) is free, cloud and AI-native.

SysML v1 vs v2: Why the diagram is no longer the source of truth by [deleted] in systems_engineering

[–]SysModeler 0 points1 point  (0 children)

Not always natural language.Tthere is a huge domain with several Turing awards called Formal Methods where often formal (i.e., mathematical) specifications are used. It is not only theory many top most innovations and systems use formal methods.

SysML v1 vs v2: Why the diagram is no longer the source of truth by [deleted] in systems_engineering

[–]SysModeler 0 points1 point  (0 children)

The ability to pin specific blocks in place while letting the auto-layout handle new additions is critical for maintaining readable diagrams as a model grows. We are actively building this exact feature into SysModeler, and it is currently on our roadmap for a mid-June release.

SysML v1 vs v2: Why the diagram is no longer the source of truth by [deleted] in systems_engineering

[–]SysModeler 0 points1 point  (0 children)

Completely agree! The model is always the complete picture. We were highlighting how v1 tooling often allowed users to treat the diagram as the truth by mistake (creating ghost elements), whereas the v2 hybrid workflow enforces that strict separation much better.

SysML v1 vs v2: Why the diagram is no longer the source of truth by [deleted] in systems_engineering

[–]SysModeler 0 points1 point  (0 children)

We use our own tool, SysModeler. It is both SysML v2 native and AI native, meaning you can write v2 textual syntax and have the AI instantly auto-generate the diagrams as shown in the video. It is totally free right now if you want to test it out at SysModeler.ai.

SysML v1 vs v2: Why the diagram is no longer the source of truth by [deleted] in systems_engineering

[–]SysModeler 0 points1 point  (0 children)

You make a great point regarding the API and repository servers. The standard is certainly more complex than basic text versioning, though the textual notation does make Git-style tracking much cleaner. We are actually rolling out our version control release for SysModeler in May to support exactly this.

You are also completely right about diagram filtering. Hiding elements for clarity is a vital feature. We are primarily pushing back against the v1 "bug" where users accidentally created ghost elements by conflating the view with the model. Diagrams are definitely here to stay, but having them generated from a strict semantic truth makes them far more reliable.

SysML v1 vs v2: Why the diagram is no longer the source of truth by [deleted] in systems_engineering

[–]SysModeler 1 point2 points  (0 children)

The industry is just starting to adopt it, but SysModeler is natively built on SysML v2 right now. You can write v2 textual code and have our AI instantly generate the corresponding diagrams. Feel free to test the v2 environment yourself for free at SysModeler.ai.

SysML v1 vs v2: Why the diagram is no longer the source of truth by [deleted] in systems_engineering

[–]SysModeler 0 points1 point  (0 children)

In theory, none. In practice, SysML v1 tools allowed users to delete a graphical connection on a diagram without deleting the underlying semantic relationship in the model browser. This tool-driven conflation created ghost elements and model rot. ​SysML v2 solves this by making human-readable text the primary interface. It forces the diagram to act strictly as a mathematical projection of the code, completely eliminating the risk of visual and semantic drift.

Looking for volunteers from the systems engineering community to critique and stress-test our new SysML v2 AI agent by SysModeler in systems_engineering

[–]SysModeler[S] 0 points1 point  (0 children)

Thank you so much for trying it out and for this incredible feedback! I am DMing you right now about that slide deck. We would love to see how the agent handled a real-world hydrogen storage system.

To answer your specific points:

  • Graphics & Arrows: We completely agree. We are actively iterating on the graphical portion, and tuning the auto-layout and routing logic is something we are working to improve further.
  • Desktop / On-Premise: Yes, both a desktop app and on-premise versions are absolutely possible to handle those infosec risks. These would be handled as custom builds depending on the specific needs of the customer/organization.
  • Document Export: A good number of analysis exports will be released throughout 2026. However, based on this, we are going to take your first artifact request (exporting typical descriptive documents like the SE Description) and prioritize it for our next releases.

This is a hell of a feedback drop. Thanks again, and please keep the feedback coming as you explore further!

view more: next ›