BUILD YOUR OWN MUSIC STORE Build a virtual music store (a sort of non-free mp3.com). These are the steps: 1. Model entities such as songs, songwriters, singers, styles, prices recording studio, etc... Create a schema and an E/R diagram representing your database. Create useful and meaningful relationships between the relations (for example one relation is between songs and singers). Also describe any constraints you want to have on your schema (referential integrity constraints, functional dependencies, etc...) 2. Transform your E/R diagram into SQL syntax and create a "real" database in SQL Server using your model. 3. Populate your database. You can either use "synthetic" data or download a list of "real" songs and populate your database. You should have at least 25 songs in the database. If you choose to use synthetic data, please use meaningful names and entries. 4. Create another table(s) storing customers along with their VISA and M/C card numbers and other relevant information. Create meaningful relationships between customers and songs, songwriters, etc... 5. Create a WEB portal to your database. Songs should be able to be found using titles, songwriters, singers. Once a search has completed, a web page should be created summarizing the results of the search. Also for each song in the summary, there is a link that the user can click on to expand the information about the respective song. 6. Add e-commerce functionality to your website. Let a user be able to "rent" a song from your database. Each buyer needs to be able to order his song, and fill in his credit card information. (Do not worry about security issues). Store the credit card information in your database, so that a user does not have to enter this information more than once. However, allow the user to modify his credit card information. In exchange for their payment users are allowed to download a song. Later users "return" a given song, i.e. they agree to erase the song from their disk (you cannot enforce that, but we will trust users in this project). For each song you have purchased a certain number of "copies" from the recording studio: you cannot rent more copies of that song than you have originally purchased. 7. Export your database in XML. Design an XML DTD that contains elements and/or attributes corresponding to the entities in your database, such as songwriters, singers, styles, etc, and write a program that exports the entire database into an XML format with that DTD. BONUS: If a user is searching for a song you don't have in stock, your database application should go to buy.com (http://www.us.buy.com/retail/list.asp?loc=6756), search for the respective song and singer and add it to your database. Assume that you buy 10 copies of that CD and charge 7% of your price whenever you rent a song. For example the following URL retrieves Glass' "Einstein on the Beach": http://www.us.buy.com/retail/searchresults.asp?search_store=6&qu=glass+einstein+on+the+beach NOTE: Do not make your schema too complex: the entire project should contain at most 3-4 entity sets plus relationships.