1 / 12

Database Project Sarah Summers

Database Project Sarah Summers. Goal: Create a web based software, music and book store. Software: Server Application: MySQL Apache Server PHP. Administrator Adds entries to db Deletes db entries Modifies db entries. User Searches book entries Searches music entries

sissy
Download Presentation

Database Project Sarah Summers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Database ProjectSarah Summers Goal: Create a web based software, music and book store. Software: Server Application: • MySQL Apache Server • PHP

  2. Administrator Adds entries to db Deletes db entries Modifies db entries User Searches book entries Searches music entries Searches software entries Add items to shopping cart Application Capabilities

  3. ER Diagram

  4. Administrators and Customers ER Diagrams

  5. Products ER Diagram

  6. Books and Authors ER Diagram

  7. Music and Artists ER Diagram

  8. Publishers and Software ER Diagrams

  9. Orders and Payments ER Diagrams

  10. Problems Encountered Original design did not include a product id number. Book, music and software entries all had their own identification numbers. This caused problems for the order entity, although each entry could be inserted using the individual identification numbers, this would lead to null values.

  11. Problems Encountered Wanted a user to register before being able to search. To register only need email, username and password. Problems arise when user purchases items and pays. Where is the customer address and payment method kept. Decided to keep additional customer details in the Payment relation.

  12. Conclusions • Database implementation can be complex. • Detailed design helps. • Implementation can still be problematic.

More Related