[cartoonfoxes]

Despite being mostly a subset of UML, SysML is a more cohesive and useful design and modeling tool. Unlike UML, I've actually used SysML on real embedded systems projects and like it. It lends itself well to model refinement, wheras UML encourages Big Design Up Front.

I'm not sold on the idea of capturing an entire design within SysML, but using it instead as a diagram format with defined semantics for situations where group discussion or communication with third-parties calls for some graphical aids. I think as long as you're not trying to make executable models, do code-generation, or replace a formal specification tool like TLA+, there is real value in it. The documentation and training ecosystem around it is pretty decent, as well. The SysML books I've read have all been way more pragmatic and grounded in actual engineering practice of building systems from many components sourced elsewhere, for which design capture is necessarily incomplete.

[kejaed]

What tool did you end up using for SysML?

[cartoonfoxes]

Currently, I'm not currently working in a dedicated modeling tool at all - just draw.io. We started with Enterprise Architect from SparxSystems - it's a bit janky and covers a lot stuff beyond SysML, but it works fine. Cameo Systems Modeler is good too - it omits the non-SysML garbage that the other platforms include, and has the best Model-to-Html rendering I have seen, but was double the cost of EA so did not use it for work. The open source tools, Modelio etc. were all a broken waste of time.

For my use, there is a sweet-spot for "models" spanning only a handful of diagrams (5-10) where any drawing software with SysML templates will do. The dedicated modeling tools like EA or Cameo become relevant once you're trying to keep model elements consistent across a large number of diagrams. Draw.io is free so the whole team can use it, and the the lack of model representation keeps diagram count low and not over-specified.

Cool products, btw.