Sequence diagrams, the only good thing UML brought to software development

1

C4 model

> What do you think is the whole point of a modeling language? Not building an entire system down to class level which is what it is all too often used for (in my experience exclusively by people who have never and cannot code). It's inefficient, doesn't play well with Software Engineering (diff, version control etc..) and is a relic of the past. Keep the classes in code, project that into a diagram for the few occasions that is actually needed, and stick to a simplified tool like C4 (https://c4model.com) for your architectural views. Sprinkle some sequence diagrams in too to help describe the key data flows (they're handy next to C4). Why use C4 over UML? Because the vast majority of the audience don't even know what UML is. So keep it extremely simple and include a key / guide to any of the (few) shapes or colors you use so that it's completely self contained. The vast majority of UML belongs to be put into the Indiana Jones storage facility along with other archaic ideas such as Function Points / Function Point Analysis.

#Flow Charts And Diagrams #Diagrams #UML 17 social mentions

2

SequenceDiagram.org

I'm not a developer (more like a translator) and love sequence diagrams. They are so useful to explore system and data flow designs. Also my favorite tool for them: https://sequencediagram.org/.

#Diagrams #Flow Charts And Diagrams #Flowcharts 29 social mentions

3

Mermaid

With a fancier image for the customer than a box. Try it out at https://mermaid.live (linked from https://mermaid.js.org/) Or this one, from a service I worked on a couple of years ago: <pre><code> sequenceDiagram.

#Flow Charts And Diagrams #Diagrams #UML 24 social mentions