Table of Contents

Introduction................................................................................................................1
Purpose...................................................................................................................3
Scope of the Project................................................................................................4
Background............................................................................................................4
Reference Materials................................................................................................5
Reference Templates:.............................................................................................5
Meeting Summaries:...............................................................................................7
Assumptions and Constraints:................................................................................7
Methodology:.............................................................................................................7
Functional Requirements.........................................................................................13
Entity – Relationship Diagram.............................................................................18
Activity Diagram..................................................................................................19
Functional requirement for website.........................................................................20
Hardware Interface...............................................................................................24
Software Interface................................................................................................25
Requirements:..........................................................................................................26
Hardware Requirement.........................................................................................26
Software Requirements........................................................................................26
Specific functional requirements:............................................................................26
Allow user to update:...........................................................................................26
Administration system:.........................................................................................26
Quality assurance:....................................................................................................28
Usability:..............................................................................................................28
Efficiency:............................................................................................................28
Adaptability:.........................................................................................................28
Extensibility:........................................................................................................28
Training requirement:...........................................................................................28
System Availability:................................................................................................29
General Performance:...........................................................................................29
Capacity:...............................................................................................................29
Introduction

This Software Requirement Specification document provides a complete

description of all the functionalities and the specifications of the Salon Website.
The developers and the testers can use this document as a reference for
developing the design and test plan documents.

Purpose

The purpose of this document is to present a detailed Salon Website. It will

explain the different functional as well as non-functional requirements of the
system, the interfaces of the system, what the system will do or how the system
will interact with the external users, the constraints under which it will operate.
This Software Requirement Specification document will provide a clear
understanding of what is expected by the client in the proposed Salon Website.
This will give a clear idea on how the software should be developed by the
development team for the end users. This SRS will provide a solid base or
foundation for the project. From this SRS, the designers can design low level
design documents and the testers can create test plans and various test case
documents.

The main goal of the project is to design a scalable and extensible system for
managing the hotel. The system will be designed with the user-centric approach
that will ensure that the user requirements mentioned in the documents must be
full filled and must conforms to the required standards. The new proposed
system will operate efficiently by eliminating all the time consuming issues and
provides a better and much enhanced services to the customers. The proposed
website is multi-platform such that it will work in all the operating systems and
most of the browsers.

Scope of the Project

The website to be produced is a Salon Website which will help the customers of
the Salon to reserve appointments and other facilities of the salon from
anywhere in the world. The core part of the project is the reservation and the
booking system to keep track of the reservations and room availability. This
will be explained in detail in ‘3 – Functional Requirements’ section. There are
three types of the end users for this Salon Website. The first ones are the
customer who uses the system for the reservation purposes. The other end users
are the admin user and the management users who are given separate
authentication to the Salon Website

The booking module is used to reserve the salon rooms. The customer can book
the appointments through online or through phone or in person. The customer
needs to enter their personal details and have to pay the total payment to
confirm the booking. An email containing the confirmation details will be sent
to the customer’s email address. When the customer books the appointment
through telephone or in person, the admin members of the Salon need to enter
the customer details by logging to employee modules with corresponding
authorization.

Background

This SRS document is developed by ‘Creative IT Solutions’ based on the

requirements provided by the ‘Curls Group of Salon’ management. This
document will be used as a base document for further project developments.
Creative IT Solutions is a software development company, which is authorized
to perform the analysis, design and implementation of the proposed E-
Commerce Project for managing salon appointment bookings, recreation and
other similar activities.

Meeting Summaries:

Meeting Summary
Meeting Information Team Members
Attended
Date: 6-Sept-2015 Tariq Siddiqui,Abhishek
Prepared by: Abhijeet Singh Pal,Akash
Agenda & Summary: Formation of the project Gaurav,Abhijeet Singh
team and defining roles
and responsibilities.

Meeting Summary
Meeting Information Team Members
Attended
Date: 13-Sept-2015 Tariq Siddiqui,Abhishek
Prepared by: Akash Gaurav Pal,Akash
Agenda & Summary: Developing the document Gaurav,Abhijeet Singh
based on the information
provided by the client.
Meeting Summary
Meeting Information Team Members Attended

Date: 20-Sept-2015 Tariq Siddiqui,Abhishek

Prepared by: Abhishek Singh Pal Pal,Akash

Agenda & Summary: Finalizing the functional Gaurav,Abhijeet Singh

requirements provided by
the client.

Meeting Summary
Meeting Information Team Members Attended

Date: 27-Sept-2015 Tariq Siddiqui,Abhishek

Prepared by: Tariq Siddiqui Pal,Akash
Gaurav,Abhijeet Singh
Agenda & Summary: Developing the SRS
document.
Assumptions and Constraints:

 The project should be completed within specified time period

including Planning, Designing, Development, Testing and
Deployment.
 The project should be completed within specified budget.
 The Requirement Traceability Matrix (RTM) should be correlated
and completed.
 All the Entry and Exit criteria of all the stages should be met.
 The product should be user-friendly, reliable and should maintain
the industry standards without compromising the quality.
 The system architecture and design should be open and in a
standard way such that additional functionalities can be added later
without much effort.
 It is the responsibility of the client company to set up hardware for
running the application.
 The consultation regarding project development comes at no cost to
the project

Methodology:

We have used both structured analysis as well as object oriented analysis for the
development of this Software Requirement Specification document. Analysis
can be defined as understanding the business needs as well as processing the
requirements. We have designed the structural chart, Data Flow Diagram and
Entity Relationship diagram for the structured analysis of the project. Similarly
we have developed Class Diagrams, Use case diagrams and Activity diagrams
for the Object Oriented view of the project.

The structured analysis make the project into a small, well defined set of
activities and specify the sequence and interaction between these activities.
They give diagrammatic and other modeling techniques to give a precise idea
on how to develop the system for the developers. One of the key tools used in
the structured analysis is the Data Flow Diagrams. The data flow diagrams will
help to identify the flow of data within an application and how the data moves
between different processes in the system. A Data flow diagram will show what
information will be input to the system and what information will be output
from the system, where the data will come from and where it is stored and how
the flow and control of data will go from one process to another. The Entity
Relationship diagram will help to identify the different entities in the system
and how it will be interacting with other entities in the system. The Activity
diagram defines the major activities that are happening in the system.

The Object-Oriented Analysis and Design is one of the main methodologies for
developing high quality object-oriented systems. The object oriented
methodology will help to reuse the existing built-in functions or models in a
much easier way. It mainly involves three steps.

1) Object-Oriented Analysis – This deals with the design requirements and

overall architecture of a system and describes what or how the system
will work with respect to the key objects.
2) Object-Oriented Design – This will help to convert the system
architecture into programming constructs such as classes etc.
3) Object-Oriented Programming – This will help to implement the object
oriented design into a well-defined application.
Software Development Methodology:

The software development life cycle model that we used for developing this
project is the waterfall model.

Waterfall Model
The waterfall model is conventional software development model in which the
different phases are sequentially organized. In this model the output of the one
phase will form the input for the succeeding phase. The main phases of the
waterfall model are

 Requirements Specification
 Design & Analysis
 Development/Implementation
 Testing
 Deployment
 Maintenance
The flow of the process in the waterfall model cannot be reversed. This
model is an old model which was proposed by Royce in 1970. In Royce’s
original water fall model it is seen to be non-flexible and non-iterative.

Requirements Specification

The Requirements Specification is the initial phase of any software

development models. In order to begin a project, we need get the requirements
from the clients or the customers. After the initial proceedings are done, it is the
responsibility of the System Analysts or the Business Analysts to collect the
required information from the clients. The System Analysts use different kinds
of methods to collect the requirements from the clients. This includes
interviews, questionnaires, communication through telephone and email,
evaluating the company documents, referring the similar applications existing in
the industry etc. The requirements are the core part of the software
development. The requirements should be well defined, complete and should be
realistic. Once the requirements specification is completed, they will be well
documented. The documents thus formed which forms the output of the
Requirements Specification stage and input of the Design and Analysis stage is
known as Software Requirement Specification (SRS) document.

Analysis and Design

The Analysis and Design is the second stage of the Waterfall model. The
requirements which are available in the form of the Software Requirement
Specification (SRS) document is analyzed in this phase. The Development Plan
and Test Plan documents are created in this stage. The Development Plan
includes the technology that they need to use in developing the software, the
environment used, software and hardware tools to be used, the right resources,
exit and entry criteria etc. The Test Plan document includes the testing
methodologies, test harness, tools and softwares to be used, resources, test
estimates, test schedules etc. The input of the Design stage will be the
Functional Specification (FS) document. During the Design process, two set of
documents will be produced known as High Level Design (HLD) document and
Low Level Design (LLD) document. The HLD will give a high level view of
the structure of the software which is going to be developed where as the LLD
will go into the depth. The test team will start developing the test cases based on
the Software Requirement Specification document. The outputs of the Analysis
and Design stage are HLD’s and LLD’s.
Development & Implementation

The input of this stage is the High Level Design documents and the Low Level
Design documents. The developers will start coding or developing the software
in this stage. They will do the Unit Testing once the development will be
completed. The Project Manager will divide and allocate the work among the
developers. The developers will be frequently communicating with the System
Analysts or the Business Analysts for clarifications. The output of this stage
will be a software product which can be compiled and working. Once the
software module is completed they will inform the Testing team for further
testing.

Testing

Testing is the process by which we can make sure that the software is running
without errors and it meets all the customer or requirement specification. The
input of this stage is the software module. The testing can be broadly divided
into two- Black box and white box. Black box testing means testing the
functionalities of an application and White box means testing the internal design
& structure of the application.

Once the developed module has been deployed, then the Test team will do a
Smoke Testing in order to make sure that all the major functionalities are
working on a high level view. If any show stoppers exist, then the test team will
reject the build otherwise they will accept the build and do further testing
activities. After the Smoke Testing, the testers will execute the test cases based
on the priority from high to low. If there is any mismatch between the expected
result and the actual result, then they will log a defect in the defect tracking
tools and assign it to the developers. The developers will fix the defects and
send it back to the tester for verification. The tester will do the fix verification in
the next build. The tester will close the issue if it is fixed, otherwise reopen it
and reassign to the corresponding developer. Once the corresponding exits
criteria such as when to stop the testing is met, the testers will deploy the build
into the production servers.

Deployment

Deployment means the installation of the product software in the corresponding

client sites. Once the software is deployed in the client sites, an end user testing
will be done at the client sites. The end user testing done at the development
sites is known as Alpha testing and at the client sites is known as Beta testing.
The project team needs to prepare the user manual or installation documents for
the clients or the customers.

Maintenance

The final stage of the waterfall model is known as the Maintenance phase.
There may be issues related to data base or any up gradation in most of the
cases and in those cases, the client need to be in contact with the project team
who developed the software. Sometimes after some years, the clients need to
implement new functionalities or customize their application according to their
needs. In that case also, the maintenance phase is also necessary.
 Requirements Specification

Design & Analysis

Development / Implementation

Testing

Deployment

Maintenance

Fig: Waterfall model

Functional Requirements
Functional requirements for the purposed system which define the fundamental
actions of the system contain all the information of the software requirements
for the development of the booking system for e-Hotel project.
1. Customer interface functional requirements

o Search services
  Customers will have be given the following access as per the
functional requirement.
 The system shall enable customer to check the availability of
applied services.
o Rate
 The system shall provide price range of all the services.
o Details of appointment
 The system shall enable customer to check and review all the
details of salon.
o Book
 The system shall have next button or cancel button for
booking procedure.
 The system shall enable customer to visit booking page,
allow booking the appointment and confirming it.
 The system shall send an email notification of booking
confirmation to customer.
 The system shall redirect customer to payment page if they
click the confirmation.
o Payment
 The system shall calculate the total bill amount.
 The system shall enable customer to pay the bill online via
credit card or PayPal.
 The system shall should verify and accept the credit card.

1. Management team interface

o Login function
  The system shall allow only management team member to
access the particular system.
 The system should recognize the member of the
management.
 The system shall give different access to management team.

o View or edit
 The system should allow management member to check
customer details.
 The system should allow team member to add information.
 The system should allow team to change the information.

2. Booking

o The system shall record all the following information of customer

 Cust_ID
 Cust_Fname
 Cust_Sname
 Cust_DOB
 Cust_Address
 Cust_Mobile
 Cust_Email

3. Database Administrator

o The system should allow admin users to access the system only
with username and password.
o The system should allow admin users to edit any files and folders.
o The system should accept any command from admin users.
o The system should provide all the details to admin:
 Service_Categ_ID
 Category
 Service_Price
 Booking_ID
 Cust_ID
 Item_ID
 Total_Amount
 Payment_ID
 Credit_Card_No
 Payment_Date
 PricePayment_Mode
Entity – Relationship Diagram
This describes the relationship between different entities in the system.

Entity: An entity can be defined as an instance of an object which has a number

of properties or attributes.

Attribute: An attribute can be defines the properties of the data object that takes
the different characteristics. The attributes can be used to :
a) Name an instance of data object
b) Describe the instance
c) Make reference to another instance in another table.

Relationships: Entities are connected to each other in a variety of different

ways.

Cardinality and Modality:

Cardinality: The data model must be capable of representing the number of
occurrences of the given object in the system. The relationship between
different entities can be represented in the following ways.
1) One to one – A relationship is said to be one-to-one if the occurrence of
an object can relate one and only one relationship with another object and
vice-versa.
2) One to many – A relationship is said to be one-to-many if the occurance
of an object ‘A’ can relate to one or more occurrences of object ‘B’, but
an occurrence of object ‘B’ can relate to only one occurrence of object
‘A’ .
3) Many-to-many – An occurrence of object ‘A’ can relate to many
occurrences of object ‘B’ and vice-versa.
Activity Diagram
Class Diagram
Functional requirement for website

1. Overview of the website

The site should be designed to allow any users to search database from hotel
system database. The system should allow customer to view information of
rooms and hotel and allow customer to book the records in the database,
accept the payment and provide confirmation. Other function that could
increase the usability of a website is:
1. Automatic email confirmation of the room booking.
2. Confirmation of payment details.
3. Provide list of room available and rates.

2. System platform and interface

Website should be accessible to every users using web browsers that is version
4.0 or higher. The website should be available in different language and used
suitable visual interface. The site should maintain the inventory of website
visited by the users from different areas in its database.
Home Page:

Home page is the first page of the website which is the index page for web
designer. It will provide all the information about the hotel and its activities. It
should give detail information and attract users to be customers. The page will
have a banner covering 25 percentage of the page with graphic appearance. The
page will have logo and site map above the banner with the entire menu bar
under the banner. The page should contain some information and images at the
middle following the entire social networking link at the bottom right of the
page while ending with privacy link at the bottom left end.

Booking page:

Booking page follows the same interface as home page. It will contain logo,
sitemap at the top following banner and entire menu bat. The page show
booking calendar, amount and booking form which contain information about
customer and payment method instead of image and other text shown in the
home page. The page then will be entire menu social networking at the bottom
right ending with privacy link at the bottom left end.

Website administration:

The site should have different page for administration users with separate
accessibilities to understand users’ behaviors. System administrators could uses
the records for user’s activities to find the lack of functional requirement and for
better improvement.
Hardware Interface

The system should run on Microsoft windows based system.

Data conversion requirements

The database plays vital role in the organization and it should be stored in
proper way that required information can be retrieve easily from stored
warehouse such as room details is stored in room database. The users should be
allowed to access the information about rooms which as available and what are
the cost of the room where as security system should be used by system so
confidential information does not access to unauthorized person. The database
system should be organized so that management can retrieve the information in
simple and summarized form.

Requirements:

Hardware Requirement

Here is some requirement of project which relates to the client side and server
side, is defined below. It just explains necessity of some hardware and software
to perform a project task.

CLIENT SIDE SERVER SIDE

Intel Pentium IV Intel Xeon processor 3000

sequence

Mouse 1024 MB RAM

Keyboard Network Interface Card

Administration system:

An interface would be provided to the website by which client can manage all the
functionalities on the website. Here administrator can also view and modify the
details provided by the customers.

Critical Some restrictions must be placed to manually add new users,

delete unnecessary data, and also to keep all the records of
all old customers.

Technical issue For all the users on the system, after some time the passwords
should be changed. For this, when a user logs in, they need
to notify to change password.
Quality assurance:
Usability:

A new user must find the functions easily that he is looking for on the system.
EXAMPLE: If a new customer wants to get information about the services and
services, so these details should be categorized in a way which makes it easy for
user to access them. The layout and performance of functionalities of the system
should be pleasing to the user. For the administrator, the updating of the system
should be easy and secure. The system should also look professional,
representing the functionalities in a categorized manner.

Efficiency:

As there can be various requirements accessed by the users, the system may
need some specific updating. But no too much time should be spent on
updating. There can be some functionality which decreases the human work and
automatically responds to the user’s requirements.

Adaptability:

The system should be able to easily accept the changes. If any time something
new is introduced to system, it is necessary that it can accept the changes easily.

Extensibility:

When we develop system, it should be created in a way which would support

the extensibility. If a new customer or staff detail is to be added, the procedure
should be easy and less time consuming, there can be also multiple
functionalities added for doing it.
Training requirement:

The client of E-Salon is going to need satisfactory training of the application,

which would enable them to use the application successfully without any help
of the developer group. The training is a crucial part of the project because if the
client doesn’t know the functionality given to him, he would not be able to
utilize the application successfully. The training will make use of the following:

 Perfect version of the application.

 Back up CD for the application.
 Instructions and Manual for the system.
 Web server instructions.

The training will also involve the client how to successfully following some
specific tasks.

 Insert user and other relevant procedures.

 Resetting the users’ passwords.
 Generating rooms and services
 Explanation of using the application in a regulated way to end users.
 Using help function effectively.
 General trouble-shooting procedures.

System Availability:

The system should be designed in such a way that the system is available 24/7
and it should not undergo any downtime due to the heavy traffic of the web
users. While developing system the market researchers must estimate the traffic
flow for the website and should design according to it. The availability of a
system is typically measured as a factor for its reliability as reliability increases,
so does the availability. The availability of a system can also be increased by
strategy focuses on increasing of test and maintain and not on reliability.
Improve maintainability is generally easier than reliability. Maintain estimates
(repair cost) are also generally more accurate. Because uncertainties in the
reliability estimate is in most cases very large, it is nevertheless likely to
dominate the availability problem, even while maintaining levels are very high.
We provide system maintenance so that we can use to maintain and upgrade our
online services and business IT systems. This maintenance can have an effect
on our online services; we decided to avoid inconvenience to the users from the
tip. During this scheduled maintenance, however, we cannot guarantee the
integrity of all the information submitted by or retrieved. But we intend to
provide a window that says that the Web site is under maintenance and is not
available until the maintenance has been completed.

General Performance:

Even a few seconds of delay is enough to cause an unpleasant user experience.

Users are no longer in control, and they've deliberately annoyed having to wait
for a computer. Thus, the short delay, users give up unless they are determined
to complete the task. The result is you can easily lose half your sales (to those
customers, less done) simply because your site is slow for a few seconds on
each page slow each page.
1 second keeps the user seamless flow of thought. Users can delay the feeling,
and so know the outcome is to generate the computer but they still feel in
control of the overall experience and that they are moving freely rather than
waiting for the computer. This degree of eligibility is needed for good
navigation. 10 seconds, the attention of the user. 1 – 10 seconds, users surely
feel at the mercy of the computer and wish it was faster, but they can handle.
After 10 seconds, they start to think about other things, making it harder to get
their brains back on track as soon as the computer finally responds.
A 10-second delay is often a site for users to leave immediately. And even if
they stay, it's harder for them to understand what's going on, making it less
likely that they will pass in difficult tasks.

Capacity:

A representative within specified service level capacity website operations

(browsing, search, navigation, etc.) to carry out each visitor is the number of
visitors that can support it.
This is a server hosted by site disaster survival means to think. Facilities two-
drive hard drive exactly the same locations we and combining a form to provide
information be stored in the database and his website to avoid losses in case of
events likely to destroy the server where both server to another multiple drives
to RAID would want to. Ability to perform functions that affect part or a
complete enterprise network damage may vary. Outgoing traffic to increase
substantially if can make due damage and critical data loss across servers.
Seriousness of the damage depends on the type of virus and results of its
activity for the user machine barely noticeable there.

TOOLS AND TECHNOLOGY USED 

Tool:
 Visual Studio 2010: Microsoft Visual Studio is a powerful IDE that
ensures quality code throughout the entire application lifecycle, from
design to deployment. Whether you’re developing applications for
SharePoint, the web, Windows, Windows Phone, and beyond, Visual
Studio is your ultimate all-in-one solution.
MSSQL:
Microsoft SQL Server is a relational database management system developed
by Microsoft. As a database, it is a software product whose primary function is
to store and retrieve data as requested by other software applications, be it those
on the same computer or those running on another computer across a network
(including the Internet). There are at least a dozen different editions of
Microsoft SQL Server aimed at different audiences and for different workloads
(ranging from small applications that store and retrieve data on the same
computer, to millions of users and computers that access huge amounts of data
from the Internet at the same time).

Technology:

 ASP.Net :ASP.NET is a Web application framework developed and

marketed by Microsoft to allow programmers to build dynamic Web
sites, Web applications and Web services. It was first released in January
2002 with version 1.0 of the .NET Framework, and is the successor to
Microsoft’s Active Server Pages (ASP) technology. ASP.NET is built on
the Common Language Runtime (CLR), allowing programmers to write
ASP.NET code using any supported .NET language
.
 C#.Net: C#.Net is a programming language developed by Microsoft.

 SQL: SQL is a structured query language used for querying

Database.

 HTML: It is used for giving eye catching look to the website. And also
providing easy to use GUI.

 CSS: CSS is cascading style sheet which is used to give designer

look to HTML using the external file.

 Java script: Java script is used for client side scripting which can
help in using validation on the website and many more
other functions.
  CONCLUSION

Project aims to develop website for Body Grafixx UniSex Salon, Lucknow.
In order to provide solution to current problems and increase the efficiency
of salon.
It is designed for people to book appointments .It is 24/7 service.
Consumers have been increasingly using the Internet to search for
appointments-related information on salon Websites.
To facilitate a better understanding of e-commerce, hospitality and tourism
researchers have shown the importance of establishing content-rich and user
friendly Websites
The system uses HTML as front end ,ASP.NET and MYSQL as backend.
 REFRENCES

 www.slideshare.net/skhabib/salon-management-ppt
 https://www.scribd.com/doc/.../Synopsis-of-salon-management-system
 www.bhms.ch/salon-Management
 www.srsalon.net/