[Q.3] Design and create a MusicStore database for developing application for selling music files to the customers in the Internet environment. . Data Requirements: Note: for this question, we do not need to have actual music files, but a music file name must be unique. You can make reasonable assumptions about the data requirements described below. Each customer must have a customerId (we assume that the customer already registered for the web music delivery service), an email address, first name, last name, street address, city, state, zip code, and a phone number). Each product (i.e., music file) must have a productId, unique name, artist name (who played the music), and unit price. Each customer can have one or more music file downloads. Same music file can be downloaded one or more times for the customer and for her/his friends. After music files are downloaded by a customer, the customer must pay the total amount of the downloaded (i.e., purchased) music files by a credit card. Valid card types are VI (visa), AX (American Express), and CA (Master Card). Each music file download must be identified by a filename (or fileId if you use unique fileId as a primary key), download date and time. The music store needs to keep each customer's purchase history. 2. Map the conceptual MusicStore database schema to logical database schema. The logical database schema must show referential constraints by drawing an arrow that connects a foreign key column of a referencing table to a primary key column of the referenced table