The words and therefore the term itself is fairly simple: a diagram is a chart or visual depiction of a system, while “architecture” typically refers to a structure. Therefore, asking “what is an architecture diagram,” in its most basic form, yields the answer: a visual depiction of a particular structure. But often, this term refers to computer systems and networks.
Many people jump to the conclusion that, since the word “architecture” is being used, a architecture diagram must be related to the building of houses. The common assumption is that this type of diagram is similar to a blueprint in that it shows a diagram of a physical building. Technically, based on word definition alone, this is a viable answer and is not untrue.
But in practical usage, the term is almost never used to describe a physical building. It is, much more commonly, used to describe the architecture of computer systems, software, networks, and other technology-related structures. Below are just a few samples of how this term can be used in the field of technology.
An architecture diagram in “system architecture” is typically a technological set-up, either various computer components working together, or steps in a software process working towards a specific end result.
The point of a system is that multiple single steps are put together in a process to result in a certain end goal; a system architecture diagram simply shows those steps in a visual way.
Most of us are familiar with the idea of a computer network; with Internet usage and home computers very common these days, we’ve probably all dealt with wireless networks or Ethernet connections via a modem and computer network.
The term “network” is another fairly broad one, which is generally used to describe any connected series involving transmission equipment, transmission of data, and various technological components working together to communicate.
A network architecture diagram, then, would be a diagram showing these particular connections. It could be as small-scale as a two-step diagram showing your home computer picking up an Internet signal, or as complex as the various connections between an entire office of computers, all communicating with each other as well as a main internet LAN, MAN, or WAN.
Software is one of the more common applications for the term “architecture diagram.” Because of the multiple layers of structures that must work together in order for software to perform properly – from the programming of the software itself, through the various computers using it and communicating with each other in the process – this is a field where diagrams especially come in handy.
A software architecture diagram can simplify the extreme complexity of such a set-up and ensure things work as they should by illustrating the various steps of the process.
In basic terms, software architecture diagrams typically include all components of the software, as well as the physical things that actually use it, from computers to phones to other communication devices. The diagram also indicates how those devices communicate to each other, if they do – such as in an office with a shared network, where everyone uses the same software installed on the main system.
Architecture diagrams are actually a fairly simple idea, expressed in somewhat complex terms. While the definition of the words can lead you in nearly any direction, chances are fairly good that when you hear the term it is meant to refer to computers, technology, networks, software, or similar types of structures.
Just keep in mind the main meaning, which is “a diagram showing the structure of a system,” and you’ll at least have a beginner’s grasp on what is being referred to that should be enough to lead you into the finer details and overall understanding of the discussion at hand.