VISVESVARAYA TECHNOLOGICAL UNIVERSITY BELAGAVI-590014,

KARNATAKA

A Mini Project Report

On

“Salon Management System”

Submitted in Partial Fulfillment of the Requirement for

“DBMS Laboratory with Mini Project(18CSL58) -V Semester”

For the Award of Degree
BACHELOR OFENGINEERING
IN

COMPUTER SCIENCE & ENGINEERING

Submitted By:
REVATHI D (1SG18CS084)
YASHASWINI S (1SG18CS127)
Under the Guidance of:
Prof. MANASA K N Prof. CHAITRA N C
Assistant Professor Assistant Professor

Department of Computer Science and Engineering

SAPTHAGIRI COLLEGE OF ENGINEERING
Affiliated to VTU, Belagavi, Approved by AICTE, NEW DELHI
(ISO 9001-2015 & ISO14001-2015 certified Institute)
14/5, Chikkasandra, Hesarghatta Main Road, Bengaluru – 560057

2020-2021
SAPTHAGIRI COLLEGE OF ENGINEERING
Affiliated to VTU Belagavi, Approved by AICTE, NEW DELHI
(ISO 9001-2015 & ISO14001-2015 Certified Institute)
14/5, Chikkasandra, Hesaraghatta Main Road, Bengaluru – 560057.

Department of Computer Science and Engineering

Certificate
Certified that the Mini Project Work entitled “SALON MANAGEMENT SYSTEM”
carried out by REVATHI D (1SG18CS084) & YASHASWINI S (1SG18CS127),
bonafide students of Sapthagiri College of Engineering, in partial fulfillment for the
award of Bachelor of Engineering degree in Computer Science and Engineering of
Visvesvaraya Technological University, Belagavi during the academic year 2020-21. It
is certified that all corrections/suggestions indicated for Internal Assessment have been
incorporated in the report deposited in the department library. The mini-project report has
been approved as it satisfies the academic requirements in respect of DBMS Laboratory
with Mini Project (18CSL58) prescribed for the said Degree.

Signature of the Guide Signature of the Guide Signature of the HOD

Prof. Manas K N Prof. Chaitra N C Dr.
KamalakshiNaganna Assistant Professor Assistant Professor
Professor & Head

EXTERNAL EXAMINATION

Name of the Examiners Signature with Date

1.

2.
ACKNOWLEDGEMENT

Any achievement does not depend solely on the individual efforts but on the guidance,
encouragement and co-operation of intellectuals, elders and friends. A number of personalities, in
their own capacities have helped us in carrying out this mini project work. We would like to take
this opportunity to thank them all.
We would like to express my profound thanks to Sri. G Dayanand, Chairman, Sapthagiri
College of Engineering Bangalore, for his continuous support in providing amenities to carry out
this Mini Project.
Special Thanks to Manoj G D, Executive Director, Sapthagiri College of Engineering
Bangalore, for his valuable suggestion.
Also we would like to express our immense gratitude to Dr. H Ramkrishna, Principal,
Sapthagiri College of Engineering Bangalore, for his help and inspiration during the tenure of the
course.
We also extend our sincere thanks to Dr. Kamalakshi Naganna, Professor and Head,
Department of Computer Science and Engineering, Sapthagiri College of Engineering, for his
constant support.
We would like to express our heartful gratitude to Prof. Manasa K N , Assistant professor
and Prof. Chaitra N C, Assistant professor, Department of Computer Science and Engineering,
Sapthagiri College of Engineering, for their timely advice on the mini project and regular
assistance throughout the work.
We also extend our sincere thanks to all the Faculty members and supporting staff
Department of Computer Science and Engineering, Sapthagiri College of Engineering, for their
constant support and encouragement.
Finally, we thank our parents and friends for their moral support.

REVATHI D
YASAHASWINI S

I
ABSTRACT

With tremendous increase in technology, information technology is a fast-developing field.

Technology which is in vogue today might become redundant tomorrow. This ever-changing
scenario makes it possible to provide the latest and most modern IT solutions to various business
and institutions. I am doing my project on Salon Management System. There is the need for
efficient management of a network-based system for handling customer orders.

This project is an endeavor to provide a solution to this. The proposed system enables an
administrator to keep track of customer orders and maintaining records of the customers. He can
view the submitted requirements made by the customer. He can also view the reports generated by
him and can also sent approvals or rejections instantly. Thus, the project is a sincere effort in
simplifying the task of administrators in an easily usable format. I finalized to make this project
and hence planned to develop this system using PHP for front end and MySQL as the Back End.

II
TABLE OF CONTENTS

SL.NO CONTENTS PAGE NO

1 INTRODUCTION

1.1 INTRODUCTION TO DBMS 1-3

1.2 OVERVIEW OF THE PROJECT 4

2 SYSTEM DESIGN AND METHODOLOGY

2.1 SYSTEM ARCHITECTURE 5-6

2.2 ER DIAGRAM 7-8

2.3 SCHEMA DIAGRAM 9

2.4 USE CASE DIAGRAM 10

2.5 ALGORITHM AND DATA FLOW DIAGRAM 11-12

3 3.1 SYSTEM IMPLIMENTATION 13

3.2 MODULE DESCRIPTION 14-17

4 RESULTS AND SCREENSHOTS 18-23

5 CONCLUSION AND FUTUREWORKS 24

6 BIBLOGRAPHY 25

III
FIGURES

SL.NO CONTENTS PAGE NO

1.1 THREE SCHEMA ARCHITECTURE 2
2.1 SYSTEM ARCHITECTURE 5
2.2 ER DIAGRAM 8
2.3 SCHEMA DIAGRAM 9
2.4 USE CASE DIAGRAM 10
2.5 DATA FLOW DIAGRAM 12

SCREENSHOTS

SL.NO CONTENTS PAGE NO

4.1 USER DASHBOARD 18

4.2 SERVICES 19

4.3 ABOUT US 20

4.4 CONTACT US 20

4.5 LOGIN PAGE 21

4.6 ADMIN PANNEL 21

4.7 MANAGE SERVICES 22

4.8 APPOINTMENTS 22

4.9 ACCEPTED APPOINTMENTS 23

4.10 INVOICES 23

IV
Salon Management System

CHAPTER 1

INTRODUCTION
1.1 Introduction to DBMS

Database is a collection of related data. DBMS came into existence in 1960 by Charles.
Again in 1960 IBM brought IMS-Information management system. In 1970 Edgor Codd at
IBM came with new database called RDBMS. In 1980 then came SQL Architecture Structure
Query Language. In 1980 to 1990 there were advances in DBMS e.g. DB2, ORACLE. A
database has the following implicit properties:

 A database represents some aspect of the real world, sometimes called the mini world
or the universe of discourse. Changes to the mini world are reflected in the database.

 A database is a logically coherent collection of data with some inherent meaning. A

random assortment of data cannot correctly be referred to as a database.

 A database is designed, built, and populated with data for a specific purpose. It has an
intended group of users and some preconceived applications in which these users are
interested.

In other words, a database has some source from which data is derived, some degree of
interaction with events in the real world, and an audience that is actively interested in its
contents.

Metadata (meta data, or sometimes meta information) is "data about data", of any sort in any
media. An item of metadata may describe a collection of data including multiple content
items and hierarchical levels, for example a database schema. In data processing, metadata is
definitional data that provides information about or documentation of other data managed
within an application or environment. The term should be used with caution as all data is
about something, and is therefore metadata.

A database management system (DBMS) is a collection of programs that enables users to

create and maintain database. The DBMS is a general-purpose software system that
facilitates the

Dept Of CSE, SCE Page 1

process of defining, constructing, manipulating and sharing databases among various users
and applications.

Defining a database specifying the database involves specifying the data types, constraints
and structures of the data to be stored in the database. The descriptive information is also
stored in the database in the form database catalogue or dictionary; it is called meta-data.
Manipulating the data includes the querying the database to retrieve the specific data. An
application program accesses the database by sending the queries or requests for data to
DBMS. The important function provided by the DBMS includes protecting the database and
maintain the database.

Figure 1.1: Three Schema Architecture

The Figure 1.1 shows the Three Schema Architecture of Database Management System. The
architecture has three levels
• External level:

The external level is the view that the individual user of the database has. This view is often a
restricted view of the database and the same database may provide a number of different
views for different classes of users. In general, the end users and even the application
programmers are only interested in a subset of the database.

• Conceptual level:

The conceptual view is the informational model of the enterprise and contains the view of the
whole enterprise without any concern for the physical implementation. The conceptual view
is the overall community view of the database and it includes all the information that is going
to be represented in the database.

• Internal level:

The internal view is the view about the actual physical storage of data. It describes what data
is stored in the database and how.
1.2 Overview of project

Problem Statement

To maintain and manipulate the data to be stored in Salon Management System.

Objectives of the project:

The main objective of the project is to manage the details of the customers appointment

date, services given, appointments, accepted appointments, rejected appointments. The

project is totally built at the admin end and thus only the admin is guaranteed the access.

It tracks the details about the customer, service, accepted appointments, invoices.

 Provides searching facilities based on various factors such as skin care, manicure,
pedicure, facial.
 It tracks all the details about the sales taken place in a month, year, reports regarding
the sales completed.
 Manage the customer information.
 Shows the information and costs of the services provided.
 It deals with monitoring information and invoices of the customer.
 Editing, Adding and Updating of appointments is improved which results in proper
resource management of services data.
 Integration of all the record of appointments accepted.
CHAPTER 2

SYSTEM DESIGN AND METHODOLOGY

2.1 System Architecture

ADMIN

LOGIN APPOINTMENTS

MANAGE CUSTOMERS AND THEIR

VIEW

DATABASE

CUSTOMER

REGISTER

LOGIN ORDER SERVICES

VIEW UPDATE

Figure 2.1: System Architecture of Salon Management System

The above figure 2.1 describes the system architecture of Salon Management System. The
architecture consists of a centralized database, which can be accessed by admin and normal
users or customers. Administrative access is required for the admin, which is implemented
through login module by which the admin can login with the registered userId and password.

Once login is successful, the admin can manipulate the updating or deleting customers
users and their services, adding, updating and deleting categories .
If the admin fails to login, the admin gets a popup message that the userId and password are
incorrect.

The admin needs to enter valid user Id and password once again.

A customer first needs to register in the website by filling up valid user Id,name, email,
address and password.

Username should be unique and if it is already been taken then a popup message is
displayed that the username is already taken.

Password confirmation should be made by retyping the password again. If the password and
password confirmation do not match then it produces a popup message stating that retype the
password again.

On successful registration, customer can login through valid userId and password. On
successful login, customer is directed to services list where customers can view services of
their interest and then add to list, select appointment time, make payment and order the.
Customer can also update their password and address.
2.2 ER DIAGRAM

An entity-relationship model describes inter-related things of interest in specific domain of

knowledge. An ER module is composed of entity types and specifies relationships that can
exist between instances of those entity types. It is a data modeling technique that graphically
illustrates an information systems entities and the relationship between those entities.

 This document is an entity-relationship diagram, or “ERD,” for a system to manage

Inventory Management System.

 An ERD is a model that identifies the concepts or entities that exist in a system and
the relationships between those entities.

 An ERD is often used as a way to visualize a relational database: each entity

represents a database table, and the relationship lines represent the keys in one table
that point to specific records in related tables.

 ERD may also be more abstract, not necessarily capturing every table needed within a
database, but serving to diagram the major concepts and relationships.

 This ERD is of the latter type, intended to present an abstract, theoretical view of the
major entities and relationships needed for management of electronic resources.

 It may assist the database design process for an e-resource management system, but
does not identify every table that would be necessary for an electronic resource
management database
Mobile no email creationdate

username password
sevicename

adminname
adminregdate

id
BPMS
cost

id

user has add services

admin

creationdate

updationdate
request details
Accept/reject
gender
email

mobileno
id appointment generate

name
customers
name
id
status
aptno
belongsto
remarkdate
email
remark
id
phoneno invoice
applydate
aptdate Userid
services Postingdate
apttime
serviceid
billingid
Figure 2.2: ER Diagram
2.3 SCHEMA DIAGRAM
A database schema is a skeleton structure that represents the logical view of the entire

database. It defines tables, views and integrity constraints.

ADMIN
ID Admin_Name User_name Mobile_number Email Password Adminreg_date

CUSTOMER
IdNameMobile_numberEmail GenderDetails Updation_date Creation_date

SERVICES
Id
Service_name Creation_date Cost

APPOINTMENTS
Id Name Apt_no Mobile_number Email Apt_date Apt_time Services Apply Remark Remark_ Status
_date date

INVOICE
Id User_id Service_id Billing_date Posting_date

Figure 2.3: Schema Diagram

Salon Management System

2.4 USE CASE DIAGRAM

Figure 2.4: Use Case Diagram

Customer:

Here the customers books for an appointment and receives the services provided by
the designer.

Designer:

They provide the services as per the requirement of the customer

Admin:

The admin has the control to accept and reject appointments , enquire about the
customer details, services updation .

Dept Of CSE, SCE Page 10

Salon Management System

2.5 ALGORITHM:

Stored procedure

STEP 1: BEGIN

STEP 2: DELIMITER $$

STEP 3: CREATE DEFINER=`root`@`localhost` PROCEDURE `appointment_list` () NO

SQL

SELECT
a.appointment_id,a.customer_id,s.service_name,CONCAT(c.phone_no,'
,’c.email_id,' ,c.state,' ,',c.city,' ) AS Address,a.number of services as NUM

FROM appointment a INNER JOIN services s ON s.service_id=a.sevice_id

INNER JOIN customer c ON c.customer_id=a.customer_id

WHERE a.appointment_status='APPOINTMENT_CONFIRMED' ORDER BY

p.time_stamp ASC$$

DELIMITER ;

STEP 4: END

Stored procedure is a set of sql statement . The procedure is created by the name appointment
list in the created definer `root`@`localhost` with select all the attributes of appointment table
by giving appointment id as condition .

Dept Of CSE, SCE Page 11

Figure 2.5: data flow diagram
CHAPTER 3

SYSTEM IMPLEMENTATION
To implement this system Java, Net Beans IDE 8.2 is used for backend and XAMPP is used
for frontend.

System Requirements:
Software Requirements
Operating system :Windows 10

Operating system Type:64-bit

Database: MySQL

Front End : PHP

Integrated Tool: Wamp Server 2.4 32-bits

Hardware Requirements:

Processor : Intel Core (TM) i5-8250U [email protected] 1-80GHz

RAM : GB

Speed :1.2GHz

Key Board : Standard Keyboard

Mouse :Wireless Mouse

Monitor :LED
3.1 Admin Module:

INPUT:

The login inputs are User Id and password.

OUTPUT:

A successful login shall direct admin to view services, also can process appointments. If the
login attempt fails, popup message will be displayed that the userId and password are invalid
admin needs to retype the userId and password again.

DESCRIPTION:

Frontend is designed using XAMPP. Login page consists of a form with userId, password
fields. On filling the form the admin should click on the login button. If the userId and
passwords are valid then admin is directed to services list page. If not popup message will be
displayed stating that the username and password are invalid.

OBJECTIVES:

• The main purpose of this module is to provide all the functionality such as create, update
and delete options to categories, products, services, appointments and their profiles only to
admin and not for customers.

• Admin can view list of appointments and only he can update appointments details or can
also reject appointments.

• Admin can view list of categories and invoices.

• Only admin can create new categories and products, update or delete existing categories
and products.

• Admin can manipulate the appointments of customers (users).

3.2 Customer Module:

INPUT:

Inputs for registration are Username, Email id, Password. Inputs for login are Username,
Password.

OUTPUT:

On successful registration, customer will be redirected to login page to login. If not popup
message will displayed informing customer that invalid email or password.

A successful login shall direct customer to services list page. If the login attempt fails, popup
message will be displayed that the email id and password are invalid and customer needs to
retype the email id and password again

DESCRIPTION:

Frontend is designed using XAMPP, Scene Builder. Registration page consists of a form with
username, email id, password ,address ,phone number fields. Login page consists of a form
with email id, password fields. On filling the form the customer should click on the submit
button. If the username and passwords are valid then admin is directed to services list page. If
not a popup message will be displayed stating that the email id and password are invalid.

OBJECTIVES:

• The main objective of customer module is to provide all the required limited functionality to
customers.

• Customer can view the list and details of categories and services.

• Customer can add different services, change the services required, select appointment time,
make payment.

• Customer can update his password and address in the settings page, He can also view his
previous appointments list.
3.3 Menu Module:

INPUT:

Inputs for menu module are appointment id, item name, service image, price.

OUTPUT:

The item will be successfully added to the appointment list and pop up message will be
displayed.

DESCRIPTION:

Frontend is designed using XAMPP, Scene Builder. The items ordered by the customer will
be added to the list and the details regarding appointment id, services name and price will be
displayed .The customer can modify services of his own interest.

OBJECTIVES:

• The main purpose for developing this module is to provide appointment id, service name
and price.

• Items will be managed by customer will be able to see services and appointments.

• Admin can create a new appointment or update an appointment.

• Admin can even reject appointment.

3.4 Order Module

INPUT:

Inputs for this module are appointment id, customer id , service name and the appointment
status.

OUTPUT:

An order will be created when customer add services to the cart with details of appointment
id, price.
DESCRIPTION:

Frontend is designed using XAMPP, Scene Builder. When customer add items to the cart the
appointment will be created with appointment id, name, price . If the services are added ,The
customer can confirm his appointment and also can view his order status. Order module also
has a method to calculate total price.

OBJECTIVES:

• The main objective of this module is to manage customer’s orders.

• Customer can order the services and also view his appointments status.

• Customer can view his previous appointments.

• The customer can manage appointments of his own interest.

CHAPTER 4

RESULTS AND SCREENSHOTS

Screenshot 4.1: User Dashboard through which user can access details of services
`

Screenshot 4.2: List of Services provided and its Service price

Salon Management System

Screenshot 4.3: Provides the information about salon and its maintainence

Screenshot 4.4: Provides contact details of salon which is accessible for customers

Dept Of CSE, SCE Page 20

Salon Management System

Screenshot 4.5: Login page through which admin can sign in through user name and
password

Screenshot 4.6: Provides details regarding about appointments status, services,

customers and sales

Dept Of CSE, SCE Page 21

Screenshot 4.7: Provides the updation of services, service cost , creation date and its
action

Screenshot 4.8: List of Appointments provided by customers

Screenshot 4.9: List of Accepted Appointments provided by the admin

Screenshot 4.10: List of Invoices which took place within a particular period
CHAPTER 5

CONCLUSION AND FUTURE WORKS

The result of this project was a successful high-fidelity prototype of a Salon management
and scheduling application. I successfully implemented all of the above mentioned use cases,
and achieved clean interfaces that further enhance the user experience.

The many-to-one database tables successfully represent a robust set of

scenarios and relationships that are critical to salon management. Web Calendar was
integrated well to provide salons with full calendaring functionality. The aesthetic
customization of Web Calendar makes it undifferentiated from the salon Book application.

For users, scheduling was the heart of the application. And indeed, users can current select a
parlor, stylist, date, and service to make an appointment. They can then view or
cancel appointments, and rate salons on parlor appointments.

Together, all of this functionality gives users an unmatched value proposition for booking
salon appointments. Users also accumulate points after attending and rating an appointment,
which, upon launch of the site, would be redeemable for parlor credit. This is an additional
source of incentive to use this application.

FUTURE WORKS:

• Customer’s activity can be studied and offers based on their activity for specific

can be given.
BIBLIOGRAPHY

1) Rakrishnan,&Gehrke,J.(2011).Databasemanagementsystems.Boston: McGraw-Hill.

2) Monson-Haefel,R.(2007).J2EEWebservices.Boston,Mass.:Addison-Wesley.
Silberschatz,A.,Korth,H.F.,&Sudarshan,S.(2011).

3) Databasesystemsconcepts.EstadosUnidos :McGraw-HillCompanies,Inc.

4) Hanna P.(2002):JSP2.0TheCompleteReference,SecondEditionMcGrawHill
Education.
•https://www.w3schools.com/
php/default.asp
•https://www.php.net/
•https://www.mysql.com/
•http://www.mysqltutorial.org
•https://www.apachefriends.org/download.html