In previous chapters, you learned about various aspects of solution architecture design and optimization. As the solution architect works on the design, it is important to have consistent communication for successful application delivery. The solution architect needs to communicate a solution design to all technical and non-technical stakeholders.
The Solution Architecture Document (SAD) provides an end-to-end view of application and helps everyone to be on the same page. In this chapter, you will learn about various aspects of the SAD, which addresses the need for all stakeholders associated with the development of the application.
You will learn about the structure of the SAD and other types of documents of which the solution architect needs to be aware, such as the request for proposal (RFP), where the solution architect needs to provide input to make strategic decisions. You will learn the following topics to gain a deeper understanding of the documentation involved in solution architecture:
- Purpose of the SAD
- Views of the SAD
- Structure of the SAD
- IT procurement documentation for a solution architecture
By the end of this chapter, you will learn about the SAD, its structure, and the various details that need to be accommodated in the documentation. You will learn about various IT procurement documentation such as the RFP, the request for information (RFI), and the request for quotation (RFQ), in which a solution architect participates to provide feedback.