Konubinix' opinionated web of thoughts

Diagram

Fleeting

A diagram is not a visual model, in the sense it is focused in being read by humans rather than machines1 and does not expose the whole complexity2. It does not have a complex meta model, only lines and shapes3.

see the Diagram review checklist

Diagram review checklist

Notes linking here

  1. Diagrams make it easier to take in information

    […]

    Diagrams offer a top-down view of a process or system, which makes it easier to get the gist of something at a glance

    — https://nulab.com/learn/software-development/what-is-an-architecture-diagram-and-why-do-you-need-one/

     ↩︎

  2. Don’t get hung up on detail: Diagrams are supposed to be overviews. They also need to be clear and easy to understand. Unfortunately, cramming as much detail in won’t do anyone any favors and negates the benefits of using a diagram

    — https://nulab.com/learn/software-development/what-is-an-architecture-diagram-and-why-do-you-need-one/

     ↩︎

  3. Architectural diagrams consist of shapes and lines

    — https://gleek.io/blog/architecture-diagrams-types.html

     ↩︎