Thesis 2014

1
Running Head: SALON MANAGEMENT SYSTEM
DEVELOPMENT OF AN ONLINE SALON MANAGEMENT SYSTEM
MARIE ELLAINE G. CASTILLO
AGNES C. PATUBO
A Thesis Presented to the Faculty

Of the College of Science
Technological University of the Philippines
Ayala Blvd., Manila
In Partial Fulfillment of the

Requirements for the Degree
Bachelor of Science in Information Technology
March 2014
2
SALON MANAGEMENT SYSTEM

COLLEGE OF SCIENCE
Manila
APPROVAL SHEET
This thesis hereto entitled:
DEVELOPMENT OF AN ONLINE SALON MANAGEMENT SYSTEM
prepared and submitted by MARIE ELLAINE G.CASTILLO and

AGNES C. PATUBO in partial fulfillment of the requirements for the degree Bachelor
of Science in Information Technology has been examined and is recommended for
acceptance and approval for ORAL EXAMINATION.
DARWIN C. VARGAS
Adviser
Approved by the Committee on Oral Examination with a grade of PASSED on March

13, 2014.
MINABELLE D. VILLAFUERTE
Chair
MARIA CARMELA F. FRANCISCO PERAGRINO B. AMADOR JR.

Member Member
Accepted in partial fulfillment of the requirements for the degree Bachelor of Science
in Information Technology.
Prof. MARILYN M. IGNACIO

Date: OIC, Office of the Dean
3
Acknowledgement
The success of this study required the help of various individuals. Without them,
the researchers could not have met their objectives in doing this study. The researchers
want to give gratitude to the following people for their invaluable help and support:
To Jesus Christ, our Lord and Savior, for giving them the wisdom, strength,
support and knowledge in exploring things; for his guidance helped them surpass all the
trials that they encountered and for giving determination to pursue their studies and to
make this study possible;
To their parents, for giving the much-needed support and encouragement to
pursue their study, for the love and time for their children;
To Mr. Darwin C. Vargas, their kind, responsible and understanding adviser, who
was always there during the process of doing this thesis giving some advice and ideas to
accomplish this thesis;
And lastly, to the people who helped and contributed great ideas and pieces of
advices, especially classmates and close friends for without them, completion of this
study would not be possible.

4
Abstract
To develop an online salon management system is the main objective of the study. This
project is designed with the following features; (1) update the records of the different
salon branches, (2) provide inquiry of the availability of the services in the different
branches, (3) compute the daily income on service and tips, and (4) generate reports
needed by the management. The system provides an online reservation for the clients for
their convenience. The system also provides accounts for the users in every branch and
for the clients to easily access information about the salon. The tools used to develop the
system were Php as the programming language, MySQL for the database and Yii for the
framework. The system was evaluated by 30 respondents composed of salon employees,
customers, Information Technology experts and students using ISO 9126, an instrument
that measures software quality. The overall weighted mean of 3.60 is interpreted as
highly acceptable. This indicates that the system exhibits the following characteristics: it
is functional, usable, reliable, maintainable, efficient, and portable.
5
Table of Contents
Preliminaries
Title Page 1
Approval Sheet 2
Acknowledgement 3
Abstract 4
Table of Contents 5
List of Tables 8
List of Figures 9
Chapter
1 THE PROBLEM AND ITS SETTINGS
Introduction 11
Background of the Study 12
Objectives of the Study 13
Scope and Limitations of the Study 14
Significance of the Study 15
2 CONCEPTUAL FRAMEWORK
Review of Related Literature 16
Related Studies 24
Conceptual Model of the Study 25
Evaluation 27
6
Operational Definition of Terms 28
3 METHODOLOGY
Project Design 29
Context Data Flow Diagram 29
Top Level Data Flow Diagram 30
Entity Relationship Diagram 31
System Flowchart 36
Project Development 38
Operation and Testing Procedure 40
Evaluation Procedure 41
4 RESULTS AND DISCUSSION
Project Description 43
Project Structure 44
Project Capabilities and Limitations 59
Project Evaluation 59
5 SUMMARY OF FINDINGS, CONCLUSIONS AND
RECOMMENDATIONS
Summary of Findings 60
Conclusions 61
Recommendations 61
References 62
7
Appendixes
Appendix A. Sample Answered Evaluation Sheet 63
Appendix B. Gant Chart 64
Appendix C. Tabulation Sheet 65

8
List of Tables
Table 1. Characteristics and Sub-characteristics Included in the ISO 9126-1 23
Table 2. Numerical Rating Scale and its Qualitative Interpretation 28
Table 3.1. Staff Database Table 33
Table 3.2. Client Database Table 33
Table 3.3. Product Database Table 34
Table 3.4. Service Database Table 34
Table 3.5. Stylist Database Table 35
Table 3.6. Sales Record Database Table 35
Table 4. Numerical Scale Table 42
Table 5. Scale Range Table 42

9
List of Figures
Figure 1. Context Data Flow Diagram of the Existing System 13
Figure 2. Conceptual Model of the Study 25
Figure 3. Context Data Flow Diagram 30
Figure 4. Top Level Data Flow Diagram 31
Figure 5. Entity Relationship Diagram 32
Figure 6. System Flowchart of the System 37
Figure 7. Log In For Admin 44
Figure 8. Customers 45
Figure 9. Items 46
Figure 10. Staffs 46
Figure 11. Services 47
Figure 12. Reservation 47
Figure 13. Branches 48
Figure 14. Users 48
Figure 15. Sales 49
Figure 16. Sales Report 50
Figure 17. User Account Login 50
Figure 18. User Account - Customers 51
Figure 19. User Account - Items 51
Figure 20. User Account - Services 52
Figure 21. User Account - Reservation 53
Figure 22. User Account - Sales 54

10
Figure 23. User Account - Sales Report 54
Figure 24. Customer Access - Homepage 55
Figure 25. Customer Access - About 56
Figure 26. Customer Access - Services 56
Figure 27. Customer Access - Items 57
Figure 28. Customer Access - Register 57
Figure 29. Customer Access - Login as a member 58
Figure 30. Customer Access - Reservation 58

11
Chapter 1
The Problem and Its Setting
As defined by the Random House Dictionary (2014), a beauty salon is
an establishment for the hairdressing, manicuring, or other cosmetic treatment of women.
Beauty salon is different from hair salon. A hair salon is a business where men
and women go to get their hair cut, styled, and dyed. Most salons employ a number of
specialists to cater to the needs of customers, including hairdressers, stylists,
cosmetologists, shampooers, and receptionists. Establishments usually offer a broad
range of hair cutting and styling services to the general public. Some specialty salons,
however, require people to make appointments to receive very particular expert
treatments (wiseGeek.com 2014).
In an article by Mott (2014), a beauty salon can be classified as several different
business types depending upon the reasons why a characterization of the business type
was requested. A beauty salon's business ownership type allows for six possible answers,
while the type of industry a beauty salon belongs to requires a set answer that can be
expanded upon to further describe the type of services a particular salon offers.
Background of the Study
The David’s Cut Expert Salon was founded in 2010. It has nine branches all over
Metro Manila. Its goal is to provide guests with flawless service and impeccable style at
great value. David’s Cut Expert Salon menu of services contains a wide range of options
12
including haircutting and styling, hair coloring, texturizing and a variety of hair
treatments.
The existing system of the David’s Cut Expert Salon is manual system of
processing of data. The customer will request to avail of the service or product and the
cashier or front desk officer of the salon uses logbooks and sheets of paper to record the
services rendered to the customers and their information. It is also used to keep track of
the transactions done in a day. The cashier will give a written receipt to the customer. At
the end of the day, the cashier tallies the income, tips received from customers, each
hairdresser’s number of customers and sharing of collected tips to employees. It will
serve as the day’s sales report that has to be submitted to the management.
The problems encountered in the existing system are possibility in data loss since
logbooks can be lost and easily destroyed and time and effort consumed in scanning and
reviewing of data of sales and customers’ information. Due to its manual system, slow
generation of reports is one of the problems since the salon has nine branches, the
management needs to wait for the sales report of all the branches to view and create a
sales report to be submitted to the owner.
Figure 1 shows the relation of every entity and how it interacts with the system.
As shown in the figure, the system will handle the order, payment and other transactions
to be done.
13
Figure 1. Context Data Flow Diagram of the Existing System
Objectives of the Study
The objective of the study is to develop an Online Salon Management System for
David’s Cut Expert Salon System. Specifically, it aims to:
1. Design the system with the following features:
a. Update the records of the different salon branches.
b. Provide inquiry of the availability of the services in the different branches
c. Compute the daily income on service and tips.
d. Generate reports needed by the management.
2. Create the system as designed.
a. Test and improve the system.

14
b. Determine the acceptability of the system according to functionality,
usability, reliability, efficiency, maintainability, and portability.
Scope and Limitations of the Study
The online system offers an easy access for the users to input and retrieve data for
the operation required. It will help in the process of improving efficient and effective
service to the customers.
The system can store customer’s information and transactions in the database
from all created accounts. The information will be accessible to all the users of the
system, which will help in retrieving records. There are some features that are not
available to other users, such as viewing of all the sales in all branches and editing
information as it will be assigned to the Management level. The main control of the
system will be given to the owner or the personnel trusted by the owner in the main
branch. This is to provide security in all transactions and also for the information of the
patron clients. However, errors because of the user may occur and the system is not
responsible for it.
The system can also be accessed by the customers after creating an account on the
Website Reservation. They can choose location of the branches they prefer and they can
even decide who will be the beautician to attend to them.
The target respondents are the employees of salon and the customers who will use
the system. The statistical tool used to determine the effectiveness of the system is the
statistical mean. The study based on the Gantt Chart (See Appendix A) took nine months
to accomplish prior to the schedule.

15
Significance of the Study
The study hopes to promote efficiency and reliability in the work environment
and its employees. It will be beneficial to the following:
The salon management, for there will be no need for the officer-in-charge in the
main branch to go to the different branches to keep track of the sales. It will help lessen
the time consumed in recording transactions. The possibility of data loss will be
eliminated since the study will have a database. The management can also have the
information regarding the clients.
The clients, for they can easily look for the services and products offered by the
salon without visiting the branches of the salon and they can also see the schedule of the
hairdressers if they are available or not.

16
Chapter 2
CONCEPTUAL FRAMEWORK
This chapter includes the review of related literature, conceptual model of the
study, evaluation system, and operational definition of terms.
Review of Related Literature
The following related literature and studies supported the creation of the system.
Yii
As written by Winesett (2012),Yii is a high-performance, component-based
framework that can be used for developing web applications on any scale. It encourages
maximum code reuse in web programming and can significantly accelerate the
development process.
Yii incorporates many of the great ideas and work from other well-known web
programming frameworks and applications. So if a personis coming to Yii from using
other web development frameworks, it is likely that he or shewill find it familiar and easy
to navigate. Yii also embraces a convention over configuration philosophy, which
contributes to its ease of use. This means that Yii has sensible defaults for almost all the
aspects that are used for configuring one's application. Following the prescribed
conventions, one can write less code and spend less time developing the application.
However, Yii does not force an individual's hand. It allows one to customize all of its
defaults and makes it easy to override all of these conventions.

17
Yii has been carefully designed to allow nearly every piece of its code to be
extended and customized to meet any project requirement. In fact, it is difficult not to
take advantage of Yii's ease of extensibility, since a primary activity when developing a
Yii application is extending the core framework classes.
Yii is a PHP script that contains user interface-related elements, often built using
HTML, but can also contain PHP statements. Usually, any PHP statements within the
view are very simple, conditional or looping statements, or refer to other Yii UI-related
elements such as HTML helper class methods or prebuilt widgets.
Database Management System
As defined by Rouse(2005), database management system (DBMS), sometimes
just called a database manager, is a program that lets one or more computer users create
and access data in a database. The DBMS manages user requests (and requests from
other programs) so that users and other programs are free from having to understand
where the data are physically located on storage media and, in a multi-user system, who
else may also be accessing the data. In handling user requests, the DBMS ensures the
integrity of the data (that is, making sure it continues to be accessible and is consistently
organized as intended) and security (making sure only those with access privileges can
access the data). The most typical DBMS is a relational database management system
(RDBMS). A standard user and program interface is the Structured Query Language
(SQL). A newer kind of DBMS is the object-oriented database management system
(ODBMS).
18
A DBMS can be thought of as a file manager that manages data in
databases rather than files in file systems. In IBM's mainframe operating systems, the
non-relational data managers were (and are, because these legacy application systems are
still used) known as access methods.
A DBMS is usually an inherent part of a database product. On PCs,
Microsoft Access is a popular example of a single- or small-group user DBMS.
Microsoft's SQL Server is an example of a DBMS that serves database requests from
multiple (client) users. Other popular DBMSs (these are all RDBMSs, by the way) are
IBM's DB2, Oracle's line of database management products, and Sybase's products.
Web-Based System
As defined by Rouse (2008), Web based project management software is the
collection of programs, processes and information that is used to manage various phases
of a project and that is accessible on the Internet. Project management entails processes
such as scheduling, calculating a critical path, building timelines, creating task lists,
managing resources, controlling documents and providing audit trails. Each of these
processes can be controlled and sometimes automated through project management
software solutions.
Web based solutions are coded in a browser supported language such as
HTML, ASP or PHP so they can be accessed by clients through a web browser. One
main software version is installed and maintained on a server so that more than one client
can access this version.

19
One disadvantage to using Web-based software is that the program is
usually slower to respond than a typical desktop or client application; Web-based
applications are limited by the speed of one's Internet connection, while client
applications operate as quickly as the client's processor speed. In addition, most
information in Web-based applications is not accessible when a user is offline.
Adobe Photoshop CS4
Based on the study of Willmore and Ablan (2009), when one first opens
Photoshop CS4, the newly designed interface is unassuming. As he or she explores
deeper into the tools and panels, however, he or she might find that the interface can
quickly become cluttered, if not downright confusing.
CS4 creative potential by blending and enhancing images, creating collages,
retouching photographs, colorizing, and working with filters and layer masks. It has
features of smoother panning and zooming, allowing faster image editing at a high
magnification. The interface is more simplified with its tab-based interface making it
cleaner to work with. Photoshop CS4 features a new 3D engine allowing the conversion
of gradient maps to 3D objects, adding depth to layers and text, and getting print-quality
output with the new ray-tracing rendering engine. It supports common 3D formats; the
new Adjustment and Mask Panels; Content-aware scaling (seam carving); Fluid Canvas
Rotation and File display options. The Content-aware scaling allows users to
intelligently size and scale images, and the Canvas Rotation tool makes it easier to rotate
and edit images from any angle.

20
PHP
As written by Gilmore(2010) the PHP language is representative of the
stereotypical open source project, created to meet a developer’s otherwise unmet needs
and refined over time to meet the needs of its growing community.
PHP can do the following:
• Create and manipulate Adobe Flash and Portable Document
• Evaluate a password for guessability by comparing it to language
dictionaries and easily broken patterns
• Parse even the most complex of strings using the POSIX and Perl-based
regular expression libraries.
MySQL
As written by TradeArabia News Service (2013)with increased performance,
scalability, reliability and manageability, MySQL 5.6 helps users meet the most
demanding Web, Cloud and embedded application requirements.
MySQL 5.6 improves developer agility with subquery optimizations, online Data
Definition Language (DDL) operations, NoSQL access to InnoDB, new instrumentation
in Performance Schema and better condition handling.
Likert Scale
According to Cherry (2014), the Likert Scale is a psychometric scale commonly used
in questionnaires and survey research. It is the sum of responses on several Likert items.
Likert scale consists of five-level items: “Strongly Disagree”, “Disagree”, “Neither Agree
21
or Disagree”, “Agree” and “Strongly Agree”. A Likert item is a statement which the
respondent is asked to evaluate according to any kind of criteria. In Likert Scale, the level
of agreement or disagreement is measured. It is a bipolar scaling method, measuring
either positive or negative response to a statement.
ISO 9126
Based on the ISO 9126 manual, it is an international standard for the evaluation of
software. The standard is divided into four parts which addresses, respectively, the
following subjects: quality model, external metrics, internal metrics, and quality in use
metrics. ISO 9126 part one, referred to as ISO 9126-1 is an extension of previous work
done by McCall, Boehm, FURPS and others in defining a set of software quality
characteristics.
The ISO 9126-1 software quality model identifies six main quality characteristics,
namely: functionality, reliability, usability, efficiency, maintainability, and portability.
These characteristics are broken down into sub-characteristics. The main characteristics
of the ISO 9126-1 quality model can be defined as follows:
Functionality. Functionality is the essential purpose of any product or service. For
certain items this is relatively easy to define. The main point to note is that functionality
is expressed as a totality of essential functions that the software product provides. It is
also important to note that the presence or absence of these functions in a software
product can be verified as either existing or not.
Reliability. Once a software system is functioning, as specified, and delivered the
reliability characteristic defines the capability of the system to maintain its service
22
provision under defined conditions for defined periods of time. One aspect of this
characteristic is fault tolerance, that is, the ability of a system to withstand component
failure. For example, if the network goes down for 20 seconds then comes back the
system should be able to recover and continue functioning.
Usability. Usability only exists with regard to functionality and refers to the ease of use
for a given function. The ability to learn how to use a system (learnability) is also a major
sub-characteristic of usability.
Efficiency. This characteristic is concerned with the system resources used when
providing the required functionality. For example, the usability of a system is influenced
by the system’s performance, in that if a system takes 3 hours to respond the system
would not be easy to use although the essential issue is a performance or efficiency
characteristic.
Maintainability. The ability to identify and fix a fault within a software component is
what the maintainability characteristic addresses. Maintainability is impacted by code
readability or complexity as well as modularization. Anything that helps with identifying
the cause of a fault and then fixing the fault is the concern of maintainability. Also the
ability to verify (or test) a system, i.e. is one of the sub-characteristics of maintainability.
Portability. This characteristic refers to how well the software can adopt to changes in its
environment or with its requirements. The sub-characteristics of this characteristic
include adaptability. Object oriented design and implementation practices can contribute
to the extent to which the characteristic is present in a given system.
The objective of this suite of standards is to provide a framework for the evaluation of
software quality. ISO/IEC 9126 does not prescribe specific quality requirements for
23
software, but instead describes a quality model, which can be applied to any software.
This ISO standard includes the user's view and introduces the concept of ‘quality in use’.
(ISO 9126 Software Quality Model, 2013)
According to Kotzes (2013), the full table of characteristics and sub-characteristics
included in the ISO 9126-1 Quality Model is shown in Table 1.
Table 1.
Characteristics and Sub-characteristics Included in the ISO 9126-1
Characteristics Sub-Characteristics Explanation
Functionality Suitability ‘Can software perform the tasks required?’

Accurateness ‘Is the result as expected?’
Compliance ‘Is the system compliant with standards?’
Security ‘Does the system prevent unauthorized access?’
Reliability Maturity ‘Have most of the faults in the software been
eliminated over time?’
Fault tolerance ‘Is the system capable of handling errors?’
Recoverability ‘Can the system resume working and restore lost
data after failure?’
Usability Understandability ‘Does the user comprehend how to use the system
easily?’
Learnability ‘Can the user learn to use it easily?’
Operability ‘Can the user use the system without much effort?’
Efficiency Time Behaviour ‘How quickly does the system respond?’
Resource utilization ‘Does the system utilize resources efficiently?’
Maintainability Analyzability ‘Can faults be easily diagnosed?’
Changeability ‘Can the system be easily modified?’
24
Stability ‘Can the system continue functioning if changes

are made?’
Portability Adaptability ‘Can the system be moved to other environments?’
Installability ‘Can the system be installed easily?’
Replaceablity ‘Can the system easily replace other software?’
Review of Related Studies
Based on the study of MarnickGatt (2013), developing a web-based driven
information software enable hair salons to capture information about their clients and
make the best use of it. To be successful the salon management must offer individual
attention to every client coming into the salon, one must keep in mind that each client
will have different needs and expectations. It is a well known fact that if the salon
succeeds in satisfying the client’s needs, they will keep coming back. By keeping records
about client purchases, the salon can offer clients other products and services that they
might be interested in.
The software intends to enhance each individual client relationship to ensure long
term client loyalty and retention. The study has shown the advantages of a salon if it uses
an automated system such as clients can be treated efficiently and information of clients
can be managed easily.

25
Conceptual Model of the Study
The conceptual framework of the system consists of INPUT, PROCESS and OUTPUT
which helped us to analyze and begin with the planning of the project.
INPUT PROCESS OUTPUT

Knowledge  Project Design
Online Salon
Requirements:
 Project Management
 Salon Development System
Management
processes  Operations and
 Online and Testing
Networking Procedures
Procedure
 Evaluation
 PHP Procedures
Programming
 Database
Management
 Lickert Scale
 ISO 9126
Software
Requirements:
 Yii
 PHP
 MYSQL
 Crystal Reports
 Adobe Photoshop
Hardware
(specifyspecs)Requirem
ents:
 Computer Unit
with 4GB RAM,
128GB Storage EVALUATION
 Printer
Figure 2.Conceptual Model of the Study

26
Input
The Input consists of three parts, knowledge requirements, software requirements, and
hardware requirements. First is the knowledge requirements which include study of
related lessons, discussion, activities, and other related information about Salon
Management and Online System Processes. Second is the software requirements, PHP
was used as the programming language of the system .PHP is a server-side
scripting language designed primarily for web development but also used as a general-
purpose programming language. For the database management MySQL was used, it is an
open source database and provides a secure, fast and reliable enough database service
which is implemented in many professional web environments. For the system’s design
and interface, Adobe Photoshop was used, the most popular program for creating and
modifying images for the web. Finally, for the hardware requirements a computer unit
with dual core processor was needed, at least 4GB RAM, disk space of 128GB and with
Windows 7 Operating System and HP LaserJet printer.
Process
There were four main steps of processes in the study namely project design, project
development, operational and testing / debugging and evaluation procedure. The project
design included the general features of the project. The project development involved
data gathering and explaining how the project was conceptualized until it was finished.
The Operation and Testing procedures dealt with how the project was encoded, debugged
and checked and the corrections made. The evaluation procedure described how the
27
project was evaluated by the users and experts. The respondents' reaction and individual
results of the entire system were also included.
Output
After conducting the process and subjecting the study to a series of evaluation, the
output is the developed Online Salon Management System.
Evaluation
Lastly, the Evaluation Process was conducted to assess the quality of the software. The
following section provides description of the evaluation system used in the study. This
section presents the Respondents' Profile, Statistical Method, the Evaluation Instruments,
and the Operational Definition of Terms.
Evaluation Instrument
Respondents answered an evaluation form using the criteria defined by ISO 9126. The
criteria include operability, maintainability, portability and efficiency. Criteria were rated
in a scale of 1-4, with four (4) as the highest or “Very Acceptable”, and three (3) as
“Acceptable”, two (2) as “Fairly Acceptable”, and one (1) as the lowest or “Not
Acceptable” as shown in Table 2:

28
Table 2.
Numerical Rating Scale and its Qualitative Interpretation
Numerical Rating Descriptive Rating

4 Highly Acceptable
3 Very Acceptable
2 Acceptable
1 Not Acceptable
Operational Definition of Terms
To further understand the study, the following terms are defined:
Inventory Data is the information about the products offered especially how many were
sold and remained.
Sales Data is the information about the sales of each branch offering services and
products.
Customer/Client Data are the data or information about the patron clients that includes
the services rendered and sold products.
Online System refers to a system that can be operated using the Internet and can be
accessed in different locations anytime.

29
Chapter 3
METHODOLOGY
This chapter discusses the project design, project development, operation and
testing procedures, and the evaluation procedures.
Project Design
The project design is meant to describe the representation of the proposed system
in terms of its flow, entities and existing relationships. Below are the illustrations of
proposed system’s Flowchart, Context Diagram, Top-Level Data Flow Diagram and
Entity-Relationship Diagram.
Context Data Flow Diagram
The Context Data Flow Diagram of the proposed system as shown in Figure 3
begins when the client request to avail the services or products of the salon. The
employee will record the services or products the customer wants to avail in the system.
The payment given by the customer will be recorded in the system and the employee will
issue receipt to the customer. The transaction will be recorded and the sales report can be
generated to submit to the management.

30
Figure 3. Context Data Flow Diagram
Top Level Data Flow Diagram
The Top-Level Data Flow Diagram of the system is shown in Figure 4. In the
beginning of the process, the customer will choose a transaction and the employee will
check on item availability or services schedules in the system (Process 1.0). Then the
next process upon completion of transaction, the customer will settle the payment. The
system will verify the records and then the employee can now proceed on processing the
payment. Upon complete payment, the employee will issue a receipt and the customer’s
record will be updated (Process 2.0). Finally, the sale transaction will be recorded on the
system and the sales reports can now be generated from the system to be submitted to the
management (Process 3.0).

31
2.0
Customer Settle Payment
Verify Record
Issue receipt Payment
Update Customer’s record
Choose Transaction Employee
1.0
D2 Customer’s Record
Orders /
Requests
Employee
3.0
Reports
View Items & On-stock / Update Record
Generation
Services Schedule
Employee
D1 Items Inventory
Viewing of Reports Management
Figure 4.Top Level Data Flow Diagram
Entity Relationship Diagram
Figure 5 shows the Entity Relationship Diagram which is a graphical
representation of entities and their relationships to each other, typically used in
computing in regard to the organization of data within databases or information systems.
An entity is a piece of data-an object or concept about which data is stored. The type of
relationship used was the One-to-Many, where one entity is associated to another entity
in many instances.
32
Figure 5.Entity Relationship Diagram

33
Normalized Table
The different database tables used in the system are explained below:
Table 3 shows the table of Staff database and it has two attributes, the StaffID and
Password.
Table 3.1
Staff Database Table
Attribute Data type
StaffID int
Password varchar
Table 3.2 shows the table of Client database, the attributes are composed of the
information of clients that are useful for the transaction and advertisement purposes.
Table 3.2.
Client Database Table
Attribute Data type
ClientID int
Name varchar
Address varchar
Conctacts int
ServiceID int
ProductID int
StylistID int
34
Table 3.3 shows the table of Product database, the attributes are composed of the Product
ID, Product Name and Price.
Table 3.3
Product Database Table
Attribute Data type
ProductID int
ProductName varchar
Price float
Table 3.4 shows the table of Service database, the attributes are composed of the Service
ID, Service Name and Price.
Table 3.4.
Service Database Table
Attribute Data type
ServiceID int
ServiceName varchar
Price float
Table 3.5 shows the table of Stylish database, the attributes are composed of the Stylish
ID, Stylish Name and Service ID.

35
Table 3.5.
Stylist Database Table
Attribute Data type
StylistID int
StylistName varchar
ServiceID int
Table 3.6 shows the table of Sales Record database, the attributes are composed of the
information that will be necessary for sales report.
Table 3.6.
Sales Record Database Table
Attribute Data type
RecordID int
Date varchar
Price float
ClientID int
ServiceID int
ProductID int
36
System Flowchart
The System Flowchart as shown in Figure 6, illustrates the process on how the
System works on Salon operations, specifically on the item purchase and online
reservation of the customers. Upon successful login, the main menu will take place and
customer can now choose between “Item Purchase” and “Services Offered” of the salon.
The employee can now proceed on transaction of the customer once they have decided.
Upon complete purchase or service has been rendered, the system will proceed to
payment and print receipt. The sale transaction has been saved on the database and the
reports will be updated. Finally, the employee can now generate the sales report of the
day and submit it to the management.

37
Start
Log In to the system
Successful NO
Login?
YES
Main Menu
Purchase Item Services
Process Transaction
Input Customer’s
Information
Input details of
Purchase/Services
Proceed on Payment
Print receipt Updated Data

on website
Transaction Sales Transaction saved

Completed on Database
END
Figure 6. System Flowchart of the proposed system

38
Project Development
The researchers decided to use the waterfall method of the systems development
life cycle. Waterfall method is ideal for this project due to its linear sequence that is
necessary for an efficient development process.
1. Requirement Gathering
Every development of a system requires data to achieve its full potential and its
desired functionality. Thus, this is the first and foremost phase of every system
development. In this phase, the necessary data gathered include the customer’s wants and
needs for the product or services, the customer’s profile and also the competitors around
the location of salon. This is the core of everything that the system will be producing. Itis
going to be the basis of every input and output of each data the system will be using.
2. System and Software Design
The next phase was the process of creating the body of the system. This is the
phase where the design of the system is well furnished and done. After gathering all data,
it is time to consolidate all wants and expectations coming from the client to what they
wanted the program to be. The appearance of the system and what market it is supposed
to be targeting. As for this system, the target market is a customer who seeks beauty
products and services. The system’s design must be appropriate for the user to improve
the efficiency of the entire salon operations.

39
3. Implementation and Testing
One of the most important phases in this development cycle is the Implementation
and Unit Testing. To achieve a successful implementation of this project, system testing
process will took an important phase to completely deliver an effective system to the
client. Every single function must be tested according to the business requirements, it
should perform the function and produce an expected result from beginning to end of the
transactions. The next step is the UAT process, where the client will be the one to do the
testing of the system to find out if it successfully meets their expectation. This phase will
help recognize and minimize the errors that the system might encounter once it is
implemented in the company.
4. Operations and Maintenance
After every implementation, the operations and maintenance of the system are the
last phase of development cycle. The Operations mainly focus on the activity of the users
in the system, in this cycle the feedback of system’s efficiency, usability, functionality
and accuracy of the reportsare taken. The system maintenance is for the purpose of
enhancing the overall system’s acceptability to the users. In addition, data files backup is
one of the most important processes of maintaining the system.

40
Operation and Testing Procedure
The system’s operational procedure was done by following the steps below:
I. INSTALLING THE SOFTWARE
1) Made sure that the computer meets the requirements of the system.
2) The manuals for the program or the readme file located in the same directory
as the installation commonly contain exact instructions on how to install the
program.
3) Waited until the application is completely installed.
II. OPERATIONS PROCEDURE
1.) Opened the website.
2.) Logged in to the website using Administrator account.
3.) Created account for Users.
4.) Logged in to the website using Users’s account
5.) Created transaction using the user’s account.
6.) Generated sales report.
III. TESTING PROCEDURE
1) The administrator/personnel-in-charge must be the one to supply the system’s
username and password in order to access and run the system.
2) Logged in to the website using the created account of Employee.
3) Created transaction by choosing ‘Item Purchase’.
4) Created transaction under ‘Services’, check on the schedule of Stylist/
Beauticians.
5) Settlement of payment and then printed receipt from the system.

41
6) Generated sales report.
Evaluation Procedures
To be able to determine if the system is acceptable and user friendly, the group
conducted an evaluation to 31 respondents.
The following procedures were followed:
1.) Each respondent was given a set of questionnaire.
2.) The researchers discussed the system flow and each was given the chance to test
and evaluate its performance.
3.) The results were tabulated and the statistical mean ratings were computed using
the scale range: at rating scale of 1 to 4 where 4 corresponds to Highly Acceptable
and 1 corresponds to Not Acceptable.
Evaluation Instrument
The evaluation instrument used the criteria as defined in ISO 9126. The criteria include
functionality, reliability, usability, efficiency, maintainability, and portability.
The numerical and descriptive rating of the evaluation instrument is found in Table 8.
This is a 4-point scale where 4 corresponds to Very Acceptable, 3 corresponds to
Acceptable, 2 corresponds to Moderately Acceptable, and 1 corresponds to Not
Acceptable.
42
Table 4.
Numerical Scale Table
Numerical Scale Rating
Numerical Rating Qualitative Interpretation
4 Very Acceptable
3 Acceptable
2 Moderately Acceptable
1 Not Acceptable
The ratings of the respondents were tabulated, means were calculated and interpreted
using the scale in Table 5. The mean range from 1.0 to 1.7 is interpreted as “Not
Acceptable”, 1.8-2.5 as “Moderately Acceptable”, 2.6-3.3 as “Acceptable”, and 3.4 -4.0
as “Very Acceptable” and the highest range in the scale.
Table 5.
Scale Range Table
Scale Range Table
Numerical Rating Qualitative Interpretation
3.4 – 4.0 Very Acceptable

2.6 – 3.5 Acceptable
1.8 – 2.5 Moderately Acceptable
1.00 – 1.7 Not Acceptable
43
Chapter 4
RESULTS AND DISCUSSION
This chapter contains the project description, project structure, project capabilities and
limitations, test results, and project evaluation.
Project Description
The development of an Online Salon Management System for David’s Cut Expert
Salon was designed and created to monitor the sales in all the branches of the salon and
for the clients to inquire reservations about its services. It was developed to help the
company in the form of advertising because of the ability of the Internet nowadays. This
kind of system will allow the customers to know information about the company and will
have comfortable ways of accessing the site. It also allows the viewing of schedules and
services in each branch.
The system has three types of user accounts namely; Administrator, Staff and
Client accounts. The Administrator account is where the setup of User Account,
Branches, Services, viewing of Reservations and Sales can be performed on this access.
The Staff Account is where the employee can process the transaction of the clients. The
Client account is where the clients can view the items and services offered by the Salon.
The accounts created on the system are secured and all transaction records will be saved
on its database. The system is capable of generating Sales report and the records are
secured on its database. It was created using PHP, CSS, and MySql. Yii was used for
creating the framework of the website.

44
Project Structure
The system was developed using the web-based portal. The following figures are
the interface of the system for Administrator account, User Account and Customer’s
Online Reservation.
The initial set-up of the system will be under the Administrator’s account. The
main function of the Admin is to create the user account, add branches and modify the
authorization level of the users as well as the assigned branch. The Admin can also
monitor the Customer’s visit on the branches, the reservation from website and the sales
of all the branches.
The Administrator System Interface
The Login page for the Admin as shown in Figure 7 is the starting point of the
system. The Administrator account has the full access of the system where he/ she can
Add, Edit or Delete entry in all modules.
Figure 7.Log In For Admin

45
The first screen of the system is the ‘Customer’ module as shown in Figure 8. In
this module the Admin can view the list of customers and create customers as well for the
new entry. Use the ‘Advance Search’ button to help in gathering specific information of
the customer.
Figure 8. Customers
The second module of the system is the ‘Items’ as shown in Figure 9. It is where the
Admin can manage the ‘Items Available’ on the branch and it will be posted on the
website for customer’s awareness. The Admin can modify the item description and
amount using the tools on the last column (Add, Edit or Delete).
46
Figure 9. Items
The third module of the system is the ‘Staff’ as shown in Figure 10. It is where the
Admin can register the information of the staffs. The details of Status and Branch can be
modify using the tools on the last column (Add, Edit or Delete).
Figure 10. Staffs

47
The ‘Services’ module as shown in Figure 11 is where the Admin can manage the
services offered by the Salon. It includes the Service Code, Service Name and Service
Charge. They can also modify the details of services using the tools on the last column.
Figure 11.Services
The ‘Reservation’ module as shown in Figure 12, is where the Admin can monitor
the information of customer’s reservation. It also has the function to add entry using the
‘Create Reservation’ operation, this is in case a problem is encountered on the website
and the customer opts to call on the Customer Support.
Figure 12.Reservation
48
The ‘Branches’ module as shown in Figure 13 is where the information about the
Branches code and corresponding users can be managed. It also has the function to Add,
Edit or Delete the created entry.
Figure 13.Branches
The ‘Users’ module as shown in Figure 14 is where the admin can add, edit or delete
user account. It also includes the authorization level and branch where they are assigned.
The Admin can modify the user's account using the tools onthe last column.
Figure 14.Users
49
The last module of the system is the ‘Sales’ as shown in Figure 15. It is where the
transactions of all the branches are consolidated. The Admin is allowed to add or modify
sales entry on the system using the Operations tools: List Sales and Create Sales.
Figure 15. Sales
The Sales Report generated from the system as shown in Figure 16is composed of
the transaction details including Customer Name, Service Availed, Date and Amount.
50
Figure 16.Sales Report
The User Account System Interface
The Login page for the User account as shown in Figure 17 is the starting
interface for the users. It is an access where they can encode sale transaction, view the
reservations, items and services details.
Figure 17. User Account Login

51
The first module for the User account is the ‘Customers’ as shown in Figure 18.
This is where the user can view the information of Customers and also create entry using
the Operation tools.
Figure 18.User Account – Customers
The next module for the User account is the ‘Items’ module as shown in Figure
19. This is where the user can view the list of items on-stock and the corresponding
amount. They do not have the access to modify the description or add entry on the list.
Figure 19. User Account - Items

52
The ‘Services’ module as shown in Figure 20 is where the users can view the
information of services. The same with the Items module, they cannot modify the
description or service charge, the access is for viewing only.
Figure 20. User Account – Services
The next module is the ‘Reservation’ as shown in Figure 21. On this module, the
user account can view the information of the Client’s reservation from the online website.
This function will help improve the efficiency of the operations as it already provided the
details of the services the client wants to receive. In this module the user can now
anticipate the sales of the day and be able to manage the tasks of the Beauticians,
Manicurist, Hair Dresser and other staffs on the specific day.

53
The user can only view the details of the reservation as a reference. They cannot
add or modify the information and the only way to change the details is through Admin
account. The client should coordinate the changes of details by calling the contact
number provided on the website reservation.
Figure 21. User Account - Reservation
The last module for the user account is the ‘Sales’ module as shown in Figure 22.
This is where the user can encode the transaction of the customers from walk-in and
online reservation. The user account has a full access on this module, they can view or
create an entry using the Operations tool, and modify the entry using the tools on the last
column that corresponds to the entry.

54
Figure 22.User Account - Sales
The ‘Sales Report’ as shown in Figure 22 can be generated from the system by
clicking the button ‘Print Report’ on Sales module.
Figure 23. User Account - Sales Report

55
The Website Reservation – Client Interface
The Home Page of the system website is shown in Figure 24,it is where the client
can view the information about the items, services and personnel of the salon. They can
also create an account to become a member and then create reservation.
Figure 24. Customer Access - Home Page
The first module of the website is ‘About’ as shown in Figure 25, it is where the
customer can view the information about the Beauticians, Manicurists, Hair Dressers and
other Staffs. Providing the customers the details of Salon’s Professional personnel will
help them to improve the relationship between clients and the staffs, as they will continue
to promote the customer’s satisfaction in all areas of their services.

56
Figure 25.Customer Access - About
The next module is the ‘Services’ as shown in Figure 26, it is where the
information of services offered in all the branches are posted.
Figure 26. Customer Access – Services

57
Then it follows with the ‘Items’ module as shown in Figure 27. This is where the
customer can see all the available items on the branch.
Figure 27. Customer Access - Items
For the customer to start on the reservation, they need to become a member (as
shown on Figure 28) and then be able to see the services & items available.
Figure 28.Customer Access - Register

58
Upon creating an account, the customer can now login on his/her account to start
on the reservation (as shown in Figure 29).
Figure 29.Customer Access - Login as a member
The Customers can now book the services they desire on their most convenient
time and it will be posted on the Admin and User account of the Salon. See Figure 30.
Figure 30. Customer Access - Reservation

59
Project Capabilities and Limitations
Capabilities of the system are as follows:
1. The Administrator account can view all the sales in each branch.
2. Create unlimited user accounts depending on the number of the branches.
3. Modify the user account’s permission and assigned branch.
4. User/staff account can update the sale of the branch assigned to him or her.
5. Customers can create reservations online anytime.
6. The system can generate a sales report of all the branches.
Limitations of the system are as follows:
1. Reservations are done using their account in the system
2. The system has no Live Chat with the customer.
3. The system cannot cater inquiry online.
Project Evaluation
The project was evaluated by 31 respondents composed of students, employees
and professors. This is to determine its functionality, reliability, usability, efficiency,
maintainability and portability. The summary of the respondents' evaluation is found in
Appendix C.
60
Chapter 5
Summary of Findings, Conclusions and Recommendations
This chapter discusses the summary of findings, conclusions, and
recommendations for the system.
Summary of Findings
Findings on the evaluation shows that:
1. The developed system yielded a mean rating of 3.60 providing to be “highly
acceptable” in terms of functionality. The functions included in the system are
fully functional.
2. The developed system yielded a mean rating of 3.38 providing to be “very
acceptable” in terms of reliability. The system does not terminate despite errors
or bugs encountered.
acceptable” in terms of usability. Display instructions and user interface are easy
to understand. The system is easy to operate.
4. The developed system yielded a mean rating of 3.44 providing to be “very
acceptable” in terms of efficiency. The system can execute the request in a timely
manner. The system uses resources efficiently and appropriately.
5. The developed system yielded a mean rating of 3.62 interpreted as “highly
acceptable” in terms of functionality. The system can easily be modified for
expansion and correction.

61
acceptable” in terms of functionality. The system can run on different operating
environments. The system can be easily installed.
Conclusions
Upon the completion of the study, the following conclusions were derived:
1. The system was developed based on the following features:
a. Updates records of different branches of salon.
b. Provides information of the available products and services in
different branches.
c. Computes the daily income of services and products.
d. Generates sales reports needed by the management.
2. The system was developed according to its functions.
3. The system was improved in terms of system’s functionality, reliability,
usability, efficiency, maintainability and portability.
4. The system was rated “Very Acceptable”.
Recommendation
For further enhancement of the system, the study recommends the following:
1. Enhancement of the design of the website interface.
2. Search engine for better browsing of the information.
3. Add Live-Chat functions on the website for better use of the clients.
62
References
Rouse, M. (2005). Database management system (DBMS).Techtarget.Retrieved from

http://searchsqlserver.techtarget.com/definition/database-management-system
Rouse, M. (2008). Web based project management software. Techtarget.Retrieved from

http://whatis.techtarget.com/definition/Web-based-project-management-software
beauty parlor. (n.d.). Random House Dictionary. US: Random House, Inc.
hair salon. (n.d.).wiseGEEK.com Unabridged. Retrieved March 08, 2014, from

wiseGEEK.com website: http://www.wisegeek.com/what-is-a-hair-salon.htm
Mott A. (2008). What type of business are beauty salons? Retrieved from:
http://smallbusiness.chron.com/type-business-beauty-salons-32010.html
TradeArabia News Service (2013, February 6). Oracle announces availability of MySQL
5.6. TradeArabia business news information.Retrieved from
http://www.tradearabia.com/news/IT_230312.html
Winesett J. (2012). Web application development with YII and PHP.Birmingham, UK:
Packtpub Publishing.
Gilmore W.J. (2010). Beginning PHP and MySQL(4th Ed.). New York, US: Apress
63
Appendix A
EVALUATION SHEET
College of Science
Mathematics Department
Name(Optional): __________________________________________ Occupation: ________________

Date:________________
Direction: Please check the appropriate column corresponding to your evaluation of the project study
entitled “Development of Online Salon Management System” using the scale below.
Numerical Rating Descriptive Rating
4 Highly Acceptable
3 Very Acceptable
2 Acceptable
1 Not Acceptable
DESIGN CRITERIA 4 3 2 1
A. Functionality
1. Quality of being suitable or fitted to the target functionality. (suitability)
2. The functions included in the system are fully functional. (accuracy)
3. Protection against malicious attacks and data protection. (security)
B. Reliability
1. The completeness of the system. (maturity)
2. Does not terminate despite errors or bugs encountered. (fault tolerance)
3. Overall reliability of the system. (reliability compliance)
C. Usability
1. Displays instructions and user interface are easy to understand. (understandability)
2. Capability of the system to enable the user to learn how to use it. (learnability)
3. The system is easy to operate. (operability)
D. Efficiency
1. The system can execute the request in a timely manner. (time behavior)
2. The system uses resources efficiently and appropriately. (resource utilization)
3. Overall efficiency of the system. (efficiency compliance)
E. Maintainability
1. Can identify the resource of failure when an error is encountered. (analyzability)
2. The system can be easily modified for expansion and correction. (changeability)
3. The ability of the system to remain stable against unusual conditions. (stability)
F. Portability
1. The system can run on different operating environments. (adaptability)
2. The system can be easily installed. (installability)
3. Overall portability quality of the system. (portability compliance)
Comments/ Suggestions:
________________________________________________________________________
________________________________________________________________________
THANK YOU!
64
Appendix B
In the image shown below, the row represents the activity to be done while the
columns represent the range of month and weeks that the system needs before it is done.
Month Jun '13 Jul '13 Aug '13 Sep '13 Oct '13 Nov '13 Dec '13 Jan '13 Feb '13 Mar'13
1 1 1 1 1 1 1 1 1 1
2 2 2 2 2 2 2 2 2 2
WEEK 3 3 3 3 3 3 3 3 3 3
4 4 4 4 4 4 4 4 4 4
Project Proposal
Project Planning
Project Initiation
Project Research
System Design
System Development
System Validation
Report Writing
Project Presentation
Completed
Continue Activity
65
Appendix C
SUMMARY OF RESPONDENTS' EVALUATION
Design Criteria Mean Interpretation

A. Functionality 3.60 Highly Acceptable
1. Suitability 3.60 Highly Acceptable
2. Accurateness 3.53 Highly Acceptable
3. Interoperability 3.67 Highly Acceptable
B. Reliability 3.38 Very Acceptable
1. Maturity 3.53 Highly Acceptable
2. Fault Tolerance 3.23 Very Acceptable
C. Usability 3.79 Highly Acceptable
1. Understandability 3.80 Highly Acceptable
2. Learning Process 3.87 Highly Acceptable
3. Operability 3.70 Highly Acceptable
D. Efficiency 3.44 Very Acceptable
1. Time Behavior 3.37 Very Acceptable
2. Resource Behavior 3.50 Highly Acceptable
E. Maintainability 3.62 Highly Acceptable
1. Stability 3.57 Highly Acceptable
2. Testability 3.67 Highly Acceptable
F. Portability 3.77 Highly Acceptable
1. Installation Process 3.80 Highly Acceptable
2. Adaptability 3.73 Highly Acceptable

Thesis 2014

Diunggah oleh

Informasi Dokumen

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Thesis 2014

Diunggah oleh

Hak Cipta:

Format Tersedia

1

Running Head: SALON MANAGEMENT SYSTEM

DEVELOPMENT OF AN ONLINE SALON MANAGEMENT SYSTEM

MARIE ELLAINE G. CASTILLO

A Thesis Presented to the Faculty

In Partial Fulfillment of the

Technological University of the Philippines

DEVELOPMENT OF AN ONLINE SALON MANAGEMENT SYSTEM

prepared and submitted by MARIE ELLAINE G.CASTILLO and

Approved by the Committee on Oral Examination with a grade of PASSED on March

MARIA CARMELA F. FRANCISCO PERAGRINO B. AMADOR JR.

Prof. MARILYN M. IGNACIO

make this study possible;

To their parents, for giving the much-needed support and encouragement to

accomplish this thesis;

study would not be possible.

1 THE PROBLEM AND ITS SETTINGS

Background of the Study 12

Objectives of the Study 13

Scope and Limitations of the Study 14

Significance of the Study 15

Review of Related Literature 16

Conceptual Model of the Study 25

Operational Definition of Terms 28

Context Data Flow Diagram 29

Top Level Data Flow Diagram 30

Entity Relationship Diagram 31

Operation and Testing Procedure 40

4 RESULTS AND DISCUSSION

Project Capabilities and Limitations 59

5 SUMMARY OF FINDINGS, CONCLUSIONS AND

Appendix A. Sample Answered Evaluation Sheet 63

Appendix B. Gant Chart 64

Appendix C. Tabulation Sheet 65

Table 1. Characteristics and Sub-characteristics Included in the ISO 9126-1 23

Table 2. Numerical Rating Scale and its Qualitative Interpretation 28

Table 3.1. Staff Database Table 33

Table 3.2. Client Database Table 33

Table 3.3. Product Database Table 34

Table 3.4. Service Database Table 34

Table 3.5. Stylist Database Table 35

Table 3.6. Sales Record Database Table 35

Table 4. Numerical Scale Table 42

Table 5. Scale Range Table 42

Figure 1. Context Data Flow Diagram of the Existing System 13

Figure 2. Conceptual Model of the Study 25

Figure 3. Context Data Flow Diagram 30

Figure 4. Top Level Data Flow Diagram 31

Figure 5. Entity Relationship Diagram 32

Figure 6. System Flowchart of the System 37

Figure 7. Log In For Admin 44

Figure 10. Staffs 46

Figure 11. Services 47

Figure 12. Reservation 47

Figure 13. Branches 48

Figure 14. Users 48

Figure 15. Sales 49

Figure 16. Sales Report 50

Figure 17. User Account Login 50

Figure 18. User Account - Customers 51

Figure 19. User Account - Items 51

Figure 20. User Account - Services 52

Figure 21. User Account - Reservation 53

Figure 22. User Account - Sales 54