| <?xml version="1.0" encoding="UTF-8"?> |
| <!DOCTYPE html PUBLIC "-//W3C/DTD XHTML 1.0 Strict//EN" "DTD/xhtml1-strict.dtd"> |
| <!-- VERSION rmc:7.1.0 --> |
| <html xmlns="http://www.w3.org/1999/xhtml"> |
| <head> |
| <meta http-equiv="Content-Type" content="text/html; charset=UTF-8"/> |
| <!-- START NON-TRANSLATABLE --> |
| <title>\openup_basic\guidances\checklists\uc_model.xmi</title> |
| </head> |
| <!-- WARNING: do not modify the generated comments in this file below this line. They are used as markers for the import process. --> |
| <body> |
| Element Name: uc_model.xmi<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: presentationName<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:presentationName,_0U6OEMlgEdmt3adZL5Dmdw CRC: 2596955702 -->Use-Case Model<!-- END:presentationName,_0U6OEMlgEdmt3adZL5Dmdw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: briefDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:briefDescription,_0U6OEMlgEdmt3adZL5Dmdw CRC: 1098136934 -->This checklist provides questions to verify that the Use-Case Model is described in a consistent and complete manner.<!-- END:briefDescription,_0U6OEMlgEdmt3adZL5Dmdw --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_rLdVMAeREduWycDgioo5rg CRC: 818635897 -->Is it easy to understand what the system does by reviewing the model?<!-- END:name,_rLdVMAeREduWycDgioo5rg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_rLdVMAeREduWycDgioo5rg CRC: 1592198705 --><ul> |
| <li> |
| The Use-Case Survey provides a clear, concise overview of the purpose and functionality of the system. |
| </li> |
| <li> |
| There are no long chains of include relationships, such as when an included use case includes other use |
| cases. These can obscure comprehensibility. |
| </li> |
| <li> |
| Included use cases should not make assumptions about use cases that include them. |
| </li> |
| <li> |
| If several use cases contain similar sub-flows investigate if factoring this common behavior into an |
| included use case will simplify the model. |
| </li> |
| </ul><!-- END:sectionDescription,_rLdVMAeREduWycDgioo5rg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,__kgR8AeREduWycDgioo5rg CRC: 3807182316 -->Have all use cases been identified?<!-- END:name,__kgR8AeREduWycDgioo5rg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,__kgR8AeREduWycDgioo5rg CRC: 3615580343 --><ul> |
| <li> |
| The use cases identified collectively account for all required behavior of the system. |
| </li> |
| <li> |
| All features identified in the Vision document for this iteration have been addressed by at least one use case. |
| </li> |
| <li> |
| All non-functional requirements that must be satisfied by a specific use case have been captured in that use case |
| </li> |
| <li> |
| The use-case model contains no superfluous behavior (gold-platting). |
| </li> |
| <li> |
| Each concrete use case must be associated with at least one actor. |
| </li> |
| <li> |
| Every actor should be associated with at least on use case. |
| </li> |
| </ul><!-- END:sectionDescription,__kgR8AeREduWycDgioo5rg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_fknU0Jz1EduBcbjYtLtItQ CRC: 1206379082 -->Is the model consistent?<!-- END:name,_fknU0Jz1EduBcbjYtLtItQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_fknU0Jz1EduBcbjYtLtItQ CRC: 231219731 --><ul> |
| <li> |
| Under the same conditions, and with the same input, the system behavior should be consistent. |
| </li> |
| </ul><!-- END:sectionDescription,_fknU0Jz1EduBcbjYtLtItQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_KowpkAeSEduWycDgioo5rg CRC: 2253122176 -->Are all relationships between use cases required?<!-- END:name,_KowpkAeSEduWycDgioo5rg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_KowpkAeSEduWycDgioo5rg CRC: 1512830752 --><ul> |
| <li> |
| Each included use case should make the model easier to understand, implement and maintain. |
| </li> |
| <li> |
| Each concrete use case (i.e. not an included use case) should be independent of other use cases. |
| </li> |
| </ul> |
| <p> |
| <br /> |
| </p><!-- END:sectionDescription,_KowpkAeSEduWycDgioo5rg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_jyHeMAeTEduWycDgioo5rg CRC: 3494360501 -->Are use-case packages used appropriately?<!-- END:name,_jyHeMAeTEduWycDgioo5rg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_jyHeMAeTEduWycDgioo5rg CRC: 1209591249 --><ul> |
| <li> |
| Cross-package dependencies have been reduced or eliminated to prevent model ownership conflicts |
| </li> |
| <li> |
| Packaging is intuitive and makes the model easier to understand and implement |
| </li> |
| </ul><!-- END:sectionDescription,_jyHeMAeTEduWycDgioo5rg --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_i-S-ADeKEdu6VLD0YaVLog CRC: 4017282728 -->Do all model elements have appropriate names?<!-- END:name,_i-S-ADeKEdu6VLD0YaVLog --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_i-S-ADeKEdu6VLD0YaVLog CRC: 388921198 --><ul> |
| <li> |
| No two use cases can have the same name. |
| </li> |
| <li> |
| Each actor has a name that effectively describes the role. |
| </li> |
| </ul><!-- END:sectionDescription,_i-S-ADeKEdu6VLD0YaVLog --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: name<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:name,_IYRUkJz2EduBcbjYtLtItQ CRC: 1975733662 -->Are individual use cases properly specified?<!-- END:name,_IYRUkJz2EduBcbjYtLtItQ --> |
| <br/><br/><br/> |
| <!-- START NON-TRANSLATABLE --> |
| Attribute: sectionDescription<br/><br/> |
| <!-- END NON-TRANSLATABLE --> |
| <!-- START:sectionDescription,_IYRUkJz2EduBcbjYtLtItQ CRC: 1657789414 --><ul> |
| <li> |
| Review the quality of each use case specification using the <a class="elementLinkWithType" |
| href="./../../../openup_basic/guidances/checklists/use_case,_0kNwINk1Edq2Q8qZoWbvGA.html" |
| guid="_0kNwINk1Edq2Q8qZoWbvGA">Checklist: Use Case</a>. |
| </li> |
| </ul><!-- END:sectionDescription,_IYRUkJz2EduBcbjYtLtItQ --> |
| </body> |
| </html> |
