Like every business proposal document, a SAD also has an Appendix section that is pretty open, to put any data that supports your choices regarding the overall architecture and solution. In the Appendix section, the solution architect can include open issues, any research data such as the outcome of the POC, tools comparison data, vendors' and partners' data, and so on.
In this topic, you got a good overview of the SAD structure with different sections. A SAD should include the major sections mentioned previously; however, the solution architect may choose to exclude some sections or include additional sections as per organization and project requirements. As with other documents, it's essential to continue to iterate upon SADs and look for an opportunity to improve. More robust SADs lead to well-defined implementation guidelines and reduce any risk of failure.
A SAD is a running document that gets created during the initial stages and is kept up...