Architectural diagram of program software#

It may be used to pitch an idea to an architecture board or describe how a business process works to a developer.

The audience for this type of diagram is generally technical. This diagram illustrates the moving parts in a business process. It is a medium-high level diagram that shows all the pieces of a workflow. The most generic and generally broadest reaching diagram you can make is the flow diagram. We will take an example from my fake business but real API, Gopher Holes Unlimited, where we add a new gopher into the system to be tracked. Today we are going to talk about the 5 different types of diagrams you should make depending on 5 different audiences. If you want to get your idea across to different sets of people, you must make multiple versions of your diagrams. Your diagrams must take that into consideration. We’ve discussed recently that a significant part of being a solutions architect is effectively communicating your ideas to both technical and non-technical audiences. Architecture diagrams are not a “one size fits all” solution. I needed a visual.īut not just any diagram. I was trying to build a mental model while following a train of thought. Words get lost when explaining complex conceptual architecture. I understood the words coming out of their mouth but they don’t make sense strung together. They were explaining the solution using hand gestures and a lot of “and this piece communicates with this one by…”. It had about eight different components to it and they all interacted with each other in multiple ways. I was having a conversation with a relatively new solutions architect who was trying to describe a system they had come up with.

Architectural diagram of program software#

Have you ever been in a meeting where someone is trying to explain how a software system works?