Tribhuvan University

Faculty of Humanities and Social Sciences

A PROJECT REPORT

ON

ONLINE GADGET SHOP

Submitted to:

Department of Computer Application

Ambition College

Mid-Baneshwor, Kathmandu

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

Submitted By:

Sushant Bista (TU No.: 6-2-1058-62-2019)

Saroj Rai (TU No.: 6-2-1058-58-2019)

June 15, 2022

Under the Supervision of

Mrs. Nani Maya Sakhya
 June 15, 2022

Ambition College

Faculty of Humanities and Social Sciences

Mid-Baneshwor, Kathmandu

Supervisor’s Recommendation

I hereby recommend that this project prepared under my supervision by Mr. Sushant Bista
and Mr. Saroj Rai entitled “Online Gadget Shop” in the partial fulfillment of the degree
of Bachelors in Computer Application is recommended for the final evaluation.

....................................

Mrs. Nani Maya Sakhya

Supervisor

BCA Department

Ambition College

Mid-Baneshwor, Kathmandu
 June 15, 2022

Tribhuvan University
Faculty of Humanities and Social Sciences
Ambition College
Mid-Baneshwor, Kathmandu

LETTER OF APPROVAL
This is to certify that the project entitled “Online Gadget Shop” has been submitted by
Mr. Sushant Bista and Mr. Saroj Rai in the partial fulfillment of the requirements for the
degree of Bachelors in Computer Application (BCA) of Tribhuvan University.

Evaluation Committee

…………………….. ……………………
Mrs. Nani Maya Sakhya Mr. Bishnu Kumar Ghimire
Supervisor Campus Chief
Ambition College Ambition College
Mid-Baneshwor, Kathmandu Mid-Baneshwor, Kathmandu

…………… …………….
Ramesh Kumar Chaudhary Prof. Dr. Subarna Sakhya
Internal External
Depn. of Electrical and Computer
Engineering
Pulchowk Campus
IOE, Tribhuvan University
 ACKNOWLEDGEMENT
We owe our most profound appreciation to the Ambition College for giving us an
opportunity to work on the project as part of our syllabus. We take this opportunity to
express this gratitude to the people who have been instrumental for the success of this
project. Our special thanks goes to all of our teachers who has provided their continuous
support and guidance.

We would like to thank Tribhuvan University, Faculty of Humanities and Social Science
for providing us the opportunity to prepare the project. This project has enhanced our
knowledge regarding how to make a desktop application. Finally, we would like to thank
our family and friends who supported us during this project.

Sushant Bista (6-2-1058-62-2019)

Saroj Rai (6-2-1058-58-2019)

i
 ABSTRACT
This is a project for Online Gadget Shop. The basic idea for this project is to allow a
customer to buy product using online system. The user can create their own accounts to
order the products and purchase the products. The Online Gadget Shop allows vendors
or admin of the page to whether add or delete specific products and maintain list of
product categories. Our “Online Gadget shop” will use the internet as sole method for
selling goods to its customers. Shopping will highly personalized and the system will
provide lower prices than most competitors. It is an online store that enables websites
owner to sell their products online. It is a web shopping cart that web enables the day-by-
day sales functions. It includes product and customer management modules. This website
will be useful to anyone who wants to purchase items using internet.

Keywords: OGS, HTML, PHP, JavaScript, CSS.

ii
 TABLE OF CONTENTS
Acknowledgement..........................................................................................................i

Abstract...........................................................................................................................ii

List of Figures.................................................................................................................v

List of Tables..................................................................................................................vi

List of Abbreviations......................................................................................................vii

Chapter 1: Introduction...............................................................................................1

1.1...................................................................................................................................Intr
oduction....................................................................................................................1
1.2...................................................................................................................................Prob
lem Statement...........................................................................................................2
1.3...................................................................................................................................Obj
ectives.......................................................................................................................2
1.4...................................................................................................................................Sco
pe and Limitations....................................................................................................2
1.5...................................................................................................................................Rep
ort organization.........................................................................................................3

Chapter 2: Background Study and Literature Review.............................................4

2.1. Background Study...................................................................................................4

2.2. Literature Review....................................................................................................4

Chapter 3: System Analysis and Design.....................................................................6

3.1. Methodology............................................................................................................6

3.1.1. Requirements Analysis.....................................................................................6

I. Functional Requirements..................................................................................6

II. Non-Functional Requirements........................................................................7

a) Reliability Requirements........................................................................7
b) Efficiency Requirements........................................................................7
c) Usability Requirements..........................................................................7
d) Implementation Requirements................................................................8

iii
3.1.2. Feasibility Analysis..........................................................................................8

i. Technical Feasibility.............................................................................8
ii. Operational Feasibility..........................................................................8
iii. Economic Feasibility.............................................................................8

3.1.3. Data Modeling (ER-Diagram)..........................................................................8

iii
 3.1.4. Process Modeling (DFD)..................................................................................11
3.1.4.1. Level 1 DFD.......................................................................................11
3.1.5. Architectural Design.........................................................................................12
3.1.6. Database Schema Design..................................................................................14
3.1.7. Interface design (UI Interface)..........................................................................15
3.2. Development Method..............................................................................................15
Chapter 4: Implementation and Testing....................................................................17
4.1. Implementation........................................................................................................17
4.1.1. Tool Used..........................................................................................................17
4.1.2. Implementation Details.....................................................................................18
4.2. Testing.....................................................................................................................19
4.2.1. Unit Testing......................................................................................................20
4.2.2. System Testing..................................................................................................23
Chapter 5: Conclusion and Future Recommendations.............................................24
5.1. Conclusion...............................................................................................................24
5.2. Future Recommendations........................................................................................24
References......................................................................................................................25
Appendix-1 System Screenshots..................................................................................26

iv
 LIST OF FIGURES

Figure 3.1: Use Case Diagram of OGS..........................................................................7

Figure 3.2: ER Diagram of OGS (Admin Side).............................................................9

Figure 3.3: ER Diagram of OGS (Customer Side).........................................................10

Figure 3.4: Context Diagram of OGS (DFD 0)..............................................................11

Figure 3.5: Level 1 DFD (Admin) of OGS....................................................................11

Figure 3.6: Level 1 DFD (Customer) of OGS................................................................12

Figure 3.8: Architectural Design of OGS.......................................................................13

Figure 3.9: Interface Design of OGS..............................................................................15

Figure 3.7: Waterfall Model...........................................................................................16

Figure 4.1: System Testing 1..........................................................................................23

Figure 4.2: System Testing 2..........................................................................................23

Figure 4.3: System Testing 3..........................................................................................23

v
 LIST OF TABLES

Table 3.1: Admin Table..................................................................................................14

Table 3.2: Product Table.................................................................................................14

Table 3.3: User Table.....................................................................................................14

Table 4.1: Login with Valid Data Testing......................................................................20

Table 4.2: Product Testing..............................................................................................20

Table 4.3: Edit Product Testing......................................................................................21

Table 4.4: Signup with Valid Data Testing....................................................................21

Table 4.5: Signup with Invalid Data Testing..................................................................22

Table 4.6: Login with Empty Data Testing....................................................................22

vi
 LIST OF ABBREVIATIONS
CSS: Cascading Style Sheet

DFD: Data Flow Diagram

ER-Diagram: Entity Relationship Diagram

HTML: Hyper Text Markup Language

OGS: Online Gadget Shop

PHP: Hypertext Preprocessor

SQL: Structured Query Language

UI: User Interface

XAMPP: Cross-platform, Apache, MariaDB (Mysql)

vii
 CHAPTER 1
INTRODUCTION
1.1. Introduction
Online Gadget Shop is a form of electronic service which allows consumers to directly
buy product from a seller over the Internet using a web browser. Online stores usually
enable shoppers to use "search" features to find specific models, brands or items. Online
Shopping is the process whereby consumers can directly buy goods, service etc. from a
seller interactively in real time without an intermediary service over the internet.

Consumers find a product of interest by visiting the website of the retailer directly or by
searching among alternative vendors using shopping search engine, which displays the
same product's availability and pricing at different retailers. Customers can shop online
using a range of different, gadgets including, smartphones, tablets, laptop, and, desktop
computer. Online Gadget shop is an online website which allows customer to buy gadget
items directly from the internet without any physical visit. It is conducted between
business and customer.

The Online Gadget Shop is designed to keep all the details about all the products related
to gadgets such as smartphones, laptops, headphones etc. In this OGS there are two types
of users available i.e., Admin and User. Admin can login in the page through separate
admin login panel with the help of their personal login details. Admin can access the
dashboard after logging in the page. Through the help dashboard admin can manage the
page such as adding the different kinds of products in their respective categories. Admin
can add/update the products with respective to their categories and also delete the
products. Admin can access the user details and delete the unwanted user and have total
no of count of the user registered in the page. Admin can access the order details and
view the details of the products that has been ordered by the users.

OGS allows users to browse the products as guests whereas guests have limited access to
only browse the product in the page or user can register and login to browse the products.
User can browse different kinds of products with the help of category tab presented for
the user. After browsing the products user can also add the product to the cart which is
later received by the admin. To add the product in the cart user has to login in the page.
Later admin can review the order detail and confirm the order placed by the user.

1
1.2. Problem Statement
With the advancement in technology, people can now do various things at the comfort of
their homes and one such thing is online shopping. There are a lot of websites on internet
whereby it offers a variety of product and services for consumer can find and buy through
online such as computer, mobile. However, there are several reasons hinder in the
consumer are involved in online shopping because some of the consumers are not willing
to take part in online purchased due to the valid reason because there are worried about
the quality of the product in online are not durable, moreover, there are not confident.
Another problem in online gadget shopping is issues with delivery. Products are often lost
or damaged while in transit, and order tracking systems are unable to accurately locate the
product.

1.3. Objectives
The main objectives of this project are as follows:

 To provide easy access to the information on different products to the customer.

 To create own accounts and purchase the products.

1.4. Scope and Limitation

Some of the scopes of this project work are as follows:

 Provides easy shopping from anywhere.

 Customer are updated to up-to-date products.
 To make easy to find the products, the product information is categorized.

Some of the limitations of this project are as follows:

 Project being developed in PHP which require Xampp Server to run, Customer
has no direct access to this system.
 It has limit up to add to cart function only and the online payment system is
excluded.

2
1.5. Report Organization
Chapter 1: In first chapter of the report, it contains the summarized introduction of the
whole report. It includes the short introduction of the system, scope and limitation,
background study, problem statement and objectives of the system.

Chapter 2: In second chapter of report, it contains background study related to the

project along with general description of project functions and components. Literature
review in order to have broader understanding of the project concept based on research
done previously and analyze similar system for comparison with project.

Chapter 3: In third chapter of report, it includes the system analysis and design phase
in which the report of functional and non-functional requirements of the project is stated
using use case and system diagram. It also includes the feasibility study about the system
which explains whether the system development process is affordable and within the
knowledge range of the developers. It includes data modelling and process modelling
which is explained by using ER diagram and Data Flow Diagram. The architectural
design, database design and the user interface design are also listed in this chapter.

Chapter 4: In fourth chapter of report, it includes the implementation and testing

phase of the proposed system. In the implementation phase, the tools like CASE tools,
programming languages and database platforms are implemented and detailly explained.

Chapter 5: In fifth chapter of report, it includes conclusion and future

recommendation. This contains the final paragraph of the report and in this phase the
overall outcome and the developers’ point of view is written.

3
 CHAPTER 2
BACKGROUND STUDY AND LITERATURE REVIEW
2.1. Background Study
The project will be built using the waterfall methodology. This project will be built with
required and specific documentation, fixed requirements and enough time, thus the
project
can be easily developed following the waterfall model.

For the identification of requirements of the project, the existing websites such as
gadgetbytenepal.com were studied and some of the other sites that were related on gadget
shopping were studied. After the study of these websites, it was concluded that an online
gadgets shopping system is required for the comfort and efficiency of the customer.
Online Gadgets Shop will be built for providing the products required by the user in
efficient way with the help of user-friendly interfaces which would enhance the shopping
experience of the customer.

2.2. Literature Review

Electronic shopping was invented by an English inventor called Michael Aldrich. In
1979, he invented the earliest form of e-commerce which allowed online transaction
processing
between business and customers, as well as between business and business. The invention
of the first ever web browser, i.e., the World Wide Web in 1990 is the second major
proponent of online shopping. Without an interconnected internet, there would be no
online marketplace at all. We owe this marvelous invention called the ‘WWW’ to Tim
Berners Lee. That man is the major reason why millions of people have access to the
internet which hosts numerous e-commerce platforms [1].

The sharp increase of Internet usage, as well as, the systematic progress of Information
Technology has transformed the way goods are bought and sold, resulting to the
exponential growth in the number of online shoppers. However, a lot of differences
regarding online purchases have been revealed due to the various consumers’
characteristics and the types of provided products and services. Therefore, understanding
who are the ones consuming and why they choose to use or avoid the Internet as a
distribution channel, is a vital issue for both e-commerce managers and consumer
theorists [2].

4
Electronic Commerce also known as e-Commerce by most has been rapidly growing in
worldwide sales ever since it was introduced almost forty years ago in the late 1970s.
Today electronic commerce is a trillion-dollar industry that is still rapidly growing and
increasing in worldwide sales. Electronic commerce wouldn't be where it is today if not
for the contribution of its innovators and pioneers. In the year 1972, ARPANET was
smartly taken advantaged of and was used to make sales transactions between students of
the Massachusetts Institute of Technology and students of the Stanford Artificial
Intelligence Laboratory. After some time, it was depicted as the "The seminal act of e-
commerce" (Markoff/2006). ARPANET was a wide area network…show more content.
In 1990, Tim Berners-Lee invented the World Wide Web, which completely redefined the
way online shopping works. With the World Wide Web being open to the masses and
getting more and more popular day by day expeditiously, an organization called Book
Stacks Unlimited capitalized on this new platform in 1992 by establishing the first ever
commercialized website selling books through the world wide web, allowing payments by
credit cards (Souder/1998).In 1995, Amazon the first commercial-free 24-hour website
was launched by Jeff Bezos, which then on became one of the largest and most profitable
electronic commerce companies in the globe[3].

Gadget Byte is the Leading Tech Review News Portal of Nepal that gives the users
information, tools, and advice that will help them decide (with Buy Guides and Tech
Guides) get the most out of the Tech. This company is spread across the internet through
our various channel which includes the website itself, YouTube, Google Plus, Facebook
and Twitter [4].

5
 CHAPTER 3
METHODOLOGY
3.1. Methodology
Methodology is a collection of methods, practices, processes, techniques, procedures, and
rules. In project management, methodologies are specific, strict, and usually contain a
series of steps and activities for each phase of the project's life cycle.

3.1.1. Requirement Analysis

Requirement analysis is used to determine the needs for the system being developed and
what the system is expected to. Requirements analysis is categorized into two types:

I. Functional Requirements

The functional requirements are mapped using Use Case diagrams as it shows the
functions of the system at the most basic level. Use Case shows the functions that are
included for the system to function as per requirement. Requirements mapped out in the
use case must be implemented in the system. It is divided into admin based and user-
based requirements.

The main functional requirements of the system are:

 Signup into the system

 Login into the system
 Add/delete/update products
 View products
 Delete user
 View order details

The admin does back-end related tasks by first registering and the logging into the system
using the login details. Add, delete, edit option is given to the admin regarding products.
Admin can also delete the user if user violates the page. User can view the products as
guests but cannot purchase the product. To add the products into the cart, user have login
in the page if they are already registered or else, they can register on the page and login.
The product that has been added to the cart by the user are later reviewed by the admin in
the admin panel.

6
 Figure 3.1: Use Case Diagram of OGS

II. Non-Functional Requirements

A non-functional requirement describes how the system performs a certain function. Non-
functional requirements generally specify the system’s quality attributes or
characteristics. The non-functional requirements in contents to project are as follows:

a) Reliability Requirements

The system must perform accordingly to the customer request. Data and information
should not be lost. Changes must be reflected to the database.

b) Efficiency Requirements

With the online gadget shop system, customer should be able to process products/items
purchase faster. With the use of software, user can access the system at any time.

c) Usability Requirements

The system must be designed with user-friendly and easy to use by the user so that the
user can perform their job nicely. It must have a clear instruction to guide user through
the system.

7
d) Implementation Requirements

While implementing the system, Xampp server must be installed as the system uses PHP
as main programming language.

3.1.2. Feasibility Study

For the development of the proposed system, the following feasibilities are studied for the
effectiveness and to reduce its complexity during development phase:

i. Technical Feasibility

While the development of the system the technological disturbance is avoided as far as
possible. Online Gadget Shop will be built with the existing hardware and software, so
the system will be technically feasible. This system comprises of specific idea so there
will be no difficulties for converting the idea into working system.

ii. Operational Feasibility

This project is platform independent and GUI based. The system will be built with user
friendly interfaces. After the design of the system, the user will be able to login in the
page or browse the product of different category as guests also. The user will be able to
add the product to their cart when the system is completed.

iii. Economic Feasibility

The system will be built in a way that require less costs. The system does not need
additional environment to run. The existing hardware and software will be enough to run
the system. Thus, the system will be built on less cost.

3.1.3. Data Modeling (ER-Diagram)

This ER (Entity Relationship) Diagram represents the model of “Online Gagdet Shop”
entity. The ER diagram shows as all the visual instrument of database tables and the
relations between shopping, order, product category. It used structure data and to define
the relationships between structured data groups of “Online Gagdet Shop” functionalities.

8
Name 1
1
Admin F has Gadget Shop
1
Password

Manages

1
F
Dashboard
1

has

OrderID
N N
Name
Users Orders

Email

Address Number
Number N
ProductDetails
Email Products

Name Price

UserID
Stock

ProductID Category

ProductName Image

Figure 3.2: ER Diagram of OGS (Admin Side)

9
 N 1
Guest has Gadget Shop

N
UserID Password

N
N
Customer

UserName Email

can
Browse
Price
Stock
can

N
Products

Category

Image
N
ProductName
Order
OrderID
ProductID
Name

Email
Number
Address

ProductDetails
Figure 3.3: ER Diagram of OGS (Customer Side)

10
3.1.4. Process Modeling (DFD)

A DFD can be referred to as a Process Model. A data-flow diagram (DFD) is a graphical

representation of the “Flow” of data through an information system a data flow diagram
(DFD) is a significant modelling technique for analyzing and constructing information
processes illustrates this flow of information in a process based on the inputs and outputs.

Add Products Products Details

Customer
Details Login
Admin Online Gadget Customer
Shop

Order Details Order Products

Figure 3.4: Context Diagram of OGS (DFD 0)

3.1.4.1. Level 1 DFD

The admin side DFD describes the functionality of admin. Admin is the owner of website.
Admin can first add category of item and then add items by category wise.
Request to login
Check Detail
Admin 1.0 AdminMst
Response Login
Reply

1.1 Insert data

Add Product ItemMst

Reply

Remove data
1.2

Delete Product ItemMst

Reply
Figure 3.5: Level 1 DFD (Admin) of OGS

11
 Customer Request to login 1.0
Response Login

1.1 View data

View Product View

Products
Reply

Add data
1.2

Purchase Add to
Product cart
Reply
Figure 3.6: Level 1 DFD (User) of OGS

3.1.5. Architectural Design

System Architectural defines the structure of a software system. This is usually a series of
diagrams that illustrate services, components, layers and interactions.

The system is based on 1-tier architecture as all the system components and resources are
located in the central place i.e., local server. This architecture allows direct and fast
access to resources and only one central admin is able to manage and maintain the
website.

12
 Online Gadget Shop

User Interface
Presentation Layer
-View Products
-signup
-login
-logout

-Validation and
verification logic Application Layer
Client
Tier -Algorithm for
curd operation
-sql
implementation

Database Layer
-Store product information
-Store user information

Figure 3.7: Architectural Design of OGS

13
3.1.6. Database Schema Design

Table 3.1: Admin Table

Column Name Data Type and Attribute

ID INT Primary key AUTO INCREMENT

Username VARCHAR (100)

User password VARCHAR (100)

Table 3.2: Product Table

Column Name Data Type and Attribute

ID INT Primary key AUTO INCREMENT

P.name VARCHAR (100)

P.prize NUMBER

P.category VARCHAR (100)

Table 3.3: User Table

Column Name Data Type and Attribute

ID INT Primary key AUTO INCREMENT

Username VARCHAR (100)

Email VARCHAR (100)

Number NUMBER

Password VARCHAR (100)

14
3.1.7. Interface Design (UI Interface)

Logo Login Admin Login

Categories

Home

Product Items Product Items

Figure 3.8: UI Interface Design of OGS

3.2. Development Method

The project will be built using the waterfall methodology. This project will be built with
required and specific documentation, fixed requirements and enough time, thus the
project
can be easily developed following the waterfall model.

The waterfall model is a linear project management approach, where stakeholder and
customer requirements are gathered at the beginning of the project, and then a sequential
project plan is created to accommodate those requirements. The waterfall model is so

15
named because each phase of the project cascades into the next, following steadily down
like a waterfall.

Requirement
Requirement Analysis
Analysis

System Design

Implementation

Testing

Deployment

Maintenance

Figure 3.9: Waterfall Model

16
 CHAPTER 4
IMPLEMENTATION AND TESTING
4.1. Implementation
4.1.1. Tool Used

Visual Studio Code: Visual Studio Code is a lightweight but powerful source code editor
which runs on Window, Linux, macOS. It comes with built-in support for JavaScript,
TypeScript and Node. The delightfully frictionless edit-build-debug cycle means less time
fiddling with your environment, and more time executing on your ideas. It aims to
provide just the tools a developer needs for a quick code-build-debug cycle and leaves
more complex workflows to fuller featured IDEs, such as Visual Studio IDE.

HTML, CSS and Bootstrap: HTML primarily used to design the UI and provide
support to Bootstrap elements by providing containers for bootstrap. CSS used to add
additional detailed design to the portal and Bootstrap used to overall design the portal by
extending tags from existing library.

JavaScript: JavaScript is used to add events and triggers to the web portal, the web portal
uses JS for date and time purpose by directly getting the system time.

PHP: The PHP Hypertext Preprocessor (PHP) is a programming language used to create
dynamic content that interacts with database. It has helped to send and get request and
data from and to database like MySQL in the project and is used for developing web-
based software applications.

MYSQL: MySQL is an open-source relational database management system (RDBMS).

we have used MySQL to store and retrieve data.

XAMPP Server: XAMPP is one of the widely used cross-platform web servers, which
helps developers to create and test their programs on a local web server. It is used in the
project development to locally host the portal and store its detailed centrally.

17
4.1.2. Implementation Details

1. Login into the System

The system checks the user credentials and matches it with the one stored in the database.
If the provided info matches with data in the database then, the user is allowed to enter
the system.

Algorithm:

Start

Enter username & password

If (username is in the database) {

if (password matches username's password in database) {

Enter in the system

} Else

Display incorrect password message

} Else Display username does not exist message.

END

2. Add User

The user can add other user and assign them role after entering into the system.

Algorithm:

Start

Enter Username, Password and Confirmation Password {

If (username already exists in database) {

Display error message

} Else If (Password does not fulfill criteria) {

Display error message

} Else If (password and confirmation password do not match) {

Display error message

} Else

18
 User created message.

END

3. Add New Category and Brand

User can add new categories and brand in the system for the products.

Algorithm:

Start

Enter brand/category name

If (Brand/category name already exist) {

Display error message

} Else

Brand/Category created message

4. Edit Category/Brand

User can edit the existing brands and categories in the database.

Algorithm:

Start

Edit brand/category name

If (Same Brand/category name as previous) {

Direct to view page

} Else

Update Brand/Category

END

5. Edit Product

User can also update the existing products details as name, quantity, brand name,
category. price.

Algorithm:

Start

Edit the product details

19
 If (same details as previous) {

Direct to view page

} Else Update the product table

END

6. Delete Brand/Category/Products

User can delete any records or items from the database in the system. User can press the
delete the option in the view and can perform the delete operation for specific data or
item.

4.2. Testing
4.2.1. Unit Testing

Table 4.1: Login with valid data Testing

Test ID Test Test steps Test data Expected Actual Pass/Fail

Scenario Result Result

T01 Admin Enter Username: Admin As pass

Login username Pawan should be expected
checking and Password: logged in
password able to view
@Ahlkalks
dashboard.

Table 4.2: Product Testing

Test Test Test Test data Expected Actual Pass/Fail

ID Scenario steps Result Result

T02 Adding new Enter ProductName Admin As Pass

products product : Samsung should be expected.
name, Category: able to
category, Smartphone add new
price, Price: 20000, product.
quantity Quantity:10

20
 Table 4.3: Edit Product Testing

Test Test Test Test data Expected Actual Pass/Fail

ID Scenario steps Result Result

T03 Editing Update ProductName Admin As Pass

Product Product : Samsung should be expected.
Details Name, Category: able to
Category, Smartphone edit the
Price, Price: 30000, product
Quantity Quantity: 15 details.

Table 4.4: Signup with valid data Testing

Test Test Scenario Test steps Test data Expected Actual Pass/Fail
ID Result Result

T04 Signup with 1) Enter Enter all Message As Pass

valid data URL valid data saying expected.

2) Click email has

signup been sent

button to email
account.
3) Enter
data in all
field

21
 Table 4.5: Signup with invalid data Testing

Test Test Scenario Test steps Test data Expected Actual Pass/Fail
ID Result Result

T05 Signup with 1) Enter Password: Error As Pass

empty data URL asdsd message expected.

2) Click Email: display

signup 12345 saying
button password

3) Enter must be

data in all at least 5

field letters
and email
must
contain
‘@’

Table 4.6: Login with empty data Testing

Test Test Scenario Test steps Test data Expected Actual Pass/Fail
ID Result Result

T06 Login with 1) Enter All fields Error As Pass

empty data URL are left message expected.

2) Click empty saying to

signup enter

button username
and
3) Enter
password
data in all
field

22
4.2.2. System Testing

Figure 4.1: System Testing 1

Figure 4.2: System Testing 2

Figure 4.3: System Testing 3

23
 CHAPTER 5

CONCLUSION AND FUTURE RECOMMENDATION

5.1. Conclusion
The project “Online Gadget Shop” has been completely successfully and also tested
successfully by taking the test cases under consideration. From a proper analysis of
positive points and constraints on the component, it can be safely concluded that the
product is highly efficient GUI based component. This application is working properly
and meeting to all the user requirements. Thus, component can be easily plugged in many
other systems. The implementation of this system will reduce data time.

We will be continuously working in this project to make it more user friendly and more
secure. We are sure implementing our system in Online shopping, make online shopping
manage much more than traditional one.

5.2. Future Recommendations

The project could have more effective if there were different modules for admin, user and
customers. The billing system and payment gateway could have been included in the
system. If this system was developed with those features it would be one of the best
online gadget shop in the modern technology. This system uses simple mechanism which
could have been advanced and could compete in the market. If the system is considered to
be built again these features will be more important.

24
 REFERENCES
[1] Odworld: History of Online Gadget Shopping [online]: Available from:
https://www/odmworld.com
[2] Computer hope: Online Gadget Shopping [online]: Available from:
https://www.computerhope.com
[3] R. G. Gagandeep Nagar, "A study of factors affecting on online shopping behavior of
consumers," International journal of scientific research publications, vol. 3, pp. 1- 4,
2013.
[4] Gadget byte: Online Gadget Shopping [online]: Available from:
https://www.gadgetbytenepal.com/

25
 APPENDIX – 1 SYSTEM SCREENSHOTS
ONLINE GADGET SHOP
Admin Login Panel

Dashboard

26
Add Product

27
Product Update

Dashboard with data

28
Order Details

Homepage

29
Product at Cart

Product from category

30
31