The solution architect needs to create a SAD in such a way that it should be understandable by both business users and technical users. 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' perspective. The solution architect evaluates both the business and technical aspects of architecture design so that they can take cognizance of all technical and non-technical users' requirements.
As illustrated in the following diagram, the holistic view of the SAD comprises various views derived from business requirements, to cover different aspects:
Solution architects can choose standard diagrams such as a Unified Modeling Language (UML) diagram or a block diagram from Microsoft Visio to represent various views. Overall, the diagram...