Project Report

On
“Hospital Management System”
Is submitted partial fulfillment of the requirement of the
T.Y.B.Sc.
Computer Science
SUBMITTED BY
MISS: - Sav Anjali Ajaykumar
UNDER GUIDANCE OF
MISS. SRAVANTI GAJJELI

Department of Computer Science

B.N.N. College, Bhiwandi
A.Y. - 2022-2023

Mumbai University
 Padmashri Annasaheb Jadhav Bharatiya Samaj Unnati Mandal’s
B. N. N. College of Arts, Science & Commerce, Bhiwandi.
(Self-Funded Courses)
(Department of Computer Science)

CERTIFICATE
This is to certify that Miss Sav Anjali Ajaykumar has successfully
completed the project titled “Hospital Management System” and duly
submitted the project in partial fulfillment of the “B.Sc. (Computer
Science)” degree from the University of Mumbai during the academic
year 2022-2023.

It is further certified that she has completed all the required phases
of project.

_
Project Guide External Examiner Signature of HOD Signature Principal
Miss. Sravanti Gajjeli. Prof. Pramod Shewale Dr. Ashok D. Wagh
 DECLARATION BY THE STUDENT
I Sav Anjali Ajaykumar student of B.Sc. (Computer Science)
hereby declare that the project for the Computer Science, “Hospital
Management System” submitted by me for Semester-V1 during the
academic year 2022-2023, is based on actual work carried out by me
under the guidance and supervision of Miss. Sravanti Gajjeli.

I further state that this work is original and not submitted

anywhere else for any examination.

Signature of Student
 EVALUATION CERTIFICATE
This is to certify that the undersigned have assessed and evaluated
the project on “Hospital Management System” submitted by Sav Anjali
Ajaykumar, student of B.Sc. (Computer Science).

This Project is original to the best of our knowledge and has

accepted for Assessment.

External Examiner
 ACKNOWLEDGEMENT

I would like to extend our heartiest thanks with a deep sense of gratitude
and respect to all those who provides me immense help and guidance during my
period.

I would like to thank my Project Guide Miss. Sravanti Gajjeli for

providing a vision about the system. I have been greatly benefited from their
regular critical reviews and inspiration throughout my work. I am grateful to
them for their guidance, encouragement, understanding and insightful support in
the development process.

I would also like to thank my college for giving required resources

whenever I wanted and for giving the opportunity to develop the project.

I would like to express my sincere thanks to our Principal Dr. Ashok D.

Wagh and our Head of Department Prof. Pramod Shewale for having
facilitated us with the essential infrastructure & resources without which this
project would not have seen light of the day.

Finally I would like to thank my fellows for their cooperation to complete

this project.

With sincere regards,

Sav Anjali Ajaykumar

 Index
Chapter No. Description Page No.
1. Project Information 1-3
1.1 Introduction
1.2 Existing System
1.3 Proposed System
1.4 Aim of the system
1.5 Objective
2. Requirement and Analysis 4-14
2.1 What is Requirement Analysis
2.2 Perspective
Interface(Hardware/Software Requirement)
2.3 System Function
2.4 User Characteristics
2.5 Specific Requirement
2.6 Process Model
3. System Design 15-22
3.1 Activity Diagram(Customer/Admin)
3.2 Use-Case Diagram
3.3 Data Dictionary
3.4 Entity Relationship Diagram
3.5 Data Flow Diagram
3.6 Gantt Chat
4. Screenshots and Coding 23-44
4.1 Coding
4.2 Screenshots
5. Testing and Implementation 45-51
5.1 Testing Approach Used
5.2 Test Cases
5.3 Implementation Approaches
6. Conclusion and Bibliography 52-59
6.1 Conclusion
6.2 Limitation
6.3 Future Scope of system
6.4 Bibliography
 Chapter – 1
Project Information

1
1.1.Introduction

Hospital Management System in PHP is web base application.

The project Hospital Management system includes registration of patients, storing their
details into the system. The software has the facility to give a unique id for every patient
and stores the details of every patient.

The Hospital Management System can be entered using a username and password. It is
accessible either by an administrator. Only they can add data into the database. The data
can be retrieved easily. The interface is very user-friendly. The data are well protected for
personal use and make the data processing very fast.

The Hospital Management System (HMS) project is a software solution designed to

improve the efficiency and effectiveness of hospital operations. The system is aimed at
automating various administrative and clinical processes in a hospital, such as patient
management, appointment scheduling.

The HMS project aims to address the challenges faced by hospitals in managing their
day-to-day operations. These challenges include the manual and paper-based processes,
lack of real-time information, difficulty in coordinating multiple departments and staff,
and inadequate patient care. The HMS project seeks to address these challenges by
providing a centralized and streamlined system that automates various hospital processes,
improves data accuracy, and enhances communication and collaboration among hospital
staff.

The HMS project is a web-based application that can be accessed by authorized hospital
staff from any device with an internet connection. The system will have multiple user
roles with varying levels of access permissions, such as doctors, administrators, and
patients.

The HMS project is expected to provide various benefits to hospitals, such as improved
patient care, reduced administrative burden, enhanced operational efficiency, better
financial management, and improved decision-making based on real-time data. The
project will also contribute to the overall modernization and digitization of the healthcare
industry.
1.2. Existing System

The existing system of hospital management typically involves manual and paper-based
processes that are time-consuming and prone to errors. The existing system may include
various standalone systems and processes that are not integrated, resulting in data silos
and duplication of efforts.
Some of the common challenges faced by hospitals with the existing system include:

1. Manual Patient Management: Hospitals typically rely on manual processes for

managing patient information, such as registration, admission, and discharge. This
can lead to errors and delays in patient care.
2. Appointment Scheduling: Many hospitals still rely on manual appointment
scheduling processes, such as phone calls or in-person visits. This can result in
scheduling conflicts and missed appointments.

1.3.Proposed System

The proposed system of the Hospital Management System (HMS) project is a

comprehensive and user-friendly software solution that will enable hospitals to
manage their operations more efficiently and effectively. The proposed system
aims to address the challenges faced by hospitals and provide a modern and
streamlined solution that will benefit both hospital staff and patients.

The proposed system of the HMS project includes the following features:

1. Patient Management: The system will automate patient registration,

admission, and discharge processes, enabling hospitals to manage patient
information more efficiently and accurately. The system will also provide
patient history, medical records, and test results in real-time, enabling
healthcare providers to make better decisions.
2. Appointment Scheduling: The system will provide an online appointment
scheduling feature, enabling patients to book appointments with healthcare
providers online.
1.4. Aim of the system

1. To provide a centralized platform for managing hospital operations and patient

data.
2. To improve the efficiency and effectiveness of hospital operations.
3. To enhance the quality of patient care and safety.
4. To streamline communication and collaboration among hospital staff.
5. To provide real-time access to patient information for healthcare providers.
6. To reduce paperwork and administrative burden.
7. To enhance data security and privacy.
8. To facilitate data analysis and decision-making.
9. To provide better patient experience and satisfaction.

1.5 Objective
 Automate administrative and clinical processes in a hospital

 Provide a centralized and streamlined system for improved data accuracy, communication,
and real-time monitoring of hospital operations
 Provide a web-based application that can be accessed by authorized hospital staff from any
device with an internet connection
 Integrate with existing hospital hardware and software systems

 Provide multiple user roles with varying levels of access permissions

 Improve patient care by providing healthcare providers with real-time access to patient
information, medical records
 Reduce administrative burden by automating hospital processes such as appointment
scheduling
 Enhance operational efficiency by providing real-time information on hospital operations for
better decision-making and resource allocation
 Chapter – 2
Requirement and
Analysis
2
2.1. What is Requirement Analysis?

1. Server Requirements:
PHP version 5.6 or higher

MySQL version 5.x or higher

XAMPP software installed on the server

2. User Interface Design:

HTML for creating web pages

AJAX for asynchronous communication between the client and server

JQuery for JavaScript library to simplify HTML DOM manipulation

JavaScript for client-side scripting

3. Web Browser Compatibility:

Mozilla Firefox

Google Chrome

Internet Explorer 8 or higher

Opera

4. Functional Requirements:
Patient management system that includes registration, admission, and discharge

Appointment scheduling system for doctors and patients

Billing system for patients and insurance providers

Pharmacy inventory management system

Electronic medical records system for patient information and test results

Staff management system for employee records and scheduling

Reporting system for hospital operations and financial data

Security system for user authentication and authorization

5. Non-Functional Requirements:
User-friendly interface design

Fast and reliable performance

System security and data privacy

Scalability and extensibility for future upgrades and changes

Error handling and system logging for troubleshooting and maintenance

a.
2.2. Perspective

The Hospital Management System (HMS) project can be viewed from multiple
perspectives, including:
1.Patient Perspective: The HMS project aims to improve patient care by providing
healthcare providers with real-time access to patient information, medical records, and
test results. Patients can benefit from a more streamlined and efficient healthcare
experience, with shorter wait times, faster access to healthcare services, and improved
accuracy of medical records.
2.Healthcare Provider Perspective: The HMS project can help healthcare providers to
better manage their day-to-day operations, enabling them to focus more on patient care.
The project can provide healthcare providers with access to real-time information,
improved communication and collaboration among hospital staff, and a more efficient
workflow.
3.Administrative Perspective: The HMS project can help hospital administrators to
streamline hospital operations, automate administrative tasks, and improve financial
management. Administrators can benefit from a more efficient and effective management
of hospital resources, improved communication and coordination among staff, and
enhanced financial performance.
4.Technological Perspective: The HMS project involves the use of modern technologies
such as web-based applications, electronic medical record systems, and automated billing
systems. The project can leverage these technologies to enhance the efficiency, accuracy,
and security of hospital operations.
2.1.1 Interface:

Hospital Management System is a web application for the hospital which manages
doctors and patients. In this project, we use PHP and MySQL database.
The entire project mainly consists of 3 modules, which are
 Admin module
 User module
 Doctor module
Admin module:
1. Dashboard: In this section, admin can view the Patients, Doctors, Appointments
and New queries.
2. Doctors: In this section, admin can add doctor’s specialization and mange doctors
(Add/Update).
3. Users: In this section, admin can view users detail (who take online appointment)
and also have right to delete irrelevant user.
4. Patients: In this section, admin can view patient’s details.
5. Appointment History: In this section, admin can view appointment history.
6. Contact us Queries: In this section, admin can view queries which are send by
users.
7. Doctor Session Logs: In this section, admin can see login and logout time of
doctor.
8. User Session Logs: In this section, admin can see login and logout time of user.
9. Reports: In this section, admin can view reports of patients in particular periods.
10. Patient Search: In this section, admin can search patient with the help of patient
name and mobile number.
Admin can also change his/her own password.
User module (patient):
1. Dashboard: In this section, patients can view the his/her profile, Appointments and
Book Appointment.
2. Book Appointment: In this section, Patient can book his/her appointment.
3. Appointment History: In this section, Patients can see his/her own appointment
history.
4. Medical History: In this section, Patients can see his/her own appointment history.
User can update his/her profile, change the password and recover the password.
Doctor module:
1. Dashboard: In this section, doctor can view his/her own profile and online
appointments.
2. Appointment History: In this section, Doctor can see patient’s appointment
history.
3. Patients: In this section, doctor can manage patients (Add/Update).
4. Search: In this section, doctor can search patient with the help of patient name and
mobile number.
Doctor can also update his profile, change the password and recover the password.

2.1.2 Hardware Requirements:

The Hospital Management System shall provide minimum hardware requirements. The
following hardware configurations are required for the PC for using the Hospital Management
System.

o Hard Disk: 2GB or more of free space.

o RAM:2 GB / 4 GB / 8 GB RAM.
o Processor: Any mobile and computer processor.

2.1.3 Software Requirements

This section lists the requirements that are needed to run the system efficiently. The
operating system needed for the system to run effectively, the interface to run application, the
integrated development environment to develop the environment and the other tools used for
editing purpose areas follow:

● Operating System: Windows 10, MAC OS or Linux

● Database: SQLite.
● Platform Used: Php
● Editer Used: Noteped/Noteped++.
● Browser Supported: Google Chrome, Internet Explorer, Safari, Microsoft Edge.

2.3. System Function

The Beauty parlour management system would have the following basic functions:

● Display all the related information about the system’s main page.

● Display all the categories on the services information page.

 ● Allow the administrator to add new services to the existing list of available
services.

● Allow the administrator to modify the price of each services.

● Users can add or remove the sevices from the customer list.

● Allow the administrator to remove sevices.

● Allow the administrator to complete the customer orders of the users.

2.4.User Characteristics
 The users of Beauty parlor management system, based on their roles, are customers (users)
and administrator (owner). These users are identified based on their experience and technical
expertise.

● Admin

○ The administrator is the owner of the Beauty parlor management system.

One must have a basic understanding of computers and the internet as well
as prior knowledge for operating the eclipse and the php programming
language. The administrator is responsible for all the training documents
required for the system. The administrator can perform the following
functions:

○ Assign or change the price of the services, update the services lists and
delete the services..
○ Can add new services to the system.

● Users
 ○ The users of the Beauty parlour management system are all customers
who would services to test the system. These users are anyone with
services experience and the know-how to browse through a application.
They must have basic understanding about computers and how to parlor
offline. The users should be able to perform the following functions using
this system:

○ Can view or select the services of from the home page.

○ Checkout the services..
○ reservation by providing required information.

2.5. Specific Requirement

 This section contains detail about the system that are required for the designer to create a
system to satisfy the users requirements and for the testers to test the given requirements.
This section contains the interface description for each GUI for the different system
users. These sections also give description about all the system inputs, all the function
performed by the system output (responses).

2.1.4 Functional Requirements

● This section contains the requirements for the Beauty parlor management system.
● The functional requirements, as collected from users, have been categorized as follows to
support the types of user interactions that the system shall have.
● There are two types ofmodule:
o User Module
o Admin Module

User Module
 The following are the functions that users are able to perform

● Reservation user.

● Able to view the services from a list of services page.

● Can view the home page,services page,about page,contect page detail.

● Users are able to view the make an appointment in tanks you page,

● Users are able to checkout services when there are services in the make an
appointment.

● Users shall be able to continue services after the checkout process.

● Users are able to view the customer orders details.

Admin Module

The admin is able to perform the following functions:

● The administration shall be able to view all the user information,

completes the user orders.
 ● The administrator shall be able to add new services to the list of services
page..

● The administrator shall be able to modify or update the items price and
description.

● The administrator shall be able to delete the services from the srevices
page of Beauty parlor management system.

● The administrator shall be able to view the entire history of checkout

services.

● The administrator shall be able to view the entire history of the users who
successfully completed the checkout process.

2.1.5 Non-Functional Requirements

● Usability
○ These requirements focus on the appearance of the user interface and how people
interact with it.
● Reliability
○ These requirements determine system availability that is able to work 24*7 for
365 days if needed.
● Performance
○ The Beauty parlour management system provides the best performance as needed.
● Security
○ Security is required so that the customer information cannot be leaked and keep
the data safe.
● Flexibility
○ This System is able to provide the flexibility to run in any browser and able to
modify in every configuration.
● Reusability
○ In future, the owner requirements will increase so that they will be able to reuse
the code and make changes to fulfill the requirements. So, this system will be
reusable in future.
2.6. Process Model

For this system, the Iterative model is selected.

What is an Iterative Model?

 In an iterative model, the iterative process starts with a simple implementation of a

small set of the software requirements and iteratively enhances the evolving versions
until the complete system is implemented and ready to deploy.

 An iterative life cycle model does not attempt to start with a full specification of
requirements. Instead, development begins by specifying and implementing just part of
the software, which is then reviewed in order to identify further requirements. This
process is then repeated, producing a new version of the software at the end of each
iteration of the model.

Iterative Model Design:

 Iterative process starts with a simple implementation of a subset of the requirements

and iteratively enhances the evolving versions until the full system is implemented.
At each iteration, design modifications are made and new functional capabilities are
added.
 The basic idea behind this method is to develop a system through repeated cycles
(iterative) and in smaller portions at a time (incremental).
 Iterative and Incremental development is a combination of both iterative design or
iterative method and incremental built model for development.
 “During software development, more than one iteration of the software development
cycle may be in progress at the same time” and “This process may be described as an
evolutionary acquisition or incremental built approach.
 In the incremental model the whole requirement is divided into various builds. During
each iteration, the development module goes through the requirements, design,
implementation and testing phases.
 The key to successful use of an iterative software development lifecycle is rigorous
validation of requirements, verification and testing of each version of the software
against those requirements within each cycle of the model.
Pictorial representation of Iterative Model:
Requirement

Analysis

Design Design
Design

Testing Testing
Testing

Implementation Implementation
Implementation

Review Review
Review

Deployment

Maintenance

Figure: Iterative Model

Advantages
● Some working functionality can be developed quickly and early in the life cycle.
● Results are obtained early and periodically.
● Parallel development can be planned.
● Progress can be measured.
● Less costly to change scope or requirements.
 ● Testing and debugging during smaller iteration are easy.

Disadvantages

● More resources may be required.

● Although the cost of change is lesser, it is not very suitable for changing requirements.
● More management attention is required.
● Defining increments may require definition of complete system.
Chapter – 3
System Design
3
3.1. Activity Diagram

 Activity Diagram is basically a flowchart to represent a flow from one activity. The activity
can be described as an operation of the system. The basic purpose of activity diagram is to
capture the dynamic behavior of the system. It is also called object-oriented flowchart.

The purpose of an activity diagram can be described as –

o Draw the activity flow of a system.

o Describe the sequence from one activity to another.
o Describe the parallel, branched and concurrent flow of the system.

Name of Symbol Symbol Description

Represent the beginning of a process or
Start Symbol workflow in activity diagram.

Represents the main component of an

Activity Symbol activity diagram. The symbol indicates
the activities that make up modelled
process.
Action Flow It indicates the transmissions from one
action state to another.
The symbol represents a decision with
alternate paths. When an activity
Decision Symbol requires a decision prior to moving on
to the next activity, add a diamond
between the two activities.
Fork A fork node is used to split a single
upcoming flow into multiple concurrent
flows.
Time event It indicates that an event that stops the
flow for a time.
End State It indicates the end of the flow.
 Figure : Symbol for activity diagram

3.1.1 Customer:

Figure : Customer Activity Diagram

 3.1.2 Admin:

Figure : Admin Activity Diagram

3.2.Use-Case Diagram

 Use-Case diagram captures the system’s functionality and requirements by using actors and
use cases. Use cases model the services, task, function that a system needs to perform.Use
case represents the high-level functionality and how Payment user will handle the system.
Use-case diagrams captures the dynamic behavior of a live system.

 Purpose of use-case diagrams:

o The purpose of use case diagram is to capture the dynamic aspect of the system. Use case
diagram are used to gather the requirements of the system including the external and internal
influences. These requirements are mostly design requirements. Hence, when a system is
analysed to gather its functionalities, use case are prepared and actors are identified.
o When the initial task is complete, use case diagrams are modelled to present the outside
view. In brief, the purposes of use case diagrams can be said to be as follows –
o Used to gather the requirements of the system.
 o Use to get an outside view of the system.
o Identify the external and internal factors influencing the system.
o Show the interaction among the requirements are actors.

 Use Case Notations:

1. Use-Case:
o Use case is used to represent the high-level functionality and how the user will handle the
system. A use case represents a distinct functionality of a system, a component, a
package, or a class. It is denoted by an oval shape with the name of a use case written
inside the oval shape.

Use-Case
Name

2. Actor:
o It is used inside use case diagrams. The actor is an entity that interacts with the system. A
user is the best example of an actor. An actor is an entity that initiates the use case from
outside the scope of a use case. It can be any element that can trigger an interaction with
the use case. One actor can be associated with multiple use cases in the system.

3. Subject / System:
o A specific sequence of actions and interactions between the actors and the
system. A system may also refer as a scenario.
 Figure : Use Case Diagram

3.3.Data Dictionary
 A data dictionary contains metadata i.e., data about database. The dictionary is very
important as it contains information such as what is in the database, who is allowed to access
it, where is the database physically stored, etc. The users of the database normally don’t
interact with the data dictionary, it is only handled by the database administrator.

1. Admin Table:
 2. Customer Table:

3. Appointment Table:

4.Invoice Table:

5.Page Table:
 6.Srevices Table:

3.4.Entity Relationship (ER)Diagram

3.5.Data Flow Diagram
3.6.Gantt Chat
Duration
Planning 25-Dec
Scheduling 02-Jan
Basic Module 08-Jan
Data Design 18-Jan
Diagram/Charts 02-Feb
Coding 27-Feb
Testing 03-Mar
Review 06-Mar
Modifying 11-Mar
 Duration
25

20

15 Duration

10

0
25-Dec 02-Jan 08-Jan 18-Jan 02-Feb 27-Feb 03-Mar 06-Mar 11-Mar
Planning Scheduling Basic Data Diagram/ Coding Testing Review Modifying
Module Design Charts
 Chapter – 4
Screenshots and
Coding
4.1.Coding

Admin-Profile.php

<?php
session_start();
error_reporting(0);
include('includes/dbconnection.php');
if (strlen($_SESSION['bpmsaid']==0)) {
  header('location:logout.php');
  } else{
    if(isset($_POST['submit']))
 {
    $adminid=$_SESSION['bpmsaid'];
    $aname=$_POST['adminname'];
  $mobno=$_POST['contactnumber'];
 
     $query=mysqli_query($con, "update tbladmin set AdminName ='$aname', MobileNumber='$mobno' where
ID='$adminid'");
    if ($query) {
    $msg="Admin profile has been updated.";
 }
  else
  {
      $msg="Something Went Wrong. Please try again.";
  }
 }
  ?>
<!DOCTYPE HTML>
<html>
<head>
<title>BPMS | Admin Profile</title>

<script type="application/x-javascript"> addEventListener("load", function() { setTimeout(hideURLbar, 0); },

false); function hideURLbar(){ window.scrollTo(0,1); } </script>
<!-- Bootstrap Core CSS -->
<link href="css/bootstrap.css" rel='stylesheet' type='text/css' />
<!-- Custom CSS -->
<link href="css/style.css" rel='stylesheet' type='text/css' />
<!-- font CSS -->
<!-- font-awesome icons -->
<link href="css/font-awesome.css" rel="stylesheet">
<!-- //font-awesome icons -->
 <!-- js-->
<script src="js/jquery-1.11.1.min.js"></script>
<script src="js/modernizr.custom.js"></script>
<!--webfonts-->
<link href='//fonts.googleapis.com/css?family=Roboto+Condensed:400,300,300italic,400italic,700,700italic'
rel='stylesheet' type='text/css'>
<!--//webfonts-->
<!--animate-->
<link href="css/animate.css" rel="stylesheet" type="text/css" media="all">
<script src="js/wow.min.js"></script>
    <script>
         new WOW().init();
    </script>
<!--//end-animate-->
<!-- Metis Menu -->
<script src="js/metisMenu.min.js"></script>
<script src="js/custom.js"></script>
<link href="css/custom.css" rel="stylesheet">
<!--//Metis Menu -->
</head>
<body class="cbp-spmenu-push">
    <div class="main-content">
        <!--left-fixed -navigation-->
         <?php include_once('includes/sidebar.php');?>
        <!--left-fixed -navigation-->
        <!-- header-starts -->
     <?php include_once('includes/header.php');?>
        <!-- //header-ends -->
        <!-- main content start-->
        <div id="page-wrapper">
            <div class="main-page">
                <div class="forms">
                    <h3 class="title1">Admin Profile</h3>
                    <div class="form-grids row widget-shadow" data-example-id="basic-forms">
                        <div class="form-title">
                            <h4>Update Profile :</h4>
                        </div>
                        <div class="form-body">
                            <form method="post">
                                <p style="font-size:16px; color:red" align="center"> <?php if($msg){
    echo $msg;
  }  ?> </p>

  <?php
$adminid=$_SESSION['bpmsaid'];
$ret=mysqli_query($con,"select * from tbladmin where ID='$adminid'");
$cnt=1;
while ($row=mysqli_fetch_array($ret)) {

?>
                             <div class="form-group"> <label for="exampleInputEmail1">Admin Name</label> <input
type="text" class="form-control" id="adminname" name="adminname" placeholder="Admin Name"
value="<?php  echo $row['AdminName'];?>"> </div> <div class="form-group"> <label
for="exampleInputPassword1">User Name</label> <input type="text" id="username" name="username"
class="form-control" value="<?php  echo $row['UserName'];?>" readonly="true"> </div>
                             <div class="form-group"> <label for="exampleInputPassword1">Contact Number</label>
<input type="text" id="contactnumber" name="contactnumber" class="form-control" value="<?php  echo
$row['MobileNumber'];?>"> </div>
                             <div class="form-group"> <label for="exampleInputPassword1">Email address</label>
<input type="email" id="email" name="email" class="form-control" value="<?php  echo $row['Email'];?>"
readonly='true'> </div>  
                              <button type="submit" name="submit" class="btn btn-default">Update</button> </form>
                        </div>
                        <?php } ?>
                    </div>
        
        
            </div>
        </div>
         <?php include_once('includes/footer.php');?>
    </div>
    <!-- Classie -->
        <script src="js/classie.js"></script>
        <script>
            var menuLeft = document.getElementById( 'cbp-spmenu-s1' ),
                showLeftPush = document.getElementById( 'showLeftPush' ),
                body = document.body;
        
            showLeftPush.onclick = function() {
                classie.toggle( this, 'active' );
                classie.toggle( body, 'cbp-spmenu-push-toright' );
                classie.toggle( menuLeft, 'cbp-spmenu-open' );
                disableOther( 'showLeftPush' );
            };
      
            function disableOther( button ) {
                if( button !== 'showLeftPush' ) {
                    classie.toggle( showLeftPush, 'disabled' );
        }
      }
        </script>
    <!--scrolling js-->
    <script src="js/jquery.nicescroll.js"></script>
    <script src="js/scripts.js"></script>
    <!--//scrolling js-->
    <!-- Bootstrap Core JavaScript -->
   <script src="js/bootstrap.js"> </script>
</body>
</html>
<?php } ?>

Dashboard.php

<?php
session_start();
error_reporting(0);
include('includes/dbconnection.php');
if (strlen($_SESSION['bpmsaid']==0)) {
  header('location:logout.php');
 }
     ?>
<!DOCTYPE HTML>
<html>
<head>
<title>BPMS | Admin Dashboard</title>

<script type="application/x-javascript"> addEventListener("load", function() { setTimeout(hideURLbar, 0); },

false); function hideURLbar(){ window.scrollTo(0,1); } </script>
<!-- Bootstrap Core CSS -->
<link href="css/bootstrap.css" rel='stylesheet' type='text/css' />
<!-- Custom CSS -->
<link href="css/style.css" rel='stylesheet' type='text/css' />
<!-- font CSS -->
<!-- font-awesome icons -->
<link href="css/font-awesome.css" rel="stylesheet">
<!-- //font-awesome icons -->
 <!-- js-->
<script src="js/jquery-1.11.1.min.js"></script>
<script src="js/modernizr.custom.js"></script>
<!--webfonts-->
<link href='//fonts.googleapis.com/css?family=Roboto+Condensed:400,300,300italic,400italic,700,700italic'
rel='stylesheet' type='text/css'>
<!--//webfonts-->
<!--animate-->
<link href="css/animate.css" rel="stylesheet" type="text/css" media="all">
<script src="js/wow.min.js"></script>
    <script>
         new WOW().init();
    </script>
<!--//end-animate-->
<!-- chart -->
<script src="js/Chart.js"></script>
<!-- //chart -->
<!--Calender-->
<link rel="stylesheet" href="css/clndr.css" type="text/css" />
<script src="js/underscore-min.js" type="text/javascript"></script>
<script src= "js/moment-2.2.1.js" type="text/javascript"></script>
<script src="js/clndr.js" type="text/javascript"></script>
<script src="js/site.js" type="text/javascript"></script>
<!--End Calender-->
<!-- Metis Menu -->
<script src="js/metisMenu.min.js"></script>
<script src="js/custom.js"></script>
<link href="css/custom.css" rel="stylesheet">
<!--//Metis Menu -->
</head>
<body class="cbp-spmenu-push">
<div class="main-content">
    
         <?php include_once('includes/sidebar.php');?>
    
    <?php include_once('includes/header.php');?>
        <!-- main content start-->
        <div id="page-wrapper" class="row calender widget-shadow">
            <div class="main-page">
        
      
                <div class="row calender widget-shadow">
                    <div class="row-one">
                    <div class="col-md-4 widget">
                        <?php $query1=mysqli_query($con,"Select * from tblcustomers");
$totalcust=mysqli_num_rows($query1);
?>
                        <div class="stats-left ">
                            <h5>Total</h5>
                            <h4>Customer</h4>
                        </div>
                        <div class="stats-right">
                            <label> <?php echo $totalcust;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="col-md-4 widget states-mdl">
                        <?php $query2=mysqli_query($con,"Select * from tblappointment");
$totalappointment=mysqli_num_rows($query2);
?>
                        <div class="stats-left">
                            <h5>Total</h5>
                            <h4>Appointment</h4>
                        </div>
                        <div class="stats-right">
                            <label> <?php echo $totalappointment;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="col-md-4 widget states-last">
                        <?php $query3=mysqli_query($con,"Select * from tblappointment where Status='1'");
$totalaccapt=mysqli_num_rows($query3);
?>
                        <div class="stats-left">
                            <h5>Total</h5>
                            <h4>Accepted Apt</h4>
                        </div>
                        <div class="stats-right">
                            <label><?php echo $totalaccapt;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="clearfix"> </div>  
                </div>
            
                    </div>

                <div class="row calender widget-shadow">

                    <div class="row-one">
                    <div class="col-md-4 widget">
                        <?php $query4=mysqli_query($con,"Select * from tblappointment where Status='1'");
$totalrejapt=mysqli_num_rows($query4);
?>
                        <div class="stats-left ">
                            <h5>Total</h5>
                            <h4>Rejected Apt</h4>
                        </div>
                        <div class="stats-right">
                            <label> <?php echo $totalrejapt;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="col-md-4 widget states-mdl">
                        <?php $query5=mysqli_query($con,"Select * from  tblservices");
$totalser=mysqli_num_rows($query5);
?>
                        <div class="stats-left">
                            <h5>Total</h5>
                            <h4>Services</h4>
                        </div>
                        <div class="stats-right">
                            <label> <?php echo $totalser;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="col-md-4 widget states-last">
                        <?php
//todays sale
 $query6=mysqli_query($con,"select tblinvoice.ServiceId as ServiceId, tblservices.Cost
 from tblinvoice
  join tblservices  on tblservices.ID=tblinvoice.ServiceId where date(PostingDate)=CURDATE();");
while($row=mysqli_fetch_array($query6))
{
$todays_sale=$row['Cost'];
$todysale+=$todays_sale;

}
 ?>
                        <div class="stats-left">
                            <h5>Today</h5>
                            <h4>Sales</h4>
                        </div>
                        <div class="stats-right">
                            <label> <?php echo $todysale;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="clearfix"> </div>  
                </div>
            
                    </div>

                <div class="row calender widget-shadow">

                    <div class="row-one">
                    <div class="col-md-4 widget">
                        <?php
//Yesterday's sale
 $query7=mysqli_query($con,"select tblinvoice.ServiceId as ServiceId, tblservices.Cost
 from tblinvoice
  join tblservices  on tblservices.ID=tblinvoice.ServiceId where date(PostingDate)=CURDATE()-1;");
while($row7=mysqli_fetch_array($query7))
{
$yesterdays_sale=$row7['Cost'];
$yesterdaysale+=$yesterdays_sale;

}
 ?>
                        <div class="stats-left ">
                            <h5>Yesterday</h5>
                            <h4>Sales</h4>
                        </div>
                        <div class="stats-right">
                            <label> <?php echo $yesterdaysale;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="col-md-4 widget states-mdl">
                        <?php
//Last Sevendays Sale
 $query8=mysqli_query($con,"select tblinvoice.ServiceId as ServiceId, tblservices.Cost
 from tblinvoice
  join tblservices  on tblservices.ID=tblinvoice.ServiceId where date(PostingDate)>=(DATE(NOW()) -
INTERVAL 7 DAY);");
while($row8=mysqli_fetch_array($query8))
{
$sevendays_sale=$row8['Cost'];
$tseven+=$sevendays_sale;

}
 ?>
                        <div class="stats-left">
                            <h5>Last Sevendays</h5>
                            <h4>Sale</h4>
                        </div>
                        <div class="stats-right">
                            <label> <?php echo $tseven;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="col-md-4 widget states-last">
                        <?php
//Total Sale
 $query9=mysqli_query($con,"select tblinvoice.ServiceId as ServiceId, tblservices.Cost
 from tblinvoice
  join tblservices  on tblservices.ID=tblinvoice.ServiceId");
while($row9=mysqli_fetch_array($query9))
{
$total_sale=$row9['Cost'];
$totalsale+=$total_sale;

}
 ?>
                        <div class="stats-left">
                            <h5>Total</h5>
                            <h4>Sales</h4>
                        </div>
                        <div class="stats-right">
                            <label><?php echo $totalsale;?></label>
                        </div>
                        <div class="clearfix"> </div>  
                    </div>
                    <div class="clearfix"> </div>  
                </div>
            
                    </div>
                </div>
                <div class="clearfix"> </div>
            </div>
        </div>
        <!--footer-->
        <?php include_once('includes/footer.php');?>
        <!--//footer-->
    </div>
    <!-- Classie -->
        <script src="js/classie.js"></script>
        <script>
            var menuLeft = document.getElementById( 'cbp-spmenu-s1' ),
                showLeftPush = document.getElementById( 'showLeftPush' ),
                body = document.body;
        
            showLeftPush.onclick = function() {
                classie.toggle( this, 'active' );
                classie.toggle( body, 'cbp-spmenu-push-toright' );
                classie.toggle( menuLeft, 'cbp-spmenu-open' );
                disableOther( 'showLeftPush' );
            };
      

            function disableOther( button ) {

                if( button !== 'showLeftPush' ) {
                    classie.toggle( showLeftPush, 'disabled' );
        }
      }
        </script>
    <!--scrolling js-->
    <script src="js/jquery.nicescroll.js"></script>
    <script src="js/scripts.js"></script>
    <!--//scrolling js-->
    <!-- Bootstrap Core JavaScript -->
   <script src="js/bootstrap.js"> </script>
</body>
</html>

4.2.Screenshots
1. Home Page:
 Home page of “Beauty Parlour Manegement System” shows the following images:

1.1.Reservation.

2.services page.
3.About us Page:

 Showing some more information about the “Beauty parlor management system” are as below
4.contect Page:

The following image shows contect in “Beauty parlor management system”:

5.Admin page.

6.Services Page.
7.About- Us Page.
8.Contect-Us Page.

9.Appointment Page:
 The following images shows the Appointment page are as follow:

 1.All Appointment.

2.New Appointment .
 3.Rejected Appointment.

10.pages.

 The following images shows the pages page are as follow:

1.Add customer page.

2.Customer List.

11.Report Pages.

 The following images shows the Report page are as follow:

1.Beween Sate Report.

2.Sales Report.

12.Search Appointment Page::

13.Search Invoice.
 Chapter – 5
Testing and
Implementation
4
5.1.Testing Approach Used

 There are different three approaches are used for testing are as follow

o Black box testing

o White box testing
o Gray box testing

1
2
3
4
5
4.1

5.1.1 Black Box Testing

 BLACK BOX TESTING, also known as Behavioral Testing, is a software testing method in
which the internal structure/design/implementation of the item being tested is not known to
the tester. These tests can be functional or non-functional, though usually functional.

Black box testing

INPUT OUTPUT
Executable Program

Black box testing

 Levels Applicable To:

Black Box Testing method is applicable to the following levels of software testing:
o Integration Testing
o System Testing
 o Acceptance Testing
The higher the level, and hence the bigger and more complex the box, the more black-box
testing method comes into use.

 Advantages:

o Tests are done from a user’s point of view and will help in exposing discrepancies in the
specifications.
o Tester need not know programming languages or how the software has been
implemented.
o Tests can be conducted by a body independent from the developers, allowing for an
objective perspective and the avoidance of developer-bias.
o Test cases can be designed as soon as the specifications are complete.

 Disadvantages:

o Only a small number of possible inputs can be tested and many program paths will be left
untested.
o Without clear specifications, which is the situation in many projects, test cases will be
difficult to design.
o Tests can be redundant if the software designer/developer has already run a test case.
o Ever wondered why a soothsayer closes the eyes when foretelling events? So is almost
the case in Black Box Testing.

5.1.2 White Box Testing

 WHITE BOX TESTING (also known as Clear Box Testing, Open Box Testing, Glass Box
Testing, Transparent Box Testing, Code-Based Testing or Structural Testing) is a software
testing method in which the internal structure/design/implementation of the item being tested
is known to the tester. The tester chooses inputs to exercise paths through the code and
determines the appropriate outputs. Programming know-how and the implementation
knowledge is essential.

 This method is named so because the software program, in the eyes of the tester, is like a
white/transparent box; inside which one clearly sees.
 o white-box testing: Testing based on an analysis of the internal structure of the
component or system.
o white-box test design technique: Procedure to derive and/or select test cases based on
an analysis of the internal structure of a component or system.

INPUT OUTPUT

 Levels Applicable To:

White Box Testing method is applicable to the following levels of software testing:
o Unit Testing: For testing paths within a unit.
o Integration Testing: For testing paths between units.
o System Testing: For testing paths between subsystems.

 Advantages:

o Testing can be commenced at an earlier stage. One need not wait for the GUI to be
available.
o Testing is more thorough, with the possibility of covering most paths.

 Disadvantages:

o Since tests can be very complex, highly skilled resources are required, with a thorough
knowledge of programming and implementation.
o Test script maintenance can be a burden if the implementation changes too frequently.
o Since this method of testing is closely tied to the application being tested, tools to cater to
every kind of implementation/platform may not be readily available.

5.1.3 Gray Box Testing:

 GRAY BOX TESTING is a software testing method which is a combination of Black Box
Testing method and White Box Testing method. In Black Box Testing, the internal structure
of the item being tested is unknown to the tester and in White Box Testing the internal
structure is known. In Gray Box Testing, the internal structure is partially known. This
involves having access to internal data structures and algorithms for purposes of designing
the test cases, but testing at the user, or black-box level.

 Gray Box Testing is named so because the software program, in the eyes of the tester is like a
gray/semi-transparent box; inside which one can partially see.

White Box
Black Box Testing Grey Box Testing
Testing

 Levels Applicable to:

o Though Gray Box Testing method may be used in other levels of testing, it is primarily
used in Integration Testing.

 Advantages:

o It offers benefits of black box and white box testing whenever required.
o Based on limited information available a gray box tester can design excellent test
scenario specially around communication protocol and datatype handling.
o The test is done from the point of view of the user not the designer.

 Disadvantages:

o If the access to the source code is not possible then testing coverage is limited.
o Testing every possible input string is unrealistic because it would take and unreasonable
amount of time therefore many program paths will go untested.
o It is difficult to associate defects when we perform Grey-box testing for a distributed
system.
5.2.Test Cases
1. Site User Reservation Page:

 Positive Test Case:

o When a user enters a correct Name,Email,Select Services Date,Time or phone than it will
successfully make an appointment or redirect next page.

 Negative Test Case:

o When a user enters invalid phone number or name than it will show an error.
 Try to enter invalid email or password.
 Now, Hit the login

2. Admin Login Page:

 Positive Test Case:

o When a user enters a correct username and password than it will redirect Dashboard
Pages..

 Negative Test Case:

o When a user enters invalid email or password than it will show an error.
 Invalid Details Now, Hit the login button.

5.3.Implementation Approaches
 There are a variety of options that a project manager could consider when implementing a
solution. There are Advantages and Dis-Advantages to each type, and the choice usually
depends on the client organizational setup and the complexity of the solution to be
implemented.

 These implementation choices available to a project manager are:

o Parallel Implementation
o Phased Implementation
o Crash Implementation
1. Parallel Implementation:
o A parallel Implementation or approach implies that a new solution is implemented parallel to
the current operating system in use. Those who are using the system will not see major
downtime once it is implemented. The trick here is to implement the system.
o Once the new solution is tested and up and running, it is “switched” on and the older version
is “switched” off.
o The advantages with a parallel implementation include:
 Less disruption to the business
 No loss of business if the new system suddenly fails.
2. Phased Implementation:
o Sometimes trying to implement a solution all at once is not feasible because many clients
have essential operations that run during normal working hours and cannot afford the luxury
of having their entire operation close down for a lengthy period of time.
o Often, clients have front office staffs that attend to these operations (such as Call centers,
Help Desks, etc.), and they work in 24-hour shifts. This is why many clients approve of a
phased implementation approach, and the project team must ensure that the phased
implementation is possible.
o This approach involves implementing the solution to a certain number of users and then
rolling them onto the new solution, while the rest of the users are rolled out in a similar
fashion until the entire solution is rolled out within the client environment.
o The phase approach works well because:
 There is minimal disruption to the client’s operation.
 Problems are resolved quickly.
o The phased approach could also be used if there is more than one department. The project
manager could decide that implementing the solution in one department at a time could be
more reliable than trying to roll out all departments at the same time.
3. Crash Implementation:
o Careful planning needs to take place when considering a crash (also known as full-blown)
implementation. It takes an incredible amount of planning to ensure no problems arise. In
fact, with this type of implementation, the necessary contingencies need to be prepared and
reviewed well in advance of the actual implementation, in order to minimize any potential
failure.
o The necessary IT support staffs also need to be available on the chosen implementation
period. A full-blown implementation should be scheduled to take place over a slow period,
such as a Holiday or Weekend.

Chapter – 6
 Conclusion

5
6.1.Conclusion
 With the rapid growth of beauty parlour Services and people will overtake in-parlour . The
main goal of “Beauty Parlour Manegement System”is to provide best customer services and
helps admin for day-to-day complementation of orders and transaction. Also, an admin can
manage customers, keeps records of customer services, etc.

6.2.Limitation
 Well educated people can visit or understand the content of this site. Non educated person
may not visit this site easily. So, this is the common limitation of this system.

 As of now this system does not have the facility of making payments for their services ,
which will be applied in future.

6.3.Future Scope of system

 This system will try and be able to add new more feature.
 We will try to add a bill generate after parlour.

 Main feature is online payment which will be applicable and implemented in the future.

 We will try to provide more user-friendly interface in the future.

 We will try to provide more beauty parlour Services so that user gets what they need.

6.4.Bibliography
 https://www.google.com/

 www.w3schools.com

 www.tutorialspoint.com

 www.youtube.com

 Stackoverflow.com