Content deleted Content added
m removed the unreliable source |
No edit summary |
||
Line 32:
There is no sharp distinction between software architecture versus design and requirements engineering (see [[#Related fields|Related fields]] below). They are all part of a "chain of intentionality" from high-level intentions to low-level details.<ref name="FAIRBANKS2010">{{cite book|author=George Fairbanks|title=Just Enough Software Architecture|year=2010|publisher=Marshall & Brainerd}}</ref>{{rp|18}}
==
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 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" />
== Characteristics ==
Software architecture exhibits the following:
| |||