A Project Report On

E-COMMERCE WEBSITE
Submitted in partial fulfillment of the

MASTER OF COMPUTER APPLICATION

By

Nitin Kumar
Enrollment No: AJU/211546

Under the esteemed guidance of

Dr Arvind Kumar Pandey

&

Ms. Alka Kumari

(Internal Guide)

DEPARTMENT OF COMPUTER SCIENCE & IT

ARKA JAIN UNIVERSITY, JHARKHAND

Jamshedpur
2021-2023

1
 ARKA JAIN UNIVERSITY

DBMS MINI
PROJECT REPORT
ON

ONLINE SHOPPING SYSTEM

IN PARTIAL FULFILLMENT OF REQUIREMENT

DEPARTMENT OF COMPUTER SCIENCE
BATCH 2021-2023

GUIDED BY: PREPARED BY:

Dr. Arvind Kumar Pandey

(HOD) Nitin Kumar
and
Ms. Alka Singh

SUBMITTED TO

DEPARTMENT OF COMPUTER SCIENCE & IT

ARKA JAIN UNIVERSITY 2
 ABSTRACT

E-Commerce website is a software used to handle different data in a shop. It stores the data
into a database in a sequential manner and easily retrieved when needed. The goal of this
software is to provide easy accessing and manipulation of data from multiple systems. Usually
databases are maintained in My SQL but it has certain limitations like the database maintained
there cannot be shared in more than two or three systems, etc. Therefore, to overcome such
problems this system would be useful.

The software “E-commerce website” is a web-based software developed by using the “PHP”,
implemented on Laravel Framework. It would be a distributed system so that multiple systems
can access and manipulate the database. The database would be maintained in My SQL.

4
 ACKNOWLEDGEMENT

I take this occasion to thank God, almighty for blessing us with his grace and taking our endeavor to a
successful culmination. I extend my sincere and heartfelt thanks to our esteemed guide, Ms. ALKA
SINGH, for providing me with the right guidance and advice at the crucial junctures and for showing me the
right way. I extend my sincere thanks to our respected Head of the Department Dr. ARVIND KUMAR
PANDEY, for allowing us to use the facilities available. I would like to thank the other faculty members
also, at this occasion. Last but not the least, I would like to thank my friends and family for the support and
encouragement they have given me during the course of our work.

With Regards
Nitin Kumar (AJU/211546)
Roll no. 39 (MCA)

5
 Table of Contents

CH:- 1 : INTRODUCTION........................................................................................................................... 8

1.1 BACKGROUND ............................................................................................................................... 8

1.2 OBJECTIVES ................................................................................................................................... 8
1.3 SCOPE............................................................................................................................................... 8

CH:-2- SURVEY OF TECHNOLOGIES .................................................................................................... 9

2.1. HTML ................................................................................................................................................ 9

2.2. CSS .................................................................................................................................................... 9
2.3. JAVA SCRIPT ................................................................................................................................ 10
2.4. BOOTSTRAP.................................................................................................................................. 10
2.5. PHP.................................................................................................................................................. 10
2.6. MYSQL ........................................................................................................................................... 11
2.7. XAMPP ........................................................................................................................................... 11
2.8. SURVEY ......................................................................................................................................... 11

CH:- 3: REQUIREMENTS AND ANALYISE PROBLEM .................................................................... 12

3.1 PROBLEM DEFINITION............................................................................................................... 12

3.2 DRAWBACKS OF EXISTING SYSTEM ...................................................................................... 12
3.3 PROPOSED SYSTEM .................................................................................................................... 13
3.4 BENEFITS OF THE EXISTING SYSTEM .................................................................................... 13
3.5 FEASIBILITY REPORT................................................................................................................. 13
3.6 ER DIAGRAM ................................................................................................................................ 15
3.7 DATA FLOW DIAGRAM (DFD) .................................................................................................. 16
3.8 NORMALISATION ........................................................................................................................ 18

CH:-4: SYSTEM DESIGN .......................................................................................................................... 23

4.1 DATA INTEGRITY ........................................................................................................................ 23

4.2 DATA DICTIONARY .................................................................................................................... 24

CH-5: IMPLEMENTATION AND TESTING ......................................................................................... 29

5.1 IMPLEMENTATION ..................................................................................................................... 29

5.2 TESTING ........................................................................................................................................ 29

6
 5.2.1 UNIT TESTING :- ....................................................................................................................... 30
5.2.2 BETA TESTING:- ....................................................................................................................... 30
5.2.3 ALPHA TESTING:- .................................................................................................................... 30

CH-6: VALIDATION CHECK .................................................................................................................. 31

6.1 TEST-CASE .................................................................................................................................... 31

6.2 OUTPUT SCREENSHOT............................................................................................................... 34
6.3 CODING ......................................................................................................................................... 48

CH:-7: CONCLUSION................................................................................................................................ 50

7.1 LIMITATIONS ............................................................................................................................... 50

7.2 FUTURE SCOPE ............................................................................................................................ 50
7.3 REFERENCES ................................................................................................................................ 51

7
 CH:- 1 : INTRODUCTION

1.1 BACKGROUND

Electronic commerce, commonly known as e-commerce, is the buying and selling of product or service
over electronic systems such as the Internet and other computer networks. Electronic commerce draws on
such technologies as electronic funds transfer, supply chain management, Internet marketing, online
transaction processing, Electronic Data Interchange (EDI), inventory management systems, and automated
data collection systems.

Modern electronic commerce typically uses the World Wide Web at least at one point in the transaction’s
life-cycle, although it may encompass a wider range of technologies such as e-mail, mobile devices and
telephones as well.

1.2 OBJECTIVES

The main objective of this website is to develop a web based interface for users, the website would be
easy to use and hence the shopping experience pleasant for the users. The main goal of this website is:
1). To develop an easy to use web based interface where users can search for products, view a
complete description of the product and order the product.
2). The main objective of the online ”E COMMERCE” is to manage the details of Shopping,
Category, Product, Internet, Customer, Delivery System , order, shopping cart.
3). The project is totally built at administrative end and thus only administrator is guaranteed access.

1.3 SCOPE

Our designed online shopping system provides the 24×7 service that is customers can surf the website,
place orders anytime they wish to. Also, the delivery system works for 24×7 hours a week. Then some
delivery persons can perform their work. This will be add on benefit for the customers as it will save
their time, plus its add on for the shopkeepers also, as people will continue to shop from local shops
rather than preferring to super markets every time.
Else the shopkeeper can ask the customer that the product will be available by next day, so if he/she
still wants to place the order, it can be done. Again return or exchange will be easy since the delivery
boy can even do it as the store is nearby.

8
 CH:-2- SURVEY OF TECHNOLOGIES

To make the website of ECART, I have used the platform of Visual Studio Code.

Some softwares and programming languages used in making this project are:

FRONT-END
1.) HTML
2.) JAVA SCRIPT
3.) CSS

TOOLS
1.) VISUAL STUDIO CODE

BACK-END
1.) PHP
2.) MYSQL

FRAMEWORK
1.) BOOTSTRAP
2.) FONT-AWESOME

2.1. HTML

Hypertext Mark-up Language (HTML) is the standard mark-up for documents designed to be displayed
in a web browser. It can be assisted by technologies such as Cascading Style Sheets (CSS) and
scripting languages such as JavaScript.

Web browsers receive HTML documents from a web server or from local storage and render the
documents into multimedia web pages. HTML describes the structure of a web page semantically and
originally included cues for the appearance of the document.

2.2. CSS

Cascading Style Sheets (CSS) is a style sheet language used for describing the presentation of a
document written in a mark-up language like HTML. CSS is a cornerstone technology of the World
Wide Web, alongside HTML and JavaScript.

9
CSS is designed to enable the separation of presentation and content, including layout, colours, and
[Link] separation can improve content accessibility, provide more flexibility and control in the
specification of presentation characteristics, enable multiple web pages to share formatting by
specifying the relevant CSS in a separate .css file, and reduce complexity and repetition in the
structural content.

2.3. JAVA SCRIPT

JavaScript often abbreviated as JS, is a programming language that conforms to the ECMAScript
specification. JavaScript is high-level, often just-in-time compiled, and multi-paradigm. It has curly-
bracket syntax, dynamic typing, prototype-based object-orientation, and first-class functions. Alongside
HTML and CSS, JavaScript is one of the core technologies of the World Wide Web. JavaScript enables
interactive web pages and is an essential part of web applications. The vast majority of websites use it
for client-side page behavior, and all major web browsers have a dedicated JavaScript engine to
execute it.

2.4. BOOTSTRAP

Bootstrap is a free and open-source CSS framework directed at responsive, mobile-first front-end web
development. It contains CSS- and JavaScript-based design templates for typography, forms, buttons,
modals navigation, and other interface components. It includes HTML and CSS based design templates
for typography, forms, buttons, tables, navigation, modals, image carousels, etc. It also gives you
support for JavaScript plugins.

2.5. PHP

PHP is a popular general-purpose scripting language that is especially suited to web development. It
was originally created by Ramos Leadoff in 1994 the PHP reference implementation is now produced
by The PHP Group. PHP originally stood for Personal Home Page, but it now stands for the recursive
initialize PHP: Hypertext Pre-processor.

PHP code is usually processed on a web server by a PHP interpreter implemented as a module, a
daemon or as a Common Gateway Interface (CGI) executable. On a web server, the result of the
interpreted and executed PHP code – which may be any type of data, such as generated HTML or
binary image data – would form the whole or part of a HTTP response.

10
2.6. MYSQL

MySQL ("My S-Q-L") is an open-source relational database management system (RDBMS). Its name
is a combination of "My", the name of co-founder Wideness’s daughter, and "SQL", the abbreviation
for Structured Query Language. MySQL is free and open-source software under the terms of the GNU
General Public License, and is also available under a variety of proprietary licenses. MySQL was
owned and sponsored by the Swedish company MySQL AB, which was bought by Sun Microsystems
(now Oracle Corporation). In 2010, when Oracle acquired Sun, Widenius forked the open-source
MySQL project to create Maria DB.

2.7. XAMPP

XAMPP is an easy to install Apache distribution containing MySQL, PHP , perl. XAMPP stands for
Cross- Platform (X), Apache (A), MySQL (M), PHP (P) and Perl (P). It is a simple, lightweight Apache
distribution that makes it extremely easy for developers to create a local web server for testing
purposes. XAMPP is also cross-platform, which means it works equally well on Linux, Mac and
Windows. XAMPP is an open source software developed by Apache friends. The use of XAMPP is to
test the clients or your website before uploading it to the remote web server. This XAMPP server
software gives you the suitable environment for testing MYSQL, PHP, Apache and Perl projects on the
local computer

2.8. SURVEY

We have been to many stores, retail shops, to understand their process of maintaining database and level
of efficiency they have in their system and drawbacks of their existing systems.
After visiting many such centers and stores we thought of developing a website which will overcome the
drawbacks of the existing systems.
This would help them to manage their data and provide fast services to customer and customers can also
order their products according to their needs of their favorite brand, color, size, etc.

11
 CH:- 3: REQUIREMENTS AND ANALYISE
PROBLEM

Analysis specifies what the software should do. Analysis is the process of gathering and interpreting
facts, diagnosing problems and using the information to recommend improvements to the system.

Analysis is a detailed study of various operations performed by a system and their relationships within
and outside the system. During analysis, data are collected on the available files, decision points and
transaction handled by the present system.

7.1 PROBLEM DEFINITION

We are going to build a software automation system that will have several features:-
Product management
Pre order booking
Customer management
Accounting
Executive information system

Future plan to add/modify:-

Some of the features that can be modified and added to this system in future involve its implementation
by local shopkeepers, where shops will be providing an online interface to customers for shopping and
placing orders.
1.) Then some delivery persons can perform their work. This will be add on benefit for the
customers as it will save their time, plus it’s add on for the shopkeepers also, as people will
continue to shop from local shops rather than preferring to super markets every time.
2.) Including a chat box for public benefit is also a great idea via which people can directly have a
conversation with some officials regarding any type of queries.

7.2 DRAWBACKS OF EXISTING SYSTEM

1.) It is a time consuming job because the work is done manually i.e. the storing of information.
2.) Since it requires operating manually hence consumes manpower.
3.) Quick generation of information is not possible.
4.)No data consistency is there.

12
 5.) Lack of data security.
6.) High implementation cost.
7.) Data redundancy

7.3 PROPOSED SYSTEM

To overcome all the drawback of the existing system, an automated system is required, which fulfills
all the requirements of the end users. This software provides a facility store the information about the
stock details.

7.4 BENEFITS OF THE EXISTING SYSTEM

• Redundancy of data is reduced at high level.

• Saves time.
• Reduces manual work.
• Quick Generation of report on time.
• Provides data security.

7.5 FEASIBILITY REPORT

The feasibility report of project “ECART” is made to determine that the project is worth doing and
we can go ahead with the data and facts. After configuring the problem faced in current system we
came to know that the major problem is time. The current system consumes lots of user’s time and
with growth in the size of database, its maintenance also become difficult. The major problem found
with the current system is its less flexibility in sharing data. If one system is accessing the data the
other system is unable to access that data. To overcome these problems “ECART” is proposed.

The following types of feasibility study were conducted:

1.) ECONOMICAL FEASIBILTY

Within economical feasibility study we determined the effectiveness of the proposed system.
Though, the proposed system is expensive than the current system but it’s a one time and its
maintenance charges are also very less as compared to the maintenance charges of the current
system.

13
2.) TECHNICAL FEASIBILTY
Within technical feasibility study we determined the equipment and software requirement of the
system. Since, the system would be a distributed system, multiple users can access the system at
the same time but there will certain restriction on each user. Only the admin user will have no
restrictions. He can implement the restrictions on different users and register other users.

3.) OPERATIONAL FEASIBILITY

This system is user friendly. This system will reduce most of the paper work resulting in
improvement of quality of work.
The system can make time available to staff & teachers for more productive activities
instead of record keeping. The system will assist management in decision-making since it
generates useful reports that give more accurate information. The system can make time available
to staff & teachers for more productive activities. The system can make time available to staff &
teachers for more productive activities instead of record keeping. The program maintenance and
modification cost is almost nil. So the system under development is operationally feasible.

4.) MANAGEMENT FEASIBILITY

Within management feasibility we found that the major problem of multi-sharing of data is
possible to solve completely.
The current system fails in sharing the data in more than two or three system but the proposed system
is capable in multi-sharing of data.

14
7.6 ER DIAGRAM

15
7.7 DATA FLOW DIAGRAM (DFD)

16
17
7.8 NORMALISATION

NORMALISATION LEVEL 0

Colunm name Data type Key contraints extra

adminId int(11) Primary Key NOT auto_increment

NULL
username varchar(40) NOT NULL
password Varchar(40) NOT NULL
categoryId Int(11) Primary Key NOT auto_increment
NULL
categoryname Varchar(100) NOT NULL
subcategoryId Int(11) Primary Key NOT auto_increment
NULL
subcategoryNam e Varchar(100) NOT NULL
ProductId Int(10) Primary Key NOT auto_increment
NULL
productName Varchar(200) NOT NULL
price Int(10) NOT NULL
discount Int(10) NOT NULL
actualPrice Int(10) NOT NULL
Quantity Int(10) NOT NULL
Photo Varchar(500) NOT NULL
frontDisplay Int(11) NOT NULL

Description Varchar(500) NOT NULL

userId Int(11) Primary Key NOT auto_increment
NULL
Email Varchar(40) NOT NULL
customerId Int(11) Primary Key NOT auto_increment
NULL
firstName Varchar(40) NOT NULL
lastName Varchar(40) NOT NULL
Address Varchar(40) NOT NULL
City Varchar(40) NOT NULL
postalCode Varchar(40) NOT NULL

18
phoneNumber Varchar(40) NOT NULL
OrdereId Int(11) Primary Key NOT auto_increment
NULL
totalAmount Int(11) NOT NULL
discountPercent Int(11) NOT NULL
discountAmount Int(11) NOT NULL
payableAmount Int(11) NOT NULL
orderDetailsId Int(11) Primary Key NOT auto_increment
NULL
ProductPrice Int(11) NOT NULL
auxId Int(11) Primary Key NOT auto_increment
NULL
aboutUsContent Text NOT NULL
deliveryContent Text NOT NULL

NORMALISATION LEVEL 1

COLUMN NAME DATA TYPE KEY CONSTRAINTS EXTRA

adminID Int(11) Primary Key NOT NULL auto_increment

username Varchar(40) NOT NULL

password Varchar(40) NOT NULL

Category Table
Column Name Data Type key Constraints Extra

categoryId int(11) NOT NULL Auto_increment

categoryName Varchar(100) NOT NULL

Subcategory Table
Column Name Data Type key Constraints Extra

subcategoryId int(11) Primary Key NOT NULL auto increment

categoryId int(11) NOT NULL

subcategoryName Varchar(100) NOT NULL

Products Description Table

Colunm name Data type Key contraints extra

19
 ProductId Int(10) Primary Key NOT NULL auto_increment

categoryname Varchar(100) NOT NULL

subcategoryName Varchar(100) NOT NULL
productName Varchar(200) NOT NULL
price Int(10) NOT NULL
discount Int(10) NOT NULL
actualPrice Int(10) NOT NULL
Quantity Int(10) NOT NULL
Photo Varchar(500) NOT NULL
frontDisplay Int(11) NOT NULL
Description Varchar(500) NOT NULL

Order Table
Colunm name Data type Key contraints extra

OrdereId Int(11) Primary Key NOT auto_increment

NULL
customerId Int(11) Primary Key NOT auto_increment
NULL
totalAmount Int(11) NOT NULL
discountPercent Int(11) NOT NULL
discountAmount Int(11) NOT NULL
payableAmount Int(11) NOT NULL

Auxiliary Table
Colunm name Data type Key contraints extra

auxId Int(11) Primary Key NOT auto_increment

NULL
aboutUsContent Text NOT NULL
deliveryContent Text NOT NULL
Normalisation level 2

Customer Login Table

COLUMN NAME DATA TYPE KEY EXTRA
CONSTRAINTS

userId Int(11) Primary Key NOT auto_increment

NULL

20
username varchar(40) NOT NULL
Email Varchar(40) NOT NULL
password Varchar(40) NOT NULL

Customers Table
COLUMN NAME DATA TYPE KEY EXTRA
CONSTRAINTS

customerId Int(11) Primary Key NOT auto_increment

NULL
firstName Varchar(40) NOT NULL
lastName Varchar(40) NOT NULL
Address Varchar(40) NOT NULL
City Varchar(40) NOT NULL
postalCode Varchar(40) NOT NULL
phoneNumber Varchar(40) NOT NULL
Email Varchar(40) NOT NULL

Products Description Table

Colunm name Data type Key contraints extra

ProductId Int(10) Primary Key NOT NULL auto_increment

categoryname Varchar(100) NOT NULL
subcategoryName Varchar(100) NOT NULL
productName Varchar(200) NOT NULL
price Int(10) NOT NULL
discount Int(10) NOT NULL
actualPrice Int(10) NOT NULL
Quantity Int(10) NOT NULL
Photo Varchar(500) NOT NULL
frontDisplay Int(11) NOT NULL
Description Varchar(500) NOT NULL

Order Table
Colunm name Data type Key contraints extra

OrdereId Int(11) Primary Key NOT auto_increment

NULL

21
customerId Int(11) Primary Key NOT auto_increment
NULL
totalAmount Int(11) NOT NULL
payableAmount Int(11) NOT NULL

Order Detail Table

Colunm name Data type Key contraints extra

orderDetailsId Int(11) Primary Key NOT auto_increment

NULL
OrdereId Int(11) Primary Key NOT auto_increment
NULL
ProductId Int(10) Primary Key NOT auto_increment
NULL
Quantity Int(10) NOT NULL
ProductPrice Int(11) NOT NULL

Interaction Table
Colunm name Data type Key contraints extra

OrdereId Int(11) Primary Key NOT auto_increment

NULL

customerId Int(11) Primary Key NOT auto_increment

NULL

22
 CH:-4: SYSTEM DESIGN
A system design includes business process design and database design. Business process design
implement the order of various function and links between the various functions. Data base design
mainly realize data table and the relationship between data table.

Data design

Data conceptual design phase .the entity relationship can be used to established the data model to form
and ER graph model independent of the machine and DBMS. ER diagram provides entities, properties
and associated method in the order to describing the conceptual model of the real world the basic
element of ER diagram are constituted by entities, attributes and links.

The representation is as following entity types:

It is expressed by rectangle. The entity name is written in the rectangle.

Attribute – it is express by oval and link with the corresponding entity by line. Multivalve attributes is
connected by the two – lane .line is added under the name of the make attribute.

Contact – it is express by the diamond and linked with the corresponding entity by line .the contact
name is written in the diamond box. The contact type is written nearby the line.

4.1 DATA INTEGRITY

Data integrity refers to the fact that data must be reliable and accurate over its entire lifecycle. Data
integrity and data security go hand in hand, even though they’re separate concepts. Uncorrupted data
(integrity) is considered to be whole and then stay unchanged relative to that complete state.

Data is expected to be:

1. Attributable – Data should clearly demonstrate who observed and recorded it, when it was
observed and recorded, and who it is about.
2. Legible – Data should be easy to understand, recorded permanently and original entries
should be preserved.

23
 3. Contemporaneous – Data should be recorded as it was observed, and at the time it was executed.

4.2 DATA DICTIONARY

24
25
26
27
28
 CH-5: IMPLEMENTATION AND TESTING

5.1 IMPLEMENTATION

After having a user acceptance of the new system develop the implement face began implementation
each the stage of the project during which theory is turn into practice during this phase all the program
of the system are loaded into the user computer After loading the system training of the user start main
topic of the such type of training are:-

• How to execute the package

• How to enter the data

• How to process

• How to take out the reports

5.2 TESTING

Testing provide and interesting anomaly for software engineer during earlier software engineering
activity the engineer create a series of test that are intended to demolish the software has been build in
fact testing is a software process that could be viewed as designative rather the constructive testing
required that the developer discard pre conceive notation of the correctness of software just developed
and overcome a conflict of interest that occur when error are uncovered. The testing phase of our
module in this we test our project with some dummy data In order to retrieve the progression of our
report functioning of the control we included in our project.

Testing should have these features:-

1. Testing should began in small and progress toward testing in the large.

2. To be most effective testing should be conducted by an independent third party.

3. All test should be traceable to customer requirement.

29
5.2.1 Unit Testing :-

It focus verification effort in the smallest unit of software design , software component or module using
the component level design description as a guide important control path are tested to uncovered error
within the boundary of the module.
It is a systematic technique for constructing the program structure while at the same time conducting
test to uncover error associated with interfacing. The objective is to take unit tested component and
build the program structure that has been dictated by design.

5.2.2 Beta testing:-

Beta testing come after alpha testing and can be considered a form of external user acceptance testing.
Version of the software it known as beta version, are realized to a limited version outside of the
programming team the software is realized to group of people so that further testing can insure the
product has few fault or bugs, some time beta version are made available to the open public to increase
the feedback field to a maximal number of future user.

5.2.3 Alpha testing:-

Alpha testing is simulated or actual operational testing by potential user or an in depended testing team
at the developer site. Alpha is often employee for of the shelf software as a form of internal acceptance
testing before a software goes to beta testing.

30
 CH-6: VALIDATION CHECK
The basic objective of the requirement validation activity is to ensure that ECART reflects the actual
requirements accurately and clearly. Checking data for appropriateness and accuracy is called
validating. Data entry checks can be built into the database packages to present invalid data from being
entered. For instance, in database, format checking (determining if data are in the correct format) is
done automatically because at the time of creating a database file. Range checking (determining if the
data fall within an accept able range and accuracy checking (making sure that an entry is possible) can
be built by writing a simple programing database.

6.1 TEST-CASE

Test Test Pre steps Input data Expected Actual Staus

Case Scenario requidle Output Output
ID
TC_01 Check Testfiled 1Select P:sarthak User As PASS
customer & Number plain text K:12345 should expected
login with filed [Link] login into
valid data should be numeric application
enable key
TC_02 Check Testfiled 1Select P:sartak User Error Fail
customer & Number plain text K:1234 should
login with filed [Link] 5 login into
invalid data should be numeric application
enable key
No special [Link]
charater special
charater
TC_03 Check Testfiled 1Select P:sarthak User As PASS
Members & Number plain text K:12345 should expected
login with filed [Link] login into
valid data should be numeric application
enable key
TC-04 Check Testfiled 1Select P:sartak User Error FAIL
Members & Number plain text K:1234 should
login with filed [Link] 5 login into
invalid data should be numeric application
enable key

31
TC-05 Check Testfiled 1Select P:sarthak User As PASS
Admin login & Number plain text K:12345 should Expected
with valid filed [Link] login into
data should be numeric application
enable key
TC-06 Check Testfiled 1Select P:sarthak User Error FAIL
Admin login & Number plain text K:12345 should
with invalid filed [Link] login into
data should be numeric application
enable key
TC-07 Check order Testfiled 1Select P:sarthak User As PASS
with valid & Number plain text K:12345 should Expected
data filed [Link] login into
should be numeric application
enable key
TC-08 Check order Testfiled 1Select P:sarthak User Error FAIL
inventory & Number plain text K:12345 should
without filed [Link] login into
valid data should be numeric application
enable key
TC-09 Check Testfiled 1Select P:sarthak User As PASS
login & Number plain text K:12345 should Expected
inventory filed [Link] login into
with valid should be numeric application
data enable key
TC-10 Check order Testfiled 1Select P:sarthak User Error FAIL
inventory & Number plain text K:1235 should
with invalid filed [Link] login into
data should be numeric application
enable key
TC-11 Check user Testfiled 1Select P:sarthak User As PASS
profile with & Number plain text K:12345 should Expected
valid data filed [Link] login into
should be numeric application
enable key
TC-12 Check user Testfiled 1Select P:sarthak User Error FAIL
profile with & Number plain text K:12345 should
invalid data filed [Link] login into
should be numeric application
enable key
TC-13 Check user Testfiled 1Select P:sarthak User As PASS
profile with & Number plain text K:12345 should Expected
valid data filed [Link] login into
should be numeric application
enable key

32
TC-14 Check user Testfiled 1Select P: sartak User Error FAIL
profile with & Number plain text K:12345 should
invalid data filed [Link] login into
should be numeric application
enable key

33
6.2 OUTPUT SCREENSHOT

my-cart

database of our project

homepage

34
 signin-signup

product-category

35
 my-cart

Payment methods

36
order-history

search-result

37
order-track

38
Admin/User-log

Admin/category

39
Admin/change-password

40
Admin/insert-product

Admin/index

41
Admin/Manage-users

42
Admin/change-passsword

43
Admin/update-order-after

Admin/update-order-before

44
Admin/todays-orders

45
Admin/manage-products

46
Admin/subcategory

Admin/manage-users

47
6.3 CODING

[Link]

<?php
session_start();
error_reporting(0);
include('includes/[Link]');
$cid=intval($_GET['cid']);
if(isset($_GET['action']) && $_GET['action']=="add"){
$id=intval($_GET['id']);
if(isset($_SESSION['cart'][$id])){
$_SESSION['cart'][$id]['quantity']++;
}else{
$sql_p="SELECT * FROM products WHERE id={$id}";
$query_p=mysqli_query($con,$sql_p);
if(mysqli_num_rows($query_p)!=0){
$row_p=mysqli_fetch_array($query_p);
$_SESSION['cart'][$row_p['id']]=array("quantity" => 1, "price" => $row_p['productPrice']);
header('location:[Link]');

48
 }else{
$message="Product ID is invalid";
}
}
}
if(isset($_GET['pid']) && $_GET['action']=="wishlist" ){
if(strlen($_SESSION['login'])==0)
{
header('location:[Link]');
}
else
{
mysqli_query($con,"insert into wishlist(userId,productId) values('".$_SESSION['id']."','".$_GET['pid']."')");
echo "<script>alert('Product aaded in wishlist');</script>";
header('location:[Link]');
}
}
?>
<!DOCTYPE html>
<html lang="en">
<head>
<!-- Meta -->
<meta charset="utf-8">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<meta name="viewport" content="width=device-width, initial-scale=1.0, user-scalable=no">
<meta name="description" content="">
<meta name="author" content="">
<meta name="keywords" content="MediaCenter, Template, eCommerce">
<meta name="robots" content="all">

<title>NS Mart | Product Category</title>

<!-- Bootstrap Core CSS -->

<link rel="stylesheet" href="assets/css/[Link]">

<!-- Customizable CSS -->

<link rel="stylesheet" href="assets/css/[Link]">
<link rel="stylesheet" href="assets/css/[Link]">
<link rel="stylesheet" href="assets/css/[Link]">
<link rel="stylesheet" href="assets/css/[Link]">
<!--<link rel="stylesheet" href="assets/css/[Link]">-->
<link href="assets/css/[Link]" rel="stylesheet">
<link rel="stylesheet" href="assets/css/[Link]">
<link rel="stylesheet" href="assets/css/[Link]">
<link rel="stylesheet" href="assets/css/[Link]">

<!-- Demo Purpose Only. Should be removed in production -->

<link rel="stylesheet" href="assets/css/[Link]">

49
 CH:-7: CONCLUSION
Ecommerce developed using Sublime Text 3 and XAMPP-MySQL fully meets the objectives of the
system for which it has been developed. The system has reached a steady state where all bugs have been
eliminated. The system is operated at a high level of efficiency and all teachers and users associated
with the system understand its advantage. The system solves the problem- it was intended to solve as
requirement specification. The system is user friendly and easy to maintain.

7.9 LIMITATIONS

Every project has some limitations like in our project are also having some kinds of limitations.
Like we don’t password encrypt option. We don’t have map option. User don’t have rating options aur
message sending option which are needed to be done.

The ECOMMERCE is developed using Sublime Text 3 and XAMPP-MySQL fully meets the
objectives of the system for which it has been developed. The system has reached a steady state where
all bugs have been eliminated. The system is operated at a high level of efficiency and all teachers and
users associated with the system understand its advantage.

7.10 FUTURE SCOPE

Future scope of the project circle around maintaining information regarding:-

1.) We can give more advance for online shopping including more facilities.
2.) We will host the platform on online servers to make it accessible worldwide.
3.) Integrate multiple load balancers to distribute load of the systems.
4.) Create the master and slave database structure to reduce the the load of the database structure.
5.) Implement the backup mechanism for taking backup of codebase and database on regular basis on
different servers.

50
 CH :-8 : REFERENCES

1. [Link]

2. [Link]

3. [Link]

4. [Link]

5. [Link]

6. [Link]

7. [Link]

8. Head first with PHP(Lynn Beighley and Michael Morrison)

9. Learn HTML and CSS faster(Mark Myers)

10. Wikipedia

51