EXERCISE: MOVIE SHOP USE-CASE MODEL

The following are the requirements for a web-based system to computerize the
management of the sale and rental of movies for a shop.

The system must be able to handle both physical and digital movies.

It must be able to record which movies are sold and rented and by whom.

For sold movies, the quantity sold should be recorded; for physical movie rental,
which copy is rented and when it is due back should be recorded.

The system should keep track of overdue rentals of physical movies and send
email notices to customers who have movies overdue.

There will be a customer membership option for an annual fee, which will entitle a
member to discounts (10%) on the sale and rental of movies.

Members should be able to make reservations for physical movie rentals either in
person at the shop, by telephone or via the Web.

A member can reserve at most five physical movies at any one time, but there is
no limit on how many physical movies a member or nonmember can rent at any
one time.

As an added feature, the shop would like to allow customers (either members or
nonmembers) to input, via the Web, mini-reviews (up to 100 words) and a rating
(from 1, lowest, to 10, highest) of movies they have purchased or rented.
EXERCISE: MOVIE SHOP USE-CASE MODEL (cont'd)

These reviews should be anonymous if the customer so wishes (i.e., customers

can specify whether they want their name to be made known when other
customers browse the reviews).

A sales clerk should be able to enter and update the following information about
all customers (members or nonmembers): name, address, phone number, age,
sex, and email address.

Members are assigned a membership number by the shop when they become
members and a password, which allows them to change their personal
information and to buy and rent digital movies via the Web.

The shop manager should be able to generate various reports on the sale and
rental of movies.

A sales clerk should be able to sell and rent physical movies and process the
return of rented physical movies.

When selling or renting physical movies, a sales clerk must be able to look up
customer information and determine whether the customer is a member.

A sales clerk must be able to enter basic information about a movie (i.e., movie
id, title, leading actor(s), director, producer, genre, synopsis, release year,
running time, selling price, and rental price).
EXERCISE: MOVIE SHOP USE-CASE MODEL (cont'd)

From the movie sales and rental shop requirements statement:

a) identify all actors and their required functionality.

b) group the functionality into use cases and show the uses
cases and their related actors in a use-case context
diagram.
 EXERCISE:
MOVIE SHOP USE-CASE MODEL ANALYSIS


 #$

#
  
 





 



 

 

 

"

#




  
 
 
!


!  





% 
#
 



 

# 

 
!

  
 


 
 

% 
 




"
!





#
"

  
Someone buy movie
Someone rent movie

% 

!

 #

 



# 
!
 

"
#



"


 
 
 


  
Someone
enter movie quantity sold
Someone
enter movie copy rented and due date
 EXERCISE:
MOVIE SHOP USE-CASE MODEL ANALYSIS
" 
!


 


 

! 




 




 


  
Customer
receive overdue notice

 




 
 








 
   

" 








 











 

 


  
Someone enter member information
Member get discount

" 




 
 

! 

 







!





  
Member reserve movie
Sales clerk reserve movie

 


  








 
   
 EXERCISE:
MOVIE SHOP USE-CASE MODEL ANALYSIS

A member can reserve at most five physical movies at any one time, but there is
no limit on how many physical movies a member or nonmember can rent at any
one time.
functionality: No new functionality.

As an added feature, the shop would like to allow customers (either members or
nonmembers) to input, via the Web, mini-reviews (up to 100 words) and a rating
(from 1, lowest, to 10, highest) of movies they have purchased or rented.
functionality: Customer: enter movie review

These reviews should be anonymous if the customer so wishes (i.e., customers

can specify whether they want their name to be made known when other
customers browse the reviews).
functionality: Customer: browse movie reviews
 EXERCISE:
MOVIE SHOP USE-CASE MODEL ANALYSIS

A sales clerk should be able to enter and update the following information about
all customers (members or nonmembers): name, address, phone number, age,
sex, and email address.
functionality: Sales clerk: enter customer information
Supersedes the requirement regarding someone entering
member information.
Sales clerk: update customer information

Members are assigned a membership number by the shop when they become
members and a password, which allows them to change their personal
information and to buy and rent digital movies via the Web.
functionality: Member: update personal information
Member: buy movie
Member: rent movie
Clarifies who can use buy and rent functionality.

The shop manager should be able to generate various reports on the sale and
rental of movies.
functionality: Manager: generate reports
 EXERCISE:
MOVIE SHOP USE-CASE MODEL ANALYSIS
 
  
 




 

 
 
 

 


 

 
 
 
  Sales clerk buy (sell) movie
Sales clerk rent movie
Sales clerk return rented movie
  
 


  
      

  
 

 
 
 

  
 







 
 

 
  

 


  
  Sales clerk lookup customer information

 
  
 




 

 



 


 
 
 

 
  
  

  
 


 
 
 

  
 
  Sales clerk enter movie information


 


 
 


 



 






 
  



   
  

 

  
 
 EXERCISE:
MOVIE SHOP USE-CASE MODEL ANALYSIS


Customer                 
                 
 

Member                  

            
    
           
     
            

Sales clerk                    

    
     
      
            
     

Manager                  

   
          
       
 EXERCISE: MOVIE SHOP USE-CASE MODEL
FUNCTIONALITY ANALYSIS AND GROUPING
Member 
Sales clerk Someone: enter movie quantity sold
Sales clerk Someone: enter movie copy rented and due date
Customer: receive overdue notice
Member: get discount
Member: reserve movie
Sales clerk: reserve movie
Customer: enter movie review
Customer: browse movie reviews
Sales clerk: enter customer information
Sales clerk: update customer information
Member: update personal information
Should customer Member: buy movie
be an actor for Member: rent movie
buy/rent movie? Manager: generate reports
Sales clerk: buy (sell) movie
No! Why? Sales clerk: rent movie
Customers do not interact Sales clerk: return rented movie
directly with the system to Sales clerk: lookup customer information
buy/rent a movie. Sales clerk: enter movie information
 EXERCISE: MOVIE SHOP USE-CASE MODEL
FUNCTIONALITY ANALYSIS AND GROUPING

Member: buy movie

Member: enter movie quantity sold
Member: get discount
Buy Movie
Sales clerk: buy (sell) movie
Sales clerk: lookup customer information
Sales clerk: enter movie quantity sold

Member: rent movie

Member: get discount
Sales clerk: rent movie
Sales clerk: lookup customer information Rent Movie
Sales clerk: enter movie copy rented and due date
Sales clerk: return rented movie
Customer
receive overdue notice
 EXERCISE: MOVIE SHOP USE-CASE MODEL
FUNCTIONALITY ANALYSIS AND GROUPING

Member: reserve movie

Reserve Movie
Sales clerk: reserve movie

Customer: enter movie review

Manage Reviews
Customer: browse movie reviews

Sales clerk: enter customer information

Sales clerk: update customer information Manage Customer
Member: update personal information

Manager: generate reports Generate Reports

Sales clerk: enter movie information Manage Movie

 EXERCISE:
MOVIE SHOP INITIAL USE-CASE DIAGRAM

Buy Movie

Rent Movie

Customer
Manage Reviews

Sales clerk

Reserve Movie

Member
Manage Customer

Manage Movie Manager

Generate Reports
 EXERCISE:
MOVIE SHOP REFINED USE-CASE DIAGRAM
Buy Movie                 
Manage Reviews                
       
Customer Rent Movie                 
Rent Movie               
  
            
                  
               
Buy Movie            
Sales clerk Manage Reviews           
                 
Reserve Movie
            

Member Reserve Movie                

Manage Customer                    
 

Manage Customer               

Manage Movie Manager          

Manage Movie             

Generate Reports Generate Reports           
        
 
 
 
 
 
EXERCISE: MOVIE SHOP USE-CASE MODEL
COMMON ERRORS

#! 





"



" 


☞

 
 
 

 



$





!





 






!
!
!

 





☞

 

   





!
 
 






! 



EXERCISE: MOVIE SHOP USE-CASE MODEL
COMMON ERRORS

Do not represent nonfunctional requirements.
(e.g., 10% discount)

Login is not a functional requirement.

– It is actually a non-functional (security) requirement that can be
represented by an administration use case.

Incorrect use of use-case generalization.

A use-case model is not a structure chart!

A use-case model is not a domain model!

A use-case model is not a work of art!