| <?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.4/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.2.0" xmlns:rmc="http://www.ibm.com/rmc" |
| rmc:version="7.2.0" xmi:id="_eUfzwMMyEdmdo9HxCRR_Gw" |
| name="requirements,_0Wh-sMlgEdmt3adZL5Dmdw" guid="_eUfzwMMyEdmdo9HxCRR_Gw" changeDate="2008-03-18T12:14:57.861-0700" |
| version="1.0.0"> |
| <mainDescription><p>
 |
| Requirements are the project team's to-do list.
 |
| </p>
 |
| <p>
 |
| Requirements define what is needed and focus the project team. They are the primary method used to communicate the
 |
| goals of the project to everyone on the team.
 |
| </p>
 |
| <p>
 |
| Requirements define:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| What the stakeholders need; and
 |
| </li>
 |
| <li>
 |
| What the system must include to satisfy the stakeholders' needs.
 |
| </li>
 |
| </ul>
 |
| <p>
 |
| Requirements are the basis for capturing and communicating needs, managing expectations, prioritizing and assigning
 |
| work, verifying and validating the system (acceptance), and managing the scope of the project.
 |
| </p>
 |
| <p>
 |
| Requirements may take different forms, including use cases and scenarios, unstructured text, structured text, or a
 |
| combination, and they may be stated at different levels of granularity. At the highest level of granularity,
 |
| features&nbsp;define the services that the system must provide to solve the customer's problem. These are captured as
 |
| structured or unstructured text in the project vision. At the next level of granularity, use cases can be used to
 |
| define the functionality that the system must provide to deliver the required features.&nbsp;Use cases&nbsp;describe
 |
| the sequence of actions performed by the system to yield an observable result of value.
 |
| </p>
 |
| <p>
 |
| As mentioned, a&nbsp;system must perform according to the behavior that can be specified as use cases. However, there
 |
| are system requirements that do not represent a specific behavior, also&nbsp;known as system-wide requirements,
 |
| including:
 |
| </p>
 |
| <ul>
 |
| <li>
 |
| Legal and regulatory requirements, as well as application standards
 |
| </li>
 |
| <li>
 |
| Quality attributes of the system to be built, including usability, reliability, performance, and supportability
 |
| requirements
 |
| </li>
 |
| <li>
 |
| Interface requirements to be able to communicate with external systems
 |
| </li>
 |
| <li>
 |
| Design constraints, such as those for operating systems and environments and for compatibility with other software
 |
| </li>
 |
| </ul></mainDescription> |
| </org.eclipse.epf.uma:ContentDescription> |
