A personal music database stores details of a personal music library, and can be used to manage your MP3, CD, or vinyl collectio
n. 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.
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.
1 answer:
Answer:
Check the explanation
Explanation:
Step 1: identify the entitles
From the statement given, the given entitles are artists, albums, tracks and played.
Step 2: identify the relationships
- One artist can make many albums
- One album can contain many tracks
- One track can be played many times.
Conversely, each play is associated with one track, a track is on one album, and an album is by one artist.
Step 3: identify the key attributes
The only strong entity in the database would be the “artist”, which has an attribute of artist ID so as to uniquely identifies it
Each album entity is uniquely identified by its album combined with the artist ID of the corresponding artist entity.
A track entity is similarly uniquely identified by its track ID combined with the related album ID and artist ID attributes.
The played entity is uniquely identified by a combination of its played time, and the related track ID attributes.
Step 4: identify other relevant attributes:
The attributes are straight forward; artist, albums, and track have names as well as identifiers to uniquely identify each entity. The track entity has a time attribute to solve the duration and the played entity has a timestamp to store when the track was played.
Step 5: Draw a complete ER diagram
The diagram explaining this question can be seen in the attached image below:
You might be interested in