Read the following case study, which describes the data requirements for a DVD rental company. • The DVD Rental Company has several branches throughout USA. • The data held on each branch is the branch address made up of street, city, state, and postal 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-to-day 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 DVDs. • The data held on a DVD is the catalog number, DVD number, title, category, daily rental, cost, status, and the names of the main actors, and the director. • The catalog number uniquely identifies each DVD. However, in most cases, there are several copies of each DVD at a branch, and the individual copies are identified using the DVD number. • A DVD is given a category such as Action, Adult, Children, Drama, Horror, or Sci-Fi. • The status indicates whether a specific copy of a DVD is available for rent. • Before renting a DVD 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 DVDs, up to maximum of ten at any one time. • The data held on each DVD rented is the rental number, the full name and number of the member, the DVD number, title, and daily rental, and the dates the DVD is rented out and date returned. • The rental number is unique throughout the company. (a) A table listing the main entity types of the DVD rental company. (b) A table listing the main relationship types between the entity types described in (a). (c) A table listing the multiplicity constraints for each relationship described in (b).
Read the following case study, which describes the data requirements for a DVD rental company.
• The DVD Rental Company has several branches throughout USA.
• The data held on each branch is the branch address made up of street, city, state, and postal
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-to-day 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 DVDs.
• The data held on a DVD is the catalog number, DVD number, title, category, daily rental, cost,
status, and the names of the main actors, and the director.
• The catalog number uniquely identifies each DVD. However, in most cases, there are several
copies of each DVD at a branch, and the individual copies are identified using the DVD
number.
• A DVD is given a category such as Action, Adult, Children, Drama, Horror, or Sci-Fi.
• The status indicates whether a specific copy of a DVD is available for rent.
• Before renting a DVD 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 DVDs, up to maximum of ten at any one time.
• The data held on each DVD rented is the rental number, the full name and number of the
member, the DVD number, title, and daily rental, and the dates the DVD is rented out and date
returned.
• The rental number is unique throughout the company.
(a) A table listing the main entity types of the DVD rental company.
(b) A table listing the main relationship types between the entity types
described in (a).
(c) A table listing the multiplicity constraints for each relationship described
in (b).
(d) A table listing attributes.
(e) A table listing primary keys for each (strong) entity type.
You may combine the above tables into fewer tables if you wish.
(f) Use appropriate diagramming software to represent the data requirements
of the DVD rental company as a single ER diagram, based on your answers (a) to
(e). Represent the multiplicities determined in (c). Represent each attribute
identified in (d) and (e).
(g) State any assumptions necessary to support your design.
Trending now
This is a popular solution!
Step by step
Solved in 4 steps with 2 images
(d) A table listing attributes.
(e) A table listing primary keys for each (strong) entity type.
You may combine the above tables into fewer tables if you wish.
(f) Use appropriate diagramming software to represent the data requirements
of the DVD rental company as a single ER diagram, based on your answers (a) to
(e). Represent the multiplicities determined in (c). Represent each attribute
identified in (d) and (e).
by Bartleby Expert
