OpenUP/OpenUP_baseline_EN/exported_HTML_0_9/openup_basic/guidances/checklists/use_case.html - epf/org.eclipse.epf.nl-libraries - Git at Google

 <?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\use_case.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: use_case.xmi<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: presentationName<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:presentationName,_0kNwINk1Edq2Q8qZoWbvGA CRC: 3319967926 -->Use Case<!-- END:presentationName,_0kNwINk1Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: briefDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:briefDescription,_0kNwINk1Edq2Q8qZoWbvGA CRC: 272819987 -->This checklist provides questions to verify that use cases are described in a consistent and complete manner.<!-- END:briefDescription,_0kNwINk1Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_663wMNk1Edq2Q8qZoWbvGA CRC: 824882437 -->Is the use-case name meaningful and un-ambiguous?<!-- END:name,_663wMNk1Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_663wMNk1Edq2Q8qZoWbvGA CRC: 1150248584 --><p>
     Does the use case have a unique name?
 </p>
 <p>
     Is the name a verb + noun phrase (for example, Withdraw Cash)?
 </p>
 <p>
     Does the name accurately&nbsp;summarize the&nbsp;main goal&nbsp;of the use case?
 </p>
 <p>
     Is the name "actor independent"?
 </p><!-- END:sectionDescription,_663wMNk1Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_ZTA8QJznEduBcbjYtLtItQ CRC: 2587034568 -->Does the brief description clearly describe the primary goal of the use case?<!-- END:name,_ZTA8QJznEduBcbjYtLtItQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_ZTA8QJznEduBcbjYtLtItQ CRC: 1481017042 --><p>
     Is it clear from the brief description what the main purpose of the use case is?
 </p>
 <p>
     Is the "observable result of value" obvious?
 </p><!-- END:sectionDescription,_ZTA8QJznEduBcbjYtLtItQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_4wJRgJznEduBcbjYtLtItQ CRC: 4162917410 -->Are associated actors and information exchanged clearly defined?<!-- END:name,_4wJRgJznEduBcbjYtLtItQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_4wJRgJznEduBcbjYtLtItQ CRC: 1381166868 --><p>
     Is the use case associated with one or more actors?
 </p>
 <p>
     Is the primary, or initiating actor, defined?
 </p>
 <p>
     Is it clear who wishes to perform the use case?
 </p>
 <p>
     Is all information exchanged between the actor(s) and the system clearly specified?
 </p>
 <p>
     If a "time" actor is used, are you sure you did not miss an important actor and associated use cases (such as
     administrative or maintenance personnel that define schedule events)?
 </p><!-- END:sectionDescription,_4wJRgJznEduBcbjYtLtItQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_Qys_INk2Edq2Q8qZoWbvGA CRC: 2655536127 -->Are the pre-conditions specified?<!-- END:name,_Qys_INk2Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_Qys_INk2Edq2Q8qZoWbvGA CRC: 3266314631 --><p>
     Does each pre-condition represent a tangible&nbsp;state&nbsp;of&nbsp;the system (for example, the Withdraw Cash use
     case for an automated teller machine has a precondition that the user has an account)?
 </p><!-- END:sectionDescription,_Qys_INk2Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_q3qV0Nk2Edq2Q8qZoWbvGA CRC: 1965870233 -->Are the Basic Flow and Alternate Flows complete, correct and consistent?<!-- END:name,_q3qV0Nk2Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_q3qV0Nk2Edq2Q8qZoWbvGA CRC: 2404604333 --><p>
     Is it clear how the use case is started?
 </p>
 <p>
     Is the triggering event clearly described?
 </p>
 <p>
     Does the flow have a definite ending?
 </p>
 <p>
     Does&nbsp;each step in the scenario contain&nbsp;the same level of abstraction?&nbsp;&nbsp;
 </p>
 <p>
     Does each step in the scenario describe something that can actually happen and that the system can reasonably detect?
 </p>
 <p>
     Does each step make&nbsp;progress towards the goal?
 </p>
 <p>
     Are there any missing steps? Is it clear how to go from one step to the next? Does the sequence of communication
     between the actors and the use case conform to the user's expectations?
 </p>
 <p>
     Does each step describe how the step helps the actor achieve their goal?
 </p>
 <p>
     Is each step technology independent? Is it free of technical details, and design decisions?
 </p>
 <p>
     Are the steps correctly numbered?
 </p>
 <p>
     For each alternate flow is the condition(s) for initiation of the flow clearly defined?
 </p>
 <p>
     For each alternate flow is it clear how the use case ends or where in the basic flow that the use case resumes?
 </p><!-- END:sectionDescription,_q3qV0Nk2Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_dnLXMNk2Edq2Q8qZoWbvGA CRC: 3961501011 -->Are the post-conditions specified?<!-- END:name,_dnLXMNk2Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_dnLXMNk2Edq2Q8qZoWbvGA CRC: 2449244277 --><p>
     If "Minimal Guarantees" are present, do they always happen when the use case completes, regardless of success? (A
     Minimal Guarantee represents&nbsp;a condition&nbsp;that will be true when the use case ends, regardless of how it
     terminates.)
 </p>
 <p>
     If "Success Guarantees" are present, do they always happen when the use case completes successfully? (A Success
     Guarantee represents a condition that will be true when the use case ends successfully, regardless of which path it
     takes.)
 </p><!-- END:sectionDescription,_dnLXMNk2Edq2Q8qZoWbvGA -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: name<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:name,_vkbMAJzrEduBcbjYtLtItQ CRC: 3928009720 -->Are applicable non-functional requirements captured?<!-- END:name,_vkbMAJzrEduBcbjYtLtItQ -->
 <br/><br/><br/>
 <!-- START NON-TRANSLATABLE -->
 Attribute: sectionDescription<br/><br/>
 <!-- END NON-TRANSLATABLE -->
 <!-- START:sectionDescription,_vkbMAJzrEduBcbjYtLtItQ CRC: 3034953606 --><p>
     Are non-functional requirements (such as performance criteria) that are&nbsp;applicable to the&nbsp;use case captured
     in the use case?
 </p>
 <p>
     Are these non-functional requirements applicable to many use cases?&nbsp; It they are, consider capturing them in the
     supporting requirements specification to simplify maintenance.
 </p><!-- END:sectionDescription,_vkbMAJzrEduBcbjYtLtItQ -->
 </body>
 </html>
	<?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\use_case.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: use_case.xmi<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: presentationName<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:presentationName,_0kNwINk1Edq2Q8qZoWbvGA CRC: 3319967926 -->Use Case<!-- END:presentationName,_0kNwINk1Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: briefDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:briefDescription,_0kNwINk1Edq2Q8qZoWbvGA CRC: 272819987 -->This checklist provides questions to verify that use cases are described in a consistent and complete manner.<!-- END:briefDescription,_0kNwINk1Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_663wMNk1Edq2Q8qZoWbvGA CRC: 824882437 -->Is the use-case name meaningful and un-ambiguous?<!-- END:name,_663wMNk1Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_663wMNk1Edq2Q8qZoWbvGA CRC: 1150248584 --><p>
	Does the use case have a unique name?
	</p>
	<p>
	Is the name a verb + noun phrase (for example, Withdraw Cash)?
	</p>
	<p>
	Does the name accurately summarize the main goal of the use case?
	</p>
	<p>
	Is the name "actor independent"?
	</p><!-- END:sectionDescription,_663wMNk1Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_ZTA8QJznEduBcbjYtLtItQ CRC: 2587034568 -->Does the brief description clearly describe the primary goal of the use case?<!-- END:name,_ZTA8QJznEduBcbjYtLtItQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_ZTA8QJznEduBcbjYtLtItQ CRC: 1481017042 --><p>
	Is it clear from the brief description what the main purpose of the use case is?
	</p>
	<p>
	Is the "observable result of value" obvious?
	</p><!-- END:sectionDescription,_ZTA8QJznEduBcbjYtLtItQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_4wJRgJznEduBcbjYtLtItQ CRC: 4162917410 -->Are associated actors and information exchanged clearly defined?<!-- END:name,_4wJRgJznEduBcbjYtLtItQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_4wJRgJznEduBcbjYtLtItQ CRC: 1381166868 --><p>
	Is the use case associated with one or more actors?
	</p>
	<p>
	Is the primary, or initiating actor, defined?
	</p>
	<p>
	Is it clear who wishes to perform the use case?
	</p>
	<p>
	Is all information exchanged between the actor(s) and the system clearly specified?
	</p>
	<p>
	If a "time" actor is used, are you sure you did not miss an important actor and associated use cases (such as
	administrative or maintenance personnel that define schedule events)?
	</p><!-- END:sectionDescription,_4wJRgJznEduBcbjYtLtItQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_Qys_INk2Edq2Q8qZoWbvGA CRC: 2655536127 -->Are the pre-conditions specified?<!-- END:name,_Qys_INk2Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_Qys_INk2Edq2Q8qZoWbvGA CRC: 3266314631 --><p>
	Does each pre-condition represent a tangible state of the system (for example, the Withdraw Cash use
	case for an automated teller machine has a precondition that the user has an account)?
	</p><!-- END:sectionDescription,_Qys_INk2Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_q3qV0Nk2Edq2Q8qZoWbvGA CRC: 1965870233 -->Are the Basic Flow and Alternate Flows complete, correct and consistent?<!-- END:name,_q3qV0Nk2Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_q3qV0Nk2Edq2Q8qZoWbvGA CRC: 2404604333 --><p>
	Is it clear how the use case is started?
	</p>
	<p>
	Is the triggering event clearly described?
	</p>
	<p>
	Does the flow have a definite ending?
	</p>
	<p>
	Does each step in the scenario contain the same level of abstraction?
	</p>
	<p>
	Does each step in the scenario describe something that can actually happen and that the system can reasonably detect?
	</p>
	<p>
	Does each step make progress towards the goal?
	</p>
	<p>
	Are there any missing steps? Is it clear how to go from one step to the next? Does the sequence of communication
	between the actors and the use case conform to the user's expectations?
	</p>
	<p>
	Does each step describe how the step helps the actor achieve their goal?
	</p>
	<p>
	Is each step technology independent? Is it free of technical details, and design decisions?
	</p>
	<p>
	Are the steps correctly numbered?
	</p>
	<p>
	For each alternate flow is the condition(s) for initiation of the flow clearly defined?
	</p>
	<p>
	For each alternate flow is it clear how the use case ends or where in the basic flow that the use case resumes?
	</p><!-- END:sectionDescription,_q3qV0Nk2Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_dnLXMNk2Edq2Q8qZoWbvGA CRC: 3961501011 -->Are the post-conditions specified?<!-- END:name,_dnLXMNk2Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_dnLXMNk2Edq2Q8qZoWbvGA CRC: 2449244277 --><p>
	If "Minimal Guarantees" are present, do they always happen when the use case completes, regardless of success? (A
	Minimal Guarantee represents a condition that will be true when the use case ends, regardless of how it
	terminates.)
	</p>
	<p>
	If "Success Guarantees" are present, do they always happen when the use case completes successfully? (A Success
	Guarantee represents a condition that will be true when the use case ends successfully, regardless of which path it
	takes.)
	</p><!-- END:sectionDescription,_dnLXMNk2Edq2Q8qZoWbvGA -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: name<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:name,_vkbMAJzrEduBcbjYtLtItQ CRC: 3928009720 -->Are applicable non-functional requirements captured?<!-- END:name,_vkbMAJzrEduBcbjYtLtItQ -->
	<br/><br/><br/>
	<!-- START NON-TRANSLATABLE -->
	Attribute: sectionDescription<br/><br/>
	<!-- END NON-TRANSLATABLE -->
	<!-- START:sectionDescription,_vkbMAJzrEduBcbjYtLtItQ CRC: 3034953606 --><p>
	Are non-functional requirements (such as performance criteria) that are applicable to the use case captured
	in the use case?
	</p>
	<p>
	Are these non-functional requirements applicable to many use cases?  It they are, consider capturing them in the
	supporting requirements specification to simplify maintenance.
	</p><!-- END:sectionDescription,_vkbMAJzrEduBcbjYtLtItQ -->
	</body>
	</html>