A personal music database stores details of a personal music library, and can be used to manage your MP3, CD, or vinyl collection. Because this database is for a personal collection, it’s relatively simple and stores only the relationships between artists, albums, and tracks.

Key requirements for the database:

The collection consists of albums.

An album is made by one or more artists.

An artist makes one or more albums.

An album contains one or more tracks

Artists, albums, and tracks each have a name.

Each track is on exactly one album.

Each track has a time length, measured in seconds.

When a track is played, the date and time the playback began (to the nearest second) should be recorded; this is used for reporting when a track was last played, as well as the number of times music by an artist, from an album, or a track has been played.

There’s no requirement to capture composers, group members or sidemen, recording date or location, the source media, or any other details of artists, albums, or tracks.

1.a) For the above problem, draw an entity relationship diagram with appropriate cardinalities (including lower and upper bounds) associated with the relationships. (20 points)

1.b) Based on the entity relationship diagram, create a relational model (in 3rd normal form). Identify any needed primary and foreign keys and draw the relationship lines between the specific attributes in each entity that are associated with the relationship.