<?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:rmc="http://www.ibm.com/rmc" rmc:version="7.5.1" xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.1" xmi:id="-i5J2T1z4y0Y1dFcHm78XXg" name="requirements_discipline,_iGSHtVZ-EdyIUdvDLLUdeg" guid="-i5J2T1z4y0Y1dFcHm78XXg" changeDate="2010-09-15T12:50:16.936-0700" version="7.2.0">
  <mainDescription>&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 stakeholders and define the problem to be solved. Having agreed on the problem to be solved, the&#xD;
    requirements for the system are elicited, organized, analyzed, validated, and specified.&#xD;
&lt;/p>&#xD;
&lt;p>&#xD;
    Throughout the lifecycle, you manage changes to the requirements.The Requirements discipline is related to the other&#xD;
    disciplines in the following ways:&#xD;
&lt;/p>&#xD;
&lt;ul>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../core.default.cat_def.base/disciplines/architecture_discipline_3A224435.html&quot;&#xD;
        guid=&quot;_iGSHsFZ-EdyIUdvDLLUdeg&quot;>Architecture&lt;/a> and &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../core.default.cat_def.base/disciplines/development_discipline_44C02445.html&quot;&#xD;
        guid=&quot;_iGSHsVZ-EdyIUdvDLLUdeg&quot;>Development&lt;/a>&amp;nbsp;disciplines get&amp;nbsp;their primary input from the Requirements&#xD;
        discipline.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot; href=&quot;./../../core.default.cat_def.base/disciplines/test_discipline_F7EB1A7A.html&quot;&#xD;
        guid=&quot;_iGSHtlZ-EdyIUdvDLLUdeg&quot;>Test&lt;/a> discipline validates the system against the requirements.&#xD;
    &lt;/li>&#xD;
    &lt;li>&#xD;
        The &lt;a class=&quot;elementLink&quot;&#xD;
        href=&quot;./../../core.default.cat_def.base/disciplines/project_management_discipline_FEB42654.html&quot;&#xD;
        guid=&quot;_iGSHtFZ-EdyIUdvDLLUdeg&quot;>Project Management&lt;/a>&amp;nbsp;discipline plans the project and assigns requirements to&#xD;
        each iteration by analyzing the prioritized requirements and assigning work.&#xD;
    &lt;/li>&#xD;
&lt;/ul></mainDescription>
</org.eclipse.epf.uma:ContentDescription>
