Use Case Diagrams
Consider the following scenario then complete the exercises below:
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.
Exercises:
Develop a Use Case diagram for the AVS scenario.
Create Use Case Descriptions for all the use cases in your use case diagram. The use case description should include the use case name, actor, brief description, normal flow of events, and exception flow of events.
Use Case Name: required
Primary Actor: required
Brief Description: required
Stakeholders: optional
Trigger: optional
Normal flow of events: required
Subflows: optional
Alternate/Exception flow: required