<?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="Domain engineering - Page 11 - Wikipedia">
<p>
<a accesskey="1" href="page.php?w=domain_engineering&amp;p=10">1.Previous</a><br />
<a accesskey="3" href="page.php?w=domain_engineering&amp;p=12">3.Next</a>
</p>
<p>analysis is derived primarily from artifacts produced from past experience in the domain. Existing systems, their artifacts (such as <a href="page.php?w=design_document">design document</a>s, <a href="page.php?w=software_requirements_specification">requirement documents</a> and <a href="page.php?w=user_manual">user manual</a>s), <a href="page.php?w=technical_standard">standards</a>, and customers are all potential sources of domain analysis input. However, unlike requirements engineering, domain analysis does not solely consist of collection</p><p>
<a accesskey="1" href="page.php?w=domain_engineering&amp;p=10">1.Previous</a><br />
<a accesskey="3" href="page.php?w=domain_engineering&amp;p=12">3.Next</a>
</p>

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

</card>
</wml>
