OpenUP/OpenUP_PT/library/openup_basic/guidances/concepts/requirements.xmi

<?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="_eUfzwMMyEdmdo9HxCRR_Gw" name="requirements,_0Wh-sMlgEdmt3adZL5Dmdw" guid="_eUfzwMMyEdmdo9HxCRR_Gw" changeDate="2006-12-21T11:21:47.640-0500" version="1.0.0">
  <mainDescription>&lt;p&gt;
    Requirements are the project team's to-do list.
&lt;/p&gt;
&lt;p align=&quot;left&quot;&gt;
    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.
&lt;/p&gt;
&lt;div class=&quot;O&quot; v:shape=&quot;_x0000_s1026&quot;&gt;
    &lt;div style=&quot;mso-line-spacing: '100 30 0'&quot;&gt;
        Requirements define:
    &lt;/div&gt;
&lt;/div&gt;
&lt;ul&gt;
    &lt;li&gt;
        What the&amp;nbsp;stakeholders&amp;nbsp;need; and
    &lt;/li&gt;
    &lt;li&gt;
        What the system must include to satisfy the stakeholder needs.
    &lt;/li&gt;
&lt;/ul&gt;
&lt;p align=&quot;left&quot;&gt;
    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.
&lt;/p&gt;
&lt;p align=&quot;left&quot;&gt;
    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,&amp;nbsp;&lt;a
    class=&quot;elementLink&quot; href=&quot;./../../../openup_basic/guidances/termdefinitions/feature,_PgYREAeYEduWycDgioo5rg.html&quot;
    guid=&quot;_PgYREAeYEduWycDgioo5rg&quot;&gt;Feature&lt;/a&gt;s define the services that the system must provide to solve the customer's
    problem. These are captured as structured or unstructured text in the &lt;a class=&quot;elementLinkWithType&quot;
    href=&quot;./../../../openup_basic/workproducts/vision,_0WVxcMlgEdmt3adZL5Dmdw.html&quot;
    guid=&quot;_0WVxcMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Vision&lt;/a&gt;. At the next level of granularity, Use Cases define the
    functionality that the system must provide to&amp;nbsp;deliver the required features. These are captured&amp;nbsp;as Use Cases
    (see &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup_basic/workproducts/use_case,_0VGbUMlgEdmt3adZL5Dmdw.html&quot;
    guid=&quot;_0VGbUMlgEdmt3adZL5Dmdw&quot;&gt;Artifact: Use Case&lt;/a&gt;)&amp;nbsp;that describe the sequence of actions performed by the
    system to yield an observable result of value.
&lt;/p&gt;
&lt;p&gt;
    A system must perform according to the behavior that Use Cases specify. However, there are system requirements that do
    not represent a specific behavior:
&lt;/p&gt;
&lt;ul&gt;
    &lt;li&gt;
        Legal and regulatory requirements, as well as application standards
    &lt;/li&gt;
    &lt;li&gt;
        Quality attributes of the system to be built, including usability, reliability, performance, and supportability
        requirements
    &lt;/li&gt;
    &lt;li&gt;
        Interface requirements to be able to communicate with external systems
    &lt;/li&gt;
    &lt;li&gt;
        Design constraints, such as those for operating systems and environments and for compatibility with other software
    &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
    These quality requirements are often referred to as &lt;strong&gt;non-functional&lt;/strong&gt; requirements.
&lt;/p&gt;
&lt;p&gt;
    Quality requirements that apply to the system as a whole are captured as structured text in &lt;a
    class=&quot;elementLinkWithType&quot;
    href=&quot;./../../../openup_basic/workproducts/supporting_requirements,_BVh9cL-CEdqb7N6KIeDL8Q.html&quot;
    guid=&quot;_BVh9cL-CEdqb7N6KIeDL8Q&quot;&gt;Artifact: Supporting Requirements&lt;/a&gt;.&amp;nbsp; Quality requirements that are closely
    associated with a particular Use Case are often captured in the Use Case itself to simplify review, understanding, and
    maintenance.
&lt;/p&gt;</mainDescription>
</org.eclipse.epf.uma:ContentDescription>