OpenUP/OpenUP_baseline_EN/library/openup_basic/guidances/checklists/uc_model.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="_MqODAMM1EdmSIPI87WLu3g" name="uc_model,_0U6OEMlgEdmt3adZL5Dmdw" guid="_MqODAMM1EdmSIPI87WLu3g" changeDate="2005-07-07T14:50:06.005-0400" 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&gt;
    &lt;li&gt;
        The Use-Case Survey provides a clear, concise overview of the purpose and functionality of the system.
    &lt;/li&gt;
    &lt;li&gt;
        There are no long chains of include relationships, such as when an included use case&amp;nbsp;includes other use
        cases.&amp;nbsp; These can obscure comprehensibility.
    &lt;/li&gt;
    &lt;li&gt;
        Included use cases should not make assumptions about use cases that include them.
    &lt;/li&gt;
    &lt;li&gt;
        If several use cases contain similar&amp;nbsp;sub-flows investigate if&amp;nbsp;factoring this&amp;nbsp;common behavior into an
        included use case will simplify the model.&amp;nbsp;
    &lt;/li&gt;
&lt;/ul&gt;</sectionDescription>
  </sections>
  <sections xmi:id="__kgR8AeREduWycDgioo5rg" name="Have all use cases been identified?" guid="__kgR8AeREduWycDgioo5rg">
    <sectionDescription>&lt;ul&gt;
    &lt;li&gt;
        The use cases identified collectively account for all required behavior of the system.
    &lt;/li&gt;
    &lt;li&gt;
        All features identified in the Vision document for this iteration have been addressed by at least one use case.
    &lt;/li&gt;
    &lt;li&gt;
        All non-functional requirements that must be satisfied by a specific use case have been captured in that use case
    &lt;/li&gt;
    &lt;li&gt;
        The use-case model contains no superfluous behavior (gold-platting).
    &lt;/li&gt;
    &lt;li&gt;
        Each concrete use case must be associated with at least one actor.
    &lt;/li&gt;
    &lt;li&gt;
        Every actor should be associated with at least on use case.
    &lt;/li&gt;
&lt;/ul&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_fknU0Jz1EduBcbjYtLtItQ" name="Is the model consistent?" guid="_fknU0Jz1EduBcbjYtLtItQ">
    <sectionDescription>&lt;ul&gt;
    &lt;li&gt;
        Under the same conditions, and with the same input, the system behavior should be consistent.
    &lt;/li&gt;
&lt;/ul&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_KowpkAeSEduWycDgioo5rg" name="Are all relationships between use cases required?" guid="_KowpkAeSEduWycDgioo5rg">
    <sectionDescription>&lt;ul&gt;
    &lt;li&gt;
        Each included use case should make the model easier to understand, implement and maintain.
    &lt;/li&gt;
    &lt;li&gt;
        Each concrete use case (i.e. not an included use case) should be independent of other use cases.
    &lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;
    &lt;br /&gt;
&lt;/p&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_jyHeMAeTEduWycDgioo5rg" name="Are use-case packages used appropriately?" guid="_jyHeMAeTEduWycDgioo5rg">
    <sectionDescription>&lt;ul&gt;
    &lt;li&gt;
        Cross-package dependencies have been reduced or eliminated to prevent model ownership conflicts
    &lt;/li&gt;
    &lt;li&gt;
        Packaging is intuitive and makes the model easier to understand and implement
    &lt;/li&gt;
&lt;/ul&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_i-S-ADeKEdu6VLD0YaVLog" name="Do all model elements have appropriate names?" guid="_i-S-ADeKEdu6VLD0YaVLog">
    <sectionDescription>&lt;ul&gt;
    &lt;li&gt;
        No two use cases can have the same name.
    &lt;/li&gt;
    &lt;li&gt;
        Each actor has a name that effectively describes the role.
    &lt;/li&gt;
&lt;/ul&gt;</sectionDescription>
  </sections>
  <sections xmi:id="_IYRUkJz2EduBcbjYtLtItQ" name="Are individual use cases properly specified?" guid="_IYRUkJz2EduBcbjYtLtItQ">
    <sectionDescription>&lt;ul&gt;
    &lt;li&gt;
        Review the quality of each&amp;nbsp;use case specification using the &lt;a class=&quot;elementLinkWithType&quot;
        href=&quot;./../../../openup_basic/guidances/checklists/use_case,_0kNwINk1Edq2Q8qZoWbvGA.html&quot;
        guid=&quot;_0kNwINk1Edq2Q8qZoWbvGA&quot;&gt;Checklist: Use Case&lt;/a&gt;.
    &lt;/li&gt;
&lt;/ul&gt;</sectionDescription>
  </sections>
</org.eclipse.epf.uma:ContentDescription>