Question

Create a set of use cases for the following system: A video store (AVS) runs a series of fairly standard video stores. Before a video can be put on the shelf , it must be catalogued 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 3 days at a time. Every time a customer rents a video the system must ensure that the customer doesn't have any overdue videos. If so the overdue videos must be returned and overdue fee paid before the customer can rent any more videos. Likewise if the customer has returned overdue videos , but has not paid the overdue fee, the fee must be paid before any new videos can be rented. Every morning the store manager prints a report that lists overdue videos, if a video is 2 or more days overdue then 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.

Please help me! CREATE USE CASE DIAGRAM for the situation in exercise F – Use MS Word to draw it using Insert and Shapes menu) – 1p. Consider that for a customer to have a valid video store card the customer must create an account. Also consider that as a step after renting a video (or videos) the customer must pay for the rental(s). The assumption is that a customer pays only using credit card

Answer 1

A use case diagram is a graphic depiction of the interactions among the elements of a system.

Use case diagrams depict:

Use cases. A use case describes a sequence of actions that provide something of measurable value to an actor and is drawn as a horizontal ellipse.

Actors. An actor is a person, organization, or external system that plays a role in one or more interactions with your system. Actors are drawn as stick figures.

Associations. Associations are modeled as lines connecting use cases and actors to one another, with an optional arrowhead on one end of the line. The arrowhead is often used to indicating the direction of the initial invocation of the relationship or to indicate the primary actor within the use case. The arrowheads should not be confused with the data flow.

System boundary boxes (optional). You can draw a rectangle around the use cases, called the system boundary box, to indicates the scope of your system.

Packages (optional). Packages are UML constructs that enable you to organize model elements (such as use cases) into groups. Packages are depicted as file folders and can be used on any of the UML diagrams, including both use case diagrams and class diagrams.

Answer:

I choose Umbrello to draw the Use Case diagram. It is the professional tool to draw the UML diagrams.

Note: While drawing Use case never relate it to flow. Treat each use case independent and draw dependencies later. This will reduce confusion.

Use Case Diagram for AVS: