Every application has an architecture that constantly evolves. Its important to not only pass everything related to it to the team but also keep the information up to date. This article focuses on how The Software House documents their architecture and provides tips on how to do it on a daily basis. Unlike API documentation, there is no standard for software architecture documentation, but there are many tools and diagram types to choose from. The article covers C4, context, container, component, and code diagrams, and suggests documenting decisions, constraints, and rationale for architecture choices. It concludes with a reminder to collect feedback to continuously improve the documentation process.
