Problem Statement –

Problem Statement – Online Shopping Management System

Online shopping has become very popular due to the growth of the
internet. In traditional shopping, customers need to visit physical stores
which takes time and effort. Also, shop owners face difficulties in
managing products, orders, and customer records manually. To solve
these problems, an Online Shopping Management System is
developed. This system provides a digital platform where customers can
view products, place orders, and make payments easily. It also helps
administrators manage products, inventory, and customer data efficiently.

Main Problems :-

1. Time-consuming shopping process – Customers have to visit

physical stores to buy products.

2. Limited product information – Customers cannot easily compare

products and prices in offline shopping.

3. Manual record management – Shop owners often manage orders

and customer data manually which may lead to errors.

4. Difficulty in inventory management – Tracking stock and

product availability becomes difficult without a proper system.

5. Limited store accessibility – Physical stores are open only during

certain hours, while customers may want to shop anytime.

6. Inefficient order processing – Handling orders manually takes

more time and effort.

Purpose of the System

 To provide 24/7 online shopping facility to customers.

 To reduce manual work and improve efficiency.

 To manage products, customers, and orders in an organized

way.

 To provide a simple and user-friendly shopping platform.

Process Model
The process model describes the sequence of steps involved in the
development and working of the Online Shopping Management System. It
explains how the system processes user requests, manages data, and
completes transactions.

Steps in the Process Model

1. User Registration / Login

o The customer first registers on the website by providing

details like name, email, and password.

o If already registered, the user can log in using their

credentials.

2. Product Browsing

o After logging in, the customer can view different product

categories.

o The system displays product details such as price, description,

and availability.

3. Product Selection

o The customer selects the desired product.

o The product is added to the shopping cart.

4. Order Placement

o The customer reviews the cart and confirms the order.

o The system records the order details.

5. Payment Process

o The customer chooses a payment method (online payment or

cash on delivery).

o The system processes and confirms the payment.

6. Order Processing by Admin

o The administrator receives the order details.

o The admin verifies the order and updates the order status.

7. Product Delivery

o The product is shipped to the customer’s address.

o The system updates the delivery status.

 8. Order Completion

o The customer receives the product.

o The system stores the order history for future reference.

Simple Flow of Process Model

Customer Registration/Login → Browse Products → Add to Cart → Place

Order → Payment → Admin Processing → Delivery → Order Completion
Requirement Analysis
Requirement Analysis is the process of identifying and defining the needs
of users and the system before development. It explains what the system
should do and how it will handle the data and processes.

A. Functional Requirements
These are the functions that the system must perform.

1. User Registration and Login

o Customers should be able to create an account and log in

using username and password.

2. Product Management

o Admin can add, update, delete, and view products in the

system.

3. Product Search and View

o Users can browse products by category and view product

details like price and description.

4. Shopping Cart

o Customers can add products to the cart and remove products

if required.

5. Order Management

o Customers can place orders and view their order history.

6. Payment System

o The system should allow payment through different methods

such as online payment or cash on delivery.

7. Admin Control

o Admin can manage users, orders, and product inventory.

B. Non-Functional Requirements
1. Security

o User data and payment information should be secure.

 2. Reliability

o The system should work properly without frequent errors.

3. Performance

o The website should load quickly and process orders efficiently.

4. Usability

o The interface should be simple and user-friendly.

Data Flow Diagram (DFD)

Level 0 – Context Diagram
+----------------------+

| Online Shopping |

Customer --->| Management System |<--- Admin

+----------------------+

| |

| |

Order Info Product Update

Payment

Explanation
 Customer interacts with the system to view products and place
orders.

 Admin manages products and orders.

 Payment system processes the transaction.

Level 1 – Data Flow Diagram
Customer
|
v
+----------------+
| User Login |
+----------------+
|
v
+----------------+
| Browse Product |
+----------------+
|
v
+----------------+
| Add to Cart |
+----------------+
|
v
+----------------+
| Place Order |
+----------------+
|
v
+----------------+
| Payment System |
+----------------+
|
v
+----------------+
| Order Database |
+----------------+

Admin ----> Manage Products ----> Product Database

Data Dictionary
A Data Dictionary is a table that describes all the data
elements used in the system such as their name, type, and
description.
Data Element Type Description
Integ Unique identification number of the
User_ID
er user
User_Name String Name of the customer
Email String Email address of the user
Password String Password used for login
Integ
Product_ID Unique ID of the product
er
Product_Name String Name of the product
Product_Price Float Price of the product
Product_Catego
String Category of the product
ry
Integ Unique identification number for an
Order_ID
er order
Order_Date Date Date when the order is placed
Integ
Quantity Number of products ordered
er
Payment_Meth
String Method of payment (Online / COD)
od
Delivery_Addre Address where the product will be
String
ss delivered
Use Cases
A Use Case describes the interaction between the user and the
system.
Main Actors
 Customer
 Admin
Use Cases
1. User Registration
Actor: Customer
Description:
The customer creates an account by entering personal details
such as name, email, and password.
2. Login
Actor: Customer / Admin
Description:
Users log into the system using their username and password.
3. Browse Products
Actor: Customer
Description:
Customers can view different product categories and see
product details.
4. Add to Cart
Actor: Customer
Description:
Customers select products and add them to their shopping cart.
5. Place Order
Actor: Customer
Description:
Customers confirm their cart and place an order.
6. Make Payment
Actor: Customer
Description:
Customers select a payment method and complete the
payment.
7. Manage Products
Actor: Admin
Description:
Admin can add, update, or delete products in the system.
8. Manage Orders
Actor: Admin
Description:
Admin processes and updates order status.

3. Sequence Diagram – Online Shopping Management

System
A Sequence Diagram shows the interaction between objects
in a particular order.
Steps in Sequence Diagram
1. Customer logs into the system.
2. System verifies user details.
3. Customer browses products.
4. Customer selects product and adds it to cart.
5. Customer places the order.
6. System sends order details to the database.
7. Customer makes payment.
 8. System confirms the order.
9. Admin processes the order.
10. Product is delivered to the customer.

PROJECT MANAGEMENT
1. Timeline Chart (Project Schedule)
A Timeline Chart shows the schedule of activities required to
complete the project.
Phas Duratio
Activity
e n
1 Requirement Analysis Week 1
2 System Design Week 2
3 Database Design Week 3
Week 4–
4 Coding / Implementation
5
5 Testing Week 6
6 Documentation Week 7
Final Review and
7 Week 8
Submission
Simple Timeline Representation
Week 1 : Requirement Analysis
Week 2 : System Design
Week 3 : Database Design
Week 4-5 : Implementation
Week 6 : Testing
Week 7 : Documentation
Week 8 : Project Submission
2. Function Point (FP) Estimation
Function Point analysis is used to estimate the size and
complexity of software.
Coun Weig Tot
Component
t ht al
External Inputs (User login, order entry) 4 4 16
External Outputs (Order confirmation,
3 5 15
reports)
External Inquiries (Product search) 3 4 12
Internal Files (User database, product
2 10 20
database)
External Interface Files 1 7 7
Total Function Points = 70

3. Effort Estimation
Effort estimation shows how much work is required to complete
the project.
Formula:
Effort = Function Points × Productivity Factor
Assume productivity factor = 5 hours per FP
Effort =
70 × 5
Effort = 350 hours

4. Cost Estimation
Cost estimation determines the total cost required for the
project.
Assume developer cost = ₹200 per hour
Cost = Effort × Cost per hour
Cost =
350 × 200
Total Project Cost = ₹70,000

5. Risk Management Table

Risk Description Impact Solution
Technical Software bugs or System
Proper testing
Risk coding errors failure
Schedule Delay in Late
Proper planning
Risk development submission
Data theft or Loss of user Strong
Security Risk
hacking data authentication
Requirement Change in Clear requirement
Extra work
Risk requirements analysis
System Server or Service Backup and
Failure database crash interruption recovery system
Design Engineering
1. Architectural Design
Architectural design describes the overall structure of the
system and how different components interact with
each other.
The Online Shopping Management System follows a three-tier
architecture:
1. Presentation Layer (User Interface)
 This is the front end of the system.
 It allows users to interact with the website.
 Customers can register, login, browse products, and place
orders.
2. Application Layer (Business Logic)
 This layer processes user requests.
 It handles operations like product search, order
processing, and payment validation.
3. Data Layer (Database)
 This layer stores all the system data.
 It contains information about users, products, and orders.
Architecture Diagram (Text Representation)
Customer / Admin
|
v
+----------------------+
| User Interface |
| (Website / App) |
+----------------------+
|
 v
+----------------------+
| Application Logic |
| Product Management |
| Order Processing |
| Payment Handling |
+----------------------+
|
v
+----------------------+
| Database |
| Users |
| Products |
| Orders |
+----------------------+
2. Pseudocode for a Small Model
Pseudocode – Online Shopping Order Process
START

DISPLAY Login Page

INPUT username and password

IF user is valid THEN

DISPLAY product list
SELECT product

ADD product to cart

DISPLAY cart details

ASK user to confirm order

IF order confirmed THEN

SELECT payment method
PROCESS payment

IF payment successful THEN

STORE order in database
DISPLAY "Order Placed Successfully"
ELSE
DISPLAY "Payment Failed"
ENDIF
ENDIF

ELSE
DISPLAY "Invalid Login"
ENDIF

END

Python Code
# Online Shopping Management System - Simple Module

# Product List

products = {

1: {"name": "Laptop", "price": 50000},

2: {"name": "Mobile Phone", "price": 20000},

3: {"name": "Headphones", "price": 2000},

4: {"name": "Smart Watch", "price": 5000}

cart = []

# Login Module

username = input("Enter Username: ")

password = input("Enter Password: ")

if username == "admin" and password == "1234":

print("Login Successful\n")

print("Available Products:")

for key, value in [Link]():

print(key, value["name"], "Price:", value["price"])

choice = int(input("Select product number to add to cart: "))

if choice in products:

[Link](products[choice])

print("Product added to cart")

 print("\nYour Cart:")

total = 0

for item in cart:

print(item["name"], "-", item["price"])

total += item["price"]

print("Total Price =", total)

else:

print("Invalid Login")

Explanation of the Module

1. The system first asks the user to enter username and password.

2. If login details are correct, the system displays the product list.

3. The user selects a product.

4. The product is added to the shopping cart.

5. The system calculates and displays the total price.

Testing – Basis Path Testing

Basis Path Testing is a white-box testing technique used to ensure that
every possible path in the program is executed at least once. It helps in
identifying logical errors in the code.

1. Program Logic (Simplified)

Start
Input Username and Password
If Login is Valid
Display Products
Select Product
Confirm Order
If Payment Successful
Display Order Success
Else
Display Payment Failed
Else
Display Invalid Login
End

2. Control Flow Graph (CFG)

1 Start
2 Enter Login Details
3 Login Valid?
4 Display Products
5 Select Product
6 Confirm Order
7 Payment Successful?
8 Order Success
9 Payment Failed
10 Invalid Login
11 End

3. Independent Paths

The independent paths for the program are:

Path 1
1 → 2 → 3 → 10 → 11
(Login fails)
Path 2
1 → 2 → 3 → 4 → 5 → 6 → 7 → 8 → 11
(Login success + payment success)

Path 3
1 → 2 → 3 → 4 → 5 → 6 → 7 → 9 → 11
(Login success + payment failure)

4. Cyclomatic Complexity

Cyclomatic Complexity formula:

V(G) = E − N + 2

Where:
E = Number of edges
N = Number of nodes

Simplified result:

V(G) = 3

This means 3 independent paths must be tested.

5. Test Cases

Test
Input Expected Output
Case

TC1 Wrong username/password "Invalid Login"

Correct login + successful "Order Placed

TC2
payment Successfully"

Correct login + failed

TC3 "Payment Failed"
payment

6. Test Result

Test Resul
Case t

TC1 Pass

TC2 Pass

TC3 Pass
Test Resul
Case t

Conclusion – Online Shopping Management System

The Online Shopping Management System project was developed to

provide an efficient and user-friendly platform for buying and managing
products online. The system helps customers easily browse products, add
items to the cart, place orders, and make payments through an online
interface. At the same time, it allows the administrator to manage
products, customer information, and orders in an organized manner.

Through this project, important concepts of Software Engineering such

as requirement analysis, system design, data flow diagrams, testing, and
project management were applied. The system reduces manual work,
saves time, and improves the overall shopping experience for users.

The implementation of this project demonstrates how online systems can

improve business operations by making shopping more convenient, fast,
and accessible. In the future, the system can be further improved by
adding features such as mobile application support, product
recommendation systems, and real-time order tracking.

Overall, the Online Shopping Management System provides a simple

and effective solution for managing online shopping activities and
demonstrates the practical application of software engineering principles.

References
1. Roger S. Pressman, Software Engineering: A Practitioner’s
Approach, McGraw-Hill Education.

2. Ian Sommerville, Software Engineering, Pearson Education.

3. Pankaj Jalote, An Integrated Approach to Software Engineering,
Springer Publications.

4. K. K. Aggarwal and Yogesh Singh, Software Engineering, New

Age International Publishers.

5. Online resources and tutorials related to software engineering

concepts and online shopping systems.

6. Study material and lecture notes provided by University of Delhi –

[Link]. Physics (Hons.) Software Engineering course.