The music database stores details of a personal music library, and could 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. The following is a list of requirements: i) The collection consists of albums; ii) An album is made by exactly one artist. There must be an artist and album; iii) An artist makes one or more albums (identifying relations); iv) An album contains one or more tracks; v) Artists, albums, and tracks each have a name; vi) Each track is on exactly one album. Vii) Each track has a time length, measured in seconds. The track may or may not be played and can be played as many times as required (non-identifying relations).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.

You are required to explain the purposes of the entity relationship diagram. You are then required to model the ERD strictly using crow foot notation based on the data provided. Include primary keys, connectivity, cardinality as well as relationship participation in your model. (20)
Where would the source of business rules come from in the above case. Identify business rules for the music database bank above. (5)
Explain the integrity rules for the music database above by pointing to actual examples in this music database. (5)