A music streaming platform is constructing a database to track information about artists, albums, and songs:

$*$ The platform has many artists. Each artist has a unique ID$,$ a name, and a nationality.

$*$ An artist can release multiple albums. Each album has a unique ID$,$ a title, and a genre $($e$.$g$.,$ pop, rock, jazz$).$

$*$ Each album contains at least one song, and each song can only belong to one album. Each song has a title, an artist's name, and a unique song ID$.$

$*$ Artists can write songs. Artists do not collaborate on different albums and songs.

$*$ The platform allows users to leave reviews for songs. A review includes a rating $($e$.$g$.,4$ stars$)$ and a comment. Each user can write a review for many songs but will write at most once for the same song.

$*$ Each user has a unique user ID and a password. We also keep track of how many times a review has been written by each user..

Design an ER diagram for this application. Please do not introduce extra entities, attributes, or relationships beyond the description provided. $[30$ marks$]$

$2$For your ER diagram given above, convert it into a relational schema using the mapping guidelines discussed in the lecture. For each relation $($table$)$ obtained, specify the name and its attributes, as well as its primary key. $[20$ marks$]$