<?xml version="1.0" encoding="UTF-8"?>
<org.eclipse.epf.uma:ContentDescription xmi:version="2.0" xmlns:xmi="http://www.omg.org/XMI" xmlns:org.eclipse.epf.uma="http://www.eclipse.org/epf/uma/1.0.6/uma.ecore" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="__rFCULv9EdmmUvZAZjqE3g" name="requirements,_0TR2ZMlgEdmt3adZL5Dmdw" guid="__rFCULv9EdmmUvZAZjqE3g" changeDate="2007-07-18T22:06:27.695+0330" version="1.0.0">
  <mainDescription>d &#xD;
&lt;p>&#xD;
    The purpose of this discipline is to:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        Understand the problem to be solved&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Understand stakeholder needs (what users want)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Define the requirements for the solution (what the system must do)&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Define the boundaries (scope) of the system&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Identify external interfaces for the system&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Identify technical constraints on the solution&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Provide the basis for planning iterations&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        Provide the initial basis for estimating cost and schedule&#xD;
    &lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p>&#xD;
    To achieve these goals, it is important to understand the definition and scope of the problem that you are trying to&#xD;
    solve. Identify &lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../openup/roles/stakeholder.html&quot;&#xD;
    guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;>Stakeholders&lt;/a> and define the problem to be solved.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Having agreed on the problem to be solved, the &lt;a class=&quot;elementLink&quot;&#xD;
    href=&quot;./../../openup/guidances/concepts/requirements-2.html&quot; guid=&quot;_0Wh-sMlgEdmt3adZL5Dmdw&quot;>Requirements&lt;/a> for the&#xD;
    system are elicited, organized, analyzed, validated, and specified.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Throughout the lifecycle, you manage changes to the requirements.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    The Requirements discipline is related to the other disciplines in the following ways:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup/disciplines/architecture.html&quot;&#xD;
        guid=&quot;_0TX9AMlgEdmt3adZL5Dmdw&quot;>Architecture&lt;/a> and &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../openup/disciplines/development.html&quot; guid=&quot;_0TeDoMlgEdmt3adZL5Dmdw&quot;>Development&lt;/a>&amp;nbsp;disciplines&#xD;
        get&amp;nbsp;their primary input from the Requirements discipline.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup/disciplines/test.html&quot; guid=&quot;_0TkKQMlgEdmt3adZL5Dmdw&quot;>Test&lt;/a>&#xD;
        discipline validates the system against the requirements.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup/disciplines/config_and_change_management.html&quot;&#xD;
        guid=&quot;_0TwXgMlgEdmt3adZL5Dmdw&quot;>Configuration and change management&lt;/a> discipline provides the mechanisms to manage&#xD;
        changes to the requirements.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup/disciplines/project_management.html&quot;&#xD;
        guid=&quot;_0TqQ4MlgEdmt3adZL5Dmdw&quot;>Project Management&lt;/a> discipline plans the project and assigns requirements to each&#xD;
        iteration by analyzing the prioritized requirements and assigning work.&#xD;
    &lt;/li>&#xD;
&lt;/ul></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
