Video Rental System Use case #1 User Authentication Actors: customers and admin Customer use case 1.

Begin on login page 2. Inputs username and password 3. Clicks on Login button 4. Success is when username and password combination exist in the database, and user is Customer type. 5. On success: send user to Customer home page 6. Alternate (on failure): send user to login page. Admin use case 1. Begin on login page 2. Inputs username and password 3. Clicks on Login button 4. Success is when username and password combination exist in the database and user is Admin type. 5. On success: send user to Admin home page 6. Alternate (on failure): send user to login page. Both admin and customer 1. Respective home pages have a logout link. 2. Click the link 3. User is logged out and directed to login page.

Use case #2 Customer options Actor: customer 1. Upon customer login he is presented with the customer home page. 2. Home page shows options available as links on the left Browse catalog (see use case 3) Search for video (see use case 4) Return a video (see use case 5) 3. The user's account balance (rent due) is always visible as the customer navigates 4. The user's rent basket is always visible as the customer navigates

Use case #3 CustomerBrowse catalog Actor: customer 1. When the customer chooses to browse the catalog of videos the application should present all available (not rented) videos in the library. Each video will be displayed with its catalog number, title, and a checkbox. 2. A customer can rent a video by selecting one or more checkboxes and clicking on a "Rent video" button. 3. Business rule: a customer may have at most five videos rented. If the total of selected videos and basket videos is less than or equal to the limit, the operation is successful. 4. Success scenario: the library is updated to reflect the video(s)' rented status. The video(s) rented get placed in the customer's basket. Customer is then redirected to customer home page. On the page, display a message indicating that rental was successful and indicate the video titles rented. 5. Failure scenario: return to browse catalog screen with a message indicating that the rental limit was exceeded. There should be no changes to the library or the baskets. 6. Include a Cancel button to return the customer to the customer home page. Use case #4 CustomerSearch catalog Actor: customer 1. Customer is presented with a search box, a button to submit search, and a button to cancel. 2. The customer can input search terms into the box. Only the first search term will be used. 3. Search will check for videos with a title that contains the text, case insensitive. So a search for "Ant" will show movies like "Antz" and "Fantastic Four." 4. The list of videos satisfying the search term will be displayed like in Use Case #3. The same business rules apply except for rental limit exceeded procedure, see 6. 5. If no video is found matching search criteria, return customer to the search page with a message saying "No videos matching search term." 6. Modification: rental limit exceeded should return customer to a page showing the list of videos from the search (see 4).

Use case #5 CustomerReturn video Actor: customer 1. The customer will be presented with his basket along with checkboxes, an text input box, a return video button, and a cancel button. 2. Cancel takes the customer back to the customer home page 3. To return a video, videos are selected by checkbox and the number of days rented are placed in the corresponding text boxes. The days rented numbers can be different. 4. For number of days rented, negative values are invalid, integers of 0 and up are acceptable. Rental rates are unchanged from first implementation. 5. Any invalid input will return customer to 1 with no operations performed even on entries with valid input. 6. Successful returns will get a library status update and will be removed from the basket. User balance is updated accordingly. Use case #6 Admin options Actor: Administrator 1. Upon admin login he is presented with the admin home page. 2. Home page shows options available as links on the left List users Add user Use case #7 Adminlist users Actor: admin 1. The admin is presented with a list of users Use case #8 Adminadd user Actor: admin 1. The admin is presented with a textfield for username input, a textfield for password input, a submit button, and a cancel button. 2. Cancel will take the admin to admin home. 3. To add a user, the admin inputs a username, password and presses submit. 4. The operation is successful if the username is unique (not already existing), passwords do not have to be uniqe. 5. Success scenario: the new user is added to the database of users. The admin is returned to admin home with a message indicating the addition of the user was successful, username is shown. 6. Failure scenario: the admin is returned to 1 along with a messsage that the username is already taken. end