3 ms·
Entity relationship models are good, but people will disagree whether they are UML. Sequence diagrams are useful, but the UML version with a vertical diagram w
by marcosdumay 4y ago
Entity relationship models are good, but people will disagree whether they are UML.
Sequence diagrams are useful, but the UML version with a vertical diagram with horizontal lines optimizes for the least necessary use cases; also, the UML one has no space for the participants states.
Use cases diagrams are useful, but the UML version just wastes all the space and takes all the useful information out (well, it keeps the actors, could be worse).
Class diagrams aren't very useful at all, and when you need them you don't need the formality that is the main point of UML.
And finally, the UML designers failed to include any data transformation diagram, because they really did only think in procedural terms.
- eastbound 4y agoI’m intrigued by the fact that there exists alternatives to UML’s diagrams? What alternative sequence diagrams are there? Because you are right, we always twist them to include supposedly-orthogonal aspects such as state or actors.
- marcosdumay 4y ago"Alternatives" imply on a formal definition, with strict semantics. IAFAIK, there is no such thing. But most of those kinds of diagram existed before UML, and are designed in very different ways on different contexts. Specifically for sequence diagrams, it's common to replace those lines with bars where you can annotate the state, and it is common to have actors instead of endpoints defining the bars. But if you are relying too heavily on those two, it may be interesting to look at process diagrams (but not strictly BPMN).