I've found that writing pseudocode with doxygen formatted comments to generate sharable diagrams is generally sufficient. I actually got into that habit back w

I've found that writing pseudocode with doxygen formatted comments to generate sharable diagrams is generally sufficient. I actually got into that habit back when I was working with the insanely expensive suite of Rational IDEs. At that point, and later with the Eclipse Modeling Framework, the goal was to generate code from diagrams.... but that took more work than it was worth in my opinion. With those tools, or with doxygen, you can get pretty far writing skeleton classes and method stubs, with exogenous systems represented the way you might mock them. Then just drop the generated SVGs into your slides, and profit. This also answers your question about the lack of tooling: whenever a promising architecture/modeling product shows up they get acquired and then just fade away.