Design a database that can be used to keep track of various aspects of a TV show streaming service:

mapping guidelines is the step of Mapping:

1. Mapping of Weak Entity Types

2. Mapping of Binary 1:1 Relationship Types

3. Mapping of Binary 1:NRelationship Types

4. Mapping of Binary M:NRelationship Types

1) Design a database that can be used to keep track of various aspects of a TV show streaming service: Each TV show has a unique name, a rating (1-10), and a set of producers. A TV show may have multiple (i.e. zero or more) seasons, and for each season we keep track of the season number and the release date. A season consists of multiple (i.e. zero or more) episodes. For each episode, we store its number within the season, and the length. An actor has a unique name and we keep track of the date of birth. Each actor may play a character in an episode, and, in that case, we store the name of the character played by the actor. For each user of the streaming service, we store a unique user ID and a credit card number. A user can add TV shows to the user's wish list. We associate each TV show with one genre, which has a unique name (e.g., drama, thriller, etc) and a description. The service provides the option for each user to subscribe to any number of genres. Design an ER diagram that models the above aspects of the streaming service. Make sure to identify weak entities and annotate the cardinality of the relationships between entities. You must state any additional assumptions that you make. [30 marks] 2. Convert your ER diagram into a relational schema using the mapping guidelines discussed in the lecture. For each relation (i.e. table) obtained, specify the name and its attributes, as well as the primary key and foreign keys (if any). [20 marks] 1) Design a database that can be used to keep track of various aspects of a TV show streaming service: Each TV show has a unique name, a rating (1-10), and a set of producers. A TV show may have multiple (i.e. zero or more) seasons, and for each season we keep track of the season number and the release date. A season consists of multiple (i.e. zero or more) episodes. For each episode, we store its number within the season, and the length. An actor has a unique name and we keep track of the date of birth. Each actor may play a character in an episode, and, in that case, we store the name of the character played by the actor. For each user of the streaming service, we store a unique user ID and a credit card number. A user can add TV shows to the user's wish list. We associate each TV show with one genre, which has a unique name (e.g., drama, thriller, etc) and a description. The service provides the option for each user to subscribe to any number of genres. Design an ER diagram that models the above aspects of the streaming service. Make sure to identify weak entities and annotate the cardinality of the relationships between entities. You must state any additional assumptions that you make. [30 marks] 2. Convert your ER diagram into a relational schema using the mapping guidelines discussed in the lecture. For each relation (i.e. table) obtained, specify the name and its attributes, as well as the primary key and foreign keys (if any). [20 marks]