Problem Description-to-ER Diagrams TO Relational Model Design a database for each of the following problems. Draw a neat Entity-Relationship Diagram for each problem. USE M.N notation. DO NOT Use crows-feet notation. Translate the diagram into a relational model. It is enough to show the table design like this: TABLE NAME (ColumnNamel, ColumnName2, ...) Underline the Primary Key Specify all the Foreign keys like this: ColName FOREIGN KEY REFERENCES ANOTHER_TABLE (othercoName) DVD Database: Mr. X has a collection of DVD's and wants to create a database to manage them. Each DVD has a DVDId (such as DVDO01) and contains ONE movie. A movie has a title, genre, year of production and many roles and is produced by a producer and directed by a director. Each role in a movie is played by an actor. An actor plays only one role in a movie, but the actor can play roles in many movies. A producer can produce many movies and a movie can have many producers. A director can direct many movies and a movie is directed by only one director. Actors, directors, producers are all people who have Id's, first names, last names, phone numbers and emails