Editing Software architecture (section)

== Anti-patterns ==
The following architectural [[Anti-pattern|anti-patterns]] can arise when [[Software architect|architects]] make decisions. These anti-patterns often follow a progressive sequence, where resolving one may lead to the emergence of another. <ref name="O'Reilly Media" />

* An architect may delay or avoid making architectural decisions due to the fear of choosing incorrectly. To address this, ongoing and close collaboration with the development team is often necessary, with architectural choices being adjusted based on their feedback. Additionally, decisions are typically made at the "last responsible moment," ensuring there is enough information to justify and validate the decision, while avoiding unnecessary delays that could lead to [[analysis paralysis]] and hinder the team's progress. <ref name="O'Reilly Media" />
* Another anti-pattern can arise when architectural decisions are forgotten, not documented, or not understood, leading to repeated discussions without resolution. This often occurs when email is used to communicate architectural decisions. To address these challenges, [[Software architect|architects]] typically provide both technical and business justifications (often related to cost, user satisfaction, and time to market) in a single record of the architectural decision (usually an Architecture Decision Record). This record can be maintained in an accessible repository, such as a wiki. Communication via email focuses on the nature and context of the change and is directed only to relevant stakeholders, with a link to the centralized record. This ensures there is always a single updated source of truth. Additionally, if an architectural decision does not offer tangible business value, or if the business value is misaligned with business stakeholders, it may need to be reconsidered. <ref name="O'Reilly Media" />