Tribhuvan University

Faculty of Humanities and Social Sciences

MULTI CUSTOMER ECOMMERCE USING

COSINE SIMILARITY RECOMMENDATION

PROJECT REPORT

Submitted to
Department of Computer Application
Xavier International College

In partial fulfillment of the requirements for the Bachelors in Computer Application

Submitted by
Pratik Khanal & Shreena Ranjit
October, 2023

Under the Supervision of

Mr. Amit Chaudhary
 Tribhuvan University
Faculty of Humanities and Social Sciences
Xavier International College

Supervisor’s Recommendation

I hereby recommend that this project prepared under my supervision by Pratik Khanal
& Shreena Ranjit entitled “Multi Customer Ecommerce” in partial fulfillment of the
requirements for the degree of Bachelor of Computer Application is recommended for
the final evaluation.

SUPERVISOR

Mr. Amit Chaudhary

Project Coordinator
Department of IT
xavier International College
Bouddha, Kathmandu

1
 Tribhuvan University
Faculty of Humanities and Social Sciences
xavier International College

LETTER OF APPROVAL
This is to certify that this project prepared by Pratik Khanal & Shreena Ranjit entitled
“Multi Customer Ecommerce” in partial fulfillment of the requirements for the
degree of Bachelor in Computer Application has been evaluated. In our opinion it is
satisfactory in the scope and quality as a project for the required degree.

SIGNATURE of Supervisor SIGNATURE of HOD/ Coordinator

Mr. Amit Chaudhary ER. Nipun Thapa

Project Coordinator Head of Department,
Department of IT Department of IT
xavier International College, xavier International College
Bouddha, kathmandu Bouddha, Gausala

Signature of Internal Examiner Signature of External Examiner

Department of IT
xavier International College,
Bouddha kathmandu

2
 ABSTRACT
The Multi-Customer E-Commerce project is an advanced web app that provides a
seamless online shopping experience for multiple users. It combines HTML, CSS, JS
for the front-end, .NET for the backend, ensuring secure shopping for both regular
and company users.

This project offers a feature-rich E-Commerce platform with an intuitive interface.

Customers can easily browse, search, and purchase products. The extensive catalog
showcases vendor offerings with detailed descriptions and advanced search options.
Shopping is easy with a user-friendly cart, secure checkout, and personalized accounts
for order management and tracking.

The admin panel offers control over accounts and transactions. Responsive design
ensures seamless shopping on all devices. Security is prioritized with encryption and
authentication for a safe environment.

3
 ACKNOWLEDGEMENT
My heartfelt appreciation goes out to our teachers, whose unwavering support and
constant guidance were instrumental in the successful completion of this project. I am
truly grateful for their valuable advice and mentorship, which played a vital role in
shaping our work.

I extend my sincere thanks to the college administration for their continuous

encouragement and assistance throughout this project. Their support provided us with
the necessary resources and conducive environment to excel in our endeavors.

A special word of thanks is reserved for Mr. Amit Chaudhary, the Project Coordinator
of our college, who provided us with invaluable guidelines and direction, leading us
on the right path to achieve our objectives.

I would like to express our gratitude to our parents and friends, whose unwavering
belief in me and valuable contributions during various phases of the project were truly
priceless. Their support motivated me to push my further and strive for excellence.

Lastly, I want to acknowledge the college administration and faculty members for
their trust in me, granting me access to essential facilities that played a significant role
in making this project a resounding success. Their cooperation and encouragement
were invaluable assets throughout this journey.

Sincerely,

Pratik Khanal & Shreena Ranjit

4
 Table of Contents
Supervisor’s Recommendation....................................................................................i
LETTER OF APPROVAL......................................................................................... ii
ABSTRACT..............................................................................................................iii
ACKNOWLEDGEMENT........................................................................................ iv
List of Tables...........................................................................................................viii
List of Figures.......................................................................................................... vii
List of Abbreviations.................................................................................................vi
Chapter 1: Introduction.................................................................................................. 1
1.1 Introduction.......................................................................................................... 1
1.4 Scope and Limitation............................................................................................2
1.5 Development Methodology..................................................................................3
1.6 Report Organization............................................................................................. 4
Chapter 2: Background Study and Literature Review................................................... 5
2.1 Background study.................................................................................................5
2.2 Literature Review................................................................................................. 5
Chapter 3: System Analysis and Design........................................................................ 7
3.1 System Analysis................................................................................................... 7
3.2 User Interface Design (UI Interface)..................................................................16
3.3 Algorithm........................................................................................................... 18
Chapter 4: Implementation and Testing....................................................................... 19
4.1 Implementation...................................................................................................19
4.2 Testing…………………………………………………………………………20
Chapter 5: Conclusion and Future Recommendation ………………………………..25
5.1 Conclusion……………………………………………………………………..25
5.2 Future Recommendation………………………………………………………25
References.................................................................................................................... 26

5
 List of Tables
Table 3.1: Use Case Login…………………………………………………….............8

Table 3.2: Use Case Add Product….…………………………………….……….…...8

Table 4.1: Description of Modules……………….………………………….……….20

Table 4.2: Unit testing……………………………………………………….……….21

Table 4.3: Test case for Purchasing Product…………….……………….….……….22

6
 List of Figures
Figure 1.1: Agile Model……...…………………………………………………….….3

Figure 3.1: Use Case Diagram……………………………...…………………………7

Figure 3.2: Gantt Chart……………………………………………………………….11

Figure 3.3: Conceptual Class Diagram…….………………………………...………12

Figure 3.4: Database Diagram……………...……………………...…………………13

Figure 3.5: Sequence Diagram….…………….…………………...…………………14

Figure 3.6: Activity Diagram….…………….…………………...…….………….…15

Figure3.7: UI of User Registration……………………………...………..………….16

Figure 3.8: UI of user Login…………………………….……………………..…….16

Figure3.9: UI of Dashboard……………………………...…………………………..16

Figure 3.10: UI of Product Detail…………………………….………………………16

Figure 3.10: Cosine Similarity ………………………………………………………18

Figure 4.1: Modules Implementation of Ecommerce System………………………..19

7
 List of Abbreviations
UI User Interface
MCE Multi Customer Ecommerce
SDLC System Development Life Cycle

8
 Chapter 1: Introduction
1.1 Introduction

Multi-Customer E-Commerce is a revolutionary concept that has transformed the way

people shop online. This cutting-edge web-based platform caters to multiple
customers creating a bustling virtual marketplace. The primary goal of
Multi-Customer E-Commerce is to provide an efficient, secure, and user-friendly
online shopping experience for customers. Leveraging modern web technologies such
as HTML, CSS, JavaScript for the front-end, and .NET for the backend, the platform
offers a seamless and engaging user interface. Customers benefit from an extensive
product catalog, advanced search options, and secure payment processing.
Personalized customer accounts allow users to manage their preferences and track
order history. Responsive design ensures a consistent shopping experience across
various devices. In conclusion, Multi-Customer E-Commerce represents the future of
online retail, catering to the evolving needs of both customers and vendors in a
dynamic digital marketplace.

1.2 Problem Statement

The E-Commerce project aims to tackle several significant challenges in order to

create a robust and user-friendly online shopping platform. One of the primary
objectives is to deliver an intuitive user experience that includes easy navigation,
quick product search, and a streamlined checkout process. Security is paramount, and
the platform must ensure the safeguarding of customer data and secure payment
processing. As the platform grows, scalability becomes crucial to handle increased
traffic and transaction volumes effectively. Moreover, providing efficient customer
support is essential for addressing customer queries and resolving issues promptly.
Seamless integration with various third-party services, such as payment gateways and
shipping providers, is also a priority. Mobile responsiveness is a must to cater to the
growing number of mobile shoppers. The project will also focus on optimizing order
fulfillment and logistics management for timely deliveries and enhanced customer
satisfaction.
By overcoming these challenges, the E-Commerce platform aims to provide a stellar
online shopping experience that meets the expectations of both customers and Seller.

1
The major problems that arise to this project are:
i. Fluctuation of network service.
ii. Some user may be illiterate and it would be hard for them to use the
system in a proper way.
iii. As the platform gains traction and attracts more customers, it must
handle increased traffic and transaction volumes. Scalability is essential
to maintain optimal performance during peak times.

1.3 Objectives

The main objectives of the projects are:

● To design a web based Multi Customer Ecommerce to fulfill requirements such as

viewing and making purchase of the product.
● To make a well-designed database to store product data.
● To develop a user friendly front-end for the user to interact with the system.

1.4 Scope and Limitation

The scope of an Multi Customer Ecommerce in DotNet can be vast and varied,
depending on the specific features and functionality desired. DotNet is a popular
open-source C# framework used for building web applications. It provides a clean and
elegant syntax while offering a wide range of features and tools that simplify the
development process.

1.4.1 Scope of the system

The scope of an Multi Customer Ecommerce is quite broad, as it involves providing a

platform that connects the vendor and customer. A Multi Customer Ecommerce can
offer a range of services and features designed to make the shopping experience a lot
better and smooth.

1.4.2 Limitations of Existing System

Some of the limitations are as follows:

2
 ● User Interface: Outdated or poorly designed user interfaces can make
navigation confusing and frustrating for users, resulting in decreased
engagement and conversion rates.

● Security Vulnerabilities: The existing system might have security loopholes or

outdated security protocols, making it vulnerable to potential data breaches or

unauthorized access, putting customer information at risk.

● Inefficient Order Management: Inadequate order processing and fulfillment
mechanisms can lead to delayed deliveries, order errors, and dissatisfied
customers.

1.5Development Methodology

Figure 1.1: Agile Model

The agile development model was chosen as the development technique for this
system because it allows for fast adaptation to changes in requirements without
delaying delivery deadlines. Agile also lowers technical debt, raises customer
happiness, and produces products of superior quality.

Here are some of the reasons why to choose agile development model:
● Easily and Quickly Adapt to Change
● Higher Quality Product

3
● Greater Customer Satisfaction
● Better Project Control
● Reduced risk

1.6 Report Organization

Chapter 1: Introduction

It describes about system, its objectives, scope and limitations as well.

Chapter 2: Background Study and Literature Review

It describes about the limitations of existing system and current trend of the
available similar systems.
Chapter 3: System Analysis and Design

It describes about the functional and non-functional requirements, feasibility

analysis, algorithm details etc.

Chapter 4: Implementation and Testing

This section describes tools used and other implementation details of modules
used.

Chapter 5: Conclusion and Future Recommendation

It describes about the outcome of this system and future recommendations of

this system.

1.5

4
 Chapter 2: Background Study and Literature Review

2.1 Background study

E-commerce, defined as the buying and selling of products or services through

electronic systems like the Internet, is gaining rapid acceptance as a prevalent
business model. Despite limited options for online bill payment and trading, the
emergence of new players like Paybill and Esewa aims to revolutionize the
e-commerce landscape. These services offer tremendous potential, enabling startups
to effortlessly sell their products and services online. With their advent, the
e-commerce industry is expected to witness significant transformation. Amidst these
newcomers, there are already well-established players known for their prowess in
money transfer and online shopping.

The project's objective is to develop a versatile e-commerce store capable of

facilitating the purchase of any product, ranging from books, CDs, computers, mobile
phones, electronic items, to home appliances, from the comfort of one's home through
the Internet. Although this project will focus on an online car store for implementation
purposes, the platform will be designed to accommodate diverse product offerings.

The online store functions as a virtual platform where customers can explore the
product catalog and select items of interest. The chosen products are collected in a
shopping cart, and upon checkout, the items are presented as an order. Additional
information, such as billing and shipping addresses, shipping options, and payment
details (like credit card numbers), may be required to complete the transaction.

The aim of this project is to create an efficient and user-friendly e-commerce

platform, making the process of online shopping increasingly common and accessible
to a broader audience.

2.2 Literature Review

E-commerce is booming in this internet age, outpacing the development of

brick-and-mortar firms by a wide margin. Often, brick and mortar businesses are
turning to the internet as a counterpart or based on e-commerce. Individuals in

5
industrialized nations and a rising number of people in the developing countries now
regularly conduct their business on e-commerce platforms. purchases. However, the
growth of e-commerce in impoverished countries is not so tremendous, and there is
much to be desired.[1]

Cosine similarity is valuable for data classification tasks, particularly in research

clustering. It assesses similarity between objects or documents by calculating the
cosine angle between their vectors. This method is crucial in text mining and natural
language processing, creating clusters of documents with similar content. Hierarchical
clustering algorithms can be developed using cosine similarity for a more nuanced
analysis. Overall, cosine similarity enhances efficiency and performance in
categorizing and understanding large datasets, benefiting fields like information
retrieval and recommendation systems.[2]

.NET is a robust Microsoft framework used for building E-Commerce applications. It

supports multiple languages like C#, VB, and F#, enabling developers to create
scalable and dynamic platforms. ASP.NET, part of .NET, simplifies web application
development with user-friendly interfaces. The framework ensures secure data
handling and seamless integration with third-party services like payment gateways. Its
scalability and performance optimization make it ideal for handling high traffic and
growth. With .NET, businesses can build efficient and competitive E-Commerce
platforms that meet modern consumer demands.[3]

E-commerce website success mode refers to the factors that drive effectiveness and
prosperity in online retail. Key components include user-friendly interfaces,
high-quality product presentation, mobile responsiveness, secure transactions,
effective marketing, and customer engagement. Data analytics aids in
decision-making, and continuous improvement ensures adaptation to customer needs.
Optimizing these elements creates a competitive advantage and fosters growth in the
E-commerce market.[4]

Online payment modes in E-commerce include credit and debit cards, digital wallets
(e.g., PayPal), bank transfers, mobile payments, cryptocurrencies, Buy Now, Pay
Later (BNPL) options, prepaid cards, and Cash on Delivery (COD). Integrating
multiple methods caters to various customer preferences and geographic locations.
Secure payment gateways ensure safe transactions and protect sensitive data.[5]

6
 Chapter 3: System Analysis and Design
3.1 System Analysis

Analysis specifies what the system should do. It is a problem-solving technique that
improves the system.
3.1.1 Requirement Analysis
It is the process used to determine the needs and expectation of the system.
i. Functional Requirements
Functional requirement is also called Functional Specification

Figure: 3.1 Use Case Diagram of Multi Customer Ecommerce

There are basically two roles in this system admin and user. Admin can manage the
overall performance of the system. Admin can perform basically any task like adding
products, managing user, proceeding the order and many more.

User can register and login the system. They will be redirected to home page where
they can view the products and also conduct a search operation. They are provided a
facility to add liked product to cart and proceed to summary of order page. Price of
the product also varies from the quantity amount. Payment is facilitated using
STRIPE in this project. Once the order is made, they are provided an order number
and they can also track the status of order. Normal customer is required to make

7
payment to confirm order but COMPANY USER can make order of goods and pay
bill within 30 days.

Table: 3.1 Login

Use Case UC -001

Identification
Use Case Name Log-In
Primary Actors Customer
Secondary Actors N/A
Description The system allows a customer to log in if registered. It
verifies the customer's userid and grants login access if
matched. If not registered, the system prompts the customer
to sign up before proceeding with login.
Preconditions The customer must have unique email.
The customer must be registered .

Post condition The customer has logged in into the system. The system has
(Success Condition) verified the password and username.

Failure The username or password is incorrect.

Table:3.2 Add Product

Use Case UC -002

Identification
Use Case Name Add Product
Actors Admin
Secondary Actors N/A
Description Allow Admin to login the system and add several category and
related products.

8
 Preconditions The Admin must have logged in .

Post condition The Admin has successfully added the product and those product
(Success Condition) are now available to be be displayed to customer.
Failure The add-product failed.

ii. Non-Functional Requirements

Nonfunctional requirements are the 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.
Some non-functional requirements of this project are listed below:
i. Availability:
The system is accessible 24/7, allowing users to access it through a web browser
at any time. However, in the unlikely event of a hardware failure or database
corruption, a replacement page will be displayed to notify users of the temporary
unavailability.
ii. Maintainability:
The system is designed with a modular approach, enabling the addition of
independent modules whenever required. This flexibility allows for seamless
expansion and customization as per changing needs. Furthermore, in the event of a
failure, the program will undergo re-initialization to ensure smooth operation. The
software design is being meticulously developed with modularity as a core
consideration, ensuring efficient maintainability and ease of updates in the future.
iii. Portability
The system is designed to be compatible with various hardware platforms, including
PCs and laptops. It is based on HTML and scripting languages, ensuring that the
end-user part is fully portable. As a result, any system equipped with a web browser
can access and utilize the system's features, regardless of the hardware platform in
use, both currently available and those that may emerge in the future. Additionally,
the system is OS-agnostic, allowing end-users to access it seamlessly on different
operating systems, be it Windows or Linux. This cross-platform compatibility ensures

9
widespread accessibility and usability of the system's features, catering to a diverse
user base.

iv External Interface Requirements

i. Hardware Interface:
ii. Hardware requirements for Insurance on internet will be same for both the
parties which are follows:
Processor: - intel i9 or above.
RAM: - 128 MB or above.
HD: - 20 GB or above.

iii. Software Interfaces:

Operating System: Linux, Windows etc.
Development Tool: HTML, CSS, JavaScript, C#
Data Base: MsSql

3.1.2 Feasibility Analysis

i. Technical Feasibility
Technical viability examines if the project's work can be completed with the
equipment, software, and staff currently on hand. In terms of technical viability, it is
important to identify hardware and software that will meet user needs. Additionally, it
examines the technical team's capacity to translate concepts into functional systems.

According to technological considerations, the suggested project "Multi Customer

Ecommerce" is possible. In terms of having new technological components placed on
the system, the proposed system is more advantageous. The suggested system may be
used on any platform that supports Windows and Internet services, although it
performs better on hardware and software that were considered while the system was
being designed so that it would be technically possible.

ii. Operational Feasibility

How successfully the system's requirements can be satisfied depends on operational
viability. It establishes the public's perception of the system. It gauges how urgent a
situation is or how acceptable a remedy is. The project's need for human resources

10
will rely on it. It concerns predicting how the system will function and be utilized
after installation.

Operationally, the "Multi Customer Ecommerce" project is possible. This project is

being built with the general public in mind, who while having very little computer
operating expertise can nevertheless readily access the databases they need and other
relevant information. As the system becomes a normalized database management
system, the redundancies may be reduced significantly.

iii. Schedule Feasibility

We planned to use the agile model with four to five iterations because our project is
small in scope and does not involve many parallel tasks. This will help ensure that the
phases of our project development life cycle are accurate and robust.

Figure: 3.2 Gantt chart of the Multi Customer Ecommerce

Although they are particularly helpful for streamlining large projects, Gantt charts are
a project management tool that aid in the planning and scheduling of projects of all
sizes. Timelines and tasks from project management are transformed into a horizontal
bar chart that displays the start and the percentage of the job that has been
accomplished at each step. When there is a large team and several stakeholders, this is
helpful to keep work on track when the scope changes.

11
3.1.3 Object Modelling
i. Class Diagram

Figure: 3.3 Descriptive Class Diagram of Multi Customer Ecommerce

In the above descriptive class diagram, there are various objects with their set of
attributes where each object identifies minimum attributes in order to describe the

12
object. User can view product and make an order where as admin can proceed them
and add products.

ii. Database Diagram

13
 Figure: 3.4 Database Diagram of Multi Customer Ecommerce

In the above figure, it is showing the database diagram of Multi Customer

Ecommerce.

14
3.1.4 Sequence Diagram

Figure: 3.5 Sequence Diagram of Multi Customer Ecommerce

In the above figure, it is showing the sequence diagram of Multi Customer
Ecommerce.

15
3.1.5 Activity Diagram

Figure: 3.6 System Flow Diagram of Multi Customer Ecommerce

The system flow diagram begins with the login of admin and customer. If the
customer is authenticated, then only the customer can login into the system and
perform further tasks. Similarly, admin also needs to login in order to perform various
tasks.

16
3.2 User Interface Design (UI Interface)

The interface design of system is shown as follows:

Figure 3.7: UI of User Registration

17
Figure 3.8: UI of user Login

Figure 3.9: UI of Dashboard

18
 Figure 3.10: UI of Product Detail

3.3 Algorithm

For recommending similar product to users, this system will use a cosine similarity
recommendation algorithm. It's a form of recommendation system that works on the
basis of content similarity. When a user searches for a product, the system looks for
other item with similar descriptions to the one the user is looking for and makes
recommendations. The similarity between the two products will be determined using
cosine similarity in this system. The data objects in a dataset are handled as a vector
in cosine similarity. The formula to find the cosine similarity between two vectors is:

Cos (x, y) = x. y / ||x|| * ||y||

where
● x. y = product (dot) of the vector’s ‘x’ and ‘y’.
● ||x|| and ||y|| = length of the two vectors ‘x’ and ‘y’.
● ||x|| * ||y|| = cross product of the two vectors ‘x’ and ‘y’.

19
Figure 3.10: Cosine Similarity

20
 Chapter 4: Implementation and Testing
4.1 Implementation

4.1.1 Tools Used

The tools used for the development of this project are:

i. Visual Studio: Visual Studio is an integrated development environment
(IDE) used for coding, debugging, and building software applications
across various platforms.
ii. Dotnet Core: .NET Core is a free, open-source, and cross-platform
framework developed by Microsoft for building modern applications.
iii. SQL server: SQL Server is designed to store, retrieve, and manage data
efficiently and securely, and it provides a wide range of features and tools
for database administrators and developers.
iv. Balsamiq: For user interface design to create wireframes
v. Visual Studio: It is an editor used which has wide range of functionalities
for programming.
vi. Draw.io: used for creating Gantt chart and other figures required.
4.1.2 Implementation details of modules

Figure 4.1: Modules Implementation of Ecommerce System

21
 Table 4.1: Description of Modules

Code Module name Arguments Return Type

M1 Login Email: string Boolean

Password: string

M2 Sign up Email: string Boolean

Password: string

Confirm Password: string

Phone no.: double

Address: string

M3 Purchasing Name: string Void

Phone no.: double

Address: string

Quantity: int

Price: double

Estimated Date: date

Total: double

M4 Payment Email: string Boolean

Card Number: int

Expiry Date: date

CCV: int

Amount: int

22
 Paid Date: date

4.2 Testing
4.2.1 Test Case for Unit Testing

Unit testing is a fundamental software testing technique that involves testing

individual units or components of a software application in isolation. The primary
goal of unit testing is to verify that each unit of the software functions as intended and
produces the correct output for a given set of inputs.

Table 4.2: Test case for Login

Project Name: Multi Customer Ecommerce

Test Case

Test Designed by: Pratik Khanal &

Test Case ID: TC_001
Shreena Ranjit

Test Priority (Low/Medium/High):

Test Designed date: 01-06-2023
Medium

Test Executed by: Pratik Khanal &

Module Name: Login
Shreena Ranjit

Test Title: Verify login Test Execution date: 20-06-2023

Description: Test the login functionality of MCE

Pre-conditions: User is already registered in the system.

Dependencies:

Test Status
Expected Not
Step Step Test Data Actual Result (Pass/Fa
Result e
s il)

23
 Navi As Expected,
gate i.e., User is
login page
1 to navigated to Pass
should open
login login page of
page MCE.

Enter
valid
Verified
usern [email protected]
credentials
2 ame Password=Custo As Excepted Pass
details are
and mer@123
entered
pass
word

Click
As Expected
on
User should i.e.
LOGI
3 click be able to User is able to Pass
N
login login in the
butto
MCE.
n

Post-conditions:
User is validated with database and successfully login to MCE system.

4.2.2 Test Case for System Testing

System testing is a software testing technique that focuses on evaluating the complete
and integrated system to ensure that it meets the specified requirements and functions
as expected in its intended environment.

Table 4.3: Test case for Purchasing Product

Project Name: Multi Customer Ecommerce

Test Case

Test Case ID: TC_002 Test Designed by: Pratik Khanal & Shreena

24
 Ranjit

Test Priority (Low/Medium/High):

Test Designed date: 25-06-2023
Medium

Test Executed by: Pratik Khanal & Shreena

Module Name: Purchase Product
Ranjit

Test Title: Purchase Product Test Execution date: 15-07-2023

Description: Test the MCE purchase system.

Pre-conditions: User should login to MCE.

User has to provide all the necessary details and add product to cart.

Dependencies:

Status
Test Expected Actual
Step Test Data (Pass/F Notes
Steps Result Result
ail)

Navigat
As Expected,
e to purchase
i.e., user is
1 purchase summary page Pass
navigated to
summar should open
page
y page

Name: Sandesh

Phone no.:
9874563210

Provide Address:
Credential can
2 own Kapan As Expected, Pass
be entered
details
Quantity: 5

Price: 100

Estimated
Date:

25
 22-07-2023

Total: 500

Click on
Purchas User should be
3 Click As Expected, Pass
e able to Click

Button

Payment
User select
4 mode is credit card As Expected, Pass
payment button
selected

Enter
credit card no.
valid Credential can
5 = 1.. As Expected, Pass
informat be entered
ccv = 322
ion

As Expected,
i.e., User is
Click on User should be
able to
6 pay click able to pay for Pass
purchase
button chosen room
product in the
MCE

Post-conditions:
User provide their information and purchase product.
The purchase details are logged in to the database.

26
 Chapter 5: Conclusion and Future Recommendation
5.1 Conclusion
By implementing DotNet as backend and HTML, CSS, JS and Bootstrap as frontend,
this website will provide user a dynamic website. the E-Commerce project
successfully developed a user-friendly and secure online shopping platform. The
system's technical feasibility was assessed, and it was designed with modularity in
mind for future scalability. The project achieved its objectives by implementing
cosine-similarity recommendation and enabling shopping carts for a personalized
shopping experience. The administrator was granted additional functionalities for
better management. Overall, the project is poised to make a positive impact in the
world of E-Commerce.

5.2 Future Recommendation

The website's administrator can be granted additional functionalities, such as
accessing a specific customer's profile, viewing the books that need to be reordered,
and more. This expanded access allows the administrator to have better control and
management over the system.

Furthermore, the system can be designed to support multiple shopping carts, enabling
users to create and manage multiple separate carts for different purposes. This feature
enhances the user experience, as customers can organize their shopping items more
efficiently, making it easier for them to keep track of various purchase scenarios. With
multiple shopping carts, users can create separate lists for personal shopping, gift
purchases, or any other distinct needs they may have.

27
 References

[1] S. E. Ullah, T. Alauddin, and H. U. Zaman, “Developing an E-commerce

website,” 2016 International Conference on Microelectronics, Computing and
Communications (MicroCom), 2016. doi:10.1109/microcom.2016.7522526

[2] A. R. Lahitani, A. E. Permanasari, and N. A. Setiawan, “Cosine similarity to

determine similarity measure: Study case in Online essay assessment,” 2016 4th
International Conference on Cyber and IT Service Management, 2016.
doi:10.1109/citsm.2016.7577578

[3] A. Wang and H. Pan, “The teaching in ASP.NET programming and the
development in E-commerce project,” 2010 Second International Workshop on
Education Technology and Computer Science, 2010. doi:10.1109/etcs.2010.111

[4] X. Hao, L. Duo-lin, and L. Zhi-jie, “The research on E-commerce website Success
Mode,” 2010 Asia-Pacific Conference on Wearable Computing Systems, 2010.
doi:10.1109/apwcs.2010.82

[5] F. Wan et al., “Research and design of E-commerce payment system,” 2017
International Conference on Computer Technology, Electronics and Communication
(ICCTEC), 2017. doi:10.1109/icctec.2017.00283

28