Why there's no universal way to draw software architecture diagram?

Question

Being a consultant I've seen so may styles of diagrams in the company. I realized even in the same company, people interpret the same diagram differently. It is very inefficient. A lot of time it is just a client, server, database, with some business logic etc. Why we cant have standardized pattern across everywhere? or does that exist? I also don't understand the concept of "reference architecture" because when i was software engineer in a big organization we never need a reference to draw diagram.

Someone · Accepted Answer

Look up UML (https://en.wikipedia.org/wiki/Unified_Modeling_Language).
It is such a language, but it’s so complex that ’not everybody’ likes it.
A big problem with such languages is that you want to use diagrams to tell a story, and that story may require showing more or less details, depending on the goals of the diagram.
Consequently, you may both need a generic “A is related to B” arrow between objects and specialized “A owns B, so if A is destroyed, so will B”, “A knows B, and nobody else does, but if A is destroyed, B may live on”, “A knows B, and they more or less are equals”, “A knows B, and so may up to 5 others”, etc.

newtritious · Answer

UML was an attempt at this.https://en.wikipedia.org/wiki/Unified_Modeling_Language

afarrell · Answer

Because we do not have the energy not inclination to enforce a universal visual language on others.

labarilem · Answer

Maybe have a look at the C4 model. You might find it useful.

kleer001 · Answer

> Why there's no universal way to ...Because PEOPLE.

Why there's no universal way to draw software architecture diagram?

UML was an attempt at this.
https://en.wikipedia.org/wiki/Unified_Modeling_Language

Because we do not have the energy not inclination to enforce a universal visual language on others.

Maybe have a look at the C4 model. You might find it useful.

> Why there's no universal way to ...
Because PEOPLE.