| <?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><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)&nbsp; |
| </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&nbsp;that we are trying |
| to solve.&nbsp; <a class="elementLinkWithUserText" href="./../../openup_basic/roles/stakeholder,_dTa6gMAYEdqX-s4mWhkyqQ.html" guid="_dTa6gMAYEdqX-s4mWhkyqQ">Stakeholders</a>&nbsp;are identified and the problem to be solved is defined. |
| </p> |
| <p> |
| Having agreed on the problem to be solved, the <a class="elementLink" href="./../../openup_basic/guidances/concepts/requirements,_0Wh-sMlgEdmt3adZL5Dmdw.html" guid="_0Wh-sMlgEdmt3adZL5Dmdw">Requirements</a>&nbsp;for the system are elicited, organized, analyzed, validated and |
| specified. |
| </p> |
| <p> |
| Throughout the lifecycle, changes to the requirements are managed. |
| </p> |
| <p> |
| The Requirements discipline is related to the other disciplines in the following ways: |
| </p> |
| <ul> |
| <li> |
| The <a class="elementLink" href="./../../openup_basic/disciplines/analysis_and_design,_0TX9AMlgEdmt3adZL5Dmdw.html" guid="_0TX9AMlgEdmt3adZL5Dmdw">Analysis & Design</a>&nbsp;discipline gets its primary input from the |
| Requirements discipline |
| </li> |
| <li> |
| The <a class="elementLink" href="./../../openup_basic/disciplines/test,_0TkKQMlgEdmt3adZL5Dmdw.html" guid="_0TkKQMlgEdmt3adZL5Dmdw">Test</a>&nbsp;discipline validates the system against the requirements |
| </li> |
| <li> |
| The <a class="elementLink" href="./../../openup_basic/disciplines/config_and_change_management,_0TwXgMlgEdmt3adZL5Dmdw.html" guid="_0TwXgMlgEdmt3adZL5Dmdw">Configuration & Change Management</a>&nbsp;discipline provides the mechanisms to |
| manage changes to the requirements |
| </li> |
| <li> |
| The <a class="elementLink" href="./../../openup_basic/disciplines/project_management,_0TqQ4MlgEdmt3adZL5Dmdw.html" guid="_0TqQ4MlgEdmt3adZL5Dmdw">Project Management</a>&nbsp;discipline plans the project and assigns |
| requirements&nbsp;to each iteration by analyzing the prioritized requirements and assigning work.&nbsp; |
| </li> |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |