<?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 and validation - Page 2 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=Software_verification_and_validation&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Software_verification_and_validation&amp;p=3">3.Next</a>
</p>
<p> It is normally the responsibility of software testers as part of the <a href="page.php?w=software_development_process">software development lifecycle</a>. In simple terms, <a href="page.php?w=software_verification">software verification</a> is: "Assuming we should build X, does our software achieve its goals without any bugs or gaps?" On the other hand, software validation is: "Was X what we should have built? Does X meet the high-level requirements?"</p>

<p><big>Definitions</big></p>
<p>Verification and validation are not the same thing, although they</p><p>
<a accesskey="1" href="page.php?w=Software_verification_and_validation&amp;p=1">1.Previous</a><br />
<a accesskey="3" href="page.php?w=Software_verification_and_validation&amp;p=3">3.Next</a>
</p>

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

</card>
</wml>
