<?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 documentation - Page 5 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=software_documentation&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=software_documentation&amp;p=6">3.Next</a>
</p>
<p>(e.g., builds can be started by right-clicking a configuration file and selecting the 'build' function), and anything in between. They can be specified as statements in <a href="page.php?w=natural_language">natural language</a>, as drawn figures, as detailed <a href="page.php?w=mathematical_formula">mathematical formula</a>s, or as a combination of them all.</p>

<p>The variation and complexity of requirement documentation make it a proven challenge. Requirements may be implicit and hard to uncover. It is difficult to know exactly how much and</p><p>
<a accesskey="1" href="page.php?w=software_documentation&amp;p=4">1.Previous</a><br />
<a accesskey="3" href="page.php?w=software_documentation&amp;p=6">3.Next</a>
</p>

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

</card>
</wml>
