<?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="Functional requirement - Page 2 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Functional_requirement&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Functional_requirement&amp;p=3">3.Next</a>
</p>
<p>to accomplish. Behavioral requirements describe all the cases where the system uses the functional requirements, these are captured in <a href="page.php?w=use_case">use case</a>s. Functional requirements are supported by <a href="page.php?w=non-functional_requirement">non-functional requirement</a>s (also known as "quality requirements"), which impose constraints on the design or implementation (such as performance requirements, security, or reliability). Generally, functional requirements are expressed in the form "system must do <requirement>," while non-functional requirements take the form "system shall be <requirement>." The plan for implementing functional requirements is detailed in the system design, whereas non-functional requirements are detailed in the <a href="page.php?w=system_architecture">system architecture</a>.</requirement></requirement></p><p>
<a accesskey="1" href="page.php?w=Functional_requirement&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Functional_requirement&amp;p=3">3.Next</a>
</p>

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

</card>
</wml>
