Provide the suitable ERD for the following system,(Entity Relationship Diagram) Any assumptions must be explicitly listed The goal of this question is to implement a database system application for a movie ratings-cum-social-network system VTFlix (like Flixster.com) where users can explore Information about movies, rate movies, and see ratings of their friends. You will work with video information, user information, ratings of videos, and users soclal network. Each video has an id, title, release date, producer, color (e.g., black-n-white, or Eastman color), and whlch country It comes from. There are 3 categories of videos: movies, TV episodes and collections. Different TV episodes are different videos. A TV episode belongs to a collection and has an episode number. Each collection can contain one or more seasons. For each collection, we want to additionally record these season numbers. E.g. we want to model that a collection titled 'Seinfeld: The Early Episodes, contains seasons1' and '2, 3 Movies don't have different parts eg. 'Harry Potter 1, and 'Harry Potter 11, are different movles. One or more directors direct each movie or a TV episode. And each director is identified by an id and has name and age. . Each video could belong to one or more genre (e.g., action, comedy, romantic horror, thriller, and historical) . VTFlix needs to keep the track of user ratings for each video (e.g., 1-5 and 1 for I hate it!', to 5, for 'I love it!'). A particular user rates a particular video at a particular time. One user can rate the same video multiple times . You also need to record the information of performers in the videos. They are identified by id, name, age, and whether they are actors or actresses Each video gets a MPAA certification [Motion Picture Association of America] Each certification has a unique name and content rating. E.g. "PG-13" rating means that some content may be inappropriate for children under the age of 13. Here the name of the certification would be PG-13, and content rating would be Inappropriate for children under the age of 13' . Each user is identified by id and has name, gender, age, and location .There is also the social network between users. Users can send 'friend-requests' to other users. Such requests can be accepted or ignored. Once accepted, the two users are considered 'friends'. If ignore, the user can send the request again. We want to additionally store when the requests were sent (timestamp), the result of the requests and when the request was answered (timestamp)