Beatlesque Records (BR) is a recording company and its executives have decided to store information about musicians who perform on its albums (as well as other company data) in a database. They want you to create a database and your first job is to listen to their requirements and create a conceptual schema. Following are their requirements: Each musician that records at BR has an SSN, a name (first name, middle initial, last name, and one or more stage names), an address, and a phone number. Poorly paid musicians often share the same address, and no address has more than one phone. Each instrument that is used in songs recorded at BR has a name (e.g., guitar, synthesizer, flute) and a musical key (e.g., C, B-flat, E-flat). Each album that is recorded on the BR label has a title, a copyright date, a format (e.g., CD or MC), and an album identifier. Each song recorded at BR has a title and an author. Musicians may play many instruments, and a given instrument may be played by more than one musicians. Each album has a number of songs on it, but no song may appear on more than one album. Each song is performed by one or more musicians, and a musician may perform a number of songs. Each album has exactly one musician who acts as its producer. A musician can of course produce several albums. (a) Design a conceptual schema for BR and draw an ER (or EER) diagram for your schema. Indicate all key and cardinality constraints and any assumptions that you make. Identify any constraints that you are unable to capture in the ER diagram and briefly explain why you could not express them. (b) Create a relational schema for the BR company database by mapping the (E)ER diagram you created in (a).