4 ms·
UML was all about that. I find myself doing sequence diagrams very often. (https://en.wikipedia.org/wiki/Sequence_diagram https://en.wikipedia.org/wiki/Sequence
by dragontamer 6y ago
UML was all about that. I find myself doing sequence diagrams very often. (https://en.wikipedia.org/wiki/Sequence_diagram https://en.wikipedia.org/wiki/Sequence_diagram)
Overall, UML was over-engineered and too complicated for most people to learn. Nonetheless, the various diagram-styles are great for communication and white-boarding purposes. https://en.wikipedia.org/wiki/Unified_Modeling_Language#Diagrams https://en.wikipedia.org/wiki/Unified_Modeling_Language#Diag...
- JNRowe 6y agoAh, I see. That speaks to why I believe flowchart vocabulary is so common around me. I'm used to working in teams where UML would be largely unknown, whereas the flowchart(or basic BPMN¹) spans the non-compsci folk too. ¹ https://en.m.wikipedia.org/wiki/Business_Process_Model_and_Notation https://en.m.wikipedia.org/wiki/Business_Process_Model_and_N...
- buescher 6y agoUML statecharts are OK too. The structure diagrams, much less so, and I still think "really?" whenever I see a use case diagram. Adding a stick figure and lines and circles to something that should be expressed in sentences and paragraphs is just absurd.