Tribhuvan University

Institute of Science and Technology (IoST)

Project report on
“STYLISTA”
Clothing and Makeup Ecommerce Website

Submitted To:
National College of Computer Studies
Department of Bachelor of Science in Computer Science and Information Technology
([Link])

In partial fulfillment of the requirement for the degree of Bachelor of Science in

Computer Science and Information Technology ([Link])

Submitted By:
Ayusha Adhikari (28863/078)
Bipasna Dulal (28867/078)
Riya Shrestha (28872/078)
Yunika Shrestha (28899/078)

[Link] (7th Semester)

 ACKNOWLEDGEMENT

We would like to extend our heartfelt thanks and gratitude to our supervisor, Mr. Anup Raj
Poudel, for granting us the valuable opportunity to work on “STYLISTA- E-commerce
Website for Clothing and Makeup” project. His insightful guidance and support have
greatly contributed to the success of this project, allowing us to explore new tools and
technologies.
Our sincere appreciation goes to NCCS College for their constant supervision, guidance, and
the necessary resources provided, which played a crucial role in the completion of this
project. The support from the library and staff members of NCCS has been invaluable, and
we are grateful for their cooperation and encouragement. Here, we would like to show an
attitude of reverence to all of them who have contributed directly or indirectly to making the
study a reality.
Finally, we shall be grateful to those people who read this project and who shall benefit from
this project at present and in future.

Yours sincerely,
Ayusha Adhikari
Bipasna Dulal
Riya Shrestha
Yunika Shrestha

i
 ABSTRACT

STYLISTA is a modern e-commerce platform dedicated to fashion and women’s makeup,

designed to offer a stylish and online shopping experience. Built with a clean interface, it
ensures seamless browsing and purchasing across devices. The platform provides essential e-
commerce functionalities such as user registration and authentication, product catalog with
detailed descriptions, “add to favorites” and “add to cart” options. With its focus on usability,
STYLISTA aims to redefine online shopping by delivering a fashionable and convenient
digital destination for modern consumers.

ii
 TABLE OF CONTENTS

ACKNOWLEDGEMENT.......................................................................................................1

ABSTRACT.............................................................................................................................2

CHAPTER 1: INTRODUCTION............................................................................................7

1.1 Introduction...................................................................................................................8

1.2 Problem Statement.........................................................................................................8

1.3 Objectives......................................................................................................................8

1.4 Scope and Limitation.....................................................................................................9

CHAPTER 2: BACKGROUND STUDY AND LITERATURE REVIEW..........................10

2.1 Background Study........................................................................................................11

2.2 Literature Review.........................................................................................................11

General E-commerce Platforms:....................................................................................11

Specialized PC Hardware Retailers:..............................................................................12

Custom PC Building Tools:...........................................................................................12

CHAPTER 3: PROJECT MANAGEMENT ACTIVITITES................................................13

3.1 Functional requirements...............................................................................................14

3.2 Project schedule management......................................................................................16

3.2.1 Project activity planning...........................................................................................16

[Link] Work Breakdown Structure...............................................................................16

 [Link] PERT..................................................................................................................18

[Link] CPM...................................................................................................................19

3.2.2 Scheduling.................................................................................................................20

[Link] Ball Chart:..........................................................................................................20

[Link] Gantt Chart:........................................................................................................20

3.2.3 Resource allocation...................................................................................................21

3.3 Cost benefit analysis....................................................................................................24

3.3.1 NPV...........................................................................................................................25

3.3.2 ROI and Payback Period...........................................................................................26

3.3.3 IRR............................................................................................................................27

3.4 Earned Value Analysis.................................................................................................29

3.5 Risk Analysis...............................................................................................................29

3.5.1 Risk Identification.....................................................................................................29

[Link] Project risk.........................................................................................................29

[Link] Budget Risk........................................................................................................30

[Link] Product risk........................................................................................................30

5.1.4 Business risk.........................................................................................................30

5.2 Risk solving.................................................................................................................30

3.6 QA Activity..................................................................................................................31

7.1 Test Cases for Unit Testing..........................................................................................31

7.2 Test Cases for System Testing.....................................................................................33

CHAPTER 8: CONCLUSION..............................................................................................35

REFERENCES......................................................................................................................36

Appendices.............................................................................................................................37
 LIST OF ABBREVIATIONS

API – Application Programming Interface

DB - Database
IDE – Integrated Development Environment
JS – JavaScript
MERN – MongoDB Express-js React Node-js
PC – Personal Computer
 LIST OF FIGURES
Figure 18: Landing Page Without Login.................................................................................12
Figure 19: Registration Page...................................................................................................12
Figure 20: Login Page.............................................................................................................13
Figure 21: Landing Page With Login......................................................................................13
Figure 22: Laptop Store...........................................................................................................14
Figure 23: PC Parts Store........................................................................................................14
Figure 24: Laptop Display.......................................................................................................15
Figure 25: PC Parts Display....................................................................................................15
Figure 26: Build A PC.............................................................................................................16
Figure 27: Cart Display...........................................................................................................16
Figure 28: Khalti Payment Gateway........................................................................................17
Figure 29: Order Page..............................................................................................................17
LIST OF TABLES
 CHAPTER 1: INTRODUCTION

1.1 Introduction
Stylista is a modern e-commerce platform dedicated to fashion and beauty enthusiasts. Our
website offers a curated selection of clothing and makeup products, ensuring a seamless
shopping experience for users looking to elevate their style. At Stylista, customers can
explore a wide variety of trendy apparel as well as premium makeup products, including
lipsticks, foundations, and skincare essentials.

It allows users to easily browse products, view detailed descriptions, select product varieties
(like sizes and colors), and make secure purchases. Stylista also includes features like user
registration, favorites, shopping cart, and smooth checkout options to enhance convenience.

1.2 Problem Statement

In today’s fast-paced digital world, consumers face challenges when shopping for fashion
and beauty products online. Existing platforms often lack personalized experience, product
variety, or clear information about size, color, and quality, making it difficult for users to
make informed choices. Additionally, managing multiple product selections and completing
secure transactions can be cumbersome on traditional e-commerce sites.

Stylista aims to solve these problems by providing a platform where customers can easily
browse, compare, and purchase a wide range of clothing and makeup products. By
integrating intuitive navigation, detailed product information, and secure payment. Stylista
ensures an efficient, enjoyable, and reliable online shopping experience for fashion and
beauty enthusiasts. By prioritizing variety our platform enhances the online shopping
experience, making fashion and beauty more accessible and enjoyable.
1.3 Objectives

The main objective of STYLISTA are as follows:

 To provide clear product descriptions, pricing, and available variations to assist users
in making informed decisions.

 To improve the shopping experience with a fast, user-friendly design.

 Allow users to save their favorite items, “add to cart” and make online payments for
easy future access and purchases.

1.4 Scope and Limitation

The scope of the STYLISTA site includes:
 STYLISTA makes buying clothes and makeup online simple and easy.
 Provide a diverse collection of clothing and makeup products, ensuring a wide
selection for different styles, preferences, and budgets.
 Focus on enhancing customer management and improving the overall user
experience.
 Implement a secure login and registration system, allowing users to manage their
profiles.
 Focus on making shopping personal and enjoyable.
Some limitations of the STYLISTA site might include:

 Tools for managing orders, including order tracking and shipping information are not
available.
 Ensuring the website is accessible and functional across various devices (desktops,
tablets, and smartphones).
 There may not be implementation of a contact form and FAQ section..
 Users cannot try on clothes or makeup virtually before making a purchase.
 Product information will be simple and may not include all technical details.
 CHAPTER 2: BACKGROUND STUDY
AND LITERATURE REVIEW

2.1 Background Study

STYLISTA is an e-commerce platform made to give users a simple and smooth online
shopping experience. It allows people to browse products, add them to a cart, and buy
them easily from their phones or computers. The platform has a clean and user-friendly
design that makes it easy for anyone to use, whether they are shopping online for the first
time or regularly.
With STYLISTA, users can create accounts, view product details, and place orders without
any confusion. The website helps users find what they need quickly and safely. It also
includes features like order history and a simple checkout process. From a technological
perspective, STYLISTA is developed using HTML, CSS, and JavaScript for the frontend,
ensuring an interactive and responsive user interface. The backend is powered by PHP,
enabling dynamic content generation, form handling, and server-side logic. MySQL is used
for managing the database, where user accounts, product information, cart details, and orders
are securely stored and retrieved.

Study of existing system

In our research of current online fashion and beauty shopping platforms, we looked at
Sephora and Shopify as references while planning the development of Stylista. These
platforms are popular and widely used for their extensive product selections, user-friendly
designs, and smooth shopping experiences. Sephora and Shopify are successful because
they make it easy for users to browse products, compare options, add items to the cart, and
place orders efficiently. They also offer features such as product reviews, ratings, order
tracking, personalized recommendations, and secure payment options. Their clean design,
smart search functionality, and responsive performance help users shop with ease. Both
platforms also support mobile applications, allowing users to shop conveniently on
smartphones or tablets. The simplicity and effectiveness of Sephora and Zalora guided the
design and development of Stylista. Our aim is to provide a similarly smooth and
engaging shopping experience, with intuitive navigation, secure checkout, and helpful
features—so that anyone, regardless of technical skills, can explore fashion and beauty
products online comfortably.

2.2 Literature Review

E-commerce has transformed how consumers purchase fashion and beauty products,
providing opportunities for personalized shopping experiences. Laudon and Traver (2020)
describe e-commerce as the use of the internet and web technologies to conduct business
transactions. They explain that e-commerce platforms allow users to browse products,
make payments, and access services through digital interfaces. The study highlights that
growth in mobile device usage and improved internet connectivity have driven the
expansion of e-commerce globally. The authors also emphasize that customer trust, secure
payment systems, and easy-to-use website interfaces are crucial for successful online
businesses. [1]

Chong et al. (2016) investigated factors influencing customer satisfaction and loyalty in
online shopping environments. Their research shows that website quality, fast delivery,
and reliable customer service significantly affect repeat purchases. They also stress the
importance of personalization in enhancing user experience, such as suggesting products
based on past behavior or preferences. Additionally, customer reviews and ratings play a
critical role in purchasing decisions, highlighting the need for transparency and trust on e-
commerce platforms. [2]

Gefen, Karahanna, and Straub (2003) explored the role of trust in e-commerce adoption.
Their study indicates that trust is essential because online transactions involve inherent
uncertainty and risk, unlike traditional in-person shopping. Key factors such as website
design, clear communication, privacy policies, and secure payment gateways contribute to
building consumer trust. Without trust, even well-designed platforms may fail to retain
users. [3]
 CHAPTER 3: PROJECT MANAGEMENT ACTIVITITES

3.1 Functional requirements

The "Mernify" system must fulfill the following functional requirements to provide
comprehensive and effective e-commerce experience:

 User registration and login: Users should be able to create an account and log in
using their email and password to access their profile, order history, and make
purchases.
 Product Browsing: Users should be able to browse all available products.
 Product Details Page: Users should be able to click on a product to view detailed
information, including name, price, description, and images.
 Shopping Cart System: Users should be able to add products to their cart, update
quantities, and remove items before proceeding to checkout.
 Checkout and Payment Process: Users should be able to place an order by
providing delivery information and choosing a payment method.
 Order Management: Users should be able to view their past orders, including
product details, order status, and delivery tracking (if available).
 Admin Panel: Admins should be able to manage the website by adding, editing, or
deleting products, and viewing customer orders.
 Responsive Design: The platform should work smoothly on all devices desktop,
tablet, and mobile for a good user experience.
 Figure 1: Use Case Diagram of Mernify

The use case diagram for Mernify blog platform outlines the key user interactions. It
includes actors such as Customer and Admin, with use cases view products, add to cart,
purchase product, payment etc. The diagram shows how users interact with the platform
and how admin manage the system. It helps visualize the system’s functionality and user
interactions, providing a clear understanding of its behaviour.

3.2 Project schedule management

Project schedule management is the process of developing a project schedule, defining
activities, sequencing them, estimating durations, and allocating resources to create a
timeline for completing the project. It also involves monitoring and controlling the schedule
to track progress, manage changes, and ensure the project is delivered on time.

3.2.1 Project activity planning

A project plan is a series of the activities stating the start and the stops of each activity in a
project. Project planning and scheduling requires careful consideration and activity planning.
It is an important part of project planning that involves breaking down of the project into
specific tasks and activities, and deciding the order of the activities that should be completed
in.

[Link] Work Breakdown Structure

Breaking work into smaller tasks is a common productivity technique used to make the work
more manageable and approachable. For projects, the Work Breakdown Structure (WBS) is
the tool that utilizes this technique and is one of the most important project management
documents. It singlehandedly integrates scope, cost and schedule baselines ensuring that
project plans are in alignment.
Figure 1: WBS of Online Mobile Shopping System
Figure 2: WBS in MS Project of Mernify

[Link] PERT
PERT (Program Evaluation and Review Technique) is a project management tool used to
analyze and manage the tasks involved in completing a project. PERT uses a network
diagram to represent the tasks and their dependencies, and estimates the time required to
complete each task. The network diagram is created by identifying the tasks required to
complete the project and the order in which they must be completed. Once the network
diagram is created, PERT uses three-time estimates for each task: the optimistic time, the
most likely time, and the pessimistic time. The optimistic time is the best-case scenario for
completing the task, the pessimistic time is the worst-case scenario, and the most likely
time is the most realistic

11
estimate. Using these time estimates, PERT calculates the expected time for each task using
the formula:

Expected Time = (Optimistic Time + 4 * Most Likely Time + Pessimistic Time) / 6

[??????]

[Link] CPM
CPM (Critical Path Method) is a project management technique that is used to determine the
critical path of a project, which is the sequence of tasks that must be completed on time in
order to complete the project on schedule. A critical path in project management is the
longest sequence of activities that must be finished on time in order for the entire project to
be complete. Any delays in critical tasks will delay the rest of the project. CPM revolves
around discovering the most important tasks in the project timeline, identifying task
dependencies, and calculating task durations.

Figure 3: Network diagram Section 1

12
Figure 4: Network diagram Section 2

Figure 5: Network diagram Section 3

13
 3.2.2 Scheduling
Project Scheduling is an essential aspect of the project management as it helps to plan and
organize the project’s task and resources to ensure that the project is completed within the
time. Generally, the scheduling refers to creating the timeline for a project, including the
completed task, milestones and the resources required to meet them.

[Link] Ball Chart:

The way of showing whether or not targets have been met or not. It is represented in the form
of circles that indicate the start and the end point completion of activities. Circles of the ball
chart mostly contain only two dates, the original and the revised one. An activity is denoted
by a red circle and green color denotes that the activity is ahead of its schedule. Slippage in
the project completion date but it is overcome by the timeline charts.

14
Figure 6: Ball Chart

15
[Link] Gantt Chart:
Gantt Chart is used to track project progress. It is the simple and the oldest form of
representing the progress of the project. It consists of an activity bar that indicates the
scheduled activity dates and the duration along with the activity floats. Gantt chart can be
defined as the horizontal bar chart which is used in project management to visually represent
the project plan over time. It is the graphical representation of the project activities that aids
in monitoring the progress of the project.

Figure 7: Gantt Chart of Online Mobile Shopping System

3.2.3 Resource allocation

Resource allocation is the process of assigning and managing assets in a manner that supports
an organization's strategic planning goals. Resource allocation includes managing tangible
assets such as hardware to make the best use of softer assets such as human capital.
After the activities has been identified using the various techniques and tabulated using the
Work Breakdown Structure the resources need to be allocated to complete the identified task.
Managing tangible assets such as hardware to make the best use of softer assets such as
human capital is an example of resource allocation. After the organization has established
their goals then they must identify or determine which resources are required in order to fulfil
those goals. Effective resource allocation in SPM requires continuous monitoring and
adjustment during the whole project lifecycle so the resources get allocated and used
effectively to get the desired output. Resource allocation involves balancing competing needs
and priorities, and determining the best course of action to maximize the use of limited
resources and get the best return on investment.

There are several types of the resources that is required in the project management and they
are as follows:

16
 1. People:
This means the human members of the team, responsible for getting each task done.
This category is first for a reason. The people on your team have more influence over the
success of your project than any other category.
You can have the best software, the cushiest office space, the most money, but if you don’t
have a good team, your project won’t go anywhere.

2. Information
Information is the knowledge you need to complete every task.
A team without information is just taking shots in the dark…and we all know how that ends.
Your team members will come aboard with much of the information you need to get started.
That includes how to use your tools, how to work within your company’s processes, and
other table-stakes stuff. The tricky part is the information specific to this project. It’s vitally
important, and it’s also subject to change rapidly.
The information required for the online mobile shopping system may include the personal
information such as name, address, contact details of the customers as well as the product
details, engagement within a brand and its products, Wishlist etc. The system should also
contain the information regarding the product attributes, functionalities, color variants and
any other requirements

3. Material
Material resources includes the raw materials and machines, tools, equipment, software,
premises etc. They include both the resources that the organization possess or those that has
to be leashed or purchased in order to carry out the project. The material resources can be any
good which are made available temporarily for the project and can be used later in different
project. The material resources required for Online Mobile shopping system are as follow:
Laptops, database servers, office supplies, software licenses etc.

4. Financial
Financial resources also called the cost resources, corresponds to the project budget, which
will be designed prior to the launch by the project sponsors. The financial resources are used

17
to manage the human and material resources, i.e., generally covering the renumeration of the
actors of the project, the rental cost for the materials, and other cost such as travel expenses,
product distribution expenses and miscellaneous expenses.

Figure 8: Resources used for project

18
 Figure 9: Resources Allocation

3.3 Cost benefit analysis

Cost Benefit Analysis (CBA) is an approach to evaluate cost and benefits of the proposed
project which helps to find the most cost-effective alternative. It is a technique that helps in
comparing the expected costs and benefits of the alternative option and make choices
accordingly. CBA is a versatile method that is often used for business, project and public
policy decisions. There are several techniques like NPV (Net-Present Value), IRR (Internal
Rate of Return), BCR (Benefit-Cost Ratio) that can be used to analyze cost-benefit analysis.
For our project we will be using Net Present Value (NPV) as a method for cost benefit
analysis.
In order to calculate our CBA, first we need to assess the cost during the development and
the benefits associated with the project. Some of the cost might include:
 Direct Cost
 Indirect Cost
 Intangible Cost
 Potential Risk

19
 Opportunity Costs

Benefits of Cost Benefit Analysis are:

 Improves decision-making
 Enhances understanding of project goals
 Helps compare information
 Increases chances of success
 Improves project planning

3.3.1 NPV
Net Present Value (NPV) is a financial metric used to determine the present value of future
cash flows, discounted at a specific rate. It is commonly used in capital budgeting to assess
the profitability of an investment.
Key Takeaways:

Net present value (NPV) is used to calculate the current value of a future stream of
payments from a company, project, or investment.
To calculate NPV, you need to estimate the timing and amount of future cash flows and pick
a discount rate equal to the minimum acceptable rate of return.
The discount rate may reflect your cost of capital or the returns available on alternative
investments of comparable risk.
If the NPV of a project or investment is positive, it means its rate of return will be above the
discount rate.
The formula for the calculation of the Net Present Value (NPV) is:
n
Cash Flo wi
NPV =∑ −Initial Investment
i=0 ( 1+r )t

Where, r = required return or discount rate t = Number of time periods

11
0
 3.3.2 ROI and Payback Period
ROI stands for Return on Investment; it is a financial ratio used to measure the profitability
of an investment. It is typically calculated as a percentage by dividing the net profit of an
investment by the cost of the investment. The higher the ROI, the more profitable the
investment. The mathematical formula of ROI is:
Net profit
ROI= ⋅100 %
Initial Investment
Payback period can be defined as the amount of time required to recover the cost of an
investment through its cash flow. It can be calculated by dividing the initial investment cost
by the average annual cashflows generated by the investment. The payback period can be
calculated as:
Cumulative Cash Flow Of previousYear
Payback Period= previous year +
Cash Flow of Current Year

3.3.3 IRR
IRR stands for Internal Rate of Return; it is a financial metric that is used to evaluate the
performance of an investment or project. It is the rate at which the NPV of the investment
cashflows equals zero. The higher the IRR the more profitable the investment or project. The
formula for IRR is given as:
n
Ct
NPV =∑ =0
t=0 ( 1+ IRR )t

For the cost benefit analysis of our project, the initial investment be Rs 70,000 at the discount
rate of 10%, expecting to generate the net cash flow of Rs. 28899, Rs. 28886, Rs. 28866, and
Rs. 28864 in the next 4 years.

11
1
So, if discount rate is 10%, the project is worth the investment. Hence, our project group can
undertake the project because NPV>0. Along with NPV, the net profit is found to be Rs.
45515, Average Annual Profit is found to be Rs. 11378.75, ROI is found to be 65.02%, and
Discounted ROI is found to be 30.78%. Similarly, the payback period is 2.22 years and total
benefit with 10% discount is Rs. 91546.49. Finally, the Benefit Cost Ratio (BCR) is 1.307.
Hence, BCR>1, so our project is feasible.

11
2
 3.4 Earned Value Analysis

Earned Value Analysis (EVA) is a project management technique used to measure project
performance and progress in terms of scope, schedule, and cost. It compares the planned
progress with the actual progress to determine if the project is on track.

Metric Formula Description

Planned Value (PV) PV = Budget × Planned % Budgeted cost of work planned to be done
Complete
Earned Value (EV) EV = Budget × Actual % Budgeted cost of work actually completed
Complete
Actual Cost (AC) AC = Actual cost spent Cost incurred for the work completed
Schedule Variance (SV) SV = EV – PV Shows if the project is ahead or behind
schedule
Cost Variance (CV) CV = EV – AC Shows if the project is under or over budget
Schedule Performance Index SPI = EV / PV Ratio showing schedule efficiency
(SPI)
Cost Performance Index (CPI) CPI = EV / AC Ratio showing cost efficiency

11
3
 3.5 Risk Analysis
Risk Analysis and Management is a key project management practice to ensure that the least
number of surprises occur while your project is underway. While we can never predict the
future with certainty, we can apply a simple and streamlined risk management process to
predict the uncertainties in the projects and minimize the occurrence or impact of these
uncertainties. This improves the chance of successful project completion and reduces the
consequences of those risks.
Risk can be defined as the uncertain events that may or may not occur during the project. On
the contrary the project risk could either have a positive or a negative effect on the progress
toward the project objectives. The identification and the management of those risk are the
keys to ensure that the project progress runs smoothly without any barricade. While there is
no way to predict the risk that can occur in the future with a certainty, but there are several
methods that can be applied to predict those uncertainties and minimize the occurrence and
the impact those risk has on the project.

3.5.1 Risk Identification

Risks are to be identified and dealt with as early as possible in the project. Risk identification
is done throughout the project life cycle, with special emphasis during the key milestones.
Risk identification is one of the key topics in the regular project status and reporting
meetings. Some risks may be readily apparent to the project team—known risks; others will
take more rigor to uncover, but are still predictable.
11
4
The medium for recording all identified risks throughout the project is the risk register,
which is stored in the central project server.
There are multiple types of the risk that might be identified during the development of the
system. The risk that might occur are as follow:

11
5
 [Link] Project risk
The experience staff in the team leave the project before it is finish, or someone was ill.
The methodology to solve the problem can't work in a proper manner.
Hardware requirement can't come in the time.

[Link] Budget Risk

There is not enough budget causing delay in the progress of the system.

[Link] Product risk

Package and development tool is not enough.
Can’t found suitable component.

[Link] Business risk

Marketing product unsuccessful.
Competition from the similar products available in the market.

3.5.2 Risk solving

There are several ways to solve the analyzed or the calculated risk. The solution to the risk
identified above are as follow:
The system can streamline the registration system by reducing the time and effort required
from the staff and the students, which results in faster processing time.
Improving the data security on the sensitive student details and reducing the risk of the
security breach.
To conduct regular system testing and quality assurance test to make sure that requirements
are met.

11
6
 3.6 QA Activity

3.6.1 Test Cases for Unit Testing

Unit testing is a software testing method where individual components or units of code (like
functions or methods) are tested in isolation to verify their correctness and ensure they
function as expected.

Test Case ID: 1

Test Title: Verify login with valid username and password.
Test Designed Date: 25 February, 2025

Pre-conditions: User has valid username and password.

Dependencies:

Table 1: Unit testing 1

Test Description Test Data Expected Actual Result Status

Result (Pass/Fail)
1. Navigate to login Username: User should be User is navigated Pass
page. mandish_nv able to login. to the landing
* Provide valid page with
username. Password: successful login.
* Provide valid mandish_nv
password.
* Click login button.
Provide invalid Username: abc User login User login Pass
username and Password: 123 invalid. invalid.

1
password.

Post-condition:

User is validated and the page is redirected to the landing page with login status.

2
Test Case ID: 2
Test Title: Display items based on the selected field.
Test Designed Date: 25 February, 2025

Pre-conditions: Items of different categories are stored in the database.

Dependencies:

Table 2: Unit testing 2

Test Description Test Data Expected Actual Result Status

Result (Pass/Fail)
Select a category. Category: CPU Items Items belonging Pass
View items in that belonging to to “CPU”
category. “CPU” category is
category displayed.
should be
displayed.

Select a category. Category: Items Items belonging Pass

View items in that Laptops belonging to to “Laptop”
category. “Laptop” category is
category displayed.
should be
displayed.

Post-condition:

The items belonging to the selected category are displayed.

3
Test Case ID: 3
Test Title: Add items to cart.
Test Designed Date: 25 February, 2025

Pre-conditions: The user must be logged in.

Dependencies:

Table 3: Unit testing 3

Test Description Test Data Expected Actual Result Status

Result (Pass/Fail)
Select an item to Item: AMD The item The item is added Pass
purchase. - AMD Ryzen should be to cart along with
Select the quantity of 7 7700X added to cart the quantity.
items to purchase. along with the
Click on “Add to quantity.
Cart” button.

Select an item to Item: Acer - The item The item is added Pass
purchase. America Acer should be to cart along with
Select the quantity of Aspire 5 15.6" added to cart the quantity.
items to purchase. Touchscreen along with the
Click on “Add to Laptop i7- quantity.
Cart” button. 13620H 16GB
RAM 1 TB
PCIe SSD
Windows 11
Home A515-

4
 58PT-746F

Post-condition:

The items are added to cart along with the selected quantity.

5
 3.6.2 Test Cases for System Testing
System testing is a level of testing that validates the complete and fully integrated software
product. The purpose of a system test is to evaluate the end-to-end system specifications.
Usually, the software is only one element of a larger computer-based system.

Test Case ID: 4

Test Title: Functionality testing.
Test Designed Date: 25 February, 2025

Pre-conditions:

Table 4: System testing 1

Test Description Test Data Expected Actual Result Status

Result (Pass/Fail)
UI Workflow. Landing page. All the buttons All the buttons Pass
and navigation and navigation
bar contents bar contents
should navigate to the
navigate to the correct location.
correct
location.
User login and Correct user The user The user can Pass
registration. registration and should be able register and then
login data. to register and login to the
then login to website. The user
the website. can access the
The user login features.
should also be
able to access

6
 the login
features.

Post-condition:

The functional components are working as intended.

7
Test Case ID: 5
Test Title: Security testing.
Test Designed Date: 25 February, 2025

Pre-conditions:

Table 5: System testing 2

Test Description Test Data Expected Actual Result Status

Result (Pass/Fail)
The user inserts valid Login page. The user The user is Pass
username and should be successfully
password. successfully logged in and has
(Authentication) logged in and access to logged
should have in features.
access to
logged in
features.
Password should be Password: test The password The password Pass
encrypted. should be should is stored
(Data Privacy) stored in in database in
database in encrypted format.
encrypted Password:
format. $2b$10$1NJAv/8
1RpIX.YbH4ru
WROEejCs/ZmV
A7Ur24KlOeHi
mtJ80qOzXi

8
Post-condition:

The security components are working as intended.

9
 CHAPTER 4: CONCLUSION

Through the Mernify eCommerce project, we gained valuable hands-on experience in

building a full-stack MERN application, from designing user-friendly interfaces to
managing databases, APIs, and secure transactions. Integrating Nepali payment gateways
like eSewa and Khalti provided practical insights into API integration and real-time
financial workflows, while managing product listings, user authentication, and order
tracking strengthened our ability to build scalable, real-world platforms. Mernify
successfully delivers a feature-rich online shopping experience, enabling users to browse
products, manage carts, place orders, and enjoy a smooth checkout process. Backed by
comprehensive system diagrams such as use case, ER, activity, and sequence diagrams,
the project effectively demonstrates the potential of the MERN stack in building responsive
and scalable eCommerce solutions.

10
 REFERENCES

[1] geeksforgeeks, "geeksforgeeks," 20 November 2024. [Online]. Available:

[Link]
[2] Amazon, "amazon," 20 April 2025. [Online]. Available: [Link]
[3] eBay, "eBay," [Online]. Available: [Link] [Accessed 20 April 2025].
[4] Nielsen Norman Group, "Nielsen Norman Group," [Online]. Available:
[Link] [Accessed 20 April 2025].
[5] [Link], "[Link]," [Online]. Available: [Link]
[Accessed 20 April 2025].
[6] Micro Center, "Micro Center," [Online]. Available: [Link]
[Accessed 20 April 2025].
[7] L. PCPartPicker, "PCPartPicker," [Online]. Available: [Link]
[Accessed 20 April 2025].

11
 APPENDICES

Figure 1: Landing Page Without Login

Figure 2: Registration Page

12
 Figure 3: Login Page

Figure 4: Landing Page With Login

13
Figure 5: Laptop Store

Figure 6: PC Parts Store

14
Figure 7: Laptop Display

Figure 8: PC Parts Display

15
 Figure 9: Build A PC

Figure 10: Cart Display

16
Figure 11: Khalti Payment Gateway

Figure 12: Order Page

17