2 ms·
You should really ask yourself why you're drawing UML diagrams at all. You know, there are lots of people selling snake-oil, drawing boxes and arrows that make
by contingencies 7y ago
You should really ask yourself why you're drawing UML diagrams at all.
You know, there are lots of people selling snake-oil, drawing boxes and arrows that make you feel good, but ultimately have no real meaning. If something is really meaningful you should be able to express it in mathematics. - Leslie Lamport
... via https://github.com/globalcitizen/taoup https://github.com/globalcitizen/taoup
If you need to visualize, take more precise states as a basis and take a look at graphviz[0]. If you need to model multi-agent systems, use mscgen[1] to draw Message Sequence Charts.
[0] https://graphviz.org/ https://graphviz.org/
[1] http://www.mcternan.me.uk/mscgen/ http://www.mcternan.me.uk/mscgen/
- flukus 7y agoI'll second graphviz, aside from it's standalone strengths it integrates well with doxygen and the two combined make for some great documentation. I use it for sequence charts as well by using sublabels (not sure what they're really called), usually I don't care so much about the sequence but where the choke points in this giant pile of steaming enterprise are: SomeObject[label="<someMethod1> someMethod1 | <someMethod2> someMethod2"]; Foo -> SomeObject:someMethod2;