blob: fe6cf15e4fc09301bfe36e0b62629b4880aad922 [file] [log] [blame]
<?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" xmi:id="_MqODAMM1EdmSIPI87WLu3g"
name="uc_model,_0U6OEMlgEdmt3adZL5Dmdw" guid="_MqODAMM1EdmSIPI87WLu3g" changeDate="2005-07-07T11:50:06.005-0700"
version="1.0.0">
<sections xmi:id="_rLdVMAeREduWycDgioo5rg" name="Is it easy to understand what the system does by reviewing the model?"
guid="_rLdVMAeREduWycDgioo5rg">
<sectionDescription>&lt;ul>&#xD;
&#xD;
&lt;li> Does the Use-Case Survey provide a clear, concise overview of the purpose &#xD;
and functionality of the system?&lt;/li>&#xD;
&lt;li> Are there no long chains of &lt;i>include &lt;/i>relationships, such as when &#xD;
an included use case&amp;nbsp;includes other use cases? These can obscure comprehension. &#xD;
&lt;/li>&#xD;
&#xD;
&lt;li> Do included use cases not make assumptions about use cases that include &#xD;
them?&lt;/li>&#xD;
&#xD;
&lt;li> If several use cases contain similar&amp;nbsp;subflows, have you investigated &#xD;
whether factoring this&amp;nbsp;common behavior into an included use case will &#xD;
simplify the model?&lt;/li>&#xD;
&lt;/ul></sectionDescription>
</sections>
<sections xmi:id="__kgR8AeREduWycDgioo5rg" name="Have all use cases been identified?"
guid="__kgR8AeREduWycDgioo5rg">
<sectionDescription>&lt;ul>&#xD;
&#xD;
&lt;li> Do the use cases identified collectively account for all required behavior &#xD;
of the system?&lt;/li>&#xD;
&#xD;
&lt;li> Have all features identified in the Vision document for this iteration &#xD;
been addressed by at least one use case?&lt;/li>&#xD;
&#xD;
&lt;li> Have all nonfunctional requirements that must be satisfied by a specific &#xD;
use case been captured in that use case?&lt;/li>&#xD;
&#xD;
&lt;li> Have you verified that the use-case model contains no superfluous behavior &#xD;
(known as &amp;quot;gold-plating&amp;quot;)?&lt;/li>&#xD;
&#xD;
&lt;li> Is each concrete use case associated with at least one Actor, as it should &#xD;
be? &lt;/li>&#xD;
&#xD;
&lt;li> Is every Actor associated with at least one use case?&lt;/li>&#xD;
&lt;/ul></sectionDescription>
</sections>
<sections xmi:id="_fknU0Jz1EduBcbjYtLtItQ" name="Is the model consistent?" guid="_fknU0Jz1EduBcbjYtLtItQ">
<sectionDescription>&lt;p>Is the system behavior consistent under the same conditions and with the same &#xD;
input? &lt;/p></sectionDescription>
</sections>
<sections xmi:id="_KowpkAeSEduWycDgioo5rg" name="Are all relationships between use cases required?"
guid="_KowpkAeSEduWycDgioo5rg">
<sectionDescription>&lt;ul>&#xD;
&#xD;
&lt;li> Does each included use case make the model easier to understand, implement, &#xD;
and maintain?&lt;/li>&#xD;
&#xD;
&lt;li> Is each concrete use case (not an included use case) independent of other &#xD;
use cases?&lt;/li>&#xD;
&lt;/ul>&#xD;
&lt;p></sectionDescription>
</sections>
<sections xmi:id="_jyHeMAeTEduWycDgioo5rg" name="Are use-case packages used appropriately?"
guid="_jyHeMAeTEduWycDgioo5rg">
<sectionDescription>&lt;ul>&#xD;
&lt;li>&#xD;
Cross-package dependencies have been reduced or eliminated to prevent model ownership conflicts&#xD;
&lt;/li>&#xD;
&lt;li>&#xD;
Packaging is intuitive and makes the model easier to understand and implement&#xD;
&lt;/li>&#xD;
&lt;/ul></sectionDescription>
</sections>
<sections xmi:id="_i-S-ADeKEdu6VLD0YaVLog" name="Do all model elements have appropriate names?"
guid="_i-S-ADeKEdu6VLD0YaVLog">
<sectionDescription>&lt;ul>&#xD;
&#xD;
&lt;li> Have you verified that no two use cases have the same name?&lt;/li>&#xD;
&#xD;
&lt;li> Does each Actor have a name that effectively describes that person's Role?&lt;/li>&#xD;
&lt;/ul></sectionDescription>
</sections>
<sections xmi:id="_IYRUkJz2EduBcbjYtLtItQ" name="Are individual use cases properly specified?"
guid="_IYRUkJz2EduBcbjYtLtItQ">
<sectionDescription>&lt;ul>&#xD;
&lt;li>&#xD;
Review the quality of each&amp;nbsp;use case specification using the &lt;a class=&quot;elementLinkWithType&quot; href=&quot;./../../../openup/guidances/checklists/use_case_C5362874.html&quot; guid=&quot;_0kNwINk1Edq2Q8qZoWbvGA&quot;>Checklist: Use Case&lt;/a>.&#xD;
&lt;/li>&#xD;
&lt;/ul></sectionDescription>
</sections>
</org.eclipse.epf.uma:ContentDescription>