1

Contents
1. Introduction...................................................................................................................................3
1.1 Document Purpose.....................................................................................................................3
1.2 Product Scope..............................................................................................................................4
1.3 Intended Audience and Reading Suggestions..........................................................................4
1.4 Definitions, Acronyms and Abbreviations...................................................................................4
 Definitions:................................................................................................................................4
Database:...........................................................................................................................................4
A database is a collection of data on which different actions can be performed................................4
2.Problem Statement:............................................................................................................................4
Objectives of the Project:......................................................................................................................5
3.Overall Description............................................................................................................................5
1. Product Perspective:..................................................................................................................5
2. Product functions:......................................................................................................................5
3. User classes and characteristics:................................................................................................6
4. Operating Environment:............................................................................................................6
5. Design and Implementation Constraints:...................................................................................6
2. Specific Requirements...................................................................................................................6
 User Interfaces:..........................................................................................................................6
 Hardware Interfaces:..................................................................................................................6
 Software interface:.....................................................................................................................7
3. Other non-functional requirements................................................................................................7
Product requirements:........................................................................................................................7
4. Software Design...........................................................................................................................7
4.1 Deployment Diagram...........................................................................................................7
4.2 System Architectural Design.....................................................................................................8
4.3 Data structure design................................................................................................................8
4.4 Use case realizations..................................................................................................................9
4.5 Use Case: Customer...................................................................................................................9
4.6 Use Case: Services...................................................................................................................10
4.7 Use Case: Employee.................................................................................................................10
4.8 Interface design........................................................................................................................11
4.9 Help system design...................................................................................................................11
5. Software implementation:.........................................................................................................11

2
Tables:.................................................................................................................................................12
S_EMP:...............................................................................................................................................12
S_CUSTOMER:..............................................................................................................................12
SERVICES:.....................................................................................................................................12
TAKES:...........................................................................................................................................13
6. Evaluation..................................................................................................................................17
Unit Testing:..................................................................................................................................17
Integration Testing:.......................................................................................................................17
System Testing:..............................................................................................................................17
User Acceptance Testing:..............................................................................................................17
6.1 Test Plan...................................................................................................................................17
6.2 User Evaluation........................................................................................................................17
Conclusion:..........................................................................................................................................18
Lessons Learnt:................................................................................................................................18
Future Developments:......................................................................................................................18
References:..........................................................................................................................................19

1. Introduction
Maintaining data has become a huge part of our lives, and retrieving data through secure
means is becoming more important. So in this computer age preventing data from getting lost
is a major concern of clients as well as management. Every day there are cases about people,
business suffering highly because of data lost and mismanagement.
We will be developing a Salon Management Database that will manage data of the clients and
staff. We will also develop a GUI that will allow the management to view that data which
they have made secure by including in the database. The database will allow user to perform
different actions which are described in the documentation.

1.1 Document Purpose

The document is 1.0 version of software requirement specification for Salon Management
Database. In this document we will describe in detail about a project requirements, overview
about its interface, a detailed explanation on the current problem that this product would help

3
 to solve. In this document, it will be explain the audience that would be able to take
advantage from this product to make their lives easier and more secure.
This SRS provides the detailed information about the requirements, constraints, product
functionalities, features and interface requirements of this database that will be the basis of
the development of the database and to have a clear idea of what is intended and what can be
achieved. This SRS will also described software and other technical dependencies. This
document is used by developing team members and project members

1.2 Product Scope

Salon Management Database will be a tool that will allow the user to maintain the
data securely without being getting the risk of lost. The database take data from user
and allow him/her to perform different action on that data

1.3 Intended Audience and Reading Suggestions

This document serves as complete guidance to seek understanding of project. Since, this
project is going to develop through mutual understanding of team members and supervisor, so
this document is reviewed by all team members and supervisor and all of them are agreed
with that what is written inside of it.
The intended audiences of this document are:
 Supervisor and Coordinator to review the document
 Developers
 Senior Design Project Evaluation Committee

1.4 Definitions, Acronyms and Abbreviations

 Definitions:
Database:
A database is a collection of data on which different actions can
be performed.
 Acronyms:
GUI: Graphical User Interface
UI: User Interface
JDK: Java Development Kit, Library package for Java supported Applications
DAIC: Design and Implementation Constraint
FR: Functional Requirement
NFR: Non-Functional Requirement

2.Problem Statement:

4
Nowadays it is easy to find Salons, Parlours and Spas at any nook and corner in this
world, as beauty and fashion has become a great trend disregarding the age limit and
gender. All the Salon Owners are relying on their Customers; who visits Salons to
fulfill their own beauty needs. Therefore, it is important to value the loyalty and the
time of those Customers.
From the other side, to make the Salon services better and to
enhance the good names of the salons, their Stylist’s/Employee’s satisfaction also
needs to be fulfilled. Not only that the income earns by selling services to the clients
should be able to monitor by the salon owners.
Using manual procedures may pave the way for a variety of obstacles when satisfying
Customers and Employees of the respective Salons. Valuable time and money of the
Salon Owners, Employees and Customers get wasted unnecessarily due to these manual
dealings. These barriers make direct harms for the incomes and the good names of the
Salons and for their Owners.

Objectives of the Project:

Objectives of doing this project are to;
 Eliminate the paper based work use at the Salon such as, usage of
diaries to note down appointment details, writing manual invoices for the
payments done by the Customers etc.
 Eliminate the data redundancy; keeping appointment details at several places
(Diary, mobile etc.) by several people (Owner, Employees, Customers etc.).
 Abolish the wastage of time, resources, efforts and money of the Employer,
Employees and Customers.
 Improve the efficiency and effectiveness of the Salon management activities,
services and processes like maintaining Customers, Employees, Appointments
and Payments etc.
 Ease the management and decision making while improving Salons’ good
name.
 Improve the Client satisfaction and Employee satisfaction.
 Enhance the Stakeholder integration.

3.Overall Description
1. Product Perspective:
Salon management system is a computerized system to ease staff and administration in
managing modules such as staff registration, customer registration, services, bookings and
payment. The requirements of this application are OS and SQL database. It reduces the non-
computerized system inconveniences , these processes were time consuming specially
searching for customer information for generating monthly and yearly revenue.

2. Product functions:

5
The salon system is created to overcome and update the previous system which used manual
method of writing report on report book to record all the registration, services, booking and
payment module that occurred. It is developed to make system more systematic and efficient.
The main purpose of this project is to reduce the manual work. This software is capable of
create and manage customer, provide list of services, finance management, manage
appointments.

3. User classes and characteristics:

The system provides services to the salon manager in making records of their employees,
clients and their services .This software makes the things lot easier. Some of the
characteristics are as follows
 The salon manager can enroll the new client.
 The salon expert can show the list of services they are providing.
 The client can select the service they want.
 The service provider/ the employee will be selected.
 If the new client enters, their record is made from the scratch.
 If he/she is already a client before whole history of their services and check-ins will be listed.
 The billing can be done simultaneously while entering the record. This helps the payment
method to be hassle free.
4. Operating Environment:
The product will be operating in windows 10 OS. Microsoft sql should also be available on
the pc. The front end of the project is on visual studio. 4GB RAM should be available at least
for good functioning with other applications.

5. Design and Implementation Constraints:

New client will be recorded. Old client’s data will be updated regularly with the services they
take. Their billing will be clear. Name of customer along with the services they take, the date
of appointment, they date they check-in and the money they spent all will be recorded.

2. Specific Requirements
 User Interfaces:
The software provides good graphical interface for the salon manager to operate on the
system, performing the required task such as entering data updating data and deleting records
of clients, customers and services.
It allows user to view quick reports like regular client/loyal clients and new clients.
It provides service verification and search facility based on different criteria.
All the modules provided with the software must fit into this graphical user interface and
accomplish to the standard defined.

6
The design should be simple and all the different interfaces should follow a standard
template.

 Hardware Interfaces:
Our software is a desktop application so it will require a Personal Computer on which it will
run. It does not require any external hardware component.

 Software interface:
This software package is developed using C# as front end which is supported by visual
studio. Microsoft SQL Server as the back end to store the database.
Operating System: Windows 8 and higher versions.
Language: C# visual studio (front end)
Database: MS SQL Server (back end)

3. Other non-functional requirements

Product requirements:
 Efficiency requirement:
The database should work efficiently like if user wants the complete information of a customer the
database must process it instantly. Each customer’s data must be stored separately in the database.

 Reliability requirements:
The system must be reliable means it must respond to user’s request efficiently. For example, if a user
update any customer’s information it must also be updated in database. If the user view the customer’s
information later it must show the updated information.

 Usability requirements:
The system must be efficient in every aspect, it must be understandable by the user. The user must be
able to use it comfortably. It must be user-friendly in such a way that if any error occur it must be
understandable by the user so that the user will be able to remove the bu

7
 4. Software Design
4.1 Deployment Diagram

4.2 System Architectural Design

4.3 Data structure design

The data is stored in a relational database using SQL Server. The relations are
described by the database administrator. The fields for transmitting to and from the
database are given in the following table.

Attribute Name Attribute Type Attribute Size

Cus_Id* Int 4
Name# String 10
Emp_Id* Int 4
Contact# Int 11

8
 Salary* Int 6
Job# String 10
Ser_Id* Int 4
Ser_Name# String 15
Charges# Int 6
Cus_Ser_Id* Int 4

Fields marked with an ‘*’ are required fields. Fields marked with a ‘#’ can be visible or
not visible and is determined by the Admin.
4.4 Use case realizations

4.5 Use Case: Customer

9
4.6 Use Case: Services

4.7 Use Case: Employee

10
4.8 Interface design

4.9 Help system design

Till now no help system is planned.

5. Software implementation:
Platform details:

Technology used Specifications

Operating system Windows 10

Database MY SQL, Oracle 11g

It supports a large part of the SQL standard and offers
many modern features like:
 complex queries
 foreign keys
 triggers
 updatable views
 transactional integrity
 multi-version concurrency control

11
 IDE’s Visual studio 2013
SQL server

languages C#

The entity table for salon management system are given below:

Tables:
S_EMP:

COLUMN NAME EMP_ID NAME SAL JOB

KEY TYPE PRIMARY KEY

NULLS/UNIQUE NOT NULL

DATA TYPE NUMBER VARCHAR2 VARCHAR VARCHAR2

2

LENGTH 25 25 25 25

S_CUSTOMER:
COLUMN NAME CUS_ID NAME CONTACT EMP_ID

KEY TYPE PRIMARY KEY FOREIGN

KEY

NULLS/UNIQUE NOT NULL

DATA TYPE NUMBER VARCHAR2 VARCHAR NUMBER

2

LENGTH 25 25 30 25

12
SERVICES:

COLUMN NAME SER_ID SER_NAME CHARGES EMP_ID

KEY TYPE PRIMARY KEY FOREIGN

KEY

NULLS/UNIQUE NOT NULL

DATA TYPE NUMBER VARCHAR2 VARCHAR NUMBER

2

LENGTH 25 26 25 25

TAKES:
COLUMN NAME CUS_SER_ID EMP_ID SER_ID CUS_ID

KEY TYPE PRIMARY KEY

NULLS/UNIQUE

DATA TYPE NUMBER NUMBER NUMBER NUMBER

LENGTH 25 25 25 25

Database connection code which should be use always when connecting to the database:

Code:
using System.Collections.Generic;
using System.ComponentModel;
using System.Data; 13
using System.Drawing;
using System.Linq;
 private void button1_Click(object sender, EventArgs e)
{
if (textBox1.Text != "" && textBox2.Text != "" && textBox3.Text != ""
)
{ 14
cmd = new SqlCommand("insert into S_customer(Cus_id,Name,Contact)
values(@Cus_id,@Name,@Contact)", con);
//Clear Data
private void ClearData()
{
textBox1.Text = "";
textBox2.Text = "";
15
textBox3.Text = ""}
private void button2_Click(object sender, EventArgs e)
private void button3_Click(object sender, EventArgs e)
{
if (textBox1.Text != "0")
{
cmd = new SqlCommand("delete S_customer where Cus_id=@Cus_id",
con); 16
con.Open();
cmd.Parameters.AddWithValue("@Cus_id", textBox1.Text);
 6. Evaluation

Evaluation chapter is based on the system testing plan and its results gained after the system
implementation.

Unit Testing:
Testing of individual software modules or components that make up an application or system. These
tests are usually done by the developers of the module and in a testdriven-development methodology.
Unit Testing was helped to find out errors and weaknesses in each individual software module.

Integration Testing:
Individual module which were subjected to unit testing were tested by integrating with each other. A
top down approach was followed. Errors that can be occur at the integration were able to find at the
end of this test.

17
System Testing:
The entire system was tested by interfacing hardware and software components of the entire system as
to find out errors with the whole system.

User Acceptance Testing:

All the system users at the salon premise were helped for the acceptance testing, to make it a success.
Hardware and software at the salon were used as to test the real status of the system. Along with these
functional testing methods, it was able to provide an error free system for the client, to prevent the
obstacle which could occur latterly.

6.1 Test Plan

Planning for test is a very important aspect for a developed system as well as for a system in progress
level. The overall functionality of the system should checked via test plan. Test cases were written for
each module to be tested before testing the system. The implemented system was tested using
different test cases.

6.2 User Evaluation

The feedback or the evaluation form were used to gain the feedback from the client.
Three evaluation forms were distribute among three employees at the salon premise along with the
salon owner; after implementing the system at the client site. Selected employees were under the three
user types maintain by the system. Main purpose of this was to get an overall feedback on each area
module of the system. Therefore System administrator commented on her experience, System Officer
fed backed on her experience and the cashier on hers.

Conclusion:
Salon Management is still an emerging business area, though it is widely
spread in the foreign developed countries. When turned into the local market, visits to
hair and beauty salons and spas in need of fulfilling the beauty needs has become a
trend among the people around the country. Therefore, providing a better service for
the customers at their first and foremost arrival to the salon, will aid to make a
good impression on their mind over the salon. It can be considered as a fine business
trick and most of the Salon Owners follows these steps.
However, at rush hours, it is very difficult to satisfy the customers, especially if the
particular salon is fully dependent on a manual process; and the staff also become fed up
when they were burdened with exhausting tasks. Un-satisfaction of both customers and
employees may pave the way for the decline of the specific salons’ businesses.
Therefore, the concept which turned into a salon management software will be a great
assistance for the salon owners to speed up their work by eliminating the unwanted barriers
by improving their quality of business.
The project started from requirement gathering phase was successfully completed after
passing the user acceptance test next to the implementation phase. However it is not
practical to fulfill all the clients’ requirements for the maximum. But the system was
up to a satisfactory level and client accepted it with a gratitude.

18
Lessons Learnt:
By doing the final project, lot of lessons were able to learn at each every phase of the
SDLC. Practical understanding on software engineering disciplines were able to
capture. Following is the lessons list learnt during the project cycle:
 Able to acquire knowledge on a different business area.
 Able to gain a practical training on requirement gathering.
 Able to enhance interpersonal skills, at frequent client meetups.
 Able to learn on new technological tools and frameworks.
 Able to improve documenting skills.
 Able to learn on facing for challenges.

Future Developments:
The software handover is the first product used by the client. So he/she may take their
time to tell the change requests that she needs to do for the salon management system.
But some suggestions were there to enhance the performance of the system as follows:
 Reminder generating facility through SMS.
 Providing online appointment creation facility.
 Giving staff rating facility.

References:
https://pdfs.semanticscholar.org/b50d/1a39b9b65912268ae0e65a64bad87c1ad184.pdf

19