| <?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.5/uma.ecore" |
| xmlns:rmc="http://www.ibm.com/rmc" rmc:version="7.5.0" xmlns:epf="http://www.eclipse.org/epf" |
| epf:version="1.5.0" xmi:id="-i5J2T1z4y0Y1dFcHm78XXg" |
| name="requirements_discipline,_iGSHtVZ-EdyIUdvDLLUdeg" guid="-i5J2T1z4y0Y1dFcHm78XXg" |
| changeDate="2008-06-17T18:08:12.420-0700" version="7.2.0"> |
| <mainDescription><p> The purpose of this discipline is to: </p>
 |
| <ul>
 |
| <li> Understand the problem to be solved </li>
 |
| <li> Understand stakeholder needs (what users want) </li>
 |
| <li> Define the requirements for the solution (what the system must do) </li>
 |
| <li> Define the boundaries (scope) of the system </li>
 |
| <li> Identify external interfaces for the system </li>
 |
| <li> Identify technical constraints on the solution </li>
 |
| <li> Provide the basis for planning iterations </li>
 |
| <li> Provide the initial basis for estimating cost and schedule </li>
 |
| </ul>
 |
| <p> To achieve these goals, it is important to understand the definition and scope 
 |
| of the problem that you are trying to solve. Identify <a class="elementLinkWithUserText" href="./../../core.default.role_def.base/roles/stakeholder_9FFD4106.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a> 
 |
| and define the problem to be solved. Having agreed on the problem to be solved, 
 |
| the <a class="elementLink" href="./../../core.tech.common.extend_supp/guidances/concepts/requirements_8006414F.html" guid="_0Wh-sMlgEdmt3adZL5Dmdw">Requirements</a> 
 |
| for the system are elicited, organized, analyzed, validated, and specified. 
 |
| </p>
 |
| <p> Throughout the lifecycle, you manage changes to the requirements.The Requirements 
 |
| discipline is related to the other disciplines in the following ways: </p>
 |
| <ul>
 |
| <li> The <a class="elementLink" href="./../../core.default.cat_def.base/disciplines/architecture_discipline_3A224435.html" guid="_iGSHsFZ-EdyIUdvDLLUdeg">Architecture</a> 
 |
| and <a class="elementLink" href="./../../core.default.cat_def.base/disciplines/development_discipline_44C02445.html" guid="_iGSHsVZ-EdyIUdvDLLUdeg">Development</a>&nbsp;disciplines 
 |
| get&nbsp;their primary input from the Requirements discipline. </li>
 |
| <li> The <a class="elementLink" href="./../../core.default.cat_def.base/disciplines/test_discipline_F7EB1A7A.html" guid="_iGSHtlZ-EdyIUdvDLLUdeg">Test</a> 
 |
| discipline validates the system against the requirements. </li>
 |
| <li> The <a class="elementLink" href="./../../core.default.cat_def.base/disciplines/project_management_discipline_FEB42654.html" guid="_iGSHtFZ-EdyIUdvDLLUdeg">Project Management</a>&nbsp;discipline plans the project and assigns requirements 
 |
| to each iteration by analyzing the prioritized requirements and assigning 
 |
| work. </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |