Chapter PageNo

1. INTRODUCTION

1.1 SYSTEM SPECIFICATION

1.1.1 HARDWARE CONFIGURATION

1.1.2 SOFTWARE SPECIFICATION

2. SYSTEM STUDY

2.1 EXISTING SYSTEM

2.1.1 DESCRIPTION

2.1.2 DRAWBACKS

2.2 PROPOSED SYSTEM

2.2.1 DESCRIPTION

2.2.2 FEATURES

3. SYSTEM DESIGN AND DEVELOPMENT

3.1 FILE DESIGN

3.2 INPUT DESIGN

3.3 OUTPUT DESIGN

3.4 CODE DESIGN

3.5 DATABASE DESIGN

3.6 SYSTEM DEVELOPMENT

3.6.1 DESCRIPTION OF MODULES

4. TESTINGAND IMPLEMENTATION

5. CONCLUSION

6. BIBLIOGRAPHY
APPENDICES

A. DATA FLOW DIAGRAM

B. TABLE STRUCTURE

C. SAMPLE CODING

D. SAMPLE INPUT

E. SAMPLE OUTPUT
ABSTRACT
 ABSTRACT
Online Shopping Portal in PHP is a web-based application. E-commerce is fast

gaining ground as an accepted and used business paradigm. More and more business houses

are implementing websites providing functionality for performing commercial transactions

over the web. It is reasonable to say that the process of shopping on the web is becoming

commonplace. The objective of this project is to develop a general-purpose e-commerce store

where any product (such as books, CDs, computers, mobile phones, electronic items, and home

appliances) can be bought from the comfort of home through the Internet.
INTRODUCTION
 1. INTRODUCTION
E-commerce is fast gaining ground as an accepted and used business paradigm. More and more
business houses are implementing web sites providing functionality for performing commercial
transactions over the web. It is reasonable to say that the process of shopping on the web is
becoming commonplace. ‘Customer is our god’ mainly this website is based on this formula.
After chosen items he bought into Pay pal process like VISA or MASTER credit cards or any
Debit cards are accepted in this website. Customer is happily shopping at his rest place.
Once customer entered with his own username and password, at that time automatically one
shopping cart will be created, once user select an item it will add to cart. In case user thinks the
selected item is not useful for me, then deleted that item from shopping cart. Customer selected
some items, but in his credit or debit cart haven’t that much balance, then he was logout from the
website, the selected items are stored at cart with specific users with his allotted carts, after some
days he bought those items then automatically deleted from the cart.

1.1 SYSTEM SPECIFICATION

1.1.1 HARDWARE CONFIGURATION

1. Pentium IV Processor

2. 512 MB RAM

3. 40GB HDD

4. 1024 * 768 Resolution Color Monitor

1.1.2 SOFTWARE SPECIFICATION
1. OS : Windows XP

2.PHP (PHP5.6, MySQL, Apache, and PhpMyAdmin)

SYSTEM STUDY
2. SYSTEM STUDY

2.1 EXISTING SYSTEM

2.1.1 DESCRIPTION

Existing system is a manual one in which users are maintaining books to store the information
like product details, purchases, sales details and accounts for every month. It is very difficult
to maintain historical data.
In the existing scenario, e-commerce has become an integral part of the business landscape,
and numerous online shopping platforms operate to facilitate commercial transactions over the
internet. However, the specific characteristics of these systems vary widely. Some existing
systems may lack the flexibility to accommodate a diverse range of products effectively.
Additionally, user interfaces might be outdated, impacting user experience and potentially
hindering the growth of online businesses. Transaction security, comprehensive product
details, and efficient order management are areas where certain systems may fall short.
.2.1.2 DRAWBACKS
The following are the disadvantages of the existing system
• It is difficult to maintain important information in books.
• More manual hours need to generate required reports.
• It is tedious to manage historical data which needs much space to keep all the previous
years’ ledgers, books etc.
• Daily sales and purchases details must be entered into booksare very difficult to maintain.
2.2 PROPOSED SYSTEM

2.2.1 DESCRIPTION

The proposed Online Shopping Portal in PHP is designed to address the limitations of
the existing systems, offering a dynamic and versatile e-commerce solution. This system aims
to provide users with a seamless and secure online shopping experience while incorporating a
broad spectrum of products. It leverages PHP technology to create a robust and flexible
platform that caters to the evolving needs of the digital marketplace.
2.2.2 FEATURES

The key features of the proposed Online Shopping Portal include:

Versatile Product Diversity: The system supports a wide range of products, ensuring
a diverse and comprehensive shopping experience for users.
• Modern User-Friendly Interface: A contemporary and user-centric design enhances
the overall user experience, making navigation intuitive and enjoyable.
• Secure Online Transactions: The system employs robust security measures to ensure
the safety of user data and financial transactions.
• Detailed Product Information and Reviews: Comprehensive product details and user
reviews empower customers to make well-informed purchase decisions.
• Efficient Order Management: The system integrates streamlined order processing,
reducing errors and ensuring timely and accurate order fulfillment.
• User Account Management: Customers can create accounts for personalized
experiences, order tracking, and a seamless shopping journey.
• Search and Filtering Capabilities: Robust search and filtering options empower users
to find specific products efficiently based on their preferences.
SYSTEM DESIGN AND DEVELOPMENT
 3. SYSTEM DESIGN AND DEVELOPMENT

3.1 FILE DESIGN

In the file design phase, we outline the structure and organization of files
within the project. This includes determining which files will contain the
code, configuration settings, templates, stylesheets, and any other necessary
resources.

PROJECT STRUCTURE:

index.php: Main entry point of the application.

config.php: Configuration file for database connection and other

settings.

/css: Directory containing CSS files for styling.

/js: Directory containing JavaScript files for frontend functionality.

/images: Directory for storing images used in the application.

3.2 INPUT DESIGN

Input design involves designing the user interfaces for data input. This
includes forms for user registration, product search, adding items to the
shopping cart, and entering payment information during checkout.

Input Forms:

User Registration Form: Collects user information such as name, email,

password, etc.

PRODUCT SEARCH FORM: Allows users to search for products by name,

category, or other criteria.
3.3 OUTPUT DESIGN

Output design focuses on presenting information to the users in a

meaningful and comprehensible manner. This includes designing the layout
and format of pages, product listings, order confirmations, etc.

Output Components:

• Product Listings: Display information about products, including name,

description, price, and images.
• Shopping Cart: Show a summary of items added to the cart with options
for editing quantities or removing items.
• Order Confirmation: Provide users with a confirmation message and order
details after completing a purchase.
• User Account Dashboard: Display user-specific information such as order
history, profile settings, etc.

3.4 CODE DESIGN

Code design involves structuring the backend codebase to ensure modularity, readability,
and maintainability. This includes organizing code into functions, classes, and modules based
on their functionality.

Code Components:

• User Authentication: Functions for user login, registration, and session

management.
• Product Management: Code for retrieving and displaying products,
handling inventory, and managing categories.
• Shopping Cart: Functions for adding, removing, and updating items in the
shopping cart.
3.5 DATABASE DESIGN

Database design involves designing the structure of the database tables and
defining relationships between them to store and manage data efficiently.

Database Tables:

• Users: Stores information about registered users (id, name, email, password,
etc.).
• Products: Contains details of products available for purchase (id, name,
description, price, quantity, etc.).
• Orders: Records information about orders placed by users (id, user_id,
status, total_amount, etc.).
• Order_Items: Stores the relationship between orders and products,
including quantity and price.

3.6 SYSTEM DEVELOPMENT

System development involves implementing the designed system using

the chosen technologies and frameworks. This includes writing code, creating
database tables, integrating frontend and backend components, and testing the
system for functionality and performance.

Development Process:

• Backend Development: Write PHP scripts to handle user

authentication, product management, shopping cart functionality, and order
processing.
• Frontend Development: Develop HTML templates, CSS stylesheets, and
JavaScript code for creating the user interface and implementing interactive
features.
• Database Implementation: Create database tables based on the designed
schema and write SQL queries for data manipulation and retrieval.
• Integration: Integrate frontend and backend components to ensure seamless
communication between the server and the client.
• Testing: Test the system thoroughly to identify and fix any bugs or issues.
Conduct unit tests, integration tests, and user acceptance tests to ensure the
system meets the requirements.
• Deployment: Deploy the application to a web server and configure it for production use.
Ensure proper security measures are in place to protect user data and prevent unauthorized
access

3.6.1 DESCRIPTION OF MODULES

Online Shopping Portal Pro Version Project Modules

This project contains two modules, those are:

• Admin
• User

ADMIN MODULE:

• Dashboard: In this section, the admin can briefly view the total orders, total new orders,
total packed orders, total dispatched orders, total in-transit orders, total out for delivery
orders, total delivered, total canceled, and total registered users.
• Category: In this section, admin can manage category of products(add/update/delete).
• Products: In this section, admin can manage products (add/update/delete).
• Orders: In this section, admin can view the mobile order details and they have also the
right to change order status according to current status.
• Search Order: In this section, admin can search particular order with the help of the order
number.
• Reports: In this section admin can view order details and sales reports according to dates.
• Registered Users: In this section, the admin can view registered users.
TESTING AND IMPLEMENTATION
 4. TESTING AND IMPLEMENTATION
Software testing is a critical element of the ultimate review of specification design and
coding. Testing of software leads to the uncovering of errors in the software functional and
performance requirements are met .Testing also provides a good indication of software
reliability and software quality as a whole. The result of different phases of testing are evaluated
and then compared with the expected results. If the errors are uncovered they are debugged and
corrected. A strategy approach to software testing has the generic characteristics:
Testing

• Testing begins at the module level and works “outwards” towards the integration of the
entire computer based system.
• Different testing techniques are appropriate at different points of time.
• Testing and debugging are different activities, but debugging must be accommodated in
the testing strategy.
GOALS AND OBJECTIVES
“Testing is a process of executing a program with the intent of finding an error”.
A good test case is one that has a probability of finding an as yet undiscovered error. A
successful test is one that uncovers an as yet undiscovered error. Our Objective is to design test
processes that systematically uncover different classes of errors and do so with minimum
amount of time and effort.

STATEMENT OF SCOPE
A description of the scope of the software testing is developed. All the features
to be tested are noted as follows. The basic principles that guides software testing are,
All test cases should be traceable top customer requirements. The most severe defects from the
customer’s point of view are those that cause the program to fail to meet its requirements.
Test case should be planned long before testing begins. Testing plan can begin as soon as the
requirement model is complete. Detailed definition of the test cases can begin as soon as the
design is solidified. Therefore, the entire test can be planned before any code has been
generated.
 • Functional Testing:

User Interface Testing: Ensure that all elements of the user interface (UI) such as buttons,
links, forms, and navigation menus work as expected across different browsers and devices.

Checkout Process Testing:Verify that users can successfully add items to their cart, proceed
through the checkout process, make payments, and receive order confirmation.

Search Functionality Testing:Test the search functionality to ensure accurate results for
product searches, including filters and sorting options.

Product Catalogue Testing: Ensure that product listings display accurate information, images,
prices, and availability status.

• Usability Testing:

Evaluate the user experience (UX) by testing the ease of use, intuitiveness, and accessibility
of the website or mobile app.

Gather feedback from real users through surveys, interviews, or usability testing sessions to
identify areas for improvement.

• Performance Testing:

Load Testing: Determine how the system behaves under normal and peak loads by simulating
a large number of concurrent users accessing the website.

Stress Testing: Evaluate the system's stability and performance under extreme conditions, such
as high traffic or sudden spikes in user activity.Speed Testing:Measure the website's response
time and loading speed to ensure fast and seamless user experience, especially on mobile
devices.

• Security Testing:

Vulnerability Assessment: Identify and mitigate potential security vulnerabilities such as

SQL injection, cross-site scripting (XSS), and cross-site request forgery (CSRF).

Data Encryption Testing:Ensure that sensitive data such as user credentials, payment
information, and personal details are encrypted during transmission and storage.
 • Compatibility Testing:
Test the website or app on different browsers (e.g., Chrome, Firefox, Safari, Edge) and
devices (e.g., desktops, laptops, tablets, smartphones) to ensure cross-platform compatibility.

Verify compatibility with various operating systems (e.g., Windows, macOS, iOS, Android)
and screen resolutions.

• Integration Testing:

Ensure seamless integration with third-party services such as payment gateways, shipping
carriers, inventory management systems, and customer relationship management (CRM) tools.

Test data synchronization and communication between different modules or components of

the system.

• Regression Testing:

Test the system after each update or change to ensure that new features or bug fixes have not
introduced any unintended side effects or regressions.Automate regression tests to save time
and effort during the testing process.

• Accessibility Testing:

Evaluate the website or app's accessibility for users with disabilities, ensuring compliance
with accessibility standards such as WCAG (Web Content Accessibility Guidelines).Test
features such as keyboard navigation, screen reader compatibility, and alternative text for
images.

• Mobile App Testing (if applicable):

Test mobile apps on different devices, operating systems, and screen sizes to ensure
functionality and usability across a variety of platforms.Verify app store compliance and
guidelines for distribution on platforms like the Apple App Store and Google Play Store.

• Localization and Internationalization Testing:

Test the website or app in different languages and regions to ensure proper localization of
content, currency conversion, and support for local payment methods and shipping.
CONCLUSION
 5. CONCLUSION
The package was designed in such a way that future modifications can be done Easily.The
following conclusions can be deduced from the development of the project. In conclusion, the
proposed Online Shopping Portal in PHP emerges as a strategic response to the evolving
landscape of e-commerce, aiming to overcome the limitations inherent in existing systems. The
dynamic nature of online shopping necessitates a platform that is not only versatile but also
user-friendly, secure, and capable of adapting to the diverse needs of consumers.

By addressing the drawbacks of some existing systems, this project introduces a modern and
efficient e-commerce solution. The emphasis on product diversity ensures that users can
explore and purchase a broad range of items, while the contemporary and userfriendly interface
enhances the overall shopping experience.The integration of robust security measures
addresses concerns related to transactional security, instilling confidence in users to conduct
online transactions securely. Detailed product information and customer reviews empower
users to make informed decisions, contributing to a more satisfying shopping journey.

Automation of the entire system improves the efficiency

• It provides a friendly graphical user interface which proves to be better when compared
to the existing system.
• It gives appropriate access to the authorized users depending on their permissions.
• It effectively overcomes the delay in communications.
• Updating of information becomes so easier.
• System security, data security and reliability are the striking features.
• The System has adequate scope for modification in future if it is necessary.
BIBLIOGRAPHY
 6. BIBLIOGRAPHY
The following books were referred during the analysis and execution phase of
the project

PHP and MySQL Web Development

Book by Luke Welling

Head First PHP & MySQL

Book by Lynn Beighley and Michael Morrison

PHP & MySQL for Dummies

Book by Janet Valade

WEBSITES:

• www.google.com
• www.w3schools.com
• www.tutorialspoint.php
• http://stackoverflow.com
APPENDICES
 APPENDICES

A.DATA FLOW DIAGRAM

• The DFD takes an input-process-output view of a system i.e. data objects flow into the
software, are transformed by processing elements, and resultant data objects flow out of
the software.
• Data objects represented by labeled arrows and transformation are represented by circles
also called as bubbles. DFD is presented in a hierarchical fashion i.e., the first data flow
model represents the system as a whole. Subsequent DFD refine the context diagram
(level 0 DFD), providing increasing details with each subsequent level.
• The DFD enables the software engineer to develop models of the information domain &
functional domain at the same time. As the DFD is refined into greater levels of details,
the analyst performs an implicit functional decomposition of the system. At the same
time, the DFD refinement results in a corresponding refinement of the data as it moves
through the process that embody the applications.
• A context-level DFD for the system the primary external entities produce information for
use by the system and consume information generated by the system. The labeled arrow
represents data objects or object hierarchy.
 RULES FOR DFD:

• Fix the scope of the system by means of context diagrams. Organize the DFD so that the
main sequence of the actions Reads left to right and top to bottom.
• Identify all inputs and outputs.
• Identify and label each process internal to the system with Rounded circles.
• A process is required for all the data transformation and Transfers. Therefore, never
connect a data store to a data Source or the destinations or another data store with just a
Data flow arrow.
• Do not indicate hardware and ignore control information.
• Make sure the names of the processes accurately convey everything the process is done.
• There must not be unnamed process.
• Indicate external sources and destinations of the data, with Squares.
• Number each occurrence of repeated external entities.
• Identify all data flows for each process step, except simple Record retrievals.
• Label data flow on each arrow.
• Use details flow on each arrow.
• Use the details flow arrow to indicate data movements.
 ContextDiagram0

Customer

Management

Shopping Payment

Management Management

Shopping

Portal Products
Order

Management
Management

Login

Management
 Context Diagram 1

Shopping
Generate Order
Management
Report

Shopping Cart Generate Sales

Management Report

Shopping wishlist Shopping

Check User Login
Management Portal Details

Generate Category
Product

Management

Generate

Subcategory
Login Management

GenerateProducts

System User

Management
Second Level DFD

Check Manage
Login to
Admin Category
system Roles of
access

Manage Sub
Category

Manage
Products

Forgot Check
Password Credential Manage Order
Details

Generate Order
Report

Manage
Modules Generate Sales
Report

Update Profile

Change
Password
 User
Signup/Lo Check Add to cart

gin to Roles of
system access

Add to wishlist

View Products

Check
Credentia
Forgot
l
Password View Status of order

Manage
Modules
Add Address

Change Profile

Change Password
E-R Diagrams:
The Entity-Relationship (ER) model was originally proposed by Peter in 1976 [Chen76] as a
way to unify the network and relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and relationships. A basic
component of the model is the Entity-Relationship diagram which is used to visually represents
data objects. Since Chen wrote his paper the model has been extended and today it is commonly
used for database design For the database designer, the utility of the ER model is:

it maps well to the relational model. The constructs used in the ER model can easily be
transformed into relational tables.

it is simple and easy to understand with a minimum of training. Therefore, the model can be
used by the database designer to communicate the design to the end user.

In addition, the model can be used as a design plan by the database developer to implement a
data model in a specific database management software.

Connectivity and Cardinality

The basic types of connectivity for relations are: one-to-one, one-to-many, and many-tomany.
A one-to-one (1:1) relationship is when at most one instance of a entity A is associated with
one instance of entity B. For example, "employees in the company are each assigned their own
office. For each employee there exists a unique office and for each office there exists a unique
employee.

A one-to-many (1:N) relationships is when for one instance of entity A, there are zero, one, or
many instances of entity B, but for one instance of entity B, there is only one instance of entity
A. An example of a 1:N relationships is a department has many employees each employee is
assigned to one department

A many-to-many (M:N) relationship, sometimes called non-specific, is when for one instance
of entity A, there are zero, one, or many instances of entity B and for one instance of entity B
there are zero, one, or many instances of entity A. The connectivity of a relationship describes
the mapping of associated
ER Notation

There is no standard for representing data objects in ER diagrams. Each modeling methodology
uses its own notation. The original notation used by Chen is widely used in academics texts
and journals but rarely seen in either CASE tools or publications by nonacademics. Today,
there are a number of notations used, among the more common are Bachman, crow's foot, and
IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of a
connection. The notation used in this document is from Martin. The symbols used for the basic
ER constructs are:

▪ Entities are represented by labeled rectangles. The label is the name of the
entity. Entity names should be singular nouns.
▪ Relationships are represented by a solid line connecting two entities. The
name of the relationship is written above the line. Relationship names should
be verbs
▪ Attributes, when included, are listed inside the entity rectangle. Attributes
which are identifiers are underlined. Attribute names should be singular
nouns.

▪ Cardinality of many is represented by a line ending in a crow's foot. If the

crow's foot is omitted, the cardinality is one.
▪ Existence is represented by placing a circle or a perpendicular bar on the
line. Mandatory existence is shown by the bar (looks like a 1) next to the
entity for an instance is required. Optional existence is shown by placing a
circle next to the entity that is optional
ER DIAGRAM
B. TABLE STRUCTURE

Tables

The data in the system has to be stored and retrieved from database. Designing the database is part of
system design. Data elements and data structures to be stored have been identified at analysis stage.
They are structured and put together to design the data storage and retrieval system.

A database is a collection of interrelated data stored with minimum redundancy to serve many
users quickly and efficiently. The general objective is to make database access easy, quick,
inexpensive and flexible for the user. Relationships are established between the data items and
data and to have minimum redundancy and maximum stability. This ensures minimizing data
storage required, minimizing chances of data inconsistencies and optimizing for updates. The
MySQL database has been chosen for developing the relevant databases.

MySQL Data Tables:

Address Table :
(Table name is addresses)

This table store billing and shipping address of users

Shopping Table :
(Table name is shopping) This table store
shopping details of users.
Category Table :
(Table name is category) This table store the

category of products.
Subcategory Table :
(Table name is subcategory) This table store the subcategory of products.

Orders Table :
(Table name is orders) This table store the

orders of users.
Orders DetailsTable :
(Table name is ordersdetails) This table store the
orders details of users.

Orders Tracking Table :

(Table name is ordertrackhistory) This table store the data
of order tracking history.
ProductsTable:

(Table name is products) This table store

the data of products.

C. SAMPLE CODING

<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width, initial-
scale=1, shrinkto-fit=no" />
<meta name="description" content="" />
<meta name="author" content="" />
<title>Shopping Portal | Product Details</title>
<!-- Favicon-->
<link rel="icon" type="image/x-icon" href="assets/favicon.ico" />
<!-- Bootstrap icons-->
<link href="https://cdn.jsdelivr.net/npm/bootstrap-
[email protected]/font/bootstrapicons.css" rel="stylesheet" />
<!-- Core theme CSS (includes Bootstrap)-->
<link href="css/styles.css" rel="stylesheet" />
</head>
<body>
<!-- Navigation-->
<?php include_once('includes/header.php');?>
<!-- Product section-->

<?php
$pid=intval($_GET['pid']);
$query=mysqli_query($con,"select products.id as
pid,products.productImage1,products.productImage2,products.productImage3,product
s.productName,category.categoryName,subcategory.subcategoryName as
subcatname,products.postingDate,products.updationDate,subcategory.id
assubid,tbladmin.username,category.id as
catid,products.productCompany,products.productPrice,products.productPriceBeforeD
iscount,products.productAvailability,products.productDescription,p
roducts.shippingC harge from products join subcategory on
products.subCategory=subCategory.id join category on
products.category=category.id join tbladmin on
tbladmin.id=products.addedBy where products.id='$pid'");
while($row=mysqli_fetch_array($query))
{

$catid=$row['catid'];

?>

<form name="productdetails" method="post">

<section class="py-5">

<div class="container px-4 px-lg-5 my-5">

<div class="row gx-4 gx-lg-5 align-items-center">

<div class="col-md-6"><img class="card-img-top mb-5 mb-md-

0" src="admin/productimages/<?php echo
htmlentities($row['productImage1']);?>" alt="<?php echo
htmlentities($row['productName']);?>" width="500" height="600"
style="border:solid 1px #000;"/>
<imgsrc="admin/productimages/<?php echo
htmlentities($row['productImage2']);?>" width="291"
style="border:solid 1px #000;">
<imgsrc="admin/productimages/<?php echo
htmlentities($row['productImage3']);?>" width="292"
style="border:solid 1px #000;">

</div>

<div class="col-md-6">

<div class="small mb-1"><strong>Category:</strong><?php echo

htmlentities($row['categoryName']);?></div>
<div class="small mb-1"><strong>Sub-Category:</strong><?php
echo htmlentities($row['subcatname']);?></div>
<h4><?php echo htmlentities($row['productCompany']);?></h4>

<h1 class="display-5 fw-bolder"><?php echo

htmlentities($row['productName']);?></h1>
<div class="fs-5 mb-5">

<span class="text-decoration-line-through">$<?php echo

htmlentities($row['productPriceBeforeDiscount']);?></span>
<span>$<?php echo htmlentities($row['productPrice']);?></span>

<div class="small mb-1"><strong>Shipping/Delivery

Chareges:</strong><?php echo
htmlentities($row['shippingCharge']);?></div>

</div>

<p class="lead"><?php echo

$row['productDescription'];?></p><?php
if($row['productAvailability']=='In Stock'):?>

<div class="d-flex">

<input class="form-control text-center me-3" id="inputQuantity"

name="inputQuantity" type="num" value="1" style="max-width:
3rem" />
<button class="btnbtn-outline-dark flex-shrink-0" type="submit"
name="addtocart">
<i class="bi-cart-fill me-1"></i>

Add to cart

</button>&nbsp;

<button class="btnbtn-outline-dark flex-shrink-0" type="submit"

name="wishlist">
<i class="bi bi-heart"></i>Wishlist </button>

</div>

<?php else: ?>

<h5 style="color:red;">Out of Stock</h5>

<button class="btnbtn-outline-dark flex-shrink-0" type="submit"

name="wishlist">
<i class="bi bi-heart"></i> Wishlist </button>

<?php endif;?>

</div>

</div>

</div>

</section>

</form>

<?php } ?>

<!-- Related items section-->

<section class="py-5 bg-light">

<div class="container px-4 px-lg-5 mt-5">

<h2 class="fw-bolder mb-4">Related products</h2>

<div class="row gx-4 gx-lg-5 row-cols-2 row-cols-md-3 row-cols-

xl-4 justify-content-center">
<?php

$query=mysqli_query($con,"select products.id as
pid,products.productImage1,products.productName,products.prod
uctPriceBeforeDisc ount,products.productPrice from products
where category='$catid' order by piddesc limit 8 "); $cnt=1;
while($row=mysqli_fetch_array($query))
 { ?>

<div class="col mb-5">

<div class="card h-100">

<!-- Product image-->

<img class="card-img-top" src="admin/productimages/<?php

echo htmlentities($row['productImage1']);?>" alt="<?php echo
htmlentities($row['productName']);?>" width="350"
height="300"/>
<!-- Product details-->

<div class="card-body p-4">

<div class="text-center">

<!-- Product name-->

<h5 class="fw-bolder"><?php echo

htmlentities($row['productName']);?></h5>
<!-- Product price-->

<span class="text-decoration-line-through">$<?php echo

htmlentities($row['productPriceBeforeDiscount']);?></span>
<span>$<?php echo htmlentities($row['productPrice']);?></span>

</div>

</div>

<!-- Product actions-->

<div class="card-footer p-4 pt-0 border-top-0 bg-

transparent"><div class="text-center"><a class="btnbtn-outline-
dark mt-auto" href="product-details.php?pid=<?php echo
htmlentities($row['pid']);?>">View options</a></div>
</div>

</div>
</div>

<?php } ?>

</div>

</div>

</section>

<!-- Footer-->

<footer class="py-5 bg-dark">

<div class="container"><p class="m-0 text-center text-

white">Copyright

&copy; Your Website 2021</p></div>

</footer>

<!-- Bootstrap core JS-->

<script src="js/bootstrap.bundle.min.js"></script>

<!-- Core theme JS-->

<script src="js/scripts.js"></script>

</body>

</html>
D. SAMPLE INPUT

HOME PAGE
VIEW SINGLE PRODUCT
 ABOUT US

Contact Us
A.SAMPLE OUTPUT

ADMIN PANEL

LOGIN

FORGOT PASSWORD
 DASHBOARD

ADMIN PROFILE
CHANGE PASSWORD

ADD SUB-ADMIN
MANAGE SUB-ADMIN

UPDATE SUB-ADMIN
RESET SUB-ADMIN PASSWORD

ADD TABLE
MANAGE TABLES

NEW BOOKING
VIEW NEW BOOKING DETAILS

ACCEPTED BOOKINGS
VIEW ACCEPTED BOOKINGS DETAIL

REJECTED BOOKINGS
VIEW REJECTED BOOKINGS DETAILS

BETWEEN DATES REPORT

VIEW BETWEEN DATES REPORT