<?xml version="1.0" encoding='utf-8'?>
<!DOCTYPE wml PUBLIC "-//WAPFORUM//DTD WML 1.1//EN" "http://www.wapforum.org/DTD/wml_1.1.xml">
<wml>
<card id="card1" title="Software architecture - Page 13 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Software_architecture&amp;p=12">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Software_architecture&amp;p=14">3.Next</a>
</p>
<p>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 <a href="page.php?w=analysis_paralysis">analysis paralysis</a> and hinder the team's progress.<br/>
* Another anti-pattern can arise when architectural decisions are forgotten,</p><p>
<a accesskey="1" href="page.php?w=Software_architecture&amp;p=12">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Software_architecture&amp;p=14">3.Next</a>
</p>

<do type="prev" label="Search">
        <go href="search.wml"/>
</do>

</card>
</wml>
