Detailed Use Case

Quality Assurance Checklist

 

Use Case Name:                    Verb/noun 

                                 

Use Case Number:                Follow current standards? (i.e. references to related systems) 

Iteration:                                Is iteration level noted? 

Description:                            Does the description:

1.      Begin with “the purpose of this use case is…”

2.      Clearly state the value provided to the actor

3.      Clearly state the purpose/goal of the use case                                 

 

Generic Scenario:                  The generic course of events should:                 

1.      Clearly state how the use case starts and ends (i.e. this use case starts when and ends when)

2.      Be written in the appropriate perspective (system perspective)

3.      Have a minimum of 3 steps identified

4.      Be consistent with description and within the scope of the description

5.      Use the active voice to describe the end user or system interface performing the steps

6.      Document the system solution, using ping pong, to identify the system interface responses clearly

7.      Identify links to other use cases, by underlining the use case name and reference the use case number

8.      Not document GUI but instead attach a prototype or an activity diagram

9.      Have no more than 9 or so steps

10.  Provide a step by step flow of events from the actor’s perspective.

Actors:                                    Are the correct actors identified?

1.      Are the users and/or systems that communicate with the solution identified?

2.      Are the actors a person or system other than the support system under development?

3.      Are the actors identified only involved in this use case? 

 

Alternate Scenario:                Are the alternate paths identified correctly?

1.      Is the path intentional by the actor and within the actor’s control?

2.      Does the title of the alternate describe the alternate path and tell why it is an alternate.

3.      Is the alternate using the appropriate numbering scheme and is referenced in the basic course of events section? (A1)

4.      Does the alternate successfully complete the use case?

 

Exceptions:                             Are the system exceptions identified?

1.      Do the exceptions result in a different outcome of the use case?

2.      Is the exception unintentional, an anticipated failure that needs a recovery plan?

3.      Is the exception using the appropriate numbering scheme (E1) and is referenced in the basic course of events section?

 

Trigger:                                 

1.      Is the event that causes the use case to occur present?

2.      Is the active voice used?

3.      Is the trigger a business event, not a system event? 

Assumptions:

1.      Is the item outside the control of development (including the out of scope) AND must be in place before the use case can run? 

Preconditions:                       

1.      Ensure the precondition is not the first step of the basic course of events.

2.      Is the item inside the control of development and in place prior to the execution of the use case?   

Post conditions:

1.      Ensure post condition is not the last step of the basic course of events.

2.      Does the post condition declare the state after the use case execution?  

Related Business Rules:

1.      Are the business rules specific to this use case?

2.      Is it a business related rule rather than a system rule?

3.      Should be written as a declarative statement

Issues:                                               

Should be NONE