Online BookShop Management System

Objectives

The objective of this system is to help manage a bookshop easily and efficiently by automating
book, customer, and sales records. It enables:

●​ Tracking books in stock.​

●​ Storing customer information.​

●​ Generating bills for sales.​

●​ Producing daily sales and stock reports.​

This reduces manual errors, saves time, and improves shop operations.

Procedure

The system starts when a user logs in with valid credentials.

●​ Admin: Adds, updates, or deletes book details (title, author, category, price, stock).​

●​ Sales Process: Customer requests a book, availability is checked, and a bill is generated.
The stock is updated automatically.​

●​ Customer Records: Stored for future reference.​

●​ Reports: Admin can view daily sales, stock levels, and profits.​

●​ Logout: Ends the session securely.

External Entities in Online bookshop management system

Entities

●​ Customer: Browses books, places orders, and makes payments.​

●​ Admin: Manages book catalogue and monitors orders/payments.​

Data Stores

1.​ Books Catalogue: Stores book details (title, author, price, stock).​

2.​ Process Order: Stores order information (book ID, customer info, quantity, status).​

3.​ Process Payment: Stores payment records (order ID, amount, method, status).​

Data Flows

●​ Customer → Books Catalogue: Search/browse request​

●​ Admin → Books Catalogue: Add/update/delete books​

●​ Customer → Process Order: Submit order​

●​ Admin → Process Order: View/manage orders​

●​ Customer → Process Payment: Submit payment​

●​ Admin → Process Payment: View payment status​

●​ Process Payment → Customer: Payment confirmation

DFD Level 0
DFD Level 1

Outputs and Implementation

DFD Level 0

This diagram presents the Online Bookshop System as a single unified process interacting with
two external entities — Customer and Admin. It highlights the primary operational flows, which
include customer login, order confirmation, admin updates, and reporting.

The Customer sends login requests and receives confirmations after transactions, while the
Admin interacts with the system for report generation and updates. The main purpose of this
level is to illustrate the overall communication between users (customers/admins) and the
central bookshop system.
Level 1

At this level, the system is decomposed into three core processes based on the detailed DFD:

1.​ Books Catalogue – Allows customers to search for and view books, add them to the cart,
and interact with stored book data (D1: Books). Admins can update book records directly.​

2.​ Process Order – Handles customer orders by checking the availability, storing them in D2:
Orders, and sending them for payment processing.​

3.​ Process Payment – Manages payment details, stores them in D3: Payments, and
confirms successful payment to both the customer and the order system.​

The database stores (Books, Orders, Payments) ensure that both the customer-facing and
admin-facing operations are backed by reliable data storage.

Output

Level 0:

●​ Diagram showing high-level interaction between:​

○​ Customer → Online Bookshop System → Admin​

Level 1:

●​ Diagram showing internal modules of the system:​

○​ Books Catalogue management​

○​ Order processing workflow​

○​ Payment handling​

○​ Database integration for Books, Orders, and Payments​

Analysis & Discussion

System Workflow:

1.​ The customer browses the book catalogue or searches for specific titles.​

2.​ Selected books are added to the cart and converted into an order stored in the Orders
database.​

3.​ Payment details are processed, stored, and confirmed.​

4.​ Admin updates book listings and manages inventory records.​

5.​ Payment confirmation triggers order status updates for the customer.​

6.​ Reports are generated for the admin, containing order and payment summaries.​

Efficiency:​
The system streamlines order handling and payment processing, reducing manual errors. It
ensures quick execution for book searches, cart management, order processing, and payment
confirmation.

Scalability:​
The architecture supports growth by allowing expansion of the book catalogue, customer base,
and payment methods without redesign. The central database design enables multiple admins
and potentially multiple store locations to operate seamlessly.

Security:​
Security measures include:

●​ User authentication for both customers and admins.​

●​ Controlled access to payment and order databases.​

●​ Data validation to prevent incorrect or incomplete entries.

Use Case Diagram

Actors:

●​ Guest User – Browse books, register.​

●​ Registered User – Search books, add to cart, place order, make payment.​

●​ Admin – Manage stock, orders, and reports.

ER Diagram

Entities: User, Book, Order, Payment, Supplier.​

Relationships: User places Order, Order contains Book, Payment is linked to Order, Supplier
provides Book.
Online Shopping System

Objectives​
The objective of this system is to efficiently manage an online shopping platform by automating
the handling of products, customers, sellers, and payment records. It allows for smooth tracking
of available stock, proper storage of seller and customer information, accurate bill generation for
purchases, and creation of daily reports covering sales, stock, and profits. By reducing manual
errors, saving time, and streamlining operations, the system ensures a better experience for
customers, sellers, and administrators alike.

Procedure​
The system begins when a customer, seller, or administrator logs in using valid credentials.
Sellers can add, update, or remove products from the catalogue, specifying details such as
name, category, price, stock quantity, and description. Customers browse through the available
products, add chosen items to their cart, and place orders, after which the system verifies stock
availability, updates the inventory, and generates a bill. All customer and seller transaction
records are stored for future reference, enabling the administrator to monitor activities. The
administrator can view and analyze daily reports containing sales performance, stock status,
profits, and seller activities to ensure smooth operation of the platform. Once tasks are
completed, users securely log out to end the session.

External Entities in Online Shopping System

Entities

●​ Customer/User – Browses products, places orders, and makes payments.​

●​ Seller – Manages product catalogue and handles order fulfillment.​

●​ Admin – Oversees platform operations, manages users/sellers, and monitors

transactions.​

Data Stores

●​ Product Catalogue – Stores product details (product ID, name, price, stock, seller info).​
 ●​ Order Records – Stores order information (order ID, customer info, product IDs, quantity,
status).​

●​ Payment Records – Stores payment data (order ID, amount, method, status).​

Data Flows

●​ Customer/User → Product Catalogue – Search/browse request.​

●​ Seller → Product Catalogue – Add/update/delete products.​

●​ Customer/User → Order Records – Submit order.​

●​ Seller → Order Records – View/manage orders.​

●​ Customer/User → Payment Records – Submit payment.​

●​ Seller → Payment Records – View payment status.​

●​ Admin → Product Catalogue – Manage product listings and seller accounts.​

●​ Admin → Order Records – Monitor order activities.​

●​ Admin → Payment Records – Monitor payment transactions.​

●​ Payment Records → Customer/User – Payment confirmation.​

DFD level 0
DFD level 1

​
​
​
Outputs and Implementation

Implementation

Level 0:​
This level represents the Online Shopping System as a single process interacting with three
external entities — Customer/User, Seller, and Admin. It depicts the major operational flows,
including product browsing, order placement, and payment processing.
Level 1:​
The system is broken down into three main processes:

1.​ Product Catalogue – Stores and manages product details such as product ID, name,
description, category, price, stock levels, and seller information. Customers can browse or
search products, sellers can add, update, or delete products, and admins can monitor and
manage product listings.​

2.​ Process Order – Handles all customer orders, including adding selected products to the
cart, confirming purchase requests, updating order status, and notifying sellers to fulfill the
orders. It maintains order records with details like customer information, product IDs,
quantities, and delivery status.​

3.​ Process Payment – Manages all payment transactions, including receiving payment details
from customers, verifying transaction success, updating payment status, and providing
confirmation to both customer and seller. It stores records such as order ID, payment
method, amount, and status.​

The core functionalities revolve around the integration of these three processes: Product
Catalogue ensures up-to-date product information, Process Order facilitates smooth purchase
operations, and Process Payment secures and confirms financial transactions.

Output

Level 0:

●​ Diagram illustrating high-level interaction between:​

Customer/User ↔ Online Shopping System ↔ Seller ↔ Admin​

Level 1:

●​ Diagram showing the three internal modules of the system:​

○​ Product Catalogue – Product browsing and management​

○​ Process Order – Order placement and tracking​

○​ Process Payment – Transaction handling and confirmation​

Analysis & Discussion

System Workflow:

1.​ Customer browses or searches the product catalogue.​

2.​ Customer places an order, which is stored in the process order records.​

3.​ The system checks stock availability from the seller’s inventory:​

○​ If available, the process moves to payment.​

○​ If unavailable, the seller updates the stock before the order proceeds.​

4.​ The customer completes payment, and the system records and confirms the transaction.​

5.​ Seller ships the order, and the order status is updated.​

6.​ Admin monitors system activities and generates reports on sales, stock, and performance.​

Efficiency:​
The automation of product browsing, order placement, and payment processing reduces
manual errors and speeds up operations, ensuring customers receive quick responses and
accurate information.

Scalability:​
The system can support a growing number of products, customers, and sellers, and can handle
expanding sales volume without sacrificing performance. It is designed for centralized data
management, enabling multiple sellers to operate simultaneously on the same platform.

Security:​
User authentication ensures secure access for customers, sellers, and admins. Payment data
is handled with secure protocols, and access to sensitive records is restricted to authorized
personnel only. Data validation ensures the integrity of all stored product, order, and payment
information.
Use Case Diagram:
ER Diagram:
Online Food Delivery System​
​
Objectives​
The objective of this system is to efficiently manage an online food delivery platform by
automating menu browsing, order processing, and payment handling. It allows customers to
quickly find and order food, enables restaurants to manage their menus and orders, and helps
delivery personnel fulfill deliveries efficiently. The system also provides administrators with tools
to monitor orders, payments, and performance, ensuring smooth operations. By reducing
manual errors, saving time, and centralizing all food ordering and delivery processes, the
system improves user satisfaction and operational efficiency.

Procedure​
The system begins when a user, restaurant, delivery person, or admin logs in with valid
credentials. Customers can browse the menu of participating restaurants, select desired items,
and place orders. The system sends these orders to the respective restaurants, which then
prepare the meals and update the status. Once an order is ready, a delivery person is assigned
to pick it up and deliver it to the customer. Payments are processed securely within the system,
and both the restaurant and customer receive confirmation. All order and payment records are
stored for future reference. The administrator can view daily reports on orders, payments, and
delivery activities to ensure everything runs smoothly. Once tasks are completed, each
participant logs out securely to end their session.​
​
​
External Entities in Online Food Delivery System

Entities

●​ User/Customer – Browses restaurant menus, places food orders, and makes payments.​

●​ Restaurant – Manages menu items and fulfills food orders.​

●​ Delivery Person – Picks up prepared orders from restaurants and delivers them to
customers.​

●​ Admin – Oversees platform operations, manages users/restaurants/delivery personnel,

and monitors transactions.​
Data Stores

●​ Menu Catalogue – Stores menu details (restaurant ID, food item name, category, price,
availability).​

●​ Orders – Stores order details (order ID, customer info, restaurant info, items, quantity,
status, delivery assignment).​

●​ Payments – Stores payment records (order ID, amount, method, status).​

Data Flows

●​ User/Customer → Menu Catalogue – Search/browse restaurant menu.​

●​ Restaurant → Menu Catalogue – Add/update/delete menu items.​

●​ User/Customer → Orders – Submit order request.​

●​ Restaurant → Orders – View/manage received orders.​

●​ Delivery Person → Orders – Update delivery status.​

●​ User/Customer → Payments – Submit payment.​

●​ Restaurant → Payments – View payment status for fulfilled orders.​

●​ Admin → Menu Catalogue – Manage restaurant menus and verify item listings.​

●​ Admin → Orders – Monitor and manage order activities.​

●​ Admin → Payments – Monitor payment transactions.​

●​ Payments → User/Customer – Send payment confirmation.

DFD level 0:

DFD level 1
Implementation and Output

Level 0:​
This level represents the Online Food Delivery System as a single process interacting with four
external entities — User/Customer, Restaurant, Delivery Person, and Admin. It covers the
primary operational flows: receiving menu browsing requests, processing food orders, and
handling payments.

Level 1:​
The system is divided into three main processes:

1.​ Process Menu – Stores and manages restaurant menus, including food items, categories,
prices, and availability. Customers browse menus, restaurants add or update food items,
and admins monitor menu details for accuracy.​

2.​ Manage Order – Handles order creation, restaurant notifications, preparation status
updates, delivery person assignment, and delivery tracking.​

3.​ Process Order & Payment – Records and processes all payment transactions linked to
orders, storing details such as order ID, amount, payment method, and transaction status.​

Output

Level 0:

●​ Diagram illustrating high-level interaction between:​

User/Customer ↔ Online Food Delivery System ↔ Restaurant ↔ Delivery Person ↔
Admin​

Level 1:

●​ Diagram showing three internal modules:​

○​ Process Menu – Menu browsing and management​

○​ Manage Order – Order placement, tracking, and delivery assignment​

○​ Process Order & Payment – Payment handling and confirmation​

Analysis & Discussion

System Workflow:

1.​ User browses the restaurant menu.​

2.​ User places an order, which is stored in the orders data store.​

3.​ The restaurant receives the order, prepares the food, and updates the status.​

4.​ The delivery person is assigned, picks up the order, and delivers it to the customer.​

5.​ The customer makes payment, which is recorded in the payments data store.​

6.​ Admin monitors and manages orders, menus, payments, and delivery operations.​

Efficiency:​
Automation of menu management, order processing, and payment handling reduces manual
work and speeds up operations. Customers receive real-time updates, restaurants get
immediate notifications, and delivery coordination is streamlined.

Scalability:​
The system supports multiple restaurants, thousands of customers, and a large network of
delivery personnel at the same time. Centralized data management ensures consistent and
up-to-date information across all processes.

Security:​
User authentication ensures secure access for customers, restaurants, delivery personnel, and
admins. Payment transactions are processed securely, and sensitive data is protected from
unauthorized access. Data validation ensures accurate menu, order, and payment records.
Use Case Diagram:
ER Diagram: