Amazon E-commerce Database Design, Cheat Sheet of English

Download Amazon E-commerce Database Design and more Cheat Sheet English in PDF only on Docsity!

Sam Boozari

B

Database Planning: We have chosen amazon as our business website. Amazon is an e- commerce store which sells and let other sellers to sell their products world wide. Homepage Products Categories

proceed to checkout.

3. New sellers will also need to provide their details before they can sell anything on our platform.
4. Verified sellers however can sell their products easily as they have already submitted all the requirements. Objective 2. The internal user view of website would be the seller who is selling his/her products on our platform. External user view of our website is the end user / customer who will be buying products from our different sellers. Requirements Collection and Analysis

Use case Description: Use case New User byes a product Trigger event When user proceeds to checkout Description A new user comes to our website for the first time, searches for his/her favourite products and purchases them. Actors Customer, System Pre-condition  User must be registered.  User must be logged in. Post-condition User must have a valid payment method. Flow User will first arrive on our homepage and will search for the product he/she wants. When the user selects the product and add them to the cart after that he/she will move towards checkout. System will check if the user is registered or logged in or not. If the user is registered and logged in the system will proceed toward checkout and if not it will ask them to register first. Exceptional Path User is already registered and logged in. Use case New Seller sells a product Trigger event When a new seller sells his/her products on our website. Description A new seller comes to our website and sells his/her products Actors Seller, System Pre-condition  Seller must be registered.  Seller must be logged in.  Seller must be verified. Post-condition Seller must have products to sell. Flow When a seller first arrives on our website they will try to sell their products and system will check if the seller is verified or not and if he/she exists in the database. If not then the system will ask them to register first and get verified then sell their products. Exceptional Path Seller is already registered / logged in and is verified.

Logical Database Design Physical Database Design Field Name Description Data Type Size Accept Nulls? Role Example Tbl Categories Category_id Primary key of categories table int 5 n PK 1

Category_nam e Name of category varchar 50 n Winter cloths Category_type Type of category varchar 50 n cloths Tbl seller Seller_id Sellers primary id. int 5 n pk 1 Product_id Product id of products table int 5 n fk 1 name Name of the seller varchar 50 n John Tbl payment Payment_id Primary id of payments int 5 n pk 1 Category_id Primary id of categories table. int 5 n fk 1 date Date of payment date n 11/15/ Tbl Shopping Order Order_id Unique identifier of orders table int 5 n pk 2 Customer_id Unique identifier of customers table. int 5 n fk 2 date Date of shopping date n 10/5/ Tbl customer Customer_id Unique identifier of customer int n pk 1

table Order_id Unique identifier of order table int 5 n fk 4 Product_id Unique identifier of product table int 5 n fk 4 Payment_id Unique identifier of payment table int 5 n fk 4 Prototype – Database Implementation

Prototype - Useful Database Objects Triggers