The Software Architecture Document (SAD) is a key artifact in the early stages of software development, as it serves to share the architectural knowledge among the key project stakeholders and to keep record of the main design decisions for satisfying the stakeholders’ concerns. Even the best architectural solution could fail its purpose if it is not properly documented, distributed and understood by the stakeholders. However, documenting an architecture is a non-trivial and time-consuming activity, usually performed with limited resources. Thus, documenting a SAD should be planned to ensure that the invested efforts are worth the cost in terms of SAD quality.
(Párrafo extraído del texto a modo de resumen)