Data Base week5_3

008 Semester 1, 2010 - Week 4 Case Study 1 Ver.1.0

Read the following case study, which describes the data requirements for a ViewMe™ video rental company. ViewMe™ video rental company has several branches throughout Auckland. The data held on each branch is the branch address made up of street, city, state, and zip code, and the telephone number. Each branch is given a branch number, which is unique throughout the company. Each branch is allocated staff, which includes a Manager. The Manager is responsible for the day-today running of a given branch. The data held on a member of staff is his or her name, position, and salary. Each member of staff is given a staff number, which is unique throughout the company.

Each branch has a stock of videos. The data held on a video is the catalog number, video number, title, category, daily rental, cost, status, and the names of the main actors, and the director. The catalog number uniquely identifies each video. However, in most cases, there are several copies of each video at a branch, and the individual copies are identified using the video number. A video is given a category such as Action, Adult, Children, Drama, Horror, or Sci-Fi. The status indicates whether a specific copy of a video is available for rent.

Before hiring a video from the company, a customer must first register as a member of a local branch. The data held on a member is the first and last name, address, and the date that the member registered at a branch. Each member is given a member number, which is unique throughout all branches of the company. Once registered, a member is free to rent videos, up to maximum of ten at any one time. The data held on each video rented is the rental number, the full name and number of the member, the video number, title, and daily rental, and the date the video is rented out and date returned. The rental number is unique throughout the company.

 

• 
  
  Identify the main entity types of the video rental company.
  Branch, Staff, Video, Copy of video, Customer, Video rented
  
• Identify the main relationship types between the entity types described in (a) and represent each relationship as an ER diagram.
  
• Determine the multiplicity constraints for each relationship described in (b). Represent the multiplicity for each relationship in the ER diagrams created in (b).
  
• Identify attributes and associate them with entity or relationship types. Represent each attribute in the ER diagrams created in Determine candidate and primary key attributes for each (strong) entity type.
  
• 
  
  Using your answers (a) to (e) attempt to represent the data requirements of the video rental company as a single ER diagram. State any assumptions necessary to support your design.
  
  
  My ER Diagram (It needs to modify some tables.)
  
  

 

 

<We have learnt>

Theoretical/ Designing

Normalisation

Scenario

-table

-attribute

-PK

-relation

-FK

-resolve

Practical

DDL

DML

 

Homework Mercy's Dry Cleaning SQL queries