7 ms·

I've used UML to communicate certain things about code. Class or sequence diagrams are great tools to explain code structure or workflow. Of course it's not ver

I've used UML to communicate certain things about code. Class or sequence diagrams are great tools to explain code structure or workflow. Of course it's not very frequent that I need to use them, but they're still useful.

jsmith45 4y ago
Sure, but were those diagrams even conforming UML? And should they be? I don't see a lot of value in UML's standardizing +,-,#,~ as access specifiers, vs just using the relevant language keywords. Generally, unless people are using CASE tools, I tend to see them draw non-conforming diagrams that just roughly resemble what the UML spec says, and that is almost always good enough. Diagrams are good, but having to worry about N different type of arrow heads, if a line should be solid or dashed, semi-obscure access symbols, etc is not good. and strictly speaking if you are not concerned about those things you are not actually using UML. The exception is that nobody can ever convince me that a UML-style usecase diagram is better than alternatives like user stories.