TRIBHUVAN UNIVERSITY

FACULTY OF HUMANITIES AND SOCIAL SCIENCE

A Project Report on
Salon Management System
Submitted to

Department of Computer Application

Southwestern State college, Basundhara, Kathmandu

In partial fulfillment of the requirements for the Bachelors in

Computer Application

Submitted By

Name: Shishir Dhakal

TU Roll no: 53002078

Name: Nishan Gurung

TU Roll no: 53002073

Jun 18, 2024

 TRIBHUVAN UNIVERSITY

FACULTY OF HUMANITIES AND SOCIAL SCIENCES

SUPERVISOR’S RECOMMENDATION

We hereby recommend that this project is prepared by Shishir Dhakal and Nishan Gurung
under supervision by Mr. Bijay Babu Regmi entitled “Salon Management System” in
partial fulfillment of the requirements for the degree of Bachelor of Computer Application
be processed for the evaluation.

Mr. Bijay Babu Regmi

Project Supervisor

ii
 LETTER OF APPROVAL

This is to certify that this project is prepared by Shishir Dhakal (53002078) and Nishan
Gurung (53002073) entitled “Salon Management System” in partial fulfillment of the
requirements for the degree of Bachelor in Computer Application has been evaluated. In
our opinion it is satisfactory in the scope and quality as a project for the required degree.

Mr. Kiran Ghimire Mr. Bijay Babu Regmi

Internal Supervisor Project Supervisor

BCA Department BCA Department

Southwestern State College Southwestern State College

Mr. Ravi Chapagain External Examiner

Academic Head

Southwestern State College

iii
 ACKNOWLEDGEMENT
Before delving into the details, we want to express our heartfelt appreciation for the
individuals who have been integral to this project since its inception. Crafting this project
has posed significant academic challenges, and it wouldn't have been accomplished without
the support, patience, and guidance of those involved. Our deepest gratitude goes out to
them.

We take great pleasure in presenting this project report on the "Salon Management
System". It has been an honor to work alongside a dedicated team, including our project
guide, who has been with us since the beginning. The success of this endeavor is a testament
to the hard work and determination we've put in, alongside the invaluable assistance of our
project guide. We wish to extend a special note of thanks to Mr. Bijay Babu Regmi, who
generously acted as our mentor despite his numerous other academic commitments. His
wisdom, knowledge, and unwavering commitment to excellence served as a constant
source of inspiration and motivation. Without his guidance and support, we wouldn't have
embarked on this journey, let alone seen it to fruition.

We also extend our deepest appreciation to our other teachers for their unwavering support
and encouragement; without them, none of this would have been possible. Lastly, we
express our heartfelt thanks and appreciation to all our colleagues for their plethora of ideas,
motivation, and encouragement throughout this project.

Shishir Dhakal

TU Symbol. No: 53002078

Nishan Gurung

TU Symbol. No: 53002073

iv
 ABSTRACT
The Salon Management System is a complete web-based tool developed to streamline and
improve salon company operations. This project seeks to provide an effective platform for
both administrators and users to handle appointments, billing, and user interactions. The
system is divided into two parts: the Admin Panel and the User Panel.
Role-based authentication, secure data storage is among the system's key features. To
deliver a solid and scalable solution, the application makes use of latest web technologies
and frameworks.
This report describes the project's objectives, requirements, design, implementation, and
testing phases in detail. It is a comprehensive documentation resource for developers,
stakeholders, and anybody interested in the Salon Management System's design and
capabilities.

Keywords: Frameworks, Metrics monitoring, Scalable solution, Streamline, Unified

dashboard, User-centric approach, Web-based tool, etc.

v
 TABLE OF CONTENTS
ABSTRACT ........................................................................................................................ v
LIST OF FIGURES ....................................................................................................... viii
LIST OF TABLES ............................................................................................................. ix
LIST OT ABBREVIATIONS ............................................................................................ x
Chapter 1: Introduction .................................................................................................... 1
1.1 Introduction ........................................................................................................... 1
1.2 Problem Statement ................................................................................................ 2
1.3 Objectives .............................................................................................................. 2
1.4 Scope and Limitation ............................................................................................ 2
1.5 Report Organization .............................................................................................. 3
Chapter 2: Background Study and Literature Review .................................................. 4
2.1 Background Study ................................................................................................. 4
2.2 Literature Review .................................................................................................. 6
Chapter 3: System Analysis and Design........................................................................... 7
3.1 System Analysis .................................................................................................... 7
3.1.1 Requirement Analysis .................................................................................... 7
i. Functional Requirements: ..................................................................................... 7
ii. Non-Functional Requirements: ............................................................................ 7
3.1.2 Feasibility Analysis ........................................................................................ 9
i. Technical ............................................................................................................... 9
ii. Operational .......................................................................................................... 9
iii. Economic ............................................................................................................ 9
iv. Schedule ............................................................................................................ 10
3.1.3 Data Modeling (ER-Diagram) ..................................................................... 11
3.1.4 Process Modeling ......................................................................................... 12
3.2 System Design ..................................................................................................... 13
3.2.1 Architectural Design .................................................................................... 13
3.2.2 Database Schema Design ............................................................................. 14
3.2.3 Interface Design ........................................................................................... 15
3.2.4 Physical DFD ............................................................................................... 16
Chapter 4: Implementation and Testing ........................................................................ 18
4.1 Implementation.................................................................................................... 18

vi
 4.1.1 Tools Used ................................................................................................... 18
4.1.2 Implementation Details of Modules............................................................. 19
4.2 Testing ................................................................................................................. 19
4.2.1 Test Cases for Unit Testing .......................................................................... 20
4.2.2 Test Cases for Integration Testing ................................................................ 21
4.2.3 Test Cases for System Testing...................................................................... 23
Chapter 5: Conclusion and Future Recommendations ................................................ 25
5.1 Lesson Learnt / Outcome .................................................................................... 25
5.2 Conclusion........................................................................................................... 25
5.3 Future Recommendations.................................................................................... 26
REFERENCES................................................................................................................. 27

vii
 LIST OF FIGURES
Figure 1: Waterfall Model of Salon Management System ................................................... 4
Figure 2: Gantt Chart of Salon Management System ........................................................ 10
Figure 3: ER Diagram of Salon Management System ....................................................... 11
Figure 4: Use Case Diagram of Salon Management System ............................................. 12
Figure 5: Architectural Design of Salon Management System .......................................... 13
Figure 6: Database Schema of Salon Management System............................................... 14
Figure 7: Landing Page of Salon Management System ..................................................... 15
Figure 8: User Dashboard of Salon Management System ................................................. 15
Figure 9: Level zero DFD of Saloon Management System ............................................... 16
Figure 10: Level One DFD of Saloon Management System ............................................. 17

viii
 LIST OF TABLES
Table 1: Software Requirements .......................................................................................... 8
Table 2: Hardware Requirements......................................................................................... 8
Table 3: Test Case-1 ........................................................................................................... 21
Table 4: Test Case-2 ........................................................................................................... 21
Table 5: Test Case-3 ........................................................................................................... 22
Table 6: Test Case-4 ........................................................................................................... 22
Table 7: Test Case-5 ........................................................................................................... 22
Table 8: System Testing ..................................................................................................... 23

ix
 LIST OT ABBREVIATIONS
CSS: Cascading Style Sheet
CV: Curriculum Vitae
DBMS: Database Management System
ER: Entity Relationship
HTML: Hypertext Markup Language
PHP: Hypertext Preprocessor
SQL: Structured Query Language

x
 Chapter 1: Introduction
1.1 Introduction
In the dynamic realm of the beauty and wellness industry, effective management of salon
operations plays a pivotal role in providing exceptional services and ensuring customer
satisfaction. To address the challenges faced by salon businesses in organizing
appointments, managing customer data, the Salon Management System emerges as a
forward-looking web-based application. By seamlessly integrating technology, this project
aims to optimize various facets of salon business management, offering a comprehensive
solution that enhances the overall experience for both salon administrators and clients. This
project is built using PHP programming language.
The project consists of two primary modules: the Admin Panel and the User Panel. The
Admin Panel provides salon administrators with a centralized hub for monitoring and
managing key metrics, user profiles, appointments. On the client-facing side, the User
Panel empowers salon customers with an interface to effortlessly navigate through their
profiles, schedule appointments, review billing information. The emphasis is on creating a
seamless, intuitive experience that aligns with modern user expectations and contributes to
positive interactions with the salon.
The project incorporates contemporary web technologies and frameworks, ensuring a
scalable and robust solution adaptable to the evolving needs of the beauty and wellness
industry.

1
1.2 Problem Statement
On a typical Saturday, as a customer seeking a haircut, I found myself in a crowded salon
without a prior appointment. The salon was overwhelmed with a large number of
customers, leading to extensive waiting times. This experience raised concerns about the
lack of an organized system for managing customer queues. Had there been an appointment
system in place, the waiting time could have been significantly reduced, optimizing the
customer experience and streamlining the overall salon management process.
This highlights a broader issue within the salon industry – the absence of an effective
appointment system. The current scenario not only inconveniences customers but also
poses operational challenges for salon staff in handling peak hours. Therefore, exploring
and implementing a robust salon management system with an integrated appointment
system is crucial to address these challenges and enhance the efficiency and satisfaction of
both customers and salon staff. Recognizing these issues, the Salon Management System
project aims to develop a web-based solution.
1.3 Objectives
• To create a platform where clients can easily make their appointment of required salon
service.
• To generate invoices for services rendered.

1.4 Scope and Limitation

1.4.1 Scope
The Salon Management System project endeavors to reshape the landscape of salon
operations, aiming to alleviate challenges faced by both administrators and clients. Focused
on simplicity and efficiency, the application will feature a centralized dashboard for
administrators to manage appointments, view customers info, add and delete services while
clients can effortlessly schedule appointments and view invoice of the service rendered.
Beyond immediate problem-solving, the project aspires to modernize salon businesses by
leveraging contemporary web technologies. Specific details and input are vital for refining
the project scope to ensure it aligns with the unique requirements of salon administrators
and clients.

2
1.4.2 Limitation
The following are the limitation of our project:
• Admin is not notified about the new appointment; admin needs to view it thoroughly.
• Admin cannot accept or reject appointments.
1.5 Report Organization
This report is structured into five main chapters, each detailing a different aspect of the
Salon Management System project. The organization is as follows:
Chapter 1: Introduction
This chapter provides an overview of the project, including its objectives, problem
statement, scope, and limitations. It sets the context for why the Salon Management System
is necessary and what it aims to achieve.
Chapter 2: Literature Review
This section reviews existing systems and literature related to salon management and
appointment scheduling. It examines current solutions, identifies gaps, and justifies the
need for the proposed system. Additionally, it outlines the methods used for requirement
collection.
Chapter 3: System Analysis and Design
Here, the detailed analysis and design of the system are presented. This includes functional
and non-functional requirements, system architecture, and design methodologies. Key
design elements such as use case diagrams, ER diagrams, and database schema are also
discussed.
Chapter 4: Implementation and Testing
This chapter covers the implementation phase, describing the tools and technologies used,
and the actual development of the system. It also details the testing processes, including
unit testing, integration testing, and the results of these tests.
Chapter 5: Conclusion
The final chapter summarizes the findings of the project, discusses the outcomes, and
suggests future improvements. It reflects on the achievements and any challenges
encountered during the project.
This structured approach ensures a comprehensive documentation of the Salon
Management System, making it easier for developers, stakeholders, and other interested
parties to understand and utilize the project.

3
 Chapter 2: Background Study and Literature Review
This is the second chapter that will focus on the outlook of existing systems and tries to
overcome the lacking of the current system. This chapter helps to justify the importance of
the project, and highlight how different it will be from other similar systems. Literature
reviews are a basis for research in nearly every academic field.
2.1Background Study
2.1.1 Fundamental Theories:
Database Management Systems (DBMS):
• Relational Database Theory: The Salon Management System relies on relational
databases to store and manage data efficiently. This theory involves organizing data
into tables (relations) where each table consists of rows and columns. Key concepts
include primary keys, foreign keys, normalization, and SQL (Structured Query
Language) for data manipulation.
• Normalization: The process of organizing data to minimize redundancy. It involves
dividing large tables into smaller, more manageable pieces and defining
relationships between them to ensure data integrity.
Software Development Life Cycle (SDLC):
To implement the project, we are going to use the waterfall model (outcome of one phase
acts as input for next phase). The following illustration is a representation of the different
phases of the Waterfall Model.

Figure 1: Waterfall Model of Salon Management System

4
Our project's description is stable. Since we have well known, clean and fixed requirements
therefore it fits best for the software development. This model is simple, easy to
comprehend and user friendly. Phases are processed and finished one at a time in this
model, and they do not overlap. The waterfall model works well for smaller tasks with well-
defined sequences.
2.1.2 General Concepts:
Appointment Scheduling:
• Online Booking System: System that allow customers to book appointments via a
web interface. These systems improve convenience for customers and efficiency for
salon staff by reducing manual scheduling errors.
Customer Relationship Management:
• Customer Profiles: Maintaining detailed profiles for each customer, including
contact information. This helps in personalizing services and improving customer
satisfaction.
2.1.3 Terminologies:
Backend and Frontend:
• Backend: The server-side part of the application where data processing and storage
occur. It includes the database, server, and application logic.
• Frontend: The client-side part of the application where the user interface resides. It
includes everything the user interacts with, such as web pages and forms.
Security:
• Data Encryption: Protecting sensitive data by converting it into a coded format that
can only be read by authorized users. This ensures data privacy and security.
• Authentication and Authorization: Ensuring that users are who they claim to be
(authentication) and granting them appropriate access levels (authorization) to
different parts of the system.

5
2.2 Literature Review
2.2.1 Existing System
Asylum Hair Salon [1]:
Asylum Hair Saloon is the online platform where user can make an appointment in the
saloon. User can make an appointment from home instead of visiting to the saloon. They
can also select the service they need from the Asylum Hair Saloon system.
Some of the disadvantages of their system are as follows:
• Doesn’t offer user account.
• A system that doesn’t provide user feedback option.
Hair n Shanti Nepal [2]:
Hair n Shanti is a chain of unisex salons (An ISO Certified NS-EN ISO 9001:2008
Company) that are swanky and classy providing international standards for hair and beauty
treatments. In the year 2000, Mrs. Bishow Shanti Shrestha, the founder of Hair n Shanti,
with experience of over 27 years in the field and always passionate about enhancing beauty
in everyone around her, started the first of Hair n Shanti centers in Delhi’s South Ex.-I area,
then called “Shanti”. Mrs. Shrestha participated in Ms. World Beauty Pageant in 1996 at
Bangalore and Seychelles as a makeup artist and hair stylist. The success story of the South
Ex. center, was retold by “Shanti” with the opening and successful execution of 8 different
salon centers across Delhi by the same name.
Some of the disadvantages of this system are as follows:
• The existing system doesn’t provide web-based appointment system.
• No section to preview bills for the customer.
• No section to provide user feedback.
While both Asylum Hair Salon and Hair n Shanti Nepal offer distinct features and cater to
the salon industry, they each have their limitations. Asylum Hair Salon excels in providing
online appointment booking and service selection but falls short in user account
functionality and feedback collection. On the other hand, Hair n Shanti Nepal, with its
established reputation and chain of salons, lacks certain online features, including web-
based appointment systems, bill previews, and user feedback sections.

6
 Chapter 3: System Analysis and Design
Well, from here the real work begins, development of the proposed system is analyzed into
details. It will analyze the tools and technologies used, data sources and programming
languages used and why. Dataflow diagrams, flowcharts, use-case diagrams, relationship
and entity diagrams, etc. will be used to explain the project.
3.1 System Analysis
3.1.1 Requirement Analysis
i. Functional Requirements:
• The system shall allow users to create unique profiles.
• Users shall be able to book appointments.
• Administrators shall have a dashboard to view appointments.
• Users shall be able to view and select specific services during the appointment
booking process.
• The system shall facilitate the generation of invoices for services rendered.
• Administrators shall have access to view and manage user profiles.
ii. Non-Functional Requirements:
• The system must be compatible with commonly used web browsers (Chrome,
Firefox, Safari, etc.).
• The system must be secure.
• The system must be easy to maintain and upgrade.
• The system response time must be fast.

7
iii. System Requirements:
For a well-developed project, the system requirement is one of the most important factors.
The system comprises of the hardware requirement and the software requirement. Software
and hardware to be used in the project are tabulated below:
Table 1: Software Requirements

S.N. Software Purpose

1 Visual Studio Code Code Editor

2 MySQL DBMS to store data and information

3 Microsoft Word For documentation

4 Snipping Tool To take screenshots

5 Draw.io To draw use-case diagram and flowcharts

6 Online Gantt To draw Gantt chart

Table 2: Hardware Requirements

S.N. Hardware Specification

1 Processor Intel Core i3 2.0 GHz or higher

2 RAM 2GB or higher

8
3.1.2 Feasibility Analysis
i. Technical
The technical feasibility of the Salon Management System project is evident through the
judicious selection of a robust software stack and tools that align with project requirements.
The development environment, including Visual Studio Code, serves as a versatile and
efficient code editor for PHP, JavaScript, HTML, and CSS. MySQL, a reliable relational
DBMS, has been chosen for its scalability and proficiency in handling the project's data
requirements. Microsoft Word is employed for comprehensive documentation, ensuring
clarity and precision in project specifications and development processes. For visual aids,
Draw.io facilitates the creation of intricate use-case diagrams and flowcharts. Additionally,
Online Gantt charts aid in project planning and timeline visualization. Overall, the
utilization of these technologies and tools underscores the technical feasibility of the
project.
ii. Operational
The operational feasibility of the Salon Management System project is inherently user-
centric, ensuring accessibility and ease of use for a diverse audience. The design philosophy
prioritizes simplicity and intuitiveness, enabling even individuals without extensive
technical expertise to navigate and utilize the website seamlessly. The user-friendly
interface allows clients to schedule appointments, select services, and provide feedback
effortlessly, fostering an inclusive platform that accommodates a wide range of users.
iii. Economic
The economic feasibility of the Salon Management System project is underscored by the
utilization of cost-effective software solutions. The project's reliance on open-source
software such as Visual Studio Code, MySQL, and Bootstrap eliminates licensing costs,
contributing to a significant reduction in the overall development expenses. Additionally,
the incorporation of freely available tools like Microsoft Word, Snipping Tool, Draw.io,
and Online Gantt charts further enhances cost-effectiveness, ensuring that the economic
investment in the project remains minimal. This approach facilitates a budget-friendly
development process while maintaining the project's functionality, making it an
economically feasible solution for salon management.

9
iv. Schedule
The schedule for the Salon Management System project outlines a phased approach to
development, starting with the active Planning stage and subsequent inactive stages of
Analysis, Design, Coding, Testing, and Delivery. The projected is time lined from January
23, 2023 to April 11, 2024. The five-day Planning phase allows for initial project
groundwork, while subsequent stages have defined durations, contributing to a balanced
and realistic timeline. This schedule feasibility is contingent on effective task management
and resource allocation during each phase, ensuring that the project progresses
systematically and meets its deadlines.

Figure 2: Gantt Chart of Salon Management System

Active Stage
Inactive Stage

10
3.1.3 Data Modeling (ER-Diagram)

Figure 3: ER Diagram of Salon Management System

11
3.1.4 Process Modeling

Figure 4: Use Case Diagram of Salon Management System

12
3.2 System Design
3.2.1 Architectural Design

Figure 5: Architectural Design of Salon Management System

13
3.2.2 Database Schema Design

Figure 6:Database Schema of Salon Management System

14
3.2.3 Interface Design

Figure 7: Landing Page of Salon Management System

Figure 8: User Dashboard of Salon Management System

15
3.2.4 Physical DFD

Figure 9: Level zero DFD of Saloon Management System

16
Figure 10: Level One DFD of Saloon Management System

17
 Chapter 4: Implementation and Testing
4.1 Implementation
This chapter will discuss about the implementation of the Computer Repair Appointment
System. Different logic thinking and coding id required at development of the system. A
lot of research has been done to enhance the efficiency when writing code.
4.1.1 Tools Used
This whole system is divided into 2 parts: the frontend and the backend.
Frontend (Development tools and programming language): The frontend is designed
using: HTML, CSS, JS and PHP.
Backend: The backend is designing using MySQL and PHP. Other Platforms used:
XAMPP, Draw.io
HTML: HTML (Hypertext Markup Language) is used in this system for denoting
structural, semantics for text such as headings, paragraphs, lists and other items. Through
html codes different labels has been implemented such as form such as text, email,
password, text area to login is implemented through html.
CSS: CSS (Cascading Style Sheet) is used in this system for designing and styling forms,
managing the padding and margin of label and bottom as well as adding background color
and images in this system. Also, it’s for designing navigation bar, header, footer and menu
of this system.
JavaScript: JS is used in this system to pop up the messages using the alter keyword to
display the message in the system such as after registering the student (“new medicine
added!”), and adding the new supplier in the system (“New supplier added”) is displayed.
PHP: PHP a server –site scripting language has been used to connect html files into
database in this system. MYSQL: MYSQL an open-source relational database management
system is used for storing the database in this system.
XAMPP: XAMPP an abbreviation for cross-platform for Apache, MYSQL, PHP and Perl
are used as a local server in this project.
Draw.io: Through the use of Draw.io, diagrams such as flowchart, sequence diagram, use
case diagram is created for this project.

18
4.1.2 Implementation Details of Modules
4.1.2.1 Admin Module:
The Admin Module is designed to manage the overall operations of the salon management
system. It includes the following functionalities:
• Admin Login: Secure authentication for administrators to access the system.
• Dashboard: Provides a comprehensive view of the salon's operations, including
appointments, user interactions, and financial metrics.
• Appointment Management: Allows administrators to view appointments made by
users.
• Service Management: Enables the addition, updating, or deletion of services offered by
the salon.
4.1.2.2 User Module:
The User Module focuses on providing a seamless experience for customers using the
salon's services. It includes:
• User Registration and Login: Allows new users to register and existing users to log in
securely.
• Profile Management: Users can update their personal information, view their service
history, and manage their preferences.
• Appointment Booking: Provides an interface for users to book appointments, select
services.
4.1.2.3 Service Module:
The Service Module handles the management of various services offered by the salon. It
includes:
• Service Catalog: A comprehensive list of all services provided, including descriptions,
durations, and prices.
• Service Customization: Allows for the customization of services based on client
preferences.
4.2 Testing
The aim of the system testing process was to determine all defects in our project. The
program was subjected to a set of test inputs and various observations were made and based
on these observations it will be decided whether the program behaves as expected or not.

19
4.2.1 Test Cases for Unit Testing
Unit testing is undertaken when a module has been created and successfully reviewed. In
order to test a single module, we need to provide a complete environment i.e. besides the
module we would require.
• The procedures belonging to other modules that the module under test calls.
• Non local data structures that module accesses.
• A procedure to call the functions of the module under test with appropriate parameters.
Unit testing was done on each and every module that is described under module description.
4.2.1.1 Testing admin login form
This form is used for log in of administrator of the system. In this section we enter the
username and password if both are correct administration page will open otherwise if any
of data is wrong it will get redirected back to the login page and again ask for username
and password.
4.2.1.2 Testing user login form
In this section user login in the system. If the username and password are correct then user
can view the computer status edited by support staff. Book Addition- Admin can enter
details of book and can add the details to the main book table also he can view the books
requests.

20
4.2.2 Test Cases for Integration Testing
In this type of testing, we test various integration of the project module by providing the
input. The primary objective is to test the module interfaces in order to ensure that no errors
are occurring when one module invokes the other module.
4.2.2.1 Test Plan
Test case description: Admin Login
Table 3: Test Case-1
Condition Input Steps Output Actual Result

Result
Should be Admin name 1. Enter the valid Admin should Navigate into Successfully
registered to and admin name and log into the the admin Completed
the application Password. password. system dashboard
2. Click submit
button

Test case description: User Login

Table 4: Test Case-2

Condition Input Steps Output Actual Result

Result
Should be User name and 1. Enter the valid Error in header Navigate into Failed
registered to the Password. username and the user
application password. dashboard
2. Click submit
button

21
Test case description: Updated User Login
Table 5: Test Case-3
Condition Input Steps Output Actual Result

Result
Should be User name and Updated User logged Navigate into Successfully
registered to Password. statement in into the the user completed
the application header (Location system dashboard
Path)

Test case description: Book Appointment

Table 6: Test Case-4
Condition Input Steps Output Actual Result

Result
Should be Username, 1. Enter the valid SQL Error User should Failed
registered to email, date, username and be able to
the application time and email book
services 2. Enter valid appointment
date and time
3. Click submit
button
Test case description: Updated Book Appointment
Table 7: Test Case-5
Condition Input Steps Output Actual Result

Result
Should be Username, SQL query was Appointment User should Successfully
registered to email, date, rewritten taking Booked be able to completed
the application time and reference to the book
services SQL error appointment

22
4.2.3 Test Cases for System Testing
System testing is a level of testing that validates the complete and fully integrated software
product. It evaluates the end-to-end system specifications to ensure that the software meets
the required functionality, performance, and quality standards.
Table 8: System Testing
Test Test Case Test Steps Expected Result Actual Status
ID Description Result (Pass/Fail)
TC001 User 1. Navigate to registration page User account is As Pass
Registration 2. Fill in required fields created and user expected,
3. Click 'Register' button is redirected to
user dashboard

TC002 User Login 1. Navigate to login page User is logged in As Pass

2. Enter valid credentials and redirected to expected,
3. Click 'Login' button the user
dashboard

TC003 Book an 1. Login to the system Appointment is As Pass

appointment 2. Navigate to 'Book successfully expected,
Appointment' page booked and
3. Select date, time and service confirmation
4. Click 'Book' button message is
displayed

23
TC004 View 1. Login to the system List of booked As Pass
Appointment 2. In the dashboard page, appointments is expected,
s inside find your appointments displayed
section filter the appointments
by date to view.
TC005 Admin View 1. Login as admin Admin can view As Pass
All 2. Navigate to 'Appointments' all booked expected,
Appointment 3. Filter appointments by date. appointments
s
TC006 View Invoice 1. Login as user User can view As Pass
by User 2. Navigate to the dashboard. invoice for the expected,
3. In the appointments section respective
you can find view invoice booked
button. appointment
4. Click ‘View Invoice’
TC007 Data 1. Register a user Password should As Pass
Encryption 2. Check the database for be stored in expected,
stored password encrypted format
TC008 Unauthorize 1. Try to access admin page User should be As Pass
d Access without login redirected to expected,
login page
TC009 Add Service 1. Login as Admin Admin should be As Pass
by Admin 2. Navigate to ‘Services’ able to add expected,
3. Click ‘Add Service’ service
TC010 View 1. Login as Admin Admin should be As Pass
Customers 2. Navigate to ‘Customers’ able to view expected,
by Admin 3. Click on the See More information of
button to view more info of their customers
customer or can search typing
the username of the customers

24
 Chapter 5: Conclusion and Future Recommendations
5.1 Lesson Learnt / Outcome
The development and implementation of the Salon Management System provided several
key lessons and outcomes:
5.1.1 Project Management and Collaboration:
Effective project management techniques are crucial in coordinating tasks and ensuring
timely completion. Collaboration among team members, facilitated by regular meetings
and clear communication, significantly contributed to the project's success.
5.1.2 Technical Proficiency:
The project enhanced our technical skills, particularly in web development technologies
such as HTML, CSS, JavaScript, PHP, and SQL. It also provided hands-on experience with
frameworks and tools essential for building scalable and efficient systems.
5.1.3 Problem-Solving and Debugging:
Encountering and resolving various technical issues during the development process
improved our problem-solving abilities. Systematic debugging and testing were essential
in refining functionalities and ensuring a robust application.
5.1.4 User-Centric Design:
Prioritizing user experience was fundamental. Feedback from friends and supervisor helped
shape the system’s design and features, ensuring it meets the needs and expectations.
5.2 Conclusion
In conclusion, the Salon Management System project represents a pivotal endeavor in
modernizing and optimizing salon operations. The anticipated outcomes, including
improved financial management, increased customer satisfaction, and adaptability to
industry trends, underscore the project's potential to make a substantial impact.
By leveraging cost-effective technologies and open-source software, the project aligns with
economic feasibility, delivering robust functionality without excessive financial
investment. The system's scalability and adaptability ensure its relevance in a dynamic
industry landscape, accommodating growth and evolving trends.
As the project progresses through its phases, continuous monitoring, and feedback
mechanisms will be vital to address challenges, refine functionalities, and meet user’s
expectations. The Salon Management System emerges as a promising solution that not only
addresses the identified challenges within the salon industry but also sets the stage for a
more efficient, responsive, and customer-centric approach to salon management.

25
5.3 Future Recommendations
Based on our findings and the current state of the system, we propose the following future
recommendations:
5.3.1 Enhanced Notification System:
Implement a real-time notification system to alert administrators of new appointments,
cancellations, or modifications, thereby improving responsiveness and customer service.
5.3.2 Integration with Third-Party Services:
Integrate the system with third-party services such as email marketing tools, payment
gateways, and social media platforms to provide a seamless experience and expand the
system’s capabilities.
5.3.3 User Feedback Mechanism:
Establish a robust feedback mechanism to continuously gather user input and improve the
system. Regular updates and feature enhancements based on user feedback will ensure the
system remains relevant and effective.
These recommendations aim to further enhance the functionality, user experience, and
overall impact of the Salon Management System, ensuring it remains a valuable tool for
salon businesses in the future

26
 REFERENCES
[1] Asylum Hair Salon, "Asylum Hair Salon - The best hair and beauty salon in
Kathmandu," Asylum Hair Salon, 2020.

[2] Hair n Shanti Nepal, "Hair n Shanti Nepal: Best beauty parlour Nepal, hair salon," Hair
n Shanti Nepal, 2017.

27
 APPENDICES
Login Page:

SignUp Page:

Appointment Form:

28
User Profile:

Services:

Admin Dashboard:

29
Admin Add-Service:

Customers:

Customer info:

30
Customer Appointments:

31