Project Report

On
Men Salon Management System

1
 Introduction to Project

With tremendous increase in technology, information technology is a fast developing field.

Technology which is in vogue today might become redundant tomorrow. This ever changing scenario
makes it possible to provide the latest and most modern IT solutions to various business and
institutions.

I am doing my project on Men’s Salon Management System. There is the need for efficient
management of a network based system for handling customer orders.

This project is an endeavor to provide a solution to this. The proposed system enables an
administrator to keep track of customer orders and maintaining records of the customers. He can view
the submitted requirements made by the customer. He can also view the reports generated by him and
can also sent approvals or rejections instantly.

Thus the project is a sincere effort in simplifying the task of administrators in an easily usable format.

I finalized to make this project and hence planned to develop this system using PHP for front end and
MySQL as the Back End.

2
 Project Details

In this project we use PHP and  MySQL database. It has two modules admin and user.

Admin

1. Dashboard: In this section admin can see all detail in brief like total number of
customer, Total number of appointment, Rejected Appointment, Accepted
Appointment, Total Services, Today’s sales, yesterday’s sale, Last seven days
sales and total sales.
2. Services: In this section admin can manage services of parlor (add and update).
3. Pages: In this section admin can manage about us and contact us pages.
4. Appointment: In this section admin can view the detail of appointments and
have right to reject and select appointment.
5. Subscriber: In this section, admin can view subscriber emails.
6. Add Customer: In this section admin can mange customer (add/update).
7. Customer List: In this section admin can view customer list and assign services
and make invoices of services which is taken by customer.
8. Reports: In this section admin can view users detail and sales in particular
periods
9. Invoice: In this section there is the list of total invoices which is viewed by
admin
10.Search Appointment: In this section admin can search appointment with the
help of his/her appointment number, name and contact number.
11.Search Invoice: In this section admin can search invoices with the help of
his/her invoice number.
Admin can also update his profile, change password and recover password.

User

In MSMS user not require to sign in

Home Page: User can take appointment with Men’s Salon on particular date and time.

Services: User views the services which is offer by Men’s Salon.

About Us: User sees the details of Men’s Salon.

Contact Us: User can contact with Men’s Salon.

3
 Limitation of the Present System
Before starting the project we have to study its limitations and objective some of them are:-
 All the processes of this management are done manually in the form of paper work and the
records are stored in the registers. In such cases there are frequent chances of data redundancy
and data is ease to lose.
 All the introductions related to the customer and others printed on the papers, this activity
generates the chances of data lost.
 All the bills structures are done by hand written; sometimes it produces mistakes in
calculation.
 This system is very time consuming and require lost of manpower

4
 Proposed System
Objective is to overcome the major limitation of the existing enabling effective management
of the customer details thereby improving the performance.
 With improved computerization being involved in the maintenance of customer details,
error and inconsistencies can be kept at par.
 Easy retrieval of data will be made possible by finding techniques.
 Validation of data will ensure only accurate, valid and complete data is stored in the
database.
 Proper monitoring of the processes from customer registration to activation. Report
generation will help make it easy to analyze the performance at the Bank.
 This will be much less time consuming comparing to existing system.

5
 Advantage of Proposed System
 With improved computerization being involved in the maintenance of user’s appointment,
customer details. Error and inconsistencies can be kept at per.
 Validation of data will be ensure only accurate valid and complete data stored in the database.
 Easy retrieval or data will be made possible by finding techniques.
 Report generation will help made it easy to analyze the performance or clinic Administration.

Objective and Scope of Proposed System

 The objectives of the proposed system are to overcome the major limitation of existing system
enabling effective management of the customer details thereby improving the performance of
SHOP ADMINISTRTION.
 The system will store all the basic data processing needs the shop management.

6
 Feasibility study
A feasibility study is undertaken to determine to the possibility or probability of either improving the
existing system or developing a completely new system. It helps to obtain the overview of the
problem and to get a rough assessment of whether other feasible solution exists.

NEEDS FOR FEASIBILITY STUDY:

The feasibility study is needed for following things:-

 Answer the questions whether a new system is to be installed or not?

 Determine the potential of the existing system.

 Improve the existing system.

 Know what should be embedded in the new system.

 Define the problems and objectives involved.

 Avoid costly repairs at later stage when system is implemented.

 Avoid crash implementation of the new system.

 Avoid the ‘Hardware approach’ i.e. getting a computer first and then deciding how to use it.

The Feasibility study is divided in to three parts:-

 TECHNICAL FEASIBILITY

 ECONOMIC FEASIBILITY

 OPERATIONAL FEASIBILITY

 ECONOMIC FEASIBILITY

Economic analysis is most frequently used for evaluation of the effectiveness of the system. More
commonly known as cost/benefit analysis the procedure is to determine the benefit and saving that
are expected from a system and compare them with costs, decisions is made to design and
Implement the system.
This part of feasibility study gives the top management the economic justification for the new system.
This is an important input to the management the management, because very often the top

7
management does not like to get confounded by the various technicalities that bound to be associated
with a project of this kind. A simple economic analysis that gives the actual comparison of costs and
benefits is much more meaningful in such cases.

In the system, the organization is most satisfied by economic feasibility. Because, if the organization
implements this system, it need not require any additional hardware resources as well as it will be
saving lot of time.

 TECHNICAL FEASIBILITY
Technical feasibility centers on the existing manual system of the test management process and to
what extent it can support the system.
According to feasibility analysis procedure the technical feasibility of the system is analyzed and the
technical requirements such as software facilities, procedure, inputs are identified. It is also one of the
important phases of the system development activities.
The system offers greater levels of user friendliness combined with greater processing speed.
Therefore, the cost of maintenance can be reduced. Since, processing speed is very high and the work
is reduced in the maintenance point of view management convince that the project is operationally
feasible.

 BEHAVIOURAL FEASIBILITY

People are inherently resistant to change and computer has been known to facilitate changes. An
estimate should be made of how strong the user is likely to move towards the development of
computerized system. These are various levels of users in order to ensure proper authentication and
authorization and security of sensitive data of the organization.

The prototyping model

Prototyping Model is based on the idea of developing an initial implementation, exposing this to user
comment and defining this through many until an adequate system has been developed.

Benefits of prototyping model

The prototyping paradigm begins with requirements gathering. Developers and customers meet and
define the overall objective for the software, identify the requirements and outline the areas where
further definitions are necessary.
The prototype design, is often, quite different from that of the final system. The benefits of
developing a prototype early in the software process are:

8
  Misunderstanding between software developers and users may be identified, as the
functions are demonstrated.

 Missing user services may be detected.

 Difficult to use or confusing user services may be indentified and refined.
 Software development staff may find incompleteness and inconsistency in requirement
as the prototype is developed.

 A working albeit limited systems is available quickly to demonstrate the feasibility

and usefulness of the application to the management.

 The prototype serves as a basis for writing the specification for a production quality
system. Though the principle purpose of prototyping is to validate software
requirements, software prototype also has other uses.

 A prototype system can be used for training users before the formal system has been
delivered.

 Prototype can be run back-to-back tests. This reduces the need for tedious manual
checking of test run. The same test is given to both the prototype and the system under
test to look for differences in the final results and thereby making necessary changes.
Thus prototype serves as a technique of risk reduction.

Selecting the prototype approach

The prototype paradigm can be either close ended (throwaway prototyping) or open ended
(evolutionary prototyping). Before selecting closed or open-ended approach, it is necessary to
determine whether the system to be built is suitable for prototyping or not. This is decided
depending on application area, complexity, and customer characteristics and projects
characteristics. Prototyping or evolutionary prototyping. The throwaway is developed to
understand the system requirements while the evolutionary prototype evolves through a
number of versions to the final system.

9
 Diagram

 The entire system is projected with a physical diagram which specifics the actual storage
parameters that are physically necessary for any database to be stored on to the disk. The
overall systems existential idea is derived from this diagram.

 The relation upon the system is structure through a conceptual ER-Diagram, which not only
specifics the existential entities but also the standard relations through which the system
exists and the cardinalities that are necessary for the system state to continue.

 The content level DFD is provided to have an idea of the functional inputs and outputs that
are achieved through the system. The system depicts the input and output standards at the
high level of the systems existence.

A DFD does not show a sequence of steps. A DFD only shows what the different process in a system
is and what data flows between them.

The following are some DFD symbols used in the project

External entities

Process: A transaction of information that resides

within the bounds of the system to be module.
DATAFLOWS

DATASTORE: A repository of data

that is to be stored for use by one or
more processes, may be as simple as
buffer of queue or as a relational
database.

10
RULES FOR DFD:

 Fix the scope of the system by means of context diagrams.

 Organize the DFD so that the main sequence of the actions reads left to right
and top to bottom.
 Identify all inputs and outputs.
 Identify and label each process internal to the system with rounded circles.
 A process is required for all the data transformation and transfers. Therefore,
never connect a data store to a data source or the destinations or another data
store with just a data flow arrow.
 Do not indicate hardware and ignore control information.
 Make sure the names of the processes accurately convey everything the process
is done.
 There must not be unnamed process.
 Indicate external sources and destinations of the data, with squares.
 Number each occurrence of repeated external entities.
 Identify all data flows for each process step, except simple Record retrievals.
 Label data flow on each arrow.
 Use details flow on each arrow.
 Use the details flow arrow to indicate data movements.
 There can’t be unnamed data flow.
 A data flow can’t connect two external entities.
LEVELS OF DFD:
The complexity of the business system means that it is a responsible to represent the operations of
any system of single data flow diagram. At the top level, an Overview of the different systems in an
organization is shown by the way of context analysis diagram. When exploded into DFD
They are represented by:
 LEVEL-0 : SYSTEM INPUT/OUTPUT
 LEVEL-1:SUBSYSTEM LEVEL DATAFLOW FUNCTIONAL

11
  LEVEL-2: FILE LEVEL DETAIL DATA FLOW.
The input and output data shown should be consistent from one level to the next.

LEVEL-0: SYSTEM INPUT/OUTPUT LEVEL

A level-0 DFD describes the system-wide boundaries, dealing inputs to and outputs from the
system and major processes. This diagram is similar to the combined user-level context diagram.

LEVEL-1: SUBSYSTEM LEVEL DATA FLOW

A level-1 DFD describes the next level of details within the system, detailing the data flows
between subsystems, which make up the whole.

0 Level Diagram

0.0

Men’s Salon Management

System
User Administrator

1st Level Diagram

12
 1.1
Appointment / Invoice
Records

Administrator Administrator

1.2
User
Employee

2nd Level Diagram

13
Unified Modelling Language Diagrams(UML):
 The unified modelling language allows the software engineer to express an analysis model
using the modelling notation that is governed by a set of syntactic semantic and pragmatic
rules.

 A UML system is represented using five different views that describe the system from
distinctly different perspective. Each view is defined by a set of diagram, which is as follows.

User Model View

i. This view represents the system from the users perspective.

ii. The analysis representation describes a usage scenario from the end-users perspective.
Structural model view

 In this model the data and functionality are arrived from inside the system.

 This model view models the static structures.

Behavioural Model View

 It represents the dynamic of behavioural as parts of the system, depicting the interactions
of collection between various structural elements described in the user model and
structural model view.

Implementation Model View

 In this the structural and behavioural as parts of the system are represented as they are to
be built.

Environmental Model View

In this the structural and behavioural aspects of the environment in which the system is to be
implemented are represented.

UML is specifically constructed through two different domains they are

 UML Analysis modelling, which focuses on the user model and structural model views
of the system?

14
  UML design modelling, which focuses on the behavioural modelling, implementation
modelling and environmental model views.

Use Case Diagrams Use

Visit the MSMS

Make Appointment

Subscribe

15
Use Case Diagrams admin

Login

Dashboard

Manage Services
Add/ update

16
 Manage Pages

Manage Appointment
(Accept / reject)

Add new Customer

Generate invoices

Generate Reports

Update Own Profile

Change Password

ENTITY RELTIONSHIP DIAGRAM (ERD)

Entity-Relationship Diagram

 This document is an entity-relationship diagram, or “ERD,” for a system to manage

Inventory Management System.
 An ERD is a model that identifies the concepts or entities that exist in a system and the
relationships between those entities.

17
 An ERD is often used as a way to visualize a relational database: each entity represents a
database table, and the relationship lines represent the keys in one table that point to
specific records in related tables.
 ERD may also be more abstract, not necessarily capturing every table needed within a
database, but serving to diagram the major concepts and relationships.
 This ERD is of the latter type, intended to present an abstract, theoretical view of the
major entities and relationships needed for management of electronic resources.
 It may assist the database design process for an e-resource management system, but does
not identify every table that would be necessary for an electronic resource management
database.

18
19
 Database Design
The data in the system has to be stored and retrieved from database. Designing the database is part of

system design. Data elements and data structures to be stored have been identified at analysis stage.

They are structured and put together to design the data storage and retrieval system.

A database is a collection of interrelated data stored with minimum redundancy to serve many users

quickly and efficiently. The general objective is to make database access easy, quick, inexpensive and

flexible for the user. Relationships are established between the data items and unnecessary data items

are removed. Normalization is done to get an internal consistency of data and to have minimum

redundancy and maximum stability. This ensures minimizing data storage required, minimizing

chances of data inconsistencies and optimizing for updates. The MS Access database has been chosen

for developing the relevant databases.

Men’s Salon Management System (MSMS) contains 7 MySQL tables :

tbladmin table Structure : This table store the admin personal and login details

tblappointment table Structure : This table store the user appointment details.

20
tblservices table Structure : This table store the services details.

tblcustomers table Structure : This table store the customer details.

tblinvoice table Structure : This table store the customer invoice details.

tblpage table Structure : This table store the pages information.

tblsubscribe table Structure: This table store emails of subscribers.

21
Class Diagram:
The class diagram shows a set of classes, interfaces, collaborations and their
relationships.

Project Output Screen

22
Home Page

23
Thank You Page

24
Services

25
Book Appointment

26
Contact

27
Admin Login

Dashboard

28
Add Services

Manage Service

29
UpdateService

About Us

30
Contactus

Appointment

31
View New Appointment

32
View Old Appointment

33
Add Customer

Customer List

34
Assign Services

35
Subscriber

Between Dates Reports

36
Detail of Between Dates Reports

Sales Report

37
Detail of Sales Report

Invoice List

38
Detail of Invoice

Search Appointment

39
Search Invoice

Change Password

40
Profile

Forgot Password

41
Reset Password

42
 System Implementation Phase
1. HTML
WHAT IS HTML?
To publish information for global distribution, one needs a university-understood language, a kind of
publishing mother tongue that all computers may potentially understand. The publishing language
used by the World Wide Web is HTML (Hyper Text Markup Language)

HTML Gives Authors the Means To

1. Publish online documents with headings, text, tables, list, photos etc.
2. Retrieve online information via hypertext links, at the click of a button
3. Design forms for conducting transactions with remote services, for use in searching
information, making reservation, ordering products etc.;
4. Includes spreadsheets, video clips, sound clips, and other applications directly in the
documents.
5.
Some HTML Tags

<HTML> :Starting an HTML tag

<HEAD> : Creating a web page’s head
<TITLE> : Giving a web page ‘s body

</HEAD> : Ending a web pages head

</BODY> : Ending a web pages body
</HTML> :Ending a web page
<FORM> : Creating a HTML forms
<INPUT TYPE=BUTTON> : Creating a buttons
<INPUT TYPE=CHECKBOX> : Creating a checkboxes
<INPUT TYPE=SUBMIT> : Creating a submit button
<INPUT TYPE=TEXT> : Creating a text fields

HTML 4.0

43
HTML 4.0 extends with mechanisms for style sheets, scripting, frames embedding objects, improved
support for right to left and mixed direction texts, richer tables and enhancements to form, offering
improved accessibilities for people with disability.

2. INTRODUCTION TO JAVA SCRIPT

WHAT IS JAVA SCRIPT?
JavaScript, originally supported by Netscape Navigator, is the most popular Web scripting language
today. JavaScript lets you embed programs right in your Web pages and run these programs using the
Web browser. You place these programs in a <SCRIPT> element. If you want the script to write
directly to the Web page, place it in the <BODY> element.

EX: <HTML>
<HEAD>
<TITLE></TITLE>
</HEAD>
<BODY>
<SCRIPT LANGUAGE=”JavaScript”>
</SCRIPT>
</BODY></HTML>

JAVASCRIPTS OBJECTS
JavaScript is an object-oriented language. JavaScript comes with a number of predefined objects.
Objects of the JavaScript
1. Document: Corresponds to the current Web page’s body. Using this object, you have access to
the HTML of the page itself, including the all links, images and anchors in it.
2. Form: Holds information about HTML forms in the current page.
3. Frame: Refers to a frame in the browser’s window.
4. History: Holds the records of sites the Web browser has visited before reaching the
current page.
5. Location: Holds information about the location of the current web page.
6. Navigator: Refers to the browser itself, letting you determine what browser the user has.
7. Window: Refers to the current browser window.

44
JAVASCRIPTS EVENTS
Some of the events of JavaScript
1. on Change: Occurs when data in a control, like a text field, changes.
2. on Click: Occurs when an element is clicked.
3. on Focus: Occurs when an element gets the focus.
4. on Mouse Down: Occurs when a mouse button goes down.
5. on Reset: Occurs when the user clicks the reset button.

JAVASCRIPTS FUNCTIONS

Declaration of function
Syntax: function function name ()
{
…
…
}

Write these functions in <SCRIPT> tag.

5.RDBMS CONCEPTS

1. DATA ABSTRACTION

A major purpose of a database system is to provide users with an abstract view of the data. This
system hides certain details of how the data is stored and maintained. However in order for the
system to be usable, data must be retrieved efficiently. The efficiency lead to the design of
complex data structure for the representation of data in the database. Certain complexity must be
hidden from the database system users. This accomplished by defining several levels of
abstraction at which the database may be viewed.

45
 2. CLASSIFICATION OF DATABASE

There are 3 types of database approaches given below,

a. Hierarchical Database:

In this type of model data is represented in simple tree structured. The record at the top
of three is known as root, the root may have any number of dependents. Each of these
may have any number of low level dependents and so on up to any number of levels.
The disadvantages of the approach are that no independent record occurrence can exist
without it’s superior.

b. Network Database:

In a Network database, data is represented by Network structure. In this approach

record occurrence can have any number of superiors as well as any number of
immediate dependents thus allow many to many correspondence directly than an
hierarchical approach. The main disadvantage of the Network model is data
representation is very complex resulting in complexity of the DML (Data
Manipulation Language).

c. Relational Database:

The Relational model represents data and relationships among data by a collection of
tables each of which has a number of columns with unique names.

6.THE SQL LANGUAGE

SQL is a language for relational database. SQL is a non-procedural i.e., when we use SQL we specify
what we want to be done not how to do it.
Features of SQL
1. SQL is an interactive query language.
2. SQL is a database administration language.
3. SQL is a database programming language.
4. SQL is a client/server language.
5. SQL is a distributed database language.
6. SQL is a database gateway language.

46
Basic SQL Commands

 Data Definition Language commands (DDL)

 Data Manipulation Language commands (DML)

 Transaction Control Language commands (TCL)

 Data control Language commands (DCL)

PHP

 PHP is an acronym for "PHP: Hypertext Preprocessor"

 PHP is a widely-used, open source scripting language
 PHP scripts are executed on the server
 PHP is free to download and use

What is a PHP File?

 PHP files can contain text, HTML, CSS, JavaScript, and PHP code
 PHP code are executed on the server, and the result is returned to the browser as plain HTML
 PHP files have extension ".php"

What Can PHP Do?

 PHP can generate dynamic page content

 PHP can create, open, read, write, delete, and close files on the server
 PHP can collect form data
 PHP can send and receive cookies
 PHP can add, delete, modify data in your database
 PHP can be used to control user-access
 PHP can encrypt data

With PHP you are not limited to output HTML. You can output images, PDF files, and even Flash
movies. You can also output any text, such as XHTML and XML.

47
 Testing
Testing of System
Testing is asset of activities that can be planned in advanced and conducted systematically.
For this reason a template for software testing a set into which we can specific test case design
techniques and testing methods should be defined for the software process.
A strategy for software testing must accommodate low-level test that are necessary to verify that a
small source code segment can be correctly implemented as well as high –level tests that validate
major system functions against customer requirements.

Types of Testing
1. Alpha Testing: -
Testing after code is mostly complete or contains most of the functional and prior to end
user being involved. More often this testing will be performed in house or by an outside
testing firm in close cooperation with the software engineering department.

2. Beta Testing: -
Testing after the product is code complete. Betas are often widely distributed or even
distributed to the public at large in hopes that they will buy the final product when it is
released.

3. Functional Testing: -
Testing two or more modules together with the intent of finding defects, demonstrating that
defects are not present, verifying that the modules performs its intended functions as stated
in the specification and establishing confidence that a program does what it is supposed do.

4. Configuration Testing: -
Testing to determine how well the product works with a broad of the hardware/peripheral
equipment configurations as on the different operating systems and software.

5. Pilot Testing: -

48
 Testing that involves the users just before actual release to ensure that users become familiar
with the release contents and ultimately accept it. Typically involves many users, is
conducted over a short period of time and is tightly controlled.

6. System Integration Testing: -

Testing a specific hardware/software installation. This is typically performed on a COTS
system or any other system comprised or the disparate parts where custom
configurations and /or unique installation are the norm .

7. Software Testing: -
The process of exercising software is with the intent of ensuring that the software system
meets its requirements and the user expectations and doesn’t file in an unacceptable
manner .

8. Security testing: -
Testing of database and network software in order to keep company data and resources from
mistaken/ accidental users, hackers and other malevolent attackers.

9. Installation Testing: -
Testing with the intent of determining if the product will install on a variety of
platforms and how easily it installs .

10. Compatibility Testing: -

Testing used to determine whether other system software components such as browsers,
utilities and competing software would conflict with the software being tested.

49
 Conclusion

The demand of Web application for application is increasing day by day in Software industry, due to
high expectations of client companies.

Hence an attempt of automating an office application had added to our learning experience.

It has also helped in adopting an analytical approach to solving and made us realize that system
development is a step by step process,

Thereby appreciating the role of SDLC model in organizing the complex process of system
development into manageable chunks. Indeed it was a great learning experience.

50
 Bibliography

For PHP
 https://www.w3schools.com/php/default.asp
 https://www.sitepoint.com/php/
 https://www.php.net/

For MySQL
 https://www.mysql.com/
 http://www.mysqltutorial.org

For XAMPP
 https://www.apachefriends.org/download.html

51