There is no definitive answer because there is not even a good definition what software architecture actually is [0]. So you need to find an answer fitting your

There is no definitive answer because there is not even a good definition what software architecture actually is [0]. So you need to find an answer fitting your organization yourself. One idea could be that you start a document with the Arc42 [1] template. Figure out how to communicate the essential structure of your software to everybody. Document why certain big decisions were made. E.g. why did you pick that programming language/framework? [0] http://beza1e1.tuxen.de/definitions_software_architecture.html http://beza1e1.tuxen.de/definitions_software_architecture.ht... [1] https://arc42.org/ https://arc42.org/