VISVESVARAYA TECHNOLOGICAL UNIVERSITY

JNANA SANGAMA, Belagavi - 590 018.

2021 - 2022

A
mini project report on

“BEAUTY PARLOUR MANAGEMENT SYSTEM”

Submitted in partial fulfillment of the requirements for the award of the degree of
BACHELOR OF ENGINEERING
in
COMPUTER SCIENCE & ENGINEERING

Submitted by
RUCHITHA BM(1AT19CS099)
SHIVANI G (1AT19CS106)

Under the guidance of.

Mrs. PADMINI C
Assistant Professor
Dept. of CSE, ATRIA

ATRIA INSTITUTE OF TECHNOLOGY

DEPARTMENT OF COMPUTER SCIENCE & ENGINEERING
Anand Nagar, Bengaluru-560 024
 ATRIA INSTITUTE OF TECHNOLOGY
(Affiliated to Visvesvaraya Technological
University) ASKB Campus, Anand Nagar,
Bengaluru – 560024

Department of Computer Science and Engineering

CERTIFICATE

Certified that the project work entitled “Beauty Parlour Management System” carried out by
RUCHITHA B M(1AT19CS099) AND SHIVANI G(1AT19CS106) are bonafide students of
ATRIA INSTITUTE OF TECHNOLOGY, Bengaluru, in partial fulfillment for the award of
Degree of Bachelor of Engineering in Computer Science & Engineering of Visvesvaraya
Technological University, Belagavi, during the academic year 2021-2022. It is certified that all
corrections/suggestions indicated for Internal Assessment have been incorporated in the report
deposited in the department library. The project report has been approved as it satisfies the
academic requirements in respect of project work prescribed for the said degree.

Guide HOD Principal

Mrs. Padmini C Dr. Aishwarya P Dr. T N Sreenivasa

(Assistant Prof., (Dept. of CSE) (Atria I T)
CSE)

External Viva

Name of Examiners Signature with date

1.

2.
2
 DECLARATION

We, RUCHITHA B M (1AT19CS099) and SHIVANI G (1AT19CS106) students of 5th semester

Bachelor of Engineering, Department of Computer Science and Engineering, Atria Institute of
Technology, Bengaluru, would hereby declare that the project entitled “BEAUTY PARLOUR
MANAGEMENT SYSTEM” has been carried out by us at Atria Institute of Technology,
Bengaluru, and submitted in partial fulfillment of the course requirement for the award of degree of
Bachelor of Engineering in Computer Science and Engineering of Visvesvaraya Technological
University, Belagavi, during the academic year 2021-2022.
We further declare that the work embodied in this report has not been submitted to any other
university or institution for the award of any other degree.

Place: Bengaluru Signature of the students

Date:

RUCHITHA B M
(1AT19CS099)

SHIVANI G
(1AT19CS106)

1
 ABSTRACT

Beauty Parlour is web-based salon management application with appointment

scheduling functionality. It connects clients, salons and stylists in online community
allowing user to browse salon and stylists and book or cancel appointments. Parlours
are a necessity for almost everyone. Nowadays, the business processes of them mostly
still use conventional methods. User can also write and read reviews of salons and
particular stylists. The users of the system include the customers where they can register
initially with the minimum details and will be allowed to make an appointment. Parlour
can specify stylists that work at their salons, as well as services they offer. salon can
also book appointment for customers and can view and print schedules in convenient
formats. All these activities of creating appointments like choosing service also as date
and time are going to be recorded within the database for all the events. This project
integrates a login panel for a more secure system. Moreover, the system also provides
contact details in order that the user has no difficulty in searching the parlour. Besides,
the user can visit parlour at a selected date and time because the system already records
the appointment made by them. In current system salon take appointment on register.
They manage customer record on register. And it is very difficult to find out old
appointment details in this system. Making report for the salon business is also very
tiresome task. this system is prone to costly human error. Beauty parlor management
system allow salon to manage stylists and services, promote sales to customers, and
track customer satisfaction.

2
 ACKNOWLEDGEMENT

We are grateful to our institution, Atria Institute of Technology, for having provided us with the
facilities to successfully complete this mini project on Beauty Parlour Management.
We thank Dr. T N SREENIVASA, principal and Dr. Aishwarya P, HOD, CSE for
providing us all the necessary facilities for the successful completion of our mini project.
Deadlines play a very important role in the successful completion of the academic project
on time, efficiently and effectively. We take this opportunity to express our deep sense of gratitude
to our guide and coordinators, Mrs. Padmini Assistant professor, Department of CSE for their
valuable guidance and help throughout the course of the academic mini-project. They have always
been patient with us and helped immensely in completing the task on hand. We also thank them for
their immense support, guidance, specifications & ideas without which seminar would have been
completed without full merit.
Last but not least from the Department of Information Science and Engineering, teaching
and non-teaching staffs for their constant encouragement, support, patience, and endurance shown
during the preparation of this report were remarkable. We also thank the management.
Finally, We thank our parents and friends for their motivation, morale and material support.

RUCHITHA BM
(1AT19CS099)

SHIVANI G

(1AT19CS106)

3
 TABLE OF CONTENTS

Chapter 1.
1.INTRODUCTION TO DATABASE
1.1 Database environment system. 6
1.2 Advantages of database. 9
1.3 Architecture of Database. 10
Chapter 2.
2.1 INTRODUCTION TO PROJECT
2.1Brief description
2.1.1 Significance of production 12
2.2 Technology 13
2.3Design Goals 14
2.3.1Target Audience
2.3.2User goals and Objectives
2.3.3Project Features and Functionality 15
2.2 Prior Work
3.HARDWARE AND SOFTWARE REQUIREMENTS 16

3.1 Algorithm details

3.2 Target platform
3.3 Project Milestones
3.4 Work Log
3.5 Functional and non-functional requirements 18
3.5.1Functional or specific requirements
3.5.2Non-functional requirements

Chapter 3.
4.SECURITY
4.1 Security Requirements. 19
4.2 Conculsion and future enhancements 20
4.3 References

4
APPENDIX ‘A’ – CODE SNIPPETS 21
A.1Index 22
A.2 Add services 24
A.3 Add customer 26
A.4 All appointment 28
A.5 Invoices

APPENDIX ‘B’ – SCREENSHOTS 29

B.1 Home Window 30
B.2 About us 33
B.3 Contact us 36
B.4 Sign In page 38
B.5 Add services 39
B.6 Manage services 41
B.7 Appointment
B.8 Add Customer
B.9 Report
B.10Invoices

5
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
CHAPTER – 1

INTRODUCTION TO DATABASE
Database and database technology has a major impact on the growing use of computers. It is
fair to say that databases play a critical role in almost all areas where computers are used,
including business, electronic commerce, engineering, medicine, genetics, law, education,
and library science. The word database is so commonly used that we must begin by defining
what the database is.
Our initial definition is quite general. A database is a collection of related data. By
data, we mean known facts that can be recorded and that have implicit meaning. For
example, consider the names, telephone numbers, and addresses of the people you know.
You may have recorded this data in an indexed address book or you may have stored it on a
hard drive, using personal computers and software such as Microsoft excel. This collection of
related data with an implicit meaning is a database.
The preceding definition of a database is quite general, for example, we may consider
the collection of words that make up this page of text to be related data and hence to
constitute a database. However, the common use of the term database is usually more
restricted. A database has the following properties:
● A database represents some aspect of the real world, sometimes called the mini world
or the universe of discourse. The 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. The end-users of the database may perform business transactions (for example a
customer buys a camera) or events may happen that may cause the information in the
database to change. In order for a database to be accurate and reliable at all times, it must
be a true reflection of the mini world that it represents; therefore changes must be
reflected in the database as soon as possible.

6
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
A database can be of any size and complexity. A database may be generated and maintained
manually or computerized. For example, a library card catalog is a database that may be created
and maintained manually. A computerized database may be created and maintained either by a
group of application programs written specifically for that task or by a database management
system.
A database is a collection of data, typically describing the activities of one or more
related organizations. For example, a university database might contain information about
the following:
● Entities such as students, faculty, courses, and classrooms.
● Relationships between entities, such as student’s enrolment in courses, faculty
teaching courses, and the use of rooms for courses.
A database management system, or DBMS, is software designed to assist in
maintaining and utilizing a large collection of data. The need for such systems as well as
their use is growing rapidly. The alternative to using a DBMS is to store the data in files
and write application-specific code to manage it.

File system versus DBMS

To understand the need for a DBMS, let us consider a motivating scenario: a company
has a large collection (say 500 GB) of data on employees, departments, products, sales,
and so on. This data is accessed concurrently by several employees. Questions about the
data must be answered quickly, changes made to the data by different users must be
applied consistently and access to certain parts of the data must be restricted. We can try
to manage the data by storing it in operating system files. This approach has many
drawbacks, including the following

● We probably do not have 500GB of main memory to hold all the data. We must,
therefore, store data in a storage device such as a disk or tape and bring relevant parts into
the main memory for processing as needed.
● Even if we have 500 GB of main memory, on computer systems with 32 bit addressing,
we cannot refer directly to more than about 4 GB of data. We have to program some
method of identifying all data items.

7
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

● We have to write special programs to answer each question a user may want to ask about
the data. These programs are likely to be complex because of the large volume of data to
be searched.
● We must protect the data from the inconsistent changes made by different users accessing
the data concurrently. If applications must address the details of such concurrent access,
this adds greatly to their complexity.
● We must ensure that the data is restored to a consistent state if the system crashes while
changes are being made.
● Operating systems provide only a password mechanism for security. This is not
sufficiently flexible to enforce security policies in which different users have permission
to access different subsets of the data.
A DBMS is a piece of software designed to make the preceding tasks easier. By
storing data in DBMS rather than as a collection of operating system files, we can use the
DBMS’s features to manage the data in a robust and efficient manner. As the volume of
data and the number of users grow hundreds of gigabytes of data and thousands of users
are common in current corporate database DBMS support becomes indispensable.

1.1 DATABASE ENVIRONMENT SYSTEM

Fig 1.1: Simplified database environment system

8
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
A database management system (DBMS) is a collection of programs that enables users to
create and maintain a database. The DBMS is a general-purpose software system that
facilities the processes of defining, constructing, manipulating and sharing databases among
various users and applications. Defining a database involves specifying the data types,
structures and constraints of the data to be stored in the database.
The database definition or description information is also stored by the DBMS in the
form of a database catalog or dictionary, it is called Metadata. Constructing the database is
the process of storing the data on some storage medium that is controlled by the DBMS.
Manipulating a database includes functions such as querying the database to retrieve specific
data, updating the database to reflect changes in the mini world and generating reports from
the data. Sharing a database allows multiple users and programs to access the database
simultaneously.
An application program accesses the database by sending queries or requests for data
to DBMS. A query typically causes some data to be retrieved; a transaction may cause some
data to be read and some data to be written into the database.

Other important functions provided by DBMS include protecting the database and maintaining it
over a long period of time, protection includes system protection against hardware or software
malfunction and security protection against unauthorized or malicious access. A typical large
database may have a life cycle of many years, so the DBMS must be able to maintain the database
system by allowing the system to evolve as requirements change over time.
It is not absolutely necessary to use general-purpose DBMS software to implement a
computerized database. We could write our own set of programs to create and maintain the
database, in effect creating our own special purpose DBMS software. In either case, whether
we use a general-purpose DBMS or not we usually have deployed a considerable amount of
complex software. In fact, most DBMSs are very complex software systems. Fig 1.1 shows a
simplified database environment system.

1.2 ADVANTAGES OF USING DBMS APPROACH

Using a DBMS to manage data has many advantages:

● Data abstraction: application program should not, ideally, be expected to details of

data representation and storage, the DBMS provides an abstract view of the data that
hides such details.
● Efficient Data Access: A DBMS utilizes a variety of sophisticated techniques to store
9
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
and retrieve data efficiently. This feature is especially important if the data is to be
stored on an external device.
● Data Integrity and Security: if data is always accessed through DBMS, the DBMS
can enforce integrity constraints. For example, before inserting salary information for
an employee, the DBMS can check that the department budget is not exceeded. Also,
it can enforce access controls that govern what data is visible to different classes of
users.
● Data Administration: when several users share data, centralizing the administration
of data can offer significant improvements. Experienced professionals who understand
the nature of the data being managed, and how different groups of users use it, it can
be responsible for organizing the data representation to minimize redundancy and for
fine- tuning the storage of the data to make retrieval efficient.

 Concurrent Access and Crash Recovery: A DBMS schedules concurrent accesses

to the data in such a manner that users can think of the data as being accessed by only
one user at a time. Further, the DBMS protects users from the effects of system failures.

● Reduced Application Development Time: clearly, the DBMS supports important

functions that are common to many applications accessing data in the DBMS. This, in
conjunction with the high-level interface to data, facilities quick application
development. DBMS applications are also likely to be more robust than a similar
stand- alone application because many important tasks are handled by the DBMS.

1.3 ARCHITECTURE OF DATABASE

The Three-Schema Architecture

The goal of the three-schema architecture illustrated in the figure is to separate the user
application from the physical database. In this architecture, schemas can be defined at the
following three levels:

● The internal level has an internal schema, which describes the physical storage structure
of the database. The internal schema uses a physical data model and describes the complete
details of data storage and access paths for the database.
● The conceptual level has a conceptual schema, which describes the structure of the whole
database for a community of users. The conceptual schema hides the details of physical
10
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
storage structures and concentrates on describing entities, data types, relationships, user
operations, and constraints. Usually, a representational data model is used to describe the
conceptual schema when a database system is implemented. This implementation conceptual
schema is often based on a conceptual schema design in a high-level data model.
● The external or view level includes a number of external schemas or user views. Each
external schema describes the part of a database that a particular user group is interested in
and hides the rest of the database from that user group. As in the previous level, each external
schema is typically implemented using a representational data model, possibly based on
external schema design in a high-level data model.

11
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

CHAPTER 2

INTRODUCTION TO PROJECT
BEAUTY PARLOUR MANAGEMENT SYSTEM

2.1 BRIEF DESCRIPTION

2.1.1 Significance of problem or production/development need
Being a salon client today is inconvenient. When you need to make an appointment,
hope you remembered during business hours, and finally scramble to find the phone
number and take them out of your busy day to make the call. And never mind finding
user reviews of local salons and stylists. And tracking those down somewhere on the
web is headache that most don’t even attempt. This is the experience of countless salons
every day, even as we move well into the twenty-first century. There is a strong, well-
articulated need for a “one-stop-shop” online hub that connects clients to salons, putting
all the information users need in one convenient place, on demand. Equally surprising,
many salons today are still using paper and pencil systems to schedule appointments and
manage customers.
These systems are grossly insufficient at sharing and syncing information
and are prone to costly human error. It promises to end the dependence on paper-pencil
systems and put salons in control with an easy-to-use interface. Salon Book will be more
than just an online scheduler. It will be a salon management tool that will allow salons to
manage stylists and services, promote sales to customers and track customer satisfaction.

2.2 Technology
My project uses MySQL and PHP to back the interface with strong database
functionality. To build the data tables we’ve used PhpMyAdmin, which is a web-based
interface for MySQL. For the front-end development, we primarily used HTML and
JavaScript widgets to style the site and create a simple, clean interface. To facilitate the
process of styling the application, used Adobe Dreamweaver. However, Dreamweaver is
very limited, and the scope of my project quickly outgrew that of Dreamweaver’s
capabilities. Nonetheless, it was a very helpful tool early on.

12
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

For a appointment scheduling, I’m going to integrate Web Calendar, a PHP-driven

calendaring application, into my Salon Book application. After much research, I decided
to implement web calendar rather than Google Calendar for a few reasons. Web
Calendar is installed locally and runs on MySQL. This means that all the code running
Web Calendar is in a subdirectory of our project. This gives me a great deal of control
and customization of the application as we integrate it into our program. It also uses
MySQL data tables that nicely sit right next to the tables storing data for Salon Book.
Thus, it is a very clean integration, and a powerful tool. Google Calendars, on the other
hand, would mean outsourcing functionality to Google. Any future changes to the
Google APIs would cause serious problems with our program. Also, viewing and
editing Google Calendars requires user authentication as a prerequisite. This means
users of our site would need Google accounts or we would personally need to be the
“owner” of all the calendars. Neither of these options offered the neat, compact solution
that Web Calendar provided, and therefore were not implemented.

2.3Design goals
2.3.1 Target audience
There are two distinct target audiences for this project. Managers and Owners make up
the first primary audience for this project. They will use the salon side of the web
application.
Salon-goers, primarily female, are the second major audience. They will use the client
side of the application, primarily using it to view user ratings, and make appointments
online all on demand.
2.3.2 User goals and objectives
USER CASES
User
i. Create a new account
ii. Log in name
iii. View and Edit Account information
iv. Make an appointment for:
Haircut
With or without color
With or without perm
With or without straightening
13
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
Specify stylist
Beauty salon services
**Allows users to make recurring appointments**
-Cancel an appointment
-View Appointment
-View “My Points”
-View Parlour Promotions
2.3.3 Project Features and Functionality
The tab menu on the Home Page allows any visitor to view the by four different
categories. When users sign in, they are directed to their dashboard, their one-stop-
shop for all salon-related information and functionality. At the dashboard they are
reminded about their points total and upcoming appointments. The JavaScript pull-
down menus give the page a clean look while still providing an abundance of
information and functionality.
Parlours have a similar dashboard that is the root point for all use cases mentioned
above
2.4 PRIOR WORK
OpenTable.com is the inspiration and the benchmark for this project. OpenTable
represents the primary body of relevant prior work. OpenTable developed a
Windows based beauty parlour management application that allows appointments to
be made, cancelled, and viewed locally. Additionally, this application stores
customer data and appointments locally. It is also in constant communication with
the website, which is designed to allow service to book appointment in real time.
This model of local software combined with a web application is ideal because it
maintains all data locally in case the internet fails, yet it still gives customers real
time access to the reservation book.

14
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
3. HARDWARE AND SOFTWARE REQUIREMENTS

3.1 ALGORITHM DETAILS

Architecture
MySQL database
PHP
User Interface
HTML
Database Design
Many-to-one relationships are key to sound database design. In designing a database,
inadequacies and inefficiencies that are noticed later in the
development cycle can be costly, and so a lot of time and thought went into this early
on. It is tempting to create database tables like classes in object oriented programming.
This would imply that a set of promotions, or stylists belonged to a salon, and thus
are fields in the “salon” table.

3.2 TARGET PLATFORM

3.2.1 Hardware
Any internet-enabled computer
3.2.2 Software
Safari, Mozilla Firefox, google chrome

3.3 PROJECT MILESTONES

-Completed Literature Review: Over the past 8 weeks, I thoroughly researched the work
and tools that have already been released. OpenTable.com is an exemplar of the
application I am aiming to create in terms of functionality. I researched their
implementation and platforms, in addition to exploring the actual application for
functionality and features. I also reviewed the functionality and usability of Google
Calendars and determined that it can be used as a backend database for appointments as
well as a potential front end user interface for appointments. I’ve also researched and
familiarized myself with all the tools mentioned below, which I have gone on to set up
and test.

- Learned PHP and MySQL: I purchased a self-teaching guide to PHP and

MySQL and read the first 300 pages. This familiarized me with the language and the
technology and walked me through a few basic PHP script and MySQL query examples.

- Set up PHP: I downloaded and installed PHP on my computer. I wrote a few basic
scripts to test my installation and confirmed that it was working.

15
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
- Set up MySQL: I downloaded and installed MySQL. I encountered problems with the
daemon but was able to change configurations using the Terminal to eventually get my
computer to run the database.

- Set up MySQL Query Browser: Downloaded and installed this GUI in order to
facilitate interaction with MySQL. I got it running and used it to create a new user
account on my database, as well as the ‘Beautyparlour’ database. Unfortunately, it was
minimally helpful, and still required me to query MySQL using SQL code.
- Set up phpMyAdmin: Downloaded and installed this web-based MySQL
interface. I found it to be extremely useful as a graphical interface for MySQL. I used
this tool to build my database tables and, in some cases, added elements to these tables
(i.e. states).

- Design and Create Database Tables: Iterative design process to eliminate

redundancies and create many-to-one relationships wherever possible

- Set up XAMPP Server: I downloaded xamp; I decided to use xamp after thoroughly
researching the many differing options available, including xamp, wamp, etc. Xampp is
a database abstraction layer that allows me to
write portable PHP code not limited to MySQL.

- Build PHP Functionality: Build the functionality of all use cases mentioned above
except appointment scheduling. This was the largest part of the project and was done
over the course of 3-4 weeks.

3.4 WORK LOG

Design choices

There are two fundamentally different approaches to creating a dynamic web application
that is backed with data. The first is to employ relational data tables in a database
(MySQL) to store, search, and retrieve data. I would then use PHP to communicate with
the database, serving as the link between the web html and the MySQL database. The
advantages of this approach are twofold. First, it makes search and sort operations very
simple. Secondly, it
supports a growing data set in a natural and well-organized fashion. The
16
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
downside is that this design is rigid once building begins. After the
various tables are defined to capture the desired data, it becomes extremely
difficult to redesign or augment the data tables to encompass more or
different data.
The second option is to use text files and file readers to act as a pseudo database.
The advantages here are essentially the reciprocals of the
disadvantages of the database design, and vice versa. While text files can be
much more flexible to changes, they make search and sort operations far more costly

THE NEW PLAN

After research, thought, and discussion with Professor Nimeroff, I've

formulated a plan that shifts the focus of my work. The mere scheduling aspect of the
site is not novel, and the management of scheduling data in my own database would be
extremely tedious and time consuming. So, I decided to look into the offerings of
various calendar toolkits already available on the web. It turns out Google Calendars has
all the functionality that I would need for the scheduling aspect of the site. Google
Calendars supports creation of new calendars, adding and deleting events (including
recurring events), and viewing the schedule. The API for this toolkit is openly available
online and will prove to be very helpful in harnessing this technology towards my
project.

3.5FUNCTIONAL AND NON-FUNCTIONAL

REQUIREMENTS
3.5.1Functional Requirement (FR) is a description of the service that the software
must offer.
Create salon staff and maintaining (Update/ Inactive) their details.
 Create regular customers and maintaining (Update/ Inactive) their details.
 Create salon services and maintaining (Update/ Delete) their details such as

17
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
prices, hours etc.
 Maintain resources (Create/Update/ Delete) at the salon premise.
 Facilitate appointment handling through an event calendar by the system.
 Downloading invoices
 If there is any new services need to be added can be done or delete.
 And we can search a particular appointment and the invoice.
 There is an option to accept the appointment or to reject due to few reasons.And the
information is sent to the client via sms/e-mail .

3.5.2Non-Functional Requirements
Basically, non-functional requirements relate to qualities of the system that cut across
user facing features, such as security, reliability, and performance [5].
 Accessibility – The system is able to be access anywhere at any time by the
authorized users.
 Accuracy – The correctness of data inputs to the system was ensured.
 Availability – System is available within working hours. But can be used at
special occasions also. E.g.: - At a bridal dressing
 Efficiency – Users were given the facility to perform the salon management
processes correctly through the salon sales record management system.
 Effectiveness – Users were given the facility to perform correct salon
management processes via the suggesting system.
 Maintainability – This is a considerable factor especially for a non-technical
user. Maintainability of the system is not more complex.
 Privacy – The confidentiality of the data inputs to the system has been assured.

Chapter 3
4.SECURITY
4.1 SECURITY REQUIREMENTS
Some of the factors that are identified to project the software from accidental or
malicious access, use, modification, destruction, or disclosure are described below.
- As certain functions to different modules
- Restrict communication between areas of the program
18
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
- Check data integrity for critical variables
- A later version of the software will incorporate encryption techniques in the
user/license authentication process
- Communication needs to be restricted when the application is validating the user or
license

CONCLUSION AND FUTURE ENHACEMENTS

Like I mentioned earlier, full integration of opensource tools is critical in creating a
seamless overall application. There are some ways in which Web Calendar was not
integrated which I would like to pursue given more time. The first is to automate Web
Calendar account creation and login when those tasks are completed for the Salon Book
application. This would require inserting a new Salon user into the appropriate
WebCalendar database tables when a parlour creates a parlour book account. Of
course,this would also ensure that the Web calendar account information matches their
parlour book account.The same for login would be an important improvement. As it
exists now, parlour have to log into the WebCalendar application Additionally with in
the Salon Book system when they navigate to it via the Dashboard.
Separate sign in is only required once session though, as the login is stored through
out as session even as they go back and forth from webCalendar to parlour Book. Even
so, automated account creation and login are important integration features that would
be next in line, given more time. Also, a constrain of WebCalendar was that it only
allowed a user to have one calendar.
Ideally, a parlour would have one calendar for each stylist. This could be achieved
using an automated Web Calendar account creation script with a well-defined prefix
naming system. Parlour would be oblivious to what is actually going on behind the
scenes, and simply be able to navigate to calendars that are
Tried to each stylist. When a parlour would add a stylist, another Web Calendar account
(and corresponding calendar) would be created, using a prefix of the stylist name and
parlour name. This would dramatically increase the power of the application as a
schedule visualization and distribution tool. Availability would be more apparent, and
schedules could be printed for each stylist at the start of the day. Additionally, I would
like to host the prototype online and run usability tests with surveys to gauge the

19
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM
effectiveness of the interface and functionality.

20
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

1)akrishnan, R., & Gehrke, J. (2011). Data base management

systems. Boston:McGraw-Hill.

2)Monson-Haefel, R.(2007). J2EE Web services. Boston, Mass.:

Addison-Wesley. Silberschatz, A., Korth, H.F., & Sudarshan,S .
(2011).

3)Data base systems concepts. Estados Unidos: McGraw-Hill

Companies, Inc.

4)Hanna P.(2002): JSP 2.0 The Complete Reference, Second Edition

McGraw Hill Education

21
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

HOME WINDOW

22
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

ABOUT US

23
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

24
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

25
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

26
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

27
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

APPOINTMENT

28
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

ADD CUSTOMER

29
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

REPORTS

30
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

INVOICES

31
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

CODE SNIPPETS
DASH INDEX

32
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

33
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

ADD SERVICES

34
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

35
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

36
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

ADD CUSTOMER

37
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

38
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

39
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

ALL APPOINTMENT

40
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

41
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

42
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

INVOICES

43
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

44
2 BEAUTY PARLOUR 2020-2021
MANAGEMENT SYSTEM

45