Scribd
Upload
9 views9 pages

OTSST

The document outlines the database design for an e-commerce system, detailing the requirement analysis, conceptual design, logical design, and physical design. It identifies key entities such as Customer, Product, Order, and Payment, along with their relationships and attributes. Additionally, it discusses indexing, partitioning, and storage solutions for efficient data management.

Uploaded by

goodbyeacc7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
9 views9 pages

OTSST

The document outlines the database design for an e-commerce system, detailing the requirement analysis, conceptual design, logical design, and physical design. It identifies key entities such as Customer, Product, Order, and Payment, along with their relationships and attributes. Additionally, it discusses indexing, partitioning, and storage solutions for efficient data management.

Uploaded by

goodbyeacc7
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 9

Home About Contact

GROUP 5

E-COMMERCE
DATABASE DESIGN
Home About Contact

REQUIREMENT ANALYSIS
Users:

Customer
Administrators Purpose:

Store product and Customer information


Process orders and payments
Needs: Track inventory and deliveries

Customers: Browse product, place orders, make payment,


and track orders.
Admin: Manage products, track orders, generate sales
report.
Home About Contact

CONCEPTUAL DESIGN
Entities:

Customer, Product, Category, Order and Payment

Relationships:

Customer PLACES an Order


Order CONTAINS Products
Product HAS Category
Customer MAKES a Payment
Home About Contact

CONCEPTUAL DESIGN
ADDRESS TOTAL AMOUNT

PHONE EMAIL ORDER DATE STATUS

NAME CUSTOMER ID ORDER ID CUSTOMER ID

CUSTOMER PLACES ORDER

NAME

MAKES CONTAINS HAS CATEGORY CATEGORY ID

DESCRIPTION

PAYMENT PRODUCT
PAYMENT ID ORDER ID PRODUCT ID NAME

PAYMENT DATE AMOUNT PRICE STOCK

METHOD CATEGORY ID
Home About Contact

LOGICAL DESIGN
Relationship Schema:

Customer (CustomerID, Name, Email, Phone, Address)

Product (ProductID, Name, Price, Stock, CategoryID)

Category (CategoryID, Name, Description)

Order (OrderID, CustomerID, OrderDate, Status, TotalAmount)

Payment (PaymentID, OrderID, PaymentDate, Amount, Method)


Home About Contact

LOGICAL DESIGN

DATABASE

CATEGORY CUSTOMER ORDER

PRODUCT PAYMENT
Home About Contact

PHYSICAL DESIGN
Indexing:

Create indexes on CustomerID, ProductID, OrderID, and


CategoryID for faster data retrieval Partitioning:

Use partitioning for large dataset


> Order table can be partitioned by orderDate
Storage: > Product table can be partitioned by CategoryID

Use SSDs for faster write / read operations


Home About Contact

PHYSICAL DESIGN
PRODUCT CATEGORY
ProductID Int PK CategorytID Int PK
Name varchar (50) Name varchar (50)
Price Int Description varchar (50)
Stock Int PAYMENT
CategoryID Int FK
PaymentD Int PK
OrderID Int FK
PaymentDate Date
Amount Int
CUSTOMER ORDER Method varchar (20)
CustomerID Int PK OrderID Int PK
Name varchar (50) CustomerID Int FK
Email varchar (50) Orderdate Date
Phone Int Status varchar (20)
Address varchar (50) TotalAmount Int
Home About Contact

LABYO

THANK YOU
Presented by GROUP 5

You might also like