DATABASE

M MYSTIQUE
( A CLOTHING BRAND)

M. IBRAHIM BSCS23165
MAIRA FATIMA BSCS23149
 DESCRIPTION
THIS PROJECT AIMS TO DEVELOP A COMPREHENSIVE DATABASE SYSTEM FOR A
CLOTHING STORE THAT MANAGES INVENTORY, CUSTOMER DATA, SALES, AND ORDER
PROCESSING.
THE DATABASE WILL STREAMLINE STORE OPERATIONS BY ALLOWING ADMINISTRATORS
TO MANAGE PRODUCTS, TRACK INVENTORY, PROCESS TRANSACTIONS, AND GENERATE
REPORTS. THE GOAL IS TO ENHANCE EFFICIENCY AND ENSURE SMOOTH DATA
HANDLING FOR BOTH ONLINE AND IN-STORE OPERATIONS.
THE SYSTEM WILL OFFER FUNCTIONALITIES SUCH AS:
• MANAGING CUSTOMER INFORMATION AND PURCHASE HISTORY.
• KEEPING TRACK OF PRODUCTS AND INVENTORY LEVELS.
• PROCESSING SALES AND ORDERS.
• GENERATING DAILY AND MONTHLY SALES REPORTS.
ERD:
 EXPLAINATION:
RELATIONSHIPS:
• CUSTOMERS ARE ASSOCIATED WITH ORDERS AND RENTALS, MEANING A CUSTOMER
CAN PLACE ORDERS OR RENT PRODUCTS.
• ORDER ITEMS REPRESENTS A MANY-TO-MANY RELATIONSHIP BETWEEN ORDERS AND
PRODUCTS.
• SALES CONNECTS EMPLOYEES AND ORDERS, INDICATING WHICH EMPLOYEE
HANDLED A PARTICULAR SALE.
• PRODUCTS ARE CATEGORIZED UNDER CATEGORIES, WHICH HELPS IN ORGANIZING
THE PRODUCTS.
• PROMOTION CAN BE APPLIED TO ORDERS, POTENTIALLY AFFECTING THE TOTAL
AMOUNT.
•Customers - Orders (One-to-Many): Each customer can place multiple orders, but each
order is linked to only one customer.
•Orders - Order Items (One-to-Many): Each order can have multiple products
(order items), but each order item belongs to one order.
•Products - Order Items (One-to-Many): Each product can appear in many orders, but
each order item refers to only one product.
•Products - Rentals (One-to-Many): Each product can be rented multiple times, but each
rental refers to a single product.
•Customers - Rentals (One-to-Many): Each customer can rent multiple products, but each
rental record is associated with only one customer.
•Orders - Sales (One-to-One): Each order corresponds to exactly one sale, and each sale
is linked to one order.
•Employees - Sales (One-to-Many): Each employee can handle multiple sales, but each
sale is processed by one employee.
•Employees - User (One-to-One): Each employee is linked to one user account, and vice
versa.
•Products - Categories (Many-to-One): Each product belongs to one category, but a
category can have many products.
•Promotion - Orders (One-to-Many, Optional): A promotion can be applied to many
orders, but not all orders have a promotion.
 EXPLANATION
4. Products
1. Customers product_id (PK): Unique identifier for each product.
customer_id (PK): Unique identifier for customers.
name: Product name.
name: Customer’s name. category_id (FK): Links to the category_id in the Categ
email: Customer’s email. table.
phone: Customer’s phone number. size: Size of the product.
address: Customer’s address. color: Color of the product.
2. Orders price: Price of the product.
order_id (PK): Unique identifier for each order.stock_quantity: Quantity of the product available in st
customer_id (FK): Links to the customer_id 5. Categories
in the Customers table. category_id (PK): Unique identifier for each product ca
order_date: Date and time when the order was placed.
category_name: Name of the category (e.g., electronic
status: Status of the order (e.g., pending, completed).
clothing).
total_amount: Total amount of the order. 6. Rentals
3. Order Items rental_id (PK): Unique identifier for each rental.
order_id (PK/FK): Refers to the order. customer_id (FK): Links to the customer_id in the Cust
product_id (PK/FK): Links to the product_id table.
in the Products table. product_id (FK): Links to the product_id in the Product
quantity: Quantity of the product in the order.rental_date: Date when the product was rented.
price: Price of the product in the order. return_date: Date when the product is expected to be
returned.
 9. User
 user_id (PK): Unique identifier for each system user.
 user_name: Username.
7. Sales
  password: User password.
sale_id (PK): Unique identifier for each sale.
  role: Role of the user (e.g., admin, employee).
employee_id (FK): Links to the employee_id in the Employees
table.  email: Email of the user.
 order_id (FK): Links to the order_id in the Orders table.  created_at: Timestamp of when the user was created.
 sale_date: Date of the sale. 10. Promotion
 total_amount: Total amount of the sale.  promotion_id (PK): Unique identifier for each
8. Employees promotion.
  description: Description of the promotion.
employee_id (PK): Unique identifier for each employee.
  start_date: Start date of the promotion.
user_id (FK): Links to the user_id in the User table.
  end_date: End date of the promotion.
name: Name of the employee.
  discount_percent: Percentage discount offered in the
contact_info: Employee contact information.
promotion
THANK YOU!