Is there an easy way to succinctly and unambiguously communicate the architecture of a software system ? Something that could highlight the requirements, and still be brief ? The Agile Manifesto prescribes that teams should value working software over comprehensive documentation. This doesn’t mean that we should not create documentation; it just means we should create documentation that provides value and at the same time does not hinder the team’s progress. We can achieve this using C4 architecture model. It …