<?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.3/uma.ecore" epf:version="1.0.0" xmi:id="__rFCULv9EdmmUvZAZjqE3g" name="requirements,_0TR2ZMlgEdmt3adZL5Dmdw" guid="__rFCULv9EdmmUvZAZjqE3g" changeDate="2006-09-20T13:00:00.125-0400">
  <mainDescription>&lt;p&gt;
    The purpose of this discipline is to:
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;
        Understand the problem to be solved
    &lt;/li&gt;
    &lt;li&gt;
        Understand stakeholder needs (what users want)&amp;nbsp;
    &lt;/li&gt;
    &lt;li&gt;
        Define the requirements for the solution (what the system must do)
    &lt;/li&gt;
    &lt;li&gt;
        Define the boundaries (scope) of the system
    &lt;/li&gt;
    &lt;li&gt;
        Identify external interfaces for the system
    &lt;/li&gt;
    &lt;li&gt;
        Identify technical constraints on the solution
    &lt;/li&gt;
    &lt;li&gt;
        Provide the basis for planning iterations
    &lt;/li&gt;
    &lt;li&gt;
        Provide the initial basis for estimating cost and schedule
    &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
    To achieve these goals, it is important to understand the definition and scope of the problem&amp;nbsp;that we are trying
    to solve.&amp;nbsp; &lt;a class=&quot;elementLinkWithUserText&quot; href=&quot;./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html&quot; guid=&quot;_dTa6gMAYEdqX-s4mWhkyqQ&quot;&gt;Stakeholders&lt;/a&gt;&amp;nbsp;are identified and the problem to be solved is defined.
&lt;/p&gt;
&lt;p&gt;
    Having agreed on the problem to be solved, the &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/guidances/concepts/requirements,_0Wh-sMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0Wh-sMlgEdmt3adZL5Dmdw&quot;&gt;Requirements&lt;/a&gt;&amp;nbsp;for the system are elicited, organized, analyzed, validated and
    specified.
&lt;/p&gt;
&lt;p&gt;
    Throughout the lifecycle, changes to the requirements are managed.
&lt;/p&gt;
&lt;p&gt;
    The Requirements discipline is related to the other disciplines in the following ways:
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/disciplines/analysis_and_design,_0TX9AMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0TX9AMlgEdmt3adZL5Dmdw&quot;&gt;Analysis &amp; Design&lt;/a&gt;&amp;nbsp;discipline gets its primary input from the
        Requirements discipline
    &lt;/li&gt;
    &lt;li&gt;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/disciplines/test,_0TkKQMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0TkKQMlgEdmt3adZL5Dmdw&quot;&gt;Test&lt;/a&gt;&amp;nbsp;discipline validates the system against the requirements
    &lt;/li&gt;
    &lt;li&gt;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/disciplines/config_and_change_management,_0TwXgMlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0TwXgMlgEdmt3adZL5Dmdw&quot;&gt;Configuration &amp; Change Management&lt;/a&gt;&amp;nbsp;discipline provides the mechanisms to
        manage changes to the requirements
    &lt;/li&gt;
    &lt;li&gt;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../openup_basic/disciplines/project_management,_0TqQ4MlgEdmt3adZL5Dmdw.html&quot; guid=&quot;_0TqQ4MlgEdmt3adZL5Dmdw&quot;&gt;Project Management&lt;/a&gt;&amp;nbsp;discipline plans the project and assigns
        requirements&amp;nbsp;to each iteration by analyzing the prioritized requirements and assigning work.&amp;nbsp;
    &lt;/li&gt;
&lt;/ul&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>