Speed Records board of directors have decided to store information about musicians who perform on its albums (as well as other company data) in a database. The board of directors company has hired you to design a database to store data for the following operations. The following are the requirements specified by the board of directors: Every musician who records at Speed has an SSN, a name, an address, and a phone number. Instruments used in songs recorded at Speed have a name (e. g., guitar, synthesizer, flute) and a musical key (e. g., C, B-flat, E-flat). Each album recorded on the Speed Records label has a title, a copyright date, a format (e.g., CD or MC), and an album identifier. Every song recorded has a title and an author. Musician may play several instruments, and a given instrument may be played by several musicians. An album has many songs on it, but no song may appear on more than one album. A song is performed by one or more musicians, and a musician may perform many songs. An album has exactly one musician who acts as its producer. A musician may produce several albums, of course. Artists, musicians who participates in promotional events for their songs must be known by speed records. Managerial board of speed records wants to know how much an album, song of the album was sold for and profit earned. With this information, do the following initial steps in your database design process: 1. Develop an ER diagram to represent the conceptual database scheme for the above "enterprise" 2. In the diagram, mark the various constraints (keys, cardinalities of the relationships, etc.) Identify any constraints that are not captured by the ER diagram. 3. Convert your ER diagram into a relational database scheme. Make refinements to your schemes, if possible Identify the primary keys and the foreign keys in the relational schemes, and hence not the referential integrity constraints in the scheme