<?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="Requirements analysis - Page 13 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Requirements_analysis&amp;p=12">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Requirements_analysis&amp;p=14">3.Next</a>
</p>
<p>have proved spectacularly unsuccessful at achieving their aims; but they are still seen to this day.</p>

<p><big>Strengths</big></p>
<p>
* Provides a checklist of requirements.<br/>
* Provide a contract between the project sponsor(s) and developers.<br/>
* For a large system can provide a high level description from which lower-level requirements can be derived.</p>

<p><big>Weaknesses</big></p>
<p>
* Such lists can run to hundreds of pages. They are not intended to serve as a reader-friendly description of the desired application.<br/>
* Such requirements lists</p><p>
<a accesskey="1" href="page.php?w=Requirements_analysis&amp;p=12">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Requirements_analysis&amp;p=14">3.Next</a>
</p>

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

</card>
</wml>
