| <?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:epf="http://www.eclipse.org/epf" epf:version="1.5.0" xmi:id="__rFCULv9EdmmUvZAZjqE3g" |
| name="requirements,_0TR2ZMlgEdmt3adZL5Dmdw" guid="__rFCULv9EdmmUvZAZjqE3g" changeDate="2007-09-06T14:43:39.235-0700" |
| version="1.0.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="./../../openup/roles/stakeholder_9FFD4106.html"
 |
| guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a> and define the problem to be solved.
 |
| </p>
 |
| <p>
 |
| Having agreed on the problem to be solved, the <a class="elementLink"
 |
| href="./../../openup/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.
 |
| </p>
 |
| <p>
 |
| The Requirements discipline is related to the other disciplines in the following ways:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| The <a class="elementLink" href="./../../openup/disciplines/architecture_1F9C65DA.html"
 |
| guid="_0TX9AMlgEdmt3adZL5Dmdw">Architecture</a> and <a class="elementLink"
 |
| href="./../../openup/disciplines/development_B5D1D8A.html"
 |
| guid="_0TeDoMlgEdmt3adZL5Dmdw">Development</a>&nbsp;disciplines get&nbsp;their primary input from the Requirements
 |
| discipline.
 |
| </li>
 |
| <li>
 |
| The <a class="elementLink" href="./../../openup/disciplines/test_FB85069.html"
 |
| guid="_0TkKQMlgEdmt3adZL5Dmdw">Test</a> discipline validates the system against the requirements.
 |
| </li>
 |
| <li>
 |
| The <a class="elementLink" href="./../../openup/disciplines/configuration_and_change_management_417EC254.html"
 |
| guid="_0TwXgMlgEdmt3adZL5Dmdw">Configuration and Change Management</a> discipline provides the mechanisms to manage
 |
| changes to the requirements.
 |
| </li>
 |
| <li>
 |
| The <a class="elementLink" href="./../../openup/disciplines/project_management_AFB03A6.html"
 |
| guid="_0TqQ4MlgEdmt3adZL5Dmdw">Project Management</a> 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> |
