Solution architects document processes to understand business needs and describe system flows and logic. Enter the UML Activity diagram!
So! Welcome to our passion and our obsession. Oxford Language defines a diagram as:
"a simplified drawing showing the appearance, structure, or workings of something; a schematic representation."
We are huge proponents of using specific visualizations to think through and communicate both problems and solutions. Diagrams can be used to adeptly analyze and clearly communicate. We standardize on Unified Modeling Language diagrams when appropriate, but also leverage other industry approaches.
As you dive into our diagram articles, we leave you with this quote from architect Daniel Burnam (1846-1912):
"Make big plans; aim high in hope and work, remembering that a noble, logical diagram once recorded will not die, but long after we are gone be a living thing, asserting itself with ever-growing insistence."
A solution architect uses conceptual solution architecture diagrams to iterate on a high-level design and to share that design with others.
While they have their place, platform-specific diagram notations are not a good choice for solution architecture diagrams. Learn why and when it is appropriate to use them.