AVS Use Case

Scenario Overview
A Video Store (AVS) runs a series of fairly standard video stores.
Before a video can be put on the shelf, it must be cataloged and entered
into the video database. Every customer must have a valid AVS
customer card in order to rent a video. Customers rent videos for three
days at a time. Every time a customer rents a video, the system must
ensure that they do not have any overdue videos. If so, the overdue
videos must be returned and an overdue fee paid before customer can
rent more videos. Likewise, if the customer has returned overdue videos,
but has not paid the overdue fee, the fee must be paid before new videos
can be rented. Every morning, the store manager prints a report that lists
overdue videos. If a video is two or more days overdue, the manager
calls the customer to remind them to return the video. If a video is
returned in damaged condition, the manager removes it from the video
database and may sometimes charge the customer.

Objective Deliverable
1. Develop a Use Case diagram for the AVS scenario.

2. Create Use Case Descriptions for all the use cases in the use case
diagram.






AVS Use Case

1. Use Case Diagram
























AVS
Management System
Maintain Video
Collection
Process Overdue
Video Rentals
Search Video
Collection
Rent Video(s)
Return Video(s)
Manager
Customer
<<actor>>
Compliance
Department
AVS Use Case

2. Use Case Descriptions
Use Case Name: Maintain Video Collection
Primary Actor: Manager
Brief Description: Prior to a video being made available to rent, it must
be cataloged and entered into the video database.
Stakeholders: optional
Trigger: optional
Normal flow of events: If new video is cataloged and entered into database
then placed on shelf. If used video is checked for
damage and then if no damage is found it is cataloged
and places on the shelf.
Subflows: Damaged Video Handling
Alternate/Exception flow: If video is deemed damaged, manager will remove
video from the database, access charges to customer
account.

Use Case Name: Process Overdue Video Rentals
Primary Actor: Manager
Brief Description: If a video is overdue, a fee is accessed to the customer
account.
Stakeholders: Customer
Trigger: Exceeds Rental Return Date of 3 days in the System
Normal flow of events: Once a video is rented, a return date of 3 days is given
to each video that is associated with a customer
account. A fee will be applied each day that the video
rental is outstanding after the return date has passed
and until video has be cataloged back into the
database.
Subflows: Two or more days overdue- Call Customer
Alternate/Exception flow: After two or more days of a video being overdue, the
manager will call the customer to remind them to
return the video.

Use Case Name: Search Video Collection
Primary Actor: Customer
Brief Description: A customer seeking to rent a video will search the
video collection of the AVS store
Stakeholders: optional
Trigger: optional
Normal flow of events: Customer will search through cataloged videos that
are on the shelf of the AVS in order to select a video
for rental.
Subflows: optional
AVS Use Case

Alternate/Exception flow: required

Use Case Name: Rent Video(s)
Primary Actor: Customer
Brief Description: After searching through the AVS for a video (s),
customer then proceeds to associate their account
with a video for a 3 day period.
Stakeholders: Manager
Trigger: optional
Normal flow of events: Customer will bring selection of video (s) to AVS
checkout. The video will be recorded in the database
as checked out to the customer with a date/time stamp
of 3 days from time of check out.
Subflows: Compliance Department
Alternate/Exception flow: Prior to a video being rented to a customer, their
account is entered into the database and a record of
any outstanding overdue video(s) and balances that
have been accessed to that customer account will
return a value of compliant with no overdue video(s)
or balances or a value of non-compliance will appear.
If non-compliant, customer will have to return all
outstanding video(s) and clear all balances prior to
rental of a new video.

Use Case Name: Return Video(s)
Primary Actor: Customer
Brief Description: A video is returned to the AVS by a customer who
has rented the video.
Stakeholders: optional
Trigger: optional
Normal flow of events: A video that has been checked out to a customer is
received by the AVS and checked in, clearing the
video from the customer account.
Subflows: optional
Alternate/Exception flow: required