Project report on

Online Shopping System

Submitted to

Department of Computer Science and Engineering

Nepal Engineering College

In Partial Fulfillment of the

Requirements for the Degree of B.E. in Computer

Submitted By:

Saphal Sapkota (020-382)

Date: 5/06/2024
Abstract
The Online Shopping is a web-based application intended for online retailers. The
main objective of this application is to make it interactive and its ease of use. It would
make searching, viewing and selection of a product easier. It contains a sophisticated
search engine for user's to search for products specific to their needs. The search
engine provides an easy and convenient way to search for products where a user can
Search for a product interactively and the search engine would refine the products
available based on the user’s input. The user can then view the complete specification
of each product. They can also view the product reviews and also write their own
reviews. The application also provides a drag and drop feature so that a user can add a
product to the shopping cart by dragging the item in to the shopping cart. The main
emphasis lies in providing a user-friendly search engine for effectively showing the
desired results and its drag and drop behavior.

[Keywords:]

i
Acknowledgement

The success of this project has been made possible by the valuable assistance of many
individuals. We must give due credit to all these individuals who have contributed so,
First, we must heartfully thank the Department of Computer Science and
Engineering, Nepal Engineering College for giving us this valuable opportunity to
undertake this project, with which we have learnt many skills of value. We would
especially like to extend our regards to Asst. Prof. Krishna Bikram Shah as our
project supervisor for his timely guidance as with his proper assistance we were able
to overcome our doubts.

Sincerely,

Sabin Sirmal (020-392)

Saphal Sapkota (020-382)

Umesh Adhikari (020-396)

ii
TABLE OF CONTENTS

Abstract........................................................................................................................i

Acknowledgement......................................................................................................ii

LIST OF FIGURES....................................................................................................v

Chapter 1- Introduction...............................................................................................1

1.1 Problem Statement.......................................................................................2

1.2 Objectives.....................................................................................................2

1.3 Aim...............................................................................................................3

1.4 Motivation....................................................................................................3

1.5 Scope............................................................................................................4

1.6 Application...................................................................................................4

1.7 Feasibility Study...........................................................................................5

1.7.1 Technical Feasibility:...........................................................................5

1.7.2 Operational Feasibility:........................................................................5

1.7.3 Economic Feasibility:..........................................................................5

1.7.4 Legal and Ethical Feasibility:..............................................................5

1.7.5 Schedule Feasibility:............................................................................5

iii
1.7.6 Market Feasibility:...............................................................................6

Chapter 2 - Literature review......................................................................................7

Chapter 3- System Design........................................................................................12

3.1 System Design................................................................................................12

Chapter 4 – Implementation and Discussion............................................................16

4.1 Task Completed..............................................................................................16

4.2 Task Remaining..............................................................................................16

Chapter 5 – Expected Output....................................................................................17

Chapter 6 – Conclusion.............................................................................................18

REFERENCES.........................................................................................................19

iv
LIST OF FIGURES
Figure 3.1: System Design...........................................................................................

Figure 3.2: Usecase diagram .......................................................................................

v
Chapter 1- Introduction
We all know that technology has become an essential tool for online marketing these
days. If we see all over the world most of the people are showing interest to buy
things in online. However, we can see that there are many small shops and grocery
stores are selling their things offline. With this type of selling most of us will face
bad experience. for instance, in some shops seller has the product to sell in the offer
but the buyer may not know about it, or the customer may need the product urgently
then he will go to the shop, but the product is out of stock, in that case, he will face
bad experience. Moreover, in online shopping customers can select a wide range of
products based upon their interests and their price also, one can compare prices also
from one store to another by using online shopping.

By encountering the all problems and weaknesses of the offline shopping system,
creating an E-commerce web application is necessary for searching and shopping in
each shop. These days we have seen so many e-commerce websites are created like
Flipkart, Amazon, Myntra one can easily buy their necessary products by using these
websites. By using these types of websites one can buy their products by staying in
their home. Eventually, we can see the difference between the prices of products also
as if we see the cost of the product will be slightly high in offline shopping when
compared to online shopping.

Online web stores, such as Amazon and eBay, have gained huge popularity over the
years because one can buy almost everything at these stores. These web stores also
give an opportunity to a lot of small-scale companies and manufactures to reach the
global market and to directly sell their products to people without involving different
other companies or middlemen before their product can reach the shelves of a
physical store. Further, instead of using the available platforms, manufacturers can

1
bring a concept of designing their own web store to sell their products directly to the
masses.

1.1 Problem Statement

The purpose of this project is to makes a web application which will be easier to find
interesting clothes and easier to sell goods. In This Online Shopping application
admin can add some categories like summer sales, winter festival, etc. which will by
attracting customers. Customers also can easily search for their favorite goods. They
can also buy them easily by just adding to the cart and they can increase or decrease
by clicking on the "+" sign and "-" sign. After adding they can check the total amount
of the thing which have been added to the cart. A successful payment gateway way
enabled so payment can be done by debit card, credit card, and net banking.

1.2 Objectives
1. Offer a User-Friendly Shopping Experience: The main goal of this online
shopping system project is to develop a platform that, by being simple to use and
intuitive, makes online purchasing easier for customers. This has a lot of
features, like easy-to-use product searches, straightforward checkout processes,
and straightforward navigation. Abstraction makes things easy for the user.
2. Secure Transactions: Implement robust security measures to protect client
information, financial data, and online transactions. This objective is crucial in
order to increase consumers self-assurance and perception of trustworthiness.
3. Effective Order Management: Make it easier for administrators to update stocks,
handle client data, and handle orders by streamlining the administrative
processes. Detailed User Documentation: To help users and administrators alike
comprehend and utilize the system efficiently, provide an in-depth user manual.

2
4. Scalability and Future-Proofing: Build the system with expansion and
improvements in mind, making it simple to include new features and
technological advancements as thee-commerce industry changes.
5. Quality Assurance and Testing: To find and fix any problems or faults in the
system and ensure a high-quality final result, do extensive testing, including unit
testing, integration testing, and user acceptability testing.
6. Customer happiness: The project's ultimate goal is to achieve high levels of
customer happiness by offering a simple and safe online shopping experience,
which promotes customer loyalty and repeat business.
By achieving these goals, the Online Shopping System project will improve the
satisfaction of customers, help the platform expand and survive in the fiercely
competitive online retail market, and assist the success of the e-commerce
industry

3
1.3 Aim
The aim of the Online Shopping System is to create a robust, user-friendly platform
that enhances the online shopping experience by offering a wide range of products,
seamless navigation, secure transactions, and efficient order management. The system
aims to cater to the needs of both customers and administrators, ensuring a
comprehensive e-commerce solution.

1.4 Motivation
The motivation for designing this shopping-cart application came because I love
online shopping rather than spending lot of time at physical markets. Further, using
the available stores to sell the products, there is also the possibility of designing one’s
own customized shopping-cart application from scratch because custom-designed
platforms are expensive. Moreover, I value recent learning about the Java and
JavaScript programming languages as well as seeing how powerful and dynamic they
are when it comes to web designing and applications. Apart from helping computer
science students understand the concepts of web-application designing, it would be
very easy to incorporate the idea of using programming techniques from the available
visuals to understand how a piece of code appears on a user interface

1.5 Scope
The scope of this report is to provide a comprehensive analysis of the online shopping
system, covering its functionality, architecture, user interactions, performance, and
non-functional requirements. The report aims to detail how the system supports
various user roles, including administrators, vendors/sellers, customers, sales
managers, purchase managers, accounts managers, and customer service
representatives. It also outlines the system's technical specifications, security
measures, reliability, availability, maintainability, and portability.

4
1.6 Application
The application of an online shopping system spans across various domains,
providing a versatile and efficient platform for conducting e-commerce transactions.
It enables customers to effortlessly browse, compare, and purchase a wide range of
products from the comfort of their homes, using a secure and user-friendly interface.
For vendors and sellers, the system offers comprehensive tools for product
management, inventory control, and promotional activities, facilitating seamless
integration with the online marketplace. Administrators benefit from robust
management features that allow them to oversee vendor activities, manage product
categories, and monitor sales and customer feedback. Additionally, the system
supports sales managers, purchase managers, and accounts managers by providing
functionalities to manage customer details, oversee stock levels, handle payment
transactions, and ensure smooth order fulfillment.

5
6
1.7 Feasibility Study

1.7.1 Technical Feasibility:

 Evaluate the technical requirements for developing the web application.

 Ensure the availability of skilled developers, necessary software, and hardware
resources.

1.7.2 Operational Feasibility:

 Assess potential users' willingness to adopt and adapt to the new application.
 Analyze how the project will integrate with existing systems and daily
operations.
 Identify training requirements for users and administrators.

1.7.3 Economic Feasibility:

 Estimate the development, implementation, and maintenance costs.

 Evaluate the potential benefits against the costs to determine the project's
financial viability.

1.7.4 Legal and Ethical Feasibility:

 Ensure the project complies with legal regulations and ethical standards.
 Implement measures to safeguard user data and ensure privacy.

1.7.5 Schedule Feasibility:

 Develop a realistic timeline for the project, considering development, testing,

and implementation phases.
 Identify potential dependencies and risks that could impact the project schedule.

7
1.7.6 Market Feasibility:

 Validate that the application meets the current and future needs of the college
community.

8
Chapter 2 – System Requirement
1.8 Overall Description
Product Perspective: This product is intended for those who don't want to visit the
store since they may not have the time or may not want to deal with the many
formalities involved in going there.

User: Administrator

•Functions: As the super user, the Administrator has total authority over every action
that may be taken. All requests for shops to be created are notified by the application
to the administrator, who has the option to accept or deny them. Additionally, the list
of possible product categories is managed by the administrator. Additionally, the
guest book entries can be viewed and removed by the administrator.

User: Shop Owner

•Functions: Through the program, any user can request the development of a shop.
The requester receives notification and is then assigned the role of Shop Owner once
the request is granted by the Administrator. The store owner is in charge of
organizing and maintaining the establishment. Managing the shop's item
subcategories is part of the job. The shop owner can also change the things that are in
his store. The store owner has access to various reports that include information on
orders and sales that are unique to his store. Additionally, the shop owner has the
option to close the store and take it down from the internet. User: Customer/Guests

• Functions: A Customer can browse through the shops and choose products to place
in a virtual shopping cart. The shopping cart details can be viewed and items can be
removed from the cart. To proceed with the purchase, the customer is prompted to
login. Also, the customer can modify personal profile information (such as phone
9
number and shipping address) stored by the application. The customer can also view
the status of any previous orders, and cancel any order that has not been shipped yet.
User: Employees

• Functions: Purchase department under a Purchase manager to overlook purchasing

activities if warehousing needs arise.

• Functions: Sales department under a Sales manager who will look after the sale of
products and services, the most important activity.

1.9 Performance Requirements

In order to maintain an acceptable speed, the maximum number of uploads allowed
from a particular customer will be any number of users can access the system at any
time. Also, connections to the servers will be based on the criteria of attributes of the
user like his location, and server will be working whole 24x7 times.

1.10Functional Requirements

Database management: Keep database control and keep track of all employee
and customer information records. This is the responsibility of the DBA (Database
Administrator). Reaching out to vendors and obtaining their consent: Get in contact
with the merchants and give them authorization to sell their products on the website
after evaluating the quality of the product. See every detail: Gain complete control
over the website and see each employee's details. In charge of making site
advertisements is Site Advertising

10
Customer:

Login: In order to use the site, users must have a working login ID.

Registration: New users can register by making a new ID. See and modify Own
Specifics: possesses the capacity to see and amend his service details, personal
information, and payment information.

Choosing and contrasting items: capable of comparing and evaluating every

product on offer and selecting the ones to purchase.

Buying: A valid credit card can be used to purchase any item. Giving Customer Care
input: Customer Care Service accepts input around-the-clock, able to share their
opinions regarding the website and services.

Logout: Users are advised to exit the website after completing a purchase.

This screen displays all the main categories from this point user can select any
category and they can proceed to select the products in this category.

Guests Accessing the Website: Access to the website is restricted to those who have
not registered. Register: If new to the site, register with your details for new account
to proceed with shopping.

Shop Owner:

Getting Administrator authorization: Vendors must have Administrator authority

in order to sell their products on the website. The administrator will assess the
product's quality in light of its going rate in order to grant the vendor permission to
sell it. Speaking with the Administrator: You can speak with the Administrator about
the caliber of the product and its advertisements. Product Promotion of Vendor Own

11
Products: The website won't be in charge of any other kind of product promotion; the
vendor is in responsibility of making product advertisements.

Sales Manager:

View client details: View the customer's personal information. Managing Sales to
Customers: This includes ensuring that the chosen product is appropriately allocated
based on the customer's preferences and that the product is delivered to the consumer.
View Product Stocks: For the purpose of selling, keep track of the stocks of each
product item.

Communicating with the Administrator: You must notify the administrator whenever
the supply of any product item falls below a certain threshold.

Purchase Manager:

Consulting with Administrator: Obtaining the Administrator's consent before making

a vendor purchase of the product. Product Stock Management: is charge of
overseeing the inventory of every product item.

Accounts Manager:

Regulating Payments: Maintain a record of each customer payment transaction and

update the payment details.

Consultation with Banks: Responsible for contacting banks to confirm the account
number provided by consumers for purchases and to carry out the transaction using
that account.

Speaking with the Administrator: Discuss the payment details of the clients with the
Administrator in order to update the database.

12
Customer Service: Receiving Customer Feedback: Answers questions, handles
concerns, and gathers customer feedback.

1.11Nonfunctional Requirements
In addition to the Non functional requirements are other requirements that don't
actually do anything, but that are critical nevertheless. Specify system characteristics
that are required for acceptance of the system by the end user.

Security

The system must automatically log out all customers after a period of inactivity. The
system’s back-end servers shall only be accessible to authenticated administrators.
Sensitive data will be encrypted before being sent over insecure connections like the
internet.

Reliability

The reliability of the overall program depends on the reliability of the separate
components. The main pillar of reliability of the system is the backup of the database
which is continuously maintained and updated to reflect the most recent changes.

Availability

The system should be available at all times, meaning the user can access it using a
web browser, only restricted by the downtime of the server on which the system runs.
In case of a hardware failure or database corruption, a replacement page will be
shown. Also, in case of a hardware failure or database corruption, backups of the
database should be retrieved from the server and saved by the administrator.

13
Maintainability

A commercial database is used for maintaining the database and the application
server takes care of the site. In case of a failure, a re-initialization of the program will
be done. Also, the software design is being done with modularity in mind so that
maintainability can be done efficiently

Portability

The application is HTML and scripting language-based. So the end-user part is fully
portable and any system using any web browser should be able to access the features
of the system, including any hardware platform that is available or the features of the
system, including any hardware platform that is available or will be available in the
future.

14
Chapter 3- System Design
3.1 Use-Case Diagram
3.1.1 Use-Case Diagram for Admin

fig3.1.1 Online Shopping Cart Application System Use-Case Diagram: Admin

15
3.1.2 Use-Case Diagram for User

fig3.1.2Online Shopping Cart Application System Use-Case Diagram: Admin

16
3.2 Activity Diagram
3.2.1 Activity Diagram for User

fig3.2.1 Activity Diagram for user side

17
3.2.2 Activity Diagram for Admin

fig3.2.2 Activity Diagram for admin side

18
3.3 DFD Diagram

3.3.1 Level-0 DFD

fig3.3.1 Level 0 DFD

3.3.2 Level-1 DFD For Admin

fig3.3.2 Level 1 DFD for Admin

19
3.3.3 Level-1 DFD For Customer

fig3.3.3 Level 1 DFD for Customer

20
3.4 E-R Diagram

fig3.4 E-R Diagram

21
3.4 State Machine Diagram

fig3.5 State Machine Diagram

22
23
Fig 3.1: System diagram

Explanation of system diagram:

The system diagram illustrate the flow of interaction within a platform. Initially,
anonymous visitors explore the system without logging in. Upon choosing to engage
further, users undergo authentication to access the system's features. Admins oversee
user management and content verification, ensuring system integrity. Teachers
contribute by uploading materials and interacting with existing content, while
students utilize these resources, providing ratings and feedback. Additionally, both
teachers and students can communicate through chat, facilitating further collaboration
and support within the platform. This structured process ensures efficient operation,
with each user playing a vital role in the system's functionality.

24
3.2 Use Case Diagram

Fig 3.2: use case diagram

25
Explanation of use case diagram:

The use case diagram shows the different things people can do in the system. There's
one block for admins, who manage users and content. Another block is for teachers,
who upload learning materials. Students have their block too, where they use the stuff
teachers upload, rate it, and give feedback. Then there's a block where users can view
profiles to know more about each other. Finally, teachers and students can chat
directly to talk about lessons and stuff. Each block represents a different job or task
people can do in the system.

26
Chapter 4 – Implementation and Discussion

Connect system architecture has two parts: the backend server and also the client-side
User Interface. The server's role is to issue authentication tokens and to serve as a
gateway to the central database to connect student and teacher by sharing different
kind of resources and communicating through personal chats.

4.1 Task Completed

1. Registration for admin and user (student and teacher).

2. Teacher’s dashboard and all the privileges.
3. Student and Teacher dashboard.
4. Content upload privileges.

4.2 Task Remaining

1. Chat system between teacher and student.

2. Validation process.

27
Chapter 5 – Expected Output

1. Seamless Connectivity and Idea Sharing: Establishment of a vibrant digital space

for students to connect and collaborate.
2. End-to-End Encrypted Personal Chat: Implementation of a secure end-to-end
encrypted personal chat system.
3. Student Portfolio Creation for Collaboration: Introduction of a feature enabling
students to create and showcase portfolios.
4. Comprehensive Teacher Information: Provision of a comprehensive database of
teacher profiles.
5. Accessible Study Materials and Resources: Curation and availability of a diverse
range of study materials and resources.
6. Bridging Resource Gaps: Mitigation of resource gaps through centralized access to
study materials.
7. Strengthened Student-Teacher Collaboration: Improved connections between
students and teachers through enhanced communication channels.
8. Informed Club Participation: Increased awareness and participation in student club
activities.
9. Holistic Community Building: Creation of a dynamic and interconnected academic
community within college

28
Chapter 6 – Conclusion
In conclusion, our project represents a transformative step towards redefining the
collegiate experience for students within a specific college. By addressing the
persistent challenges of resource scarcity, communication gaps, and fragmented
club activities, our application aims to create a cohesive, interconnected network
that fosters collaboration, innovation, and collective learning [2]. It has been a
great pleasure for me to work on this exciting and challenging project. This
project proved good for me as it provided practical knowledge of not only in
HTML, CSS and JavaScript web-based application and no some extent Windows
Application and SQL Server, but also about backend language PHP. It also
provides knowledge about the latest technology used in developing web enabled
application. This will provide better opportunities and guidance in future in
developing projects independently.

29
REFERENCES
[1] L.Aroyo et al., "Interoperability in Personalized Adaptive Learning," Journal of
Educational Technology & Society, vol. 9, no. 2, pp. 4–18, 2006.

[2] Aydin, C.C., & Tirkes, G. (2010). Open-source learning management systems in
e-learning and Moodle. In Proceedings of IEEE EDUCON 2010 - IEEE Engineering
Education 2010, Madrid, 14 16 April, 593 – 600.

[3] N. Geri, R. Gafni, and A. Winer, "The u-curve of e-learning: Course website and
online video use in blended and distance learning," Interdisciplinary Journal of E-
Learning and Learning Objects, vol. 10, no. 1, pp. 1-16, 2014.

[4] S.C. Chang and F.C. Tung, "An empirical investigation of students' behavioural intentions
to use the online learning course websites," British Journal of Educational Technology, vol.
39, no. 1, pp. 71-83, 2008.

30
31