| <?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.5/uma.ecore" |
| xmlns:epf="http://www.eclipse.org/epf" epf:version="1.5.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><ul>
 |
| <li>
 |
| Does the Use-Case Survey provide a clear, concise overview of the purpose and functionality of the system?
 |
| </li>
 |
| <li>
 |
| Are there no long chains of <i>include</i> relationships, such as when an included use case&nbsp;includes other use
 |
| cases? These can obscure comprehension.
 |
| </li>
 |
| <li>
 |
| Are&nbsp;included use cases independent of the use cases that include them?
 |
| </li>
 |
| <li>
 |
| If several use cases contain similar&nbsp;subflows, have you investigated whether factoring this&nbsp;common
 |
| behavior into an included use case will simplify the model?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="__kgR8AeREduWycDgioo5rg" name="Have all use cases been identified?" |
| guid="__kgR8AeREduWycDgioo5rg"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Do the use cases identified collectively account for all required behavior of the system?
 |
| </li>
 |
| <li>
 |
| Have all features identified in the Vision document for this iteration been addressed by at least one use case?
 |
| </li>
 |
| <li>
 |
| Have all nonfunctional requirements that must be satisfied by a specific use case been captured in that use case?
 |
| </li>
 |
| <li>
 |
| Have you verified that the use-case model contains no superfluous behavior (known as "gold-plating")?
 |
| </li>
 |
| <li>
 |
| Is each concrete use case associated with at least one Actor, as it should be?
 |
| </li>
 |
| <li>
 |
| Is every Actor associated with at least one use case?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_fknU0Jz1EduBcbjYtLtItQ" name="Is the model consistent?" guid="_fknU0Jz1EduBcbjYtLtItQ"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Is the system behavior consistent under the same conditions and with the same input?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_KowpkAeSEduWycDgioo5rg" name="Are all relationships between use cases required?" |
| guid="_KowpkAeSEduWycDgioo5rg"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Does each included use case make the model easier to understand, implement, and maintain?
 |
| </li>
 |
| <li>
 |
| Is each concrete use case (not an included use case) independent of other use cases?
 |
| </li>
 |
| </ul><br />
 |
| <br /></sectionDescription> |
| </sections> |
| <sections xmi:id="_jyHeMAeTEduWycDgioo5rg" name="Are use-case packages used appropriately?" |
| guid="_jyHeMAeTEduWycDgioo5rg"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have cross-package dependencies been reduced or eliminated to prevent model ownership conflicts
 |
| </li>
 |
| <li>
 |
| Is packaging intuitive?&nbsp; Does the packaging make the model easier to understand and implement?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_i-S-ADeKEdu6VLD0YaVLog" name="Do all model elements have appropriate names?" |
| guid="_i-S-ADeKEdu6VLD0YaVLog"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have you verified that no two use cases have the same name?
 |
| </li>
 |
| <li>
 |
| Does each Actor have a name that effectively describes that person's Role?
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| <sections xmi:id="_IYRUkJz2EduBcbjYtLtItQ" name="Are individual use cases properly specified?" |
| guid="_IYRUkJz2EduBcbjYtLtItQ"> |
| <sectionDescription><ul>
 |
| <li>
 |
| Have you reviewed the quality of each&nbsp;use case specification using the <a class="elementLinkWithType"
 |
| href="./../../../openup/guidances/checklists/use_case.html" guid="_0kNwINk1Edq2Q8qZoWbvGA">Checklist: Use Case</a>.
 |
| </li>
 |
| </ul></sectionDescription> |
| </sections> |
| </org.eclipse.epf.uma:ContentDescription> |
