Views of the SAD
The solutions architect needs to create a SAD that both business and technical users understand. A SAD bridges the communication gap between the business user and the development team to understand the function of the overall application. The best way to capture all stakeholders’ input is by putting yourself in their situation and looking at problems from the stakeholders’ perspectives. The solutions architect evaluates the business and technical aspects of architecture design to take cognizance of all technical and non-technical user requirements.
As illustrated in the following diagram, a holistic overview of the SAD comprises various views to cover different aspects derived from the business requirements:
Figure 16.1: SAD views
Solutions architects can choose standard diagrams such as a Unified Modeling Language (UML) diagram or a block diagram from Microsoft Visio to represent various views. These tools are widely recognized and...
