Project Report

on
Nursery Management System
 ACKNOWLEDGEMENT

I extend my deepest appreciation to my esteemed guide, Mr. XYZ for providing me with
the possibility to complete this project with the right guidance and advice.

Special gratitude I give to my respected head of the division Mr.XYZ, for allowing me to
use the facilities available and also help me to coordinate my project
Furthermore, I would also like to acknowledge with much appreciation the crucial role of
faculty members on this occasion.

Last but not least, I would like to thank friends who help me to assemble the parts and
gave a suggestion about the project.
.

----------------------
 ABSTRACT

The “Nursery Management System” provides convenience for the person who wants to
purchase plants online. It overcomes the disadvantages of the traditional queuing system.
This system increases the take away of plants online. Therefore, this system enhances the
speed and standardization of taking the order from the customer. It provides a better
communication platform. The user’s details are noted electronically.

The “Nursery Management System” set up all details of plants, flowers and seeds online
and the customers easily places the order with a simple mouse click. Also with a order
number user can easily track the orders, maintain customer's database and improve your
plants delivery service. This system allows the user to select the desired plants flowers and
seed from the displayed menu. The user orders the plants flowers and seed. The payment
can be made online or pay-on-delivery system. The user’s details are maintained
confidential because it maintains a separate account for each user. An id and password is
provided for each user. Therefore it provides a more secured nursery ordering.
 Introduction
The Nursery Management System has been designed to override the problem of existing
manual system. This web application is supported to eliminate and in some case reduce the
hardship faced by manual system. The application is reduced as much as possible to avoid
errors while entering the data. It’s also provide message while entering invalid data. No
formal knowledge is required for the user to operate this system. Overall we said that
Nursery Management System is user friendly.

In Nursery Management System we use PHP and MySQL Database. This project keeps
the records of orders, clients and products (Plants, Flower and Seeds). Nursery
Management System has two module i.e. admin and user.

Admin Module
This module provides administrator-related functionalities. The administrator manages the
entire application and maintains the profiles of users and information on products.

Dashboard: In these sections, the admin can briefly view the total registered users, total
products, status of orders and inquiry.
Categories: In this section, the admin can manage categories of products
(add/update/delete).
Products: In this section, admin can manage the products (add/update/delete.
Pages: In this section, admin can manage the about us and contact us pages.
Orders: In this section, admin can view the nursey order details and they have also the
right to change order status according to current status.
Inquiry: In this section, admin can view the inquiry which is sent by users.
Reports: In this section admin can view order details, order counts, and sales reports
according to dates.
Search Order: In this section, admin can search particular order with the help of the order
number.
Reg Users: In this section, the admin can view registered users.
Subscriber: In this section, admin views subscriber mails.
Admin can also update his profile, change the password and recover the password.
User Module

1. Home: It is the welcome page for users who can view products which is available in
nursery.
2. Category: In this section, users can view nursery products according to category.
3. Products: In this section, users can view the nursery products and order that nursery
products after registering.
4. About Us: In this section, user can view about us of a nursery shop.
5. Contact Us: In this section, user can view the contact us of a nursery shop.
6. Cart: In this section, the user can add the nursery products which he/she want to order.
7. Wishlist: In this section, the user can add nursery products to the wishlist.
8. My Profile: In this section, the user can view and change his/her profile.
9. My orders: In this section, users can view order history after login.
10. Setting: In this section, user can change his/her account password.
11. The user has also a facility to download his/her invoice and cancel orders if he/she
wants to cancel.
 OBJECTIVE
The main objective of this project is to develop an application which gives provision
to the nursery owners to flourish their business by uploading products details at no
cost and will invariably lead to higher customer retention and acquisition rates. This
Nursery Management System will definitely reduce the time, energy and money wasted in
manually searching the details of the plants and registered users. With the help of this
software, all the services and users can be properly channelized.

EXISTING SYSTEM
Maintaining critical information in the files and manuals is full of risk and a tedious
process. The present scenario offers manual data entry. A lot of time is wasted in creating
the reports as well as maintaining them. In case, if any query arises to get the information
about the orders, queries and registered users, the whole report is re-typed or xeroxed. This
seriously affects the authentication of the system. This Nursery Management System is
totally outdated and involves high risk of ambiguity and redundancy.

PROPOSED SYSTEM
The proposed system is computerized and has been developed using advance language
therefore it gives more facilities than present system. It provides quick access to any data.
In this system user have to enter the data only once and then it get linked with all files.
This reduces the workload of user and it is also a time saving process. The information
about any Subscriber can be easily retrieved. The system maintains all records easy

Advantages of Proposed System:

❖ All the information about sale, purchase will be maintain

properly in this system.

❖ All manual calculation of sale or all the money

management will beperformed by the computer
automatically.
 ❖ This system will provide timely report information.

❖ It will produce report for sale.

❖ The computer can hold amount of data in its storage device.

❖ The operation and speed of the computer is very high.

❖ We can calculate result and print any report within seconds.

❖ Any difficulties we can solve easily.

❖ A database application can be stored in computer effectively.

❖ It is very user friendly and easy to handle.

So the computerized system is more suitable than the manual system.

 HARDWARE AND SOFTWARE REQUIREMENTS
Hardware Requirement:

 Hardware - Pentium
 Speed - 1.1 GHz
 RAM - 1GB

 Hard Disk - 20 GB

 Key Board - Standard Windows Keyboard

 Mouse - Two or Three Button Mouse

 Monitor - SVGA

Software Requirements:

 Operating System : Windows / Linux / Mac

 Technology : PHP
 Web Technologies : Html, JavaScript, CSS
 IDE : Notepad++
 Web Server : WAMP / XAMPP / LAMP / MAMP (any one)
 Database : My SQL
 DESIGN
INTRODUCTION:
Design is the first step in the development phase for any techniques and principles for the
purpose of defining a device, a process or system in sufficient detail to permit its physical
realization.

Once the software requirements have been analyzed and specified the software design
involves three technical activities - design, coding, implementation and testing that are
required to build and verify the software.

The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its ease of
maintenance are made. These decisions have the final bearing upon reliability and
maintainability of the system. Design is the only way to accurately translate the customer’s
requirements into finished software or a system.

Design is the place where quality is fostered in development. Software design is a process
through which requirements are translated into a representation of software. Software
design is conducted in two steps. Preliminary design is concerned with the transformation
of requirements into data.

UML Diagrams:
Actor:
A coherent set of roles that users of use cases play when interacting with the use `cases.

Use case:

A description of sequence of actions, including variants, that a system performs that yields
an observable result of value of an actor.
UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any product
after analysis. The goal from this is to produce a model of the entities involved in the
project which later need to be built. The representation of the entities that are to be used in
the product being developed need to be designed.

There are various kinds of methods in software design:

They are as follows:

 Use case Diagram

 Sequence Diagram
 Collaboration Diagram
 Activity Diagram
 State chat Diagram

USECASE DIAGRAMS:

Use case diagrams model behavior within a system and helps the developers understand of
what the user require. The stick man represents what’s called an actor.

Use case diagram can be useful for getting an overall view of the system and clarifying
who can do and more importantly what they can’t do.

Use case diagram consists of use cases and actors and shows the interaction between the
use case and actors.
  The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user’s perspective.
 An actor could be the end-user of the system or an external system.

USECASE DIAGRAM:

A Use case is a description of set of sequence of actions. Graphically it is rendered as an

ellipse with solid line including only its name. Use case diagram is a behavioral diagram
that shows a set of use cases and actors and their relationship. It is an association between
the use cases and actors. An actor represents a real-world object. Primary Actor – Sender,
Secondary Actor Receiver.
Admin Use Case Diagram :

Dashboard

Manage Registered
Users

Manage Categories

Add / update/Del

Manage Nursery
Products

Add/ Update
Admin
Manage Enquiry

View Subscriber

Order Management

Report Generation

Update Profile

Change Password
User Use Case Diagram :
Signup

Sign in

Place order

Order Tracking

User

Change Password

Update Profile

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-to-
many. 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 non-
academics. 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

Data Flow Diagram

A data flow diagram is graphical tool used to describe and analyze movement of data
through a system. These are the central tool and the basis from which the other
components are developed. The transformation of data from input to output, through
processed, may be described logically and independently of physical components
associated with the system.

These are known as the logical data flow diagrams. The physical data flow
diagrams show the actual implements and movement of data between people,
departments and workstations.

A full description of a system actually consists of a set of data flow

diagrams. Using two familiar notations Yourdon, Gane and Sarson notation develops
the data flow diagrams. Each component in a DFD is labeled with a descriptive name.
Process is further identified with a number that will be used for identification purpose.

The development of DFD’S is done in several levels. Each process in lower

level diagrams can be broken down into a more detailed DFD in the next level. The
lop-level diagram is often called context diagram.

It consists single process bit, which plays vital role in studying the current
system. The process in the context level diagram is exploded into other process at the
first level DFD.

The idea behind the explosion of a process into more process is that
understanding at one level of detail is exploded into greater detail at the next level.
This is done until further explosion is necessary and an adequate amount of detail is
described for analyst to understand the process.
DFD SYMBOLS:

In the DFD, there are four symbols:

• A square defines a source(originator) or destination of system data

• An arrow identifies data flow. It is the pipeline through which the
information flows
• A circle or a bubble represents a process that transforms incoming data
flow into outgoing data flows.
• An open rectangle is a data store, data at rest or a temporary repository of
data
DFD Zero Level

Customer Category mgmt

Mgmt

Wish list Mgmt Payment

Mgmt

Shopping Cart Order Mgmt

NMS

Enquiry Mgmt
Login Mgmt

Subscriber Product Mgmt

Mgmt
DFD First Level

Category

Product Mgmt
Contact us/ about
us mgmt

Shopping Cart
Mgmt Enquiry Mgmt

Wish list Mgmt Between dates

Report
NMS

Order Mgmt
Sales Report
Mgmt

Login Mgmt Count Report

Mgmt

User Mgmt

Subscriber Mgmt

Search Order
DFD Second Level
Check
Role of
access
Manage category
Admin Login
to
Admin system

Manage Products

Forgot
Passwo Manage Manage Pages
rd modules

Check Manage Orders

creden
tial
Manage Enquiry

Manage
Subscriber

Manage Users

Generate Report

Change Password Update Profile Search Order

 User Signup Check
/Signin Role of Place Orders
User access

Wish list
Products
Forgot
Check Subscribe
Password
credential Manage
Modules Contact

View Orders
history
 Database Design
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 unnecessary data items are removed.

Normalization is done to get an internal consistency of 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.

Nursery Management System (NMS) contains 11 MySQL tables:

tbladmin : This table store the admin login details

tblcategory : This table stores the nursery category

tblcontact: This table stores enquiry detail of users.

tblproducts: This tables stores the nursery details (used for nursery available

products)

tbltracking: This table stores the nursery tacking data.

tblorderaddresses : This table stores the delivery address.

orders: This table store the nursery order details.

tblpage: This table store the details of contact us and about us page.

users : This table store the user details.

tblsubcriber: This table store the subscriber emails.

wishlist: This table store the wishist products which is selected by users.
Tables Relationship Diagram (Class Diagram)
 SYSTEM TESTING
Project Implementation & Testing

At the end of the system design, it is the beginning for the actual coding to develop
the proposed system. During development phase, the table structure of the database
will be first built in order to provide a suitable data types that suit the system back
end development, system connection and data transfer. Next, the computer side
client program will be developed and follow by will be the web services that allow
mobile phone client program to communicate with the server and lastly mobile
phone side client program will be developed. In testing phase, several test cases
will be carrying out to test the system in order to determine the system reliability
and system accuracy. According to the test cases, a system testing report will be
generated for further review to figure out the system weaknesses and made
improvement accordingly. In the deployment phase, several training will be
provided for the particular nursery staff such as how to operate the system, the
procedure of handling different event and several instruction that need to be follow
when operating the system.

Implementation Issues & Challenges

During the system implementation phase, several challenges need to be confront

because it involve end users to test the production system with various situation.
The possible challenges may face are as following:

User without background

The users are required to have basic knowledge of how to operate a computer
system and android mobile phone in order to use the system. This will be difficult
to give training to the user as the basic knowledge information can be obtained
from internet easily.

The screen size of different device

This would be one of the issues that will encounter while implementing the system.
Because user are able to download the mobile application from the official website
and use it as a client device to place order. Therefore, if the user device screens
size are too small or too big. The content and interface of the application may not
consistence.
Server performance

During real time system implementation, three would be a huge number of client
that access to the server at the same time. Therefore, it may slow down the
connection and performances of the system and even causes the server down if the
issue goes beyond the level of acceptance.

Development Tools

Database Environment

The proposed system will need a database system to support in order to store the
huge amount of data. MySQL database system will be chosen to support the
proposed system because it is well-known open source relational database
management system. Other than that, MySQL database system provides software
developer with a client program with easy understanding graphical user interface
that can communicate to the MySQL database server named as MySQL
Workbench 6.3 CE. By doing so, software developer can interact with the database
system with the user friendliness client program and without using the command
prompt, at the end it may speed up the development progress.

Web Technology

The proposed system is a cross platform system, which include Windows desktop
client and Android mobile phone client. Therefore, it require to implement web
services in order to support the Android mobile phone client device to fetch data
from the database server and store data back to the database server. In this project,
WampServer is used to support the issue that mention earlier. WampServer is a
Windows web development environment that built-in comes together with the
Apache, PHP and MySQL database. Furthermore, PHP will be the programming
language that used to create the web services that store in the server and it is able
to call by the Android mobile phone client to perform particular task.

System Platform

The project is a cross platform based system which includes Windows desktop
client device and Android mobile phone client device in order to operate the
proposed system
Therefore, IOS mobile phone client device will not compatible with the proposed
system.

Project Management Tool

For the rule of thumb to develop a system, it requires to have an intact system
planning which serve as a guide line during the development phases. Microsoft
Project is a project management software program and it has been used in the
project to design the system planning, project timeline, managing of resources,
tracking development progress and etc.

Visual Paradigm Community Edition

In this project, Visual Paradigm software has been used to create document for
several system planning diagram such as Use-Case diagram, Activity diagram,
Class diagram and etc. By doing so, software developer are able to visualize the
system communicate information much more concisely and clearly.

Test Plan

After the system has been developed, it will move to system testing phase. In
system testing phase, the developed system is required to install on appropriate
devices for testing purpose. After the system installation has been completed, the
system testing task will be performed by different roles of user such as manager
role and staff role. The purpose of system testing is to identify and determine the
degree of system stability. At the same time, it is given an opportunity for
developer to figure out error or bug that has not been raise and encounter during
the system development phase. Those error or bug that has been found during the
system testing activities will be solved before the system release. Each and every
testing before system testing phases is actually tested by the system developer
itself. Therefore, it might cause some biases toward the testing due to the system
developer have knowledge about the system software logics and lead the result to
be inappropriate. There are four types of testing that will be used to test the
developed system which includes unit testing, integration testing, system testing
and acceptance testing.
Unit Testing

First of all, unit testing will be the first testing method that used to test the
developed system. It consists of testing activities that test the system module by
module which has not been integrated as a whole. By doing unit testing, developer
are able to identify error and bug easily since it is finding the error and bug through
a unit part of the system rather than finding error through the complete system. In
addition, developer will test the unit part of the system with the validation and the
correctness of data value. Valid and invalid input will be entering to test and ensure
the system processes perform with an expected result.

Functional Testing

After conducted the unit testing, functional testing will begin to test the developed
system. Functional testing is performed to verify that the system application
processes that perform and functioning appropriately according to the design
specifications. In functional testing, the core system application functions will be
tested with several test cases in order to ensure that the entire system functioning
as a whole and perform task that with the expected results.

Testing

System testing of the software and hardware is a testing conducted on a system

which is complete, integrated system that works as a whole. System testing is a
critical testing procedure that must be conducted by software developer before the
system released. During system testing it can evaluate the system’s compliance
with its specified requirements according to the system design. Furthermore,
several testing activities in system testing test not only the design of the system,
but also the behavior and the believed expectations result from the customer. In
addition, various complex test cases that used to test the system are according to
the business process requirements which are collected from the user. Meanwhile,
errors or bugs that detected during the testing is required software developer look
into it from the initial step of the business process to the end of the process to
ensure it have expected result in order to solve the errors or bugs to determine the
degree of system stability.
Acceptance Testing

Last but not lease, acceptance testing also known as user acceptance testing would
be the final testing procedure that perform to test the developed software system.
In acceptance testing, the testing activities are different compare to the testing
activities that mentioned previously because the tester that tests the system will be
the final user which do not have knowledge about the system logic. If the final user
encountered an error while using the system, system developer are required to
maintain the system as soon as possible and release a new patch for the existing
system to recover the error. Meanwhile, final user will use the system that
visualized as to support their real business routine operation, therefore software
support team are required to stand by to provide technical support while final user
need any help or support that regarding the system. If there is no errors detected by
the final user while using the system for a long period, the development job of
developer is consider as complete and the system will be a final system product.
 SYSTEM EVALUATE AND DISCUSSION

Proposed System Completion

The proposed system is designed and developed to solve all the problem
statements which are stated in chapter one of this report. First of all, the developed
system provides a feature that is able to solve the problem of difficulties in nursery
order ticket tracking and achieve the project objective of prevention of nursery
serves not in sequence. By using the system, it allow staff to placed order ticket
through using the system and the system will automatically queue the nursery
order information according to the first come first serve basis and nursery staff is
able to follow the nursery queue to serve customer accordingly. It also eliminates
all the manual processes that involve in the traditional method of delivering
nursery order ticket. In addition, the developed system allows manager to update
all the nursery information as it is needed. This features helps nursery to eliminate
duplicated physical menu card which contain misleading information and also
allow staff and customer to view the latest updated nursery menu information
through using the system. By doing so, it helps nursery to solve the problem which
regarding difficulties in updating menu card information, difficulties in providing
appropriate updated nursery information and the potential of increase cost of
operation as the system will automatically refresh all the updated information that
is edited by manager. Furthermore, the project objective which regarding provides
convenience for both employees and consumers has been achieved because the
system allow consumer to view all the updated information through the mobile
phone client devices and it reduce the number of manual work which nursery staff
need to be performed. Last but not lease, the project objective of assisting nursery
to plan ahead has been achieved due to the system allow manager to generate
several types of report in order to assist the nursery to plan ahead. By analyzing the
generated report, manager is able to carry out a planning for the next business
routine of the nursery in order to improve the nursery operation efficiency. In a
nutshell, the system has fulfilled all significant outcomes that according to all the
problem statements and project objectives that are stated.
System Strength and Limitation

System Strength

The system provide customer with good dine in experience as it allow customer to
view nursery information and place order through using the mobile phone device.
The mobile application also provides ease of use because it has easy
understandable graphic user interface and minimal instruction to follow while
place order through the application. Next, it helps nursery staff to serve their value
customer in minimal delay. Furthermore, the system can be implemented with low
cost and is affordable for most of the small medium enterprise nursery, because the
hardware requirements are not required to be high end powerful in order to support
the system. Lastly, server and client are communicating within the nursery which
is intranet therefore it does not need to have internet access.

System Limitation
The system is not compatible with IOS mobile devices as the mobile application is
developed in Android environment. Therefore, for IOS mobile phone user may not
able to install the application in their mobile phone and experience the system.
Meanwhile, the nursery has prepared some Android mobile devices which are used
to resolve the issue that mention above. Next, due to the mobile phone client
devices are required to connect to the wireless intranet in order to communicate
with the server. It is very important to identify a suitable location that used to
install and set up the wireless access point in order to ensure the wireless signal
coverage is able to reach the entire nursery area.

Future Enhancement

The future scope of the project includes that what all future enhancements can
be done in this system to make it more feasible to us:-

• Databases for different products range and storage can be

provided.
• Multilingual support can be provided so that it can be
understandable by the person of any language.
• More graphics can be added to make it more user-friendly and
understandable. Manage & backup versions of documents online.
 PROJECT OUTPUT SCREENS
Home Page
Plants

Flowers
Seeds

About Us
Contact Us

Order
Wishlist

Cart Items
User Profile

Change Password
Checkout Page

User Sign Up
User Sign in

Forgot Password
 Admin Panel
Login Page

Forgot Password

Reset Password
Dashboard

Admin Profile
Change Password

Register Users
View User Order Details

Subscriber Mails
Add Category

Manage Nursery Category

Edit Category

Add Nursery
Manage Nursery Products

Update Nursery Detail

About Us

Contact Us
New Order

Details of New Order

Confirmed Orders

Details of Order Confirmed

Order Pickup

View Details of Order Pickup

Order of on the way

View Details of on the way orders

Delivered Order

View Details of Delivered Order

Read Enquiry

View Enquiry Detail

Between Dates Report

View Details of Reports

Request Count Report

Detail of Request Count Report

Sales Report

Details Sales Report

Search Order
 CONCLUSION
After a decade, the advancement and innovation of technology help people to
manage their task easily and efficiently. In many other industry area have been
used management system to assist their business grow long time ago, therefore it is
also a trend that cause industry to make use of a management system for their
business. At the end of this project, the system can reduce and replace the human
manpower task, reduce the time consume for each transaction and generate report
for further management purpose by fully utilizing the system. While developing
the system a conscious effort has been made to create and develop a software
package, making use of available tools, techniques and resources – that would
generate a proper System While making the system, an eye has been kept on
making it as user-friendly, as cost-effective and as flexible as possible. As such one
may hope that the system will be acceptable to any user and will adequately meet
his/her needs. As in case of any system development processes where there are a
number of shortcomings, there have been some shortcomings in the development
of this system also. The project is still under modification.
 REFRENCES

For PHP

 https://www.w3schools.com/php/default.asp
 https://www.sitepoint.com/php/
 https://www.php.net/

For MySQL

 https://www.mysql.com/
 http://www.mysqltutorial.org

For XAMPP

 https://www.apachefriends.org/download.html