#Architecture program usage diagram software#

It allows us to start working together straight away, building a shared understanding of what we're trying to achieve. Putting something on a whiteboard is 'low risk' for the participants as its really easy to wipe and redraw.

#Architecture program usage diagram software#

Most pieces of software architecture I do, work starts by building a rough solution architecture diagram on a whiteboard. If you want to save paper, and increase collaboration, a great alternative is the trusty old whiteboard.įor me its all about building a shared understanding between the client and the developers. There's nothing wrong with starting out with pen and paper, but your hand-drawn sketch should not be considered your 'done' final architecture diagram. Make sure you use the right tools when creating your architecture diagrams. as well as all the icons and typography being consistent, you can see that data is a solid line and auth traffic is a dotted line Tip #6: Start with paper. See SSW rule: Do you generate the VS Dependency Graph?įigure: Good example - SSW Rewards (Xamarin with Azure Active Directory B2C) - consistent styling is used. NET dependency diagram, but don't use it here in place of the architecture diagram. If it adds value to your documentation (i.e., there is a specific reason to include it) you can include the. NET dependency diagram is a useful tool, but it drills down into a specific component of the solution (the code) while ignoring the rest of it (the infrastructure). NET Dependency Graph as a Architecture Diagram Your diagram needs to include the relationships between these components, and how they share and process data. Usually, the longer an architecture diagram takes you to make, the more important it is for your project.Īn architecture diagram is part of the 7 crucial documents you need for your project, see our rule: Do you make awesome documentation? Tip #1: Include your most important componentsĪt a minimum, your architecture diagram should include: Figure: Bad example - A screenshot of the Azure resources used helps, but doesn't show data flows or dependenciesĭepending on the complexity of your solution and your comfort/familiarity with the tools, an architecture diagram could take you anywhere from half an hour to a couple of days.