I need help with this project. The description is below, and very VERY basic diagrams of the ER Example and Normalized relations, part one and two are on there. I need complete help and would like the project completely finished. Please do parts 1-3 in full and have the project completed.

MIS331 Semester Project - Spring 2016 Your Assignment: Developing a database to fit the needs of an organization involves interpreting requirements, designing the database, and then implementing your design. To better prepare you for post-graduation work in MIS related fields, you will work through these processes during the course of this semester. Students are required to work independently. You will be given a business case and application requirements. All student will be given the same scenario and requirements, but each individual is expected to come up with his/her own interpretation of the requirements, and his/her own unique solution. Your Grade: Your overall project grade will be a combination of the following: Deliverable 1. Entity Relationship Diagram Grade 25 points max 2. Logical Database Design 25 points max Description Create and submit both a preliminary and an implementation entityrelationship diagram showing the conceptual data model for your system. Normalize the relations to at least third normal form. Due Date March 7 March 28 Identify the primary and foreign keys for each relation (using appropriate notation). Identify and describe referential integrity constraints needed to guarantee the integrity of your database - Explain your choices. Submit your normalized relations with the PKs, FKs, and constraints identified. 3. Database implementation 20 points max Define your database (1) Create the tables needed to implement your database (2) Define keys and indexes (3) Define the relationships among your tables. (4) Define any necessary referential integrity constraints between your tables. (5) Add sample data to the database tables (each table should have at least April 29 10 rows). (6) Perform SQL queries listed at the end of this document. 4. SQL 30 points max Submit all of the SQL code needed to perform the above operations. For the SQL queries, submit your code and the output generated. In-class Knowledge Assessment May 2 Business Case: MusicMash is a startup business specializing in online music sales. After receiving initial funding from investors, the founders of MusicMash are ready to start developing their online business. The owners are University of Arizona MIS graduates and know that the success of the business will depend on efficient and thorough data management. This means that the database behind MusicMash must be well designed and professionally implemented. The Business Environment MusicMash anticipates having 100,000 customers after the first year of operation. MusicMash needs to track as much information about customers as possible, including name, address, age, email address, credit card number, and sign-up date. Most competitors in the online music streaming market have at least 1 million songs in their inventory provided by roughly 50,000 artists. MusicMash knows it needs to have a similar sized music inventory to stay competitive. The music inventory is expected to grow by 5% each year. Therefore, it must be easy to add additional songs and artists. Data Overview: 1. A customer signs up to use the service by entering their name, address, age, email address, and credit card number. Sign-up ensures that customers always have a one-click option to purchase songs. Sign up does not imply that a customer has made a purchase. 2. After signing-up, customers can browse music by searching artist names, genre, or release date. 3. MusicMash must store the title, release date, genre, duration (length in seconds), and price of each song. Most songs in the MusicMash sales library belong to an album. However, in some cases, an artist releases a single song. In this case, there is no album associated with the song. For songs that do belong to an album, MusicMash must know the title and city where it was produced 4. MusicMash also stores a variety of information about each artist. This information includes name, age, home town/city, and current city of residence. An artist can create/produce many songs and albums, but songs are only associated with one artist. 5. Song purchases made by each customers must be carefully tracked including the date the music was purchased. If a customer wants all the songs on an album, they must purchase the songs individually. You are responsible for interpreting the information above and then designing and implementing a database that will work for MusicMash. Just like real-world scenario, the information provided is fairly vague. For example, address should not be designed as a single attribute, but rather split into street, city, state, and zip to ensure a variety of queries can be executed. It's up to you to determine what should be an entity, what should be an attribute, and how everything is related. SQL Queries 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. How many customers are currently in the database? How many songs fall into each of the music genres? List all attributes for artists currently living in Los Angeles. Find the average number of songs purchased by customers. For songs that belong to an album, list the album title, song name, and artist name. What customers have purchased music? Be sure to list each customer one time. List the customers over the age of 30 that have not ordered any music yet. Output a list of Song Names that are priced above the average of all other songs. What songs do not belong to an album? List all song purchases where the Artist of the song is from the same City as the Customer who purchased the song. Semester Project - Normalized Relations The set of relations below identify the most basic relations and attributes needed to maintain referential integrity for the MIS331 semester project: CUSTOMER(CUST_ID, ...) PURCHASES(CS_ID, CUST_ID, SONG_ID, ...) SONG(SONG_ID, ARTIST_ID, ALBUM_ID, ...) ARTIST(ARTIST_ID, ... ) ALBUM(ALBUM_ID, ARTIST_ID, ... ) Solid underlined attributes represent primary keys, and dashed underlined attributes represent foreign keys. This structure is needed to successfully execute the project SQL queries. Each relation is missing at least one attribute needed to complete the SQL queries. You must review the case study (including the SQL queries listed on the last page) and include any other necessary attributes in your database