They need a conceptual depiction of the solution architecture that is accurate enough to ensure everyone is on the same page but pretty enough for a presentation. The Conceptual Architecture ViewĮnter stage left… Powerpoint! All solution architects must be prepared to present proposed architectures to a broad audience, from engineering to executive management. Finally, while it starts simple, you can layer additional dimensions using colors, fonts, and grouping boxes.Īlthough we are discussing this view in the context of solution architecture, I have frequently used it to confirm the scope across a group of stakeholders even when no technical solution is in play for projects and business process initiatives. You can make it in just about any tool you can use to write words, enabling just about anybody to create one. You create “user cards” with roles and list architecturally significant use cases on the cards. So, people can understand it or even create one with little or no training or prior experience. Many diagrams notations can depict who and what, like a system context diagram or UML use case, but I prefer using a solution user diagram.Ī solution user diagram is simple it is barely a diagram. Knowing who and what is usually enough for an architect to design a solution without having detailed requirements. Therefore, the first and most critical view for describing an architecture is one that clarifies who is using the solution and what they are using it for. All technology solutions are designed to address people’s needs: all architecture is people-centric. Nobody designs technology solutions in a vacuum. Without further ado, here are the four views I recommend. While it seems counter-intuitive, using multiple fit-for-purpose views is more understandable than trying to jam everything onto a single diagram. You will note that I said diagram s and not a diagram. Finally, the diagram becomes a historical record of the architecture (even a dated design is better than no design).Īfter decades of designing solution architectures, I have landed on a set of views that I use to depict any solution architecture. Firstly, a solution architect can use them to effectively think through an architecture design because the diagrams help to structure thinking and because the architect can put the diagram down and come back to it later with a “fresh set of eyes.” Secondly, a solution architect can use the diagrams to effectively facilitate the conversations required to share the design, gather feedback, and gain approval. If you are going to share it in internet broadcasts, you have to show a source.Diagrams are a powerful tool for solution architecture design. □ Not Available in Your Country? Check this link □ ✅ More than 15 different types of diagramsĪfter entering your email address, you will see the download button on the screen :) Also, a link will be sent (by Gumroad) to your email address.īy downloading this Architectural Diagrams eBook, you will receive all of our "Architectural Diagrams eBook " updates for free, forever. ✅ Diagram types and choosing the best for your project ✅ What is a diagram? + and why do we create it? And by removing all the other details that can make the concept harder to see, the public can see your idea clearly. drawings can be hard for the public and clients to understand, so we use diagrams to explain the most important parts of the "concept" using simple drawings that everyone can get easily. One of the reasons we do diagrams for that arch.It is a record of physical and spatial features that define the unique and distinctive features of a building, site or program. Diagram is the process of abstracting and simplifying an idea so that it can be easily understood.□ Learn How To Create Architectural Diagrams!
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |