Part III. Normalization for Relational Databases

The following attributes represent data about a movie copy at an online video rental service. Each movie is identified by a movie number and has a title and information about the director and the studio that produced the movie. Each movie has one or several characters, and there is exactly one actor playing the role of each of the characters (but one actor can play multiple roles in each of the movies). The video rental service has multiple licenses for the same movie, and the service differentiates the licenses with a movie copy number, which is unique within a single movie but not unique between different movies. Each movie license has a rental status and return date; in addition, each license has a type (Regular or HD). The rental price depends on the movie and the license type, but the price is the same for all licenses of the same type. The attributes are as follows:

Movie Nbr, Title, Director ID, Director Name, Studio ID, Studio Name, Studio Location, Studio CEO, Character, Actor ID, Name, Movie License Nbr, Movie license Type, Movie Rental Price, License Rental Status, License Return Date

A sample data set regarding a movie would be as follows (the data in the curly brackets are character / actor data, in this case for four different characters):

567, "It's a Wonderful Life", 25, "Frank Capra", 234, "Liberty Films", "Hollywood, CA", "Orson Wells", {"George Bailey", 245, "James Stewart" | "Mary Bailey", 236, "Donna Reed" | "Clarence Oddbody", 765, "Henry Travers" | "Henry F.Potter", 325, "lionel Barrymore"}, 5434, "HD", 3.95, "Rented", "12/15/2018"

Therefore, following functional dependencies are expected in this table:

Each movie is identified by a movie number

Each movie has a title, information about the director and the studio that produced the movie.

 MovieNbr --> Ttile, DirectorID, StudioID

 DirectorID--> DirectorName

 StudioID--> StudioName, StudioLocation, StudioCEO

Each movie has one or several characters, and there is exactly one actor playing the role of each of the characters (but one actor can play multiple roles in each of the movies).

MovieNbr, Charter-->ActorID

 ActorID-->ActorName

The video rental service has multiple licenses for the same movie, and the service differentiates the licenses with a movie copy number, which is unique within a single movie but not unique between different movies. Each movie license has a rental status and return date;

MovieNbr, LicenseNbr-->LicenseRentalStatus, LicneseReturnDate, MovieLienceType

in addition, each license has a type (Regular or HD). The rental price depends on the movie and the license type, but the price is the same for all licenses of the same type.

MovieNbr, MovieLicenseType-->MovieRentalPrice

5 Among the functional dependencies, list transitive dependencies if any.

6. Explain the reasons why this relation is not in 3NF

7. Perform normalization so that the resulting relation schemas are in 3NF. 

- Clearly indicate the primary key (PK) of each relation.

- If any, denote the foreign keys (e.g., FK, FK1, K2). To indicate the table referenced by a foreign key, use an arrow line.

- The domain constraint (e.g., data type, data length) of each attribute is not required.

You can use any drawing tool or database modeling tool for relational schemas. For example, MS Visio supports relational schema notations. Use an arrow line to indicate the table referenced by a foreign key.