June 24, 2004

Use Case Template

For the change management application, that I am still toying with the idea of building. I figure that if requirements come about they can't be all that damaging. The worse thing that can happen is that when we do get approval to move forward, at least we will have something that everyone can start from. One of the things that needs to be done for requirements is the uses cases, the detailed overview and then the drill down. Below is a template for use cases, that I'm thinking of using. After a quick perusal does anyone see any room for improvement?

           

Use Case ID

 

Use Case Name

 

Use Case Goal

The goal of the use case

Created By

 

Date Created

 

Last Updated By

 

Date Last Updated

 

Primary Actor

Actor

StakeHolder and Interest

Whom is interested in this use case and what is the impact or area of interest.

Use Case Description

A detailed description of the use case includes activity, and data captured.

 

Preconditions

What needs to be in place before the use case is triggered

Post conditions

How is the successful completion of the use case determined

Priority

Critical, High, Medium, Low, Cosmetic

Frequency of Use

 

Basic Flow

The Detailed WorkFlow

Alternative Flow

Possible Alternate WorkFlows that exhaust the same use case

Exceptions

 

Includes

Other uses included in this flow

Special Requirements

 

Assumptions

 

Notes and Issues

 

 

Posted by Elyse at June 24, 2004 6:52 AM | TrackBack
Comments

Most of the use cases I have seen are excel spreadsheets with a list of possible good/bad things for the web application.

Is this a next step up? And who uses similar forms?

Posted by: Craig M. Rosenblum at June 24, 2004 10:10 AM
Post a comment









Remember personal info?