<?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="Separation of concerns - Page 3 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=separation_of_concerns&amp;p=2">1.Previous</a><br />
<a accesskey="3" href="page.php?w=separation_of_concerns&amp;p=4">3.Next</a>
</p>
<p>concerns is broader. For example, separating requirements analysis from implementation in a project timeline, or separating functional from non-functional requirements in a specification, are valid forms of separation of concerns that do not necessarily require a modular design.</p>

<p><a href="page.php?w=Edsger_W._Dijkstra">Edsger W. Dijkstra</a> in his 1974 paper "On the Role of Scientific Thought", coined the term separation of concerns in relation to software qualities such as <a href="page.php?w=correctness_%28computer_science%29">correctness</a></p><p>
<a accesskey="1" href="page.php?w=separation_of_concerns&amp;p=2">1.Previous</a><br />
<a accesskey="3" href="page.php?w=separation_of_concerns&amp;p=4">3.Next</a>
</p>

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

</card>
</wml>
