question archive For Question 2) design an entity—relationship diagram that captures
Subject:Computer SciencePrice:2.86 Bought9
For Question 2) design an entity—relationship diagram that captures. as far as possible. the requirements stated below. If you make any assumptions in your design. please write them down. Assumptions. however, must not contradict the requirements. A database needs to be developed that keeps track of compact disks, and songs recorded on them, together with authors and performers of the songs. The data requirements are as follows: - For each disk, we want to store the disk ID, the title, and the year of production. Disk IDs are unique. - A song is recorded on some disk. It has a title and a number that indicates on which track it is recorded on the disk. For each disk, a song is uniquely identi?ed by its track number. - For each person that may occur as an author or a performer we want to store the person ID, the name, and the nationality. Person lD’s are unique. - Each song has at least one author who is a person. There are different types of authorship, e.g., composer, text writer, or arranger. For each author of a song, we want to store the type of authorship. - Each song has at least one performer who is a person. There are different instruments for a performer, e.g., voice, piano, violin. We want to store for each performerthe instrument they have played during the recording.

All of them are on one-is-to-many connections. Meaning to say, the primary key of one table could be used several times as reference to other tables (e.g. one song could be found on several disks and several disks may contain the same song). The RecordedOnDisk and SongAuthorPerformers tables serve as the relationships or connections of the entity of the entity.
Please see the attached file for the complete solution

