Use Case Diagram should be completed using Astah

Description of the Proposed New System

Your client organization is A Video Store (AVS), a company that owns a chain of discount video rental stores. Given declining revenue in recent years, AVS has decided to shut down its brick-and-mortar locations and only rent DVDs online (via mail order, similar to the Netflix DVD rental service).

The proposed functionality for the new DVD rental service is as follows:

When new movies come out on DVD and arrive at the AVS headquarters, the stockroom manager must catalogue each DVD by entering it in the database. As DVDs are lost or damaged over time, he/she must be able to update this inventory information accordingly.

Every customer must register online for an AVS account before they can rent DVDs through the mail. Registration requires entering your name, contact information, and a valid credit card, among other things. You must also set up your login information (ID and password) for future visits to the website. Obviously, you may need to make changes to this account information in the future, if you move, get a new credit card, etc. Logging in is required to make any changes to your account information in the future.

Customers can search the website to see what DVDs are available for rental. It is not necessary to be logged in to conduct a search. However, it is necessary to be logged in if you find a movie you like and want to add it to your rental wish list (or make any other changes to that list).

There will be only one subscription plan for now. For $10/month, a customer is eligible to receive one DVD at a time from the top of their wish list. There are no deadlines for returning DVDs. In other words, a customer can keep a DVD for as long as they want. However, they cannot rent another DVD until the previous one has been returned. If the customer informs AVS that a DVD has been lost or damaged, AVS will charge their account for the replacement value of that DVD.

An AVS employee will be responsible for processing all DVD rentals and returns. Processing a rental includes updating the system to show that a copy of the movie has been rented out to a particular customer, as well as recording shipment information (date/time, carrier, etc.). Processing a return includes updating the system to show that the customers copy of the movie has been returned, and recording the date/time, etc. of that return.

While there are no deadlines for returning DVDs, the system will send out a courtesy reminder notice after 30 days if the DVD has not yet been returned. This email notice is triggered automatically by the date/time of the original rental, and thus does not require any human (employee) interaction with the system.

The AVS owner would like to be able to generate an inventory report on demand, showing how many copies of each movie are currently in stock, and how many have been rented out, over a given time period. This information will help him to determine the most popular movies (and genres) to stock in the future.

Keep the following points in mind:

1. It is not necessarily true that all activities alluded to above involve the computerized system. For purposes of this assignment (and our class in general), your use case diagram should include only those use cases that involve the computerized system. For example, does the customer receiving a DVD in their postal mailbox, or taking it to the post office when they are done watching it, require interacting with the AVS IS in any way? If not, leave it out of your diagram.
2. The narrative may not give you all of the information that you feel you need to complete the assignment properly. If not, you should complete it to the extent possible and (1) make a list of questions that you, as a systems analyst, would need to get answered in order to finish it, or (2) make any necessary assumptions needed to finish it and turn in that list with your assignment. This list of questions and assumptions represents things that you, as a systems analyst, would need to follow up with your client about. This is crucial because in real life, users will often accidentally leave out requirements when they first talk to you, or otherwise not give you all of the information you need. Thus, you need to get in the habit of writing down any follow-up questions that you may need to go back and ask them. Whenever you find it necessary to make assumptions about how the system will work, you will also need to discuss these with the client to make sure they were correct. (You might find out, for example, that you made an assumption that directly contradicts how they actually do business.) TO REPEAT: In this and all future assignments, you need to turn in both the use case diagram and your list of any necessary questions/assumptions.
3. Do not read more into the narrative than it says. For example, do not add use cases to handle functionality that is not explicitly mentioned on the narrative. If you think critical functionality has been left out of the narrative, include this in your list of questions and assumptions. Finally, keep in mind that just because Netflix or Blockbuster does things a certain way does not mean that this is the way that AVS will do things!!
4. Be sure to add one or more use cases to show the maintenance of critical database tables that would need to exist in order to support your system. For example, since the system tracks DVDs, you know that there must be some way to add new movies/DVDs into the system, search for specific movies/DVDs, update information on movies/DVD copies, and potentially delete movies/DVDs from the system. Therefore, there must be a use case to maintain or manage movie/DVD information. Strive to use more appropriate, user-friendly names that describe the use case from a business perspective (for example, Manage Movies or Manage DVD Inventory).

5. Use Extension Points whenever you have Extend relationship in UC diagram.