YURIM

Pioneering Digital
Dreams

Table of Contents

Entity Relationship Diagram

1

2 Business Component, Role, and

Purpose
Business Rules
3
Data Dictionary and Meta Data
4
 YURIM
Pioneering Digital
Dreams

Deliverables:
1. System Models
a. An Entity Relationship Diagram (ERD)
of the proposed system that
identifies key attributes and primary
relations.
b. Descriptions of each business
component, role, and purpose.
c. Business Rules
d. Data Dictionary, complete with
meta-data
 YURIM
Pioneering Digital
Dreams

1. Business Components, Roles, and Purposes

Customer

• Role: End-user of the platform.

• Purpose: To browse products, add products to cart, place order(s), make payment, and make
payment.

Order

Role: Representation of a customer's purchase.

Purpose: To capture the details of a purchase/Order made by a customer.

Payment

• Role: Financial transaction’s record.

• Purpose: To manage the financial aspects of orders, including payment processing and
tracking.

Location

• Role: Physical storage information of products in the storage area.

• Purpose: To identify and manage where products are stored within the storage area
(Refrigerators).

Product_Order

• Role: Junction entity for products in orders.

• Purpose: To link products with orders, managing quantities of products ordered.

Product

• Role: Item available for purchase.

• Purpose: To provide information about product(s), including description, pricing, and stock
availability.

Inventory_Track

• Role: Inventory management record.

• Purpose: To track inventory levels.

 YURIM
Pioneering Digital
Dreams

2. Business Rules

1. Customers can place an order only if the product is in stock.

2. A customer can buy one or more products.

3. A customer can have one or more orders.

4. An order is considered valid only after successful payment processing.

5. Inventory levels must be updated post every sale or Inventory updation.

6. Each order must have a payment record.

7. A product can be part of multiple orders.

8. Each order can contain multiple products

9. Each product must have a defined location in the storage area.

3. Data Dictionary and Metadata

Customer

• Customer_ID: Unique identifier for each customer - Integer - PK

• Customer_Info: Information including contact and demographic details - String

Order

• Order_ID: Integer - PK - Unique identifier for each order.

• Customer_ID: Integer - FK - Links to Customer.

• Product_ID: Integer - FK - Links to Product in ProductOrder.

Payment

• Pay_ID: Integer - PK - Unique identifier for each payment.

• Order_ID: Integer - FK - Links to Order.

• Pay_Info: String - Details of payment method and transaction.

 YURIM
Pioneering Digital
Dreams

Location

• Location_ID: Integer - PK - Unique identifier for each location.

• Product_Location: String - Physical location of the product.

Product_Order

• Product_ID: Integer - FK - Links to Product.

• Order_ID: Integer - FK - Links to Order.

• Quantity_Ordered: Integer - Number of units of the product ordered.

Product

• Product_ID: Integer - PK - Unique identifier for each product.

• Product_Info: String - Description and details of the product.

• Product_Quantity: Integer - Available quantity.

• Location_ID: Integer - FK – Unique Location Identifier.

InventoryTrack

• Inventory_ID: Integer - PK - Unique identifier for each inventory record.

• Product_ID: Integer - FK - Links to Product.

• Pre_Level: Integer - Inventory level before transaction.

• Post_Level: Integer - Inventory level after transaction.

• Quantity: Integer - Quantity of product in inventory.