COMP 3005: Database Management Systems (Due: Apr. 6, 2020 (11:59 PM))COMP3005 Project (Winter 2020)Instructor: Ahmed El-Roby1. Problem StatementDesign and implement an application for an online bookstore (Look Inna Book). This application lets usersbrowse a collection of books that are available in the bookstore. A user can search the bookstore by bookname, author name, ISBN, genre, etc.. When a book is selected, information on the author(s), genre, publisher,number of pages, price, etc. can be viewed. A user can select as many books as she likes to be added tothe checkout basket. A user needs to be registered in the bookstore to be able to checkout. When checkingout, the user inserts billing and shipping information (can be different than those used in registration), andcompletes the order. The bookstore has the feature of tracking an order via an order number. A user canuse this order number to track where the order is currently. Although shipping is carried out by a third-partyshipping service, the online bookstore should have the tracking information available for when the user inquiresabout an order using the order number. Assume all books are shipped from only one warehouse (no multipleorder numbers for multiple books shipped from multiple warehouses). The bookstore owners can add new booksto their collections, or remove books from their store. They also need to store information on the publishersof books such as name, address, email address, phone number(s), banking account. The banking account forpublishers is used to transfer a percentage of the sales of books published by these publishers. This percentageis variable and changes from one book to another. The owners should have access to reports that show salesvs. expenditures, sales per genres, sales per author, etc.. The application should also be able to automaticallyplace orders for new books if the remaining quantity is less than a given threshold (e.g., 10 books). This is doneby sending an email to the publisher of the limited books to order a number of books equal to how many bookswere sold in the previous month (you do not have to implement the email sending component).2. Project ReportYou need to submit one report file that contains the following sections. You can add other sections, but thefollowing sections (except Bonus Features) must be in the report:2.1. Conceptual DesignThis section should explain the conceptual design of the database. That is, the ER-diagram of the databasefor the bookstore and explanation of all the assumptions made in the diagram regarding cardinalities andparticipation types. Make sure that the assumptions do not contradict with the problem statement in Section 1.2.2. Reduction to Relation SchemasReduce your ER-diagram into relation schemas and list these in this section.2.3. Normalization of Relation SchemasThis section should show that your relation schemas are either in a good normal form (show tests), or if theyare not, show how to decompose them into a good normal form (show decomposition work), then show thetesting work to make sure that they are in a good normal form.2.4. Database Schema DiagramThis section should show the final schema diagram for the database of the bookstore. This diagram should besimilar to the schema diagram of the university database that we study in this course.1– COMP3005 Project (Winter 2020) 22.代写COMP 3005作业、代写Database作业、SQL语言作业代做、SQL程序设计作业调试 代写R语言编程|代做P5. ImplementationFeel free to use whichever programming language(s) for your application. Your application can be a web-basedapplication, or a desktop application. In this section, you should describe the architecture of your application.That is, what the modules in your application are and how they interact. You are encouraged to includea diagram of the application’s architecture and explain (in text) scenarios of using the application and theworkflow of your application.Your application should have two different user interfaces: The first is for the users of the application throughwhich the user can browse and buy books. The second is for the bookstore owners/managers through whichthey can add/remove books, display reports, etc. (more details about the application’s features can be foundin Section 1).Include screenshots of your application’s two interfaces in different scenarios (e.g., checking out, displayinga report, etc.).2.6. Bonus Features (Optional Section)You are free to add bonus features to your online bookstore. You will be rewarded bonus marks for thesefeatures. The choice of bonus features is entirely up to you. An example of a bonus feature is approximatesearch for books. For example, when the user searches for “The Lord of The Rings”, the user would find multiplematches “The Lord of The Rings: The Fellowship of the Ring”, “The Lord of The Rings: The Two Towers”,“The Lord of The Rings: The Return of the King”, “Lord of Flies”, etc., assuming that these were the titles ofthe books in the database. Note that this approximate match is not limited to matching prefixes only. Anotherexample of a bonus feature would be to show similar books (e.g., other books by the same author, or otherbooks with the same genre). The latter feature is a good example of using views.2.7. GitHub RepositoryAll your source code for your application should be uploaded to a public GitHub repository. The GitHubrepository should also include a directory titled “SQL” that includes all the SQL DDL statements and SQLqueries used in your application. You can organize the files in this directory in whichever way you would like. Butall the files should have the .sql extension. For example, the directory “SQL” could have four files “DDL.sql”,“Functions.sql”, “Triggers.sql”, and “Queries.sql”. The files should be well-documented using comments in SQL(e.g., purpose of trigger, what a query retrieves from the database, etc.). This section should include the url tothis GitHub repository.2.8. Appendix IThis section should include your availability (from 9 am to 5 pm) for a 20 minutes demosntration of your workon April 7th. Please list at least three time slots. Please see the instructions in Section 3.3. Instructions for SubmissionPlease follow these instructions in your submission:• Submit your project report as one pdf file.• Make sure that your GitHub repository is public.• The due date (April 6th) is a hard deadline. No submissions will be accepted after the deadline. It isyour responsibility to guarantee there is a version of your report uploaded before the due date. If there isno submission after the due date, you will receive no marks for the project.• Some students will be randomly selected to demonstrate their work one day after the due date (i.e., onApril 7th). It is your responsibility to make sure that your system is working properly.转自：http://www.daixie0.com/contents/15/4920.html
