System1
sub-system1a
sub-system1b
System2
sub-system2a
sub-system2b
(This is the reason indentation in programming languages is a thing.)(Yes most programming languages use trees, it has some advantages. But most people program in excel anyway.)
Graphs are reducible to lists of nodes and edges which are very linearizable.
That may not be the most useful form for comprehension, but linear forms are quite good for writing and storing. Visual notation is useful for presentation here, but IME quality is much lower in drawn diagrams than rendered-from-linearly-authored-text diagrams, which explains why most of my diagramming is done in a text editor (e.g., in Markdown+Mermaid) with visual preview.
What will you do when you need to describe a graph with (say) more than a thousand nodes? I hope you won't try to draw a picture of it.
Creating a graphical rendering of data is not what I was referring to when I spoke of drawing a picture. What I meant was actually drawing, i.e. using MacDraw or PowerPoint or a pencil and paper and drawing. Because that is what people mostly do when they use UML.
English is linear in a way diagrams are not.