Scribd
Upload
98 views2 pages

Use Case Template

This document provides a template for writing use cases with sections for a unique ID, title, description, primary actor, preconditions, postconditions, main success scenario, extensions, frequency of use, status, owner, and priority. It includes an example use case for a student registering for courses using the template format.

Uploaded by

Satish Jadhao
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
98 views2 pages

Use Case Template

This document provides a template for writing use cases with sections for a unique ID, title, description, primary actor, preconditions, postconditions, main success scenario, extensions, frequency of use, status, owner, and priority. It includes an example use case for a student registering for courses using the template format.

Uploaded by

Satish Jadhao
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 2

Use Case Template:

(Courtesy of Accompa, Inc. Our affordable web-based software helps you create use cases like
these easily, using customizable templates.)

Template:
ID: [Unique ID of this use case]
Title: [Enter the goal of the use case - preferably as a short, active verb
phrase]
Description: [Describe the goal and context of this use case. This is usually an
expanded version of what you entered in the "Title" field.]
Primary Actor: [A person or a software/hardware system that interacts with your system
to achieve the goal of this use case.]
Preconditions: [Describe the state the system is in before the first event in this use
case.]
Postconditions: [Describe the state the system is in after all the events in this use case
have taken place.]
Main
[Describe the flow of events from preconditions to postconditions, when
Success
nothing goes wrong. This is the meat of the use case.]
Scenario:
Extensions:
[Describe all the other scenarios for this use case - including exceptions
and error cases.]
Frequency of Use: [How often will this use case be used?]
Status: [Development status]
Owner: [Who owns this use case, in your project team?]
Priority: [Priority of this use case]

Example:
This example uses this template to write a use case for helping a student register for courses.
The system under design is a University Registration System.
ID: UC-6
Title: Register for courses
Description: Student accesses the system and views the courses currently available
for him to register. Then he selects the courses and registers for them.
Primary Actor: Student
Preconditions: Student is logged into system
Postconditions: Student is registered for courses
Main 1. Student selects "Register New Courses" from the menu.
Success 2. System displays list of courses available for registering.
Scenario: 3. Student selects one or more courses he wants to register for.
4. Student clicks "Submit" button.
5. System registers student for the selected courses and displays a
confirmation message.
Extensions: 2a. No courses are available for this student.
--- 2a1. System displays error message saying no courses are available,
and provides the reason & how to rectify if possible.
--- 2a2. Student either backs out of this use case, or tries again after
rectifying the cause.

5a. Some courses could not be registered.


--- 5a1. System displays message showing which courses were
registered, and which courses were not registered along with a reason
for each failure.

5b. None of the courses could be registered.


--- 5b1. System displays message saying none of the courses could be
registered, along with a reason for each failure.
Frequency of Use: A few times every quarter
Status: Pending Review
Owner: John Smith
Priority: P3 - Medium

You might also like