<?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 verification - Page 8 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=software_verification&amp;p=7">1.Previous</a><br />
<a accesskey="3" href="page.php?w=software_verification&amp;p=9">3.Next</a>
</p>
<p>calculated expected values to establish conformance with requirements.</p>

<p><big> Narrow scope </big></p>
<p>When it is defined more strictly, verification is equivalent only to static testing and it is intended to be applied to artifacts. And, validation (of the whole software product) would be equivalent to dynamic testing and intended to be applied to the running software product (not its artifacts, except requirements). Notice that requirements validation can be performed statically and dynamically (See <a href="page.php?w=Software_verification_and_validation">artifact validation</a>).</p><p>
<a accesskey="1" href="page.php?w=software_verification&amp;p=7">1.Previous</a><br />
<a accesskey="3" href="page.php?w=software_verification&amp;p=9">3.Next</a>
</p>

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

</card>
</wml>
