ONLINE HOSPITAL MANAGEMENT SYSTEM

A MINOR PROJECT REPORT

Submitted in Partial Fulfillment of the requirement for the Award of Diploma

TO

COMPUTER SCIENCE AND ENGINEERING

By
STUDENT ONE (1902200026)
STUDENT TWO ()

Under the Esteemed Guidance of

[Ajay Nautiyal]
Asst. Professor

Department of Computer Science and Engineering

DEPARTEMENT OF COMPUTER SCIENCE AND ENGINEER

UTTARANCHAL COLLEGE OF POLYTECHNIC
(An Autonomous Institution)
UTTRANCHAL UNIVERSITY ,DEHRADUN
2019-2021
 ACKNOWLEGEMENT

There are many people who helped directly or indirectly on the successful completion of my
mini project.

I would like to express my deepest appreciation to everyone who helped me in the completion
of’ the report. Without their support I wouldn’t able to complete my project.
Furthermore I would also thanks the Principle of Polytechnice Dr. Sanjeev Kumar Shah for
giving me this golden opportunity or making this wonderful project. Also I would like to
thank my project mentor and assistance professor Ajay Nautiyal. From the starting to end
they helped me in every aspects, not only I completed this project but also learn a lot about
my topic and research works.
Finally, I am very much indebted to my parents for moral support and encouragement to
achieve goals. I have no words to express my gratitude and still I am very thankful to my
parents who have shown me this world and for every support they gave me.
Swati Mishra
Shivani Gusain
Polytechnice
V Sem

CERTIFICATE OF ORIGINALITY

This is to certify that the project entitled “online hospital management system” by Swati
Mishra Shiavni gusain has been submitted in the partial fulfillment of the requirements for the
award of the diploma of polytechnice from Uttaranchal University, Dehradun.The results
embodied in this project have not been submitted to any other University or Institution for the
record of any degree.
 Mentor:
Ajay Nautiyal
Asst. Professor

DECLARATION

I hereby declare that the project report entitled Online hospital management system

submitted by Swati Mishra and Shivani Gusain to Uttaranchal Institute of management. The
project was done under the Guidance of Ajay Nautiyal. I further declare that the work
reported in this project has Not been submitted and will not be submitted, either in part or in
full, for the award of any other degree or diploma in this university or any other university or
institute.
 Swati Mishra

Shivani Gusain

polytechnic v sem

TABLE OF CONTENT
1. INTRODUCTION…………………………………………………………03

2. OBJECTIVE………………………………………………………………..04

3.System Analysis……………………………………………………………05

a. Problem Identification……………………………………………...07

b. Proposed System……………………………………………………08

3. Feasibility Report……………………………………………………………10

a. Technical Feasibility…………………………………………………12

b. Operational Feasibility……………………………………………….14

c. Economical Feasibility………………………………………………..15

4. Project Planning and Scheduling……………………………………………...17

a. Gantt Chart……………………………………………………………….18

b. Pert Chart…………………………………………………………………20
 c. Software Requirement Specification (SRS)…………………………..….. 21

d. Tools Used……………………………………………………………….22

e. Flow Chart………………………………………………………………..23

f. ER Diagram………………………………………………………………24

6. REPORTS TO BE GENERATED…………………………………………..25

7.SYSTEM SECURITY AND MEASURES………………………………….26

8. TESTING……………………………………………………………………..27

9.FUTURE SCOPE OF THE PROJECT………………………………………27

10.APPENDICES………………………………………………………………..28

10.1) SNAPSHOTS……………………………………………………….

INTRODUCTION:

1.1 ABSTRACT

Hospital Management System is an organized computerized system designed and programmed to

deal with day to day operations and management of the hospital activities. The program can look
after inpatients, outpatients, records, database treatments, status illness, billings in the pharmacy and
labs. It also maintains hospital information such as ward id, doctors in charge and department
administering. The major problem for the patient nowadays to get report after consultation , many
hospital managing reports in their system but it's not available to the patient when he / she is
outside. In this project we are going to provide the extra facility to store the report in the database
and make available from anywhere in the world.

1.2 Introduction:
The project Hospital Management system includes registration of patients, storing their details into
the system, and also computerized billing in the pharmacy, and labs. The software has the facility to
give a unique id for every patient and stores the details of every patient and the staff automatically. It
includes a search facility to know the current status of each room. User can search availability of a
doctor and the details of a patient using the id.

The Hospital Management System can be entered using a username and password. It is accessible
either by an administrator or receptionist. 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
makes the data processing very fast.

Hospital Management System is powerful, flexible, and easy to use and is designed and developed to
deliver real conceivable benefits to hospitals.
Hospital Management System is designed for multispecialty hospitals, to cover a wide range of
hospital administration and management processes. It is an integrated end-to end Hospital
Management System that provides relevant information across the hospital to support effective
decision making for patient care, hospital administration and critical financial accounting, in a
seamless flow.
Hospital Management System is a software product suite designed to improve the quality and
management of hospital management in the areas of clinical process analysis and activity-based
costing. Hospital Management System enables you to develop your organization and improve its
effectiveness and quality of work. Managing the key processes efficiently is critical to the success of
the hospital helps you manage your processes

IDENTIFICATION OF NEED

1. Existing System.

In hospital management System, presently all Patient and staff management operations are
being done manually. Various books and Registers are maintained for entries about partients and staff
enquiry, registration and fess submission. Final report preparation is very cumbersome and time consuming,
as even for a single record, several books have to be preferred, all immediate updating ,validation and
reporting is just too large.
Hospitals currently use a manual system for the management and maintenance of critical information.
The current system requires numerous paper forms, with data stores spread throughout the hospital
management infrastructure. Often information (on forms) is incomplete, or does not follow management
standards. Forms are often lost in transit between departments requiring a comprehensive auditing process to
ensure that no vital information is lost. Multiple copies of the same information exist in the hospital and may
lead to inconsistencies in data in various data stores.

2. Proposed System
The Hospital Management System (HMS) is designed for Any Hospital to replace their existing
manual, paper based system. The new system is to control the following information; patient information,
room availability, staff and operating room schedules, and patient invoices. These services are to be provided
in an efficient, cost effective manner, with the goal of reducing the time and resources currently required for
such tasks.

3. Objective of the System

Hospitals currently use a manual system for the management and maintenance of critical information.
The current system requires numerous paper forms, with data stores spread throughout the hospital
management infrastructure. Often information (on forms) is incomplete, or does not follow management
standards. Forms are often lost in transit between departments requiring a comprehensive auditing process to
ensure that no vital information is lost. Multiple copies of the same information exist in the hospital and may
lead to inconsistencies in data in various data stores.
A significant part of the operation of any hospital involves the acquisition, management and timely
retrieval of great volumes of information. This information typically involves; patient personal information
and medical history, staff information, room and ward scheduling, staff scheduling, operating theater
scheduling and various facilities waiting lists. All of this information must be managed in an efficient and
cost wise fashion so that an institution's resources may be effectively utilized HMS will automate the
management of the hospital making it more efficient and error free. It aims at standardizing data,
consolidating data ensuring data integrity and reducing inconsistencies.
.

System Specifications

Hardware Requirements:-

 Laptop or desktop with supported internet connection .

 Intel Processor 2.0 GHz or above
 512 KB Cache Memory
 2GB RAM or more.
 Microsoft Compatible 101 or more Key Board

Software Requirements: -
 Operating System: Windows XP or Linux
 Programming language: Html CSS JS
 Web-Technology: Html CSS JS PHP SQL
 Front-End: HTML CSS JS
  Back-End: Sql Server 2000
 Web Server: XAMPP (MYSQL, Apache, PHP)

FEASIBILITY STUDY

The applications of technology to the Hospital Management allow producers to supply new and flexible
services that are cost-competitive with conventional mass, standardized and rigidly packaged options.
Technology gives Institute the flexibility to react to Patient demands.

Economical Feasibility
Our Software’s Hospital Management System is to provide properties of all sizes with an affordable,
effective, user-friendly Hospital Management System. The products are designed to control costs and
resources, therefore improving long-term profitability and efficiency.
Our software is an affordable Hospital Management System software package that caters to small to medium-
sized properties. It effectively manages Patient and staff Records, Registration Process and Staff records. A
reliable answer to tracking availability and property statistics.

Operational Feasibility

Project is not rejected simply because of operational unfeasibility but such consideration is likely to critically
affect the nature and scope of the eventual recommendations. As we know the users have very little
knowledge of computer, a user-friendly environment will be required. The system should be GUI based. This
goal can be met by using the Visual Basic as Front end and Oracle as Back end. A little consideration and
training may enable the user to handle this package.
For Hospital Management System apart from other facts as per operational feasibility is concerned we need to
see to it that the system to be developed should be user-friendly so that staff personnel’s who are not
computer literate find it easy to work with. As the office staff does most of the work, so they might have to be
trained.

1.2 Problem Introduction:

Lack of immediate retrievals: -
The information is very difficult to retrieve and to find particular information like- E.g. - To find out about
the patient’s history, the user has to go through various registers. This results in in convenience and wastage
of time.

Lack of immediate information storage: -

The information generated by various transactions takes time and efforts to be stored at right place.

Lack of prompt updating: -

Various changes to information like patient details or immunization details of child are difficult to make as
paper work is involved.

Error prone manual calculation: -

Manual calculations are error prone and take a lot of time this may result in incorrect information. For
example calculation of patient’s bill based on various treatments.

Preparation of accurate and prompt reports: -

This becomes a difficult task as information is difficult to collect from various register.

Objective: -
1) Define hospital
2) Recording information about the Patients that come.
3) Generating bills.
4) Recording information related to diagnosis given to Patients.
 5) Keeping record of the Immunization provided to children/patients.
6) Keeping information about various diseases and medicines available to cure them.

These are the various jobs that need to be done in a Hospital by the operational staff and Doctors. All these
works are done on papers.

Scope of the Project:-

1) Information about Patients is done by just writing the Patients name, age and gender. Whenever the
Patient comes up his information is stored freshly.
2) Bills are generated by recording price for each facility provided to Patient on a separate sheet and at
last they all are summed up.
3) Diagnosis information to patients is generally recorded on the document, which contains Patient
information. It is destroyed after some time period to decrease the paper load in the office.
4) Immunization records of children are maintained in pre-formatted sheets, which are kept in a file.
5) Information about various diseases is not kept as any document. Doctors themselves do this job by
remembering various medicines.

1.3 MODULES:

 Admin module

i. Dashboard: In this section, admin can view the Patients, Doctors, Appointments and
New queries.
ii. Doctors: In this section, admin can add doctor’s specialization and mange doctors
(Add/Update).
iii. Users: In this section, admin can view users’ detail (who take online appointment)
and also have right to delete irrelevant user.
iv. Patients: In this section, admin can view patient’s details.
v. Appointment History: In this section, admin can view appointment history.
vi. Contact us Queries: In this section, admin can view queries which are send by users.
vii. Doctor Session Logs: In this section, admin can see login and logout time of doctor.
viii. User Session Logs: In this section, admin can see login and logout time of
user.
ix. Reports: In this section, admin can view reports of patients in particular periods.
x. 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)
i. Dashboard: In this section, patients can view the his/her profile, Appointments and
Book Appointment.
 ii. Book Appointment: In this section, Patient can book his/her appointment. iii.
Appointment History: In this section, Patients can see his/her own appointment
history. iv. 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
i. Dashboard: In this section, doctor can view his/her own profile and online
appointments.
ii. Appointment History: In this section, Doctor can see patient’s appointment
history.
iii. Patients: In this section, doctor can manage patients (Add/Update).
iv. 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.

Processing Environment

 Software Requirements

Minimum software requirements needed to run the system efficiently.

i. Microsoft Windows 7/8/10 or Linux. ii. Browser

iii. XAMPP (MySQL, Apache, PHP)
iv. Sublime or any other text editor

 Hardware Requirements

Minimum software requirements needed to run the system efficiently.

i. Laptop or desktop with:
ii. Intel Processor 2.0 GHz or above.
iii. 2 GB RAM or more.
iv. Internet connection
v. Good amount of free memory
System Requirement Specifications:

 Functional Requirements

Dashboard (Patient):

In this section, patients can view the his/her profile, Appointments and Book Appointment. Also
Patients can update his/her profile, change the password and recover the password.

Book Appointment (Patient):

In this section, Patient can book his/her appointment.

Appointment History (Patient):

In this section, Patients can see his/her own appointment history.

Medical History (Patient):

In this section, Patients can see his/her own appointment history.

Back to Home Page or logout (Patient):

This will take the user back to the main page.
 Dashboard (Doctor):

In this section, doctor can view his/her own profile and online appointments.

Appointment History (Doctor):

In this section, Doctor can see patient’s appointment history.

Patients (Doctor):

In this section, doctor can manage patients (Add/Update).

Search (Doctor):

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.

 Non-Functional Requirements

The non-functional requirements the system should satisfy are as follows:

i. Security Issues: In this system unauthorized users cannot access the data and cannot
perform any operation, because the system does not allow them to login. So security is
provided.

ii. User Interface: The system is designed in such a way that instructions are given clearly
to navigate through the System. Warnings and error messages are provided throughout
the system.

iii. Scalability: The system is scalable in the sense, it supports large amounts of data that
can be stored and retrieved.
 DATA DICTIONARY

A data dictionary is a file or a set of files that includes a database's metadata. The data
dictionary holds records about other objects in the database, such as data ownership,
data relationships to other objects, and other data.

The data dictionary is an essential component of any relational database. Ironically,

because of its importance, it is invisible to most database users. Typically, only database
administrators interact with the data dictionary.

The data dictionary in general contains information about the following −

i. Names of all the database tables and their schemas.

ii. Details about all the tables in the database, such as their owners, their
security constraints, when they were created etc.
ii. Physical information about the tables such as where they are stored and how.
iv. Table constraints such as primary key attributes, foreign key information
etc.
v. Information about the database views that are visible.
Tables used in the database
Admin table: This table store the login details of admin.

Doctor specialization table: This table store the specializations of doctors.

Doctors table: This table store the logins and personal details of doctors.
 Doctors log table: This table store the doctor login and logout details.

Users table: This table store the user’s login and personal details.

User log table: This table store the user’s login and personal details.
Appointment table: The table store the appointment details.

tblpatient table: This table store the patient details.

tblmedicalhistory table: This table store the patient medical history.

tblcontactus table: This table store the contact us query details .

4.1 SYSTEM DESIGN:

UML Design

The Unified Modelling Language (UML) is a standard language for specifying, visualizing,
constructing, and documenting the software system and its components. It is a graphical language , which
provides a vocabulary and set of semantics and rules. The UML focuses on the conceptual and physical
representation of the system. It captures the decisions and understandings about systems that must be
constructed. It is used to understand, design, configure, maintain, and control information about the
systems.

The UML is a language for:

 Visualizing
 Specifying
  Constructing
 Documenting

Visualizing
Through UML we see or visualize an existing system and ultimately we visualize how the system is
going to be after implementation. Unless we think, we cannot implement. UML helps to visualize,
how the components of the system communicate and interact with each other.

Specifying
Specifying means building, models that are precise, unambiguous and complete UML addresses the
specification of all the important analysis design, implementation decisions that must be made in
developing and deploying a software system.

Constructing
UML models can be directly connected to a variety of programming language through mapping a
model from UML to a programming language like JAVA or C++ or VB. Forward Engineering and
Reverse Engineering is possible through UML.

Documenting
The Deliverables of a project apart from coding are some Artefacts, which are critical in controlling,
measuring and communicating about a system during its developing requirements, architecture,
desire, source code, project plans, tests, prototypes releasers, etc...

4.2 UML Approach

UML Diagram

A diagram is the graphical presentation of a set of elements, most often rendered as a connected graph of
vertices and arcs . you draw diagram to visualize a system from different perspective, so a diagram is a
projection into a system. For all but most trivial systems, a diagram represents an elided view of the elements
that make up a system. The same element may appear in all diagrams, only a few diagrams , or in no
diagrams at all. In theory, a diagram may contain any combination of things and relationships. In practice,
however, a small number of common combinations arise, which are consistent with the five most useful
views that comprise the architecture of a software-intensive system. For this reason, the UML includes nine
such diagrams:

1. Use case diagram

2. Sequence diagram
3. State chart diagram
 4. Activity diagram
5. ER diagram

Activity diagram for Admin:

Login

view patients/
doctors/user

Add/update/
Manage doctor

view /delete
patient details

view /delete
appointment
history

view /manage
queries of user

view /manage
user/ doctor login /out
time

view patients
Search patients
Activity diagram for Doctor:

Login

View /update
His profile

View /manage
Patients appointment time

View patients
Medical history

Add/update
patients

Search patients
Details

View patients
Reports / suggestions
Activity diagram for user, patients:

Login

View/update
His/her
Profile

View and book

Appointment

View own appointment

History

View/add
His own medical history

View/search

Doctor

Ask
queries

View reports
STATECHART DIAGRAMS

UML State chart Diagram

A state chart diagram shows the behavior of classes in response to external stimuli. This
diagram models the dynamic flow of control from state to state within a system.
Basic State chart Diagram Symbols and Notations

States
States represent situations during the life of an object. You can easily illustrate a state in
Smart Draw by using a rectangle with rounded corners.

Transition
A solid arrow represents the path between different states of an object. Label the transition
with the event that triggered it and the action that results from it.

Initial State
A filled circle followed by an arrow represents the object's initial state.
Learn how to rotate objects.

Final State
An arrow pointing to a filled circle nested inside another circle represents the object's final
state
Synchronization and Splitting of Control

A short heavy bar with two transitions entering it represents a synchronization of control. A
short heavy bar with two transitions leaving it represents a splitting of control that creates
multiple states.
USE CASE DIAGRAM:

1. Use case diagram consist of use cases and actors and shows the interaction between
them.
2. The main purpose is to show the interaction between the use cases and the actors.
3. To represent the system requirements from user’s perspective.
4. The use cases are the functions that are to be performed in the module.

Purpose of Use Case Diagrams

The purpose of use case diagram is to capture the dynamic aspect of a system. However,
this definition is too generic to describe the purpose, as other four diagrams (activity,
sequence, collaboration, and State chart) also have the same purpose. We will look into
some specific purpose, which will distinguish it from other four diagrams.
Use case diagrams are used to gather the requirements of a system including internal and
external influences. These requirements are mostly design requirements. Hence, when a
system is analysed to gather its functionalities, use cases are prepared and actors are
identified.
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 −
 Used to gather the requirements of a system.

• Used to get an outside view of a system.

• Identify the external and internal factors influencing the system.
• Show the interaction among the requirements are actors.
Use case diagram of our project:
Use Case Diagram Admin Sign in

Dashboard

Manage Doctor
Specialization /
Doctors

View Users

View Patients

View Appointment
History

View Appointment
History

Manage Queries

Doctors /Users
Session Logs

Generate Reports

Doctors /Users
Session LogsS
S
S
Patient Search
S
Doctor Use Case Diagram
Sign in

Dashboard

Manage
Appointment History

Manage Patient
(Add / Update
)

Add patient
History

Search Patient

Update Own
Profile

Change Password

Password Recovery
 Signup

Sign in

Dash board
h

Book Appointment

Appointment History

View Medical
History

Update Own
Profile

Change Password

Password
Recovery

Patient Use Case Diagram

Data Flow Diagram

A Data Flow Diagram (DFD) is a graphical representation of the “flow” of data through
an Information System. A data flow diagram can also be used for the visualization of
Data Processing. It is common practice for a designer to draw a context-level DFD first
which shows the interaction between the system and outside entities. This context-level
DFD is then “exploded” to show more detail of the system being modelled.

A DFD represents flow of data through a system. Data flow diagrams are commonly
used during problem analysis. It views a system as a function that transforms the input
into desired output. A DFD shows movement of data through the different
transformations or processes in the system.

Dataflow diagrams can be used to provide the end user with a physical idea of where the
data they input ultimately has an effort upon the structure of the whole system from
order to dispatch to restock how any system is developed can be determined through a
dataflow diagram. The appropriate register saved in database and maintained by
appropriate authorities.

Data Flow Diagram Notation

Function

file/database
Input/ output

Flow

DFD 0-Level

Admin

request respond

Hospital
Management System request
request

respond
respond

User Doctor
DFD 1-level Admin Side

ADMIN ADMIN D/B

Login

Appointment Appointment D/B

Management

Patient
Patient D/B
Management

Medical History
Management Medical history D/B

Doctor
Management Doctor D/B

User Log
Management
User Log D/B

User
Management User D/B
DFD 1-level User Side-Doctor

Doctor Login Doctor D/B

Appointment
Appointment D/B
Management

Patient
Patient D/B
Management

Update Profile
Doctor D/B
DFD 1-LEVEL USER SIDE-Patient

Patient
Login Patient D/B

Appointment
Appointment D/B
Management

View Profile Patient D/B

Medical
History Medical history D/B

DFD 2-Level Admin

Appointment Management

ADMIN Login Admin D/B

View
Appointment Appointment D/B

Appointment
History

Update
Appointment
 LevelAdmin
Patient Management

Add Patient

View Patient

ADMIN Update Patient Patient D/B

Delete Patient

View Patient
Report
 LeveL ADMIN
SIDE
Doctor Management

Add Doctor

View Doctor

Update Doctor Doctor D/B

ADMIN

Add
Specialization

Delete Doctor
 Level 2 ADMIN SIDE

User Log Management

ADMIN User User D/B

View Details

Login Time
User Log D/B

Logout Time
 DFD 2-Level ADMIN
SIDE
User Management

Add User

View User

User D/B
ADMIN

Update User

Delete User
DFD 2-Level USER SIDE –
DOCTOR

Appointment Management

DOCTOR Login Doctor D/B

View Profile

View Appointment D/B

Appointment

HMS Page41
DOCTOR
Patient Management

Add Patient

View Patient

Patient D/B
DOCTOR

Delete Patient

Patient Appointment D/B

Appointment
History

HMS Page42
 DOCTOR

Profile Management

DOCTOR
Login

View Profile Doctor D/B

Update Profile

Change
Password

HMS Page43
Appointment Management

PATIENT Login/Register Patient D/B

View
Appointment Appointment D/B

Book Appointment

Update
Appointment

Appointment
History

HMS Page44
Medical-History Management

PATIENT Login Patient D/B

View Profile

View Medical Medical History D/B

History

HMS Page45
Profile Management

PATIENT Login

View Profile Patient D/B

Update
Profile

Change
Password

HMS Page46
Entity Relationship Diagram (ER-Diagram):
An entity-relationship (ER) diagram is a specialized graphic that illustrates the
interrelationships between entities in a database. ER diagrams often use symbols to
represent three different types of information. Boxes are commonly used to
represent entities. Diamonds are normally used to represent relationships and ovals
are used to represents attributes.

An entity-relationship model (ERM) in software engineering is an abstract and

conceptual representation of data. Entity-relationship modelling is a relational
schema database modelling method, used to produce a type of conceptual schema
or semantic data model of a system, often of a system, often a relational database,
and its requirements in a top-down fashion.

Symbols used in this ER-Diagram:

Entity: Entity is a “thing” in the real world with an independent existence. An

entity may be an object with a physical existence such as person, car or employee.
Entity symbol is as follows.

Attributes: Attributes are the properties of entities. Attributes are represented by

means of ellipses. Every ellipse represents one attribute and is directly connected
to its entity (rectangle). Attribute symbol is as follows.

HMS Page47
Types of Attributes
1. Composite Attribute: If the attributes are composite, they are further
divided in a tree like structure. Every node is then connected to its attribute. That
is, composite attributes are represented by ellipses that are connected with an
ellipse. Attribute symbol is as follows.

2. Multivalued Attribute: These attributes are depicted by double ellipse.

Attribute symbol is as follows.

3. Derived Attribute: These attributes are depicted by dashed ellipse.

Attribute symbol is as follows.

HMS Page48
ER Diagram

TESTING –

HMS Page49
Testing is a process of executing a program with the intent of finding an error.
Testing is a crucial element of software quality assurance and presents ultimate
review of specification, design and coding.
System Testing is an important phase. Testing represents an interesting anomaly
for the software. Thus a series of testing are performed for the proposed system
before the system is ready for user acceptance testing.
A good test case is one that has a high probability of finding as undiscovered error.
A successful test is one that uncovers an undiscovered error.

Testing Objective:
Testing is a process of executing a program with the intent of finding an error. A
good test case is one that has a probability of finding a yet undiscovered error.
A successful test is one that uncovers an undiscovered error.

Testing Principles:
• All tests should be traceable to end user requirements.
• Tests should be planned long before testing begins.
• Testing should begin on a small scale and progress towards testing in
large.
• Exhaustive testing is not possible.
• To be most effective testing should be conducted by an independent third
party.

Test Case Design

HMS Page50
White Box Testing:
White box testing is a testing case design method that uses the control structure of
the procedure design to derive test cases. All independents path in a module are
exercised at least once, all logical decisions are exercised at once, execute all loops
at boundaries and within their operational bounds exercise internal data structure
to ensure their validity. Here the customer is given three chances to enter a valid
choice out of the given menu. After which the control exits the current menu.

Black Box Testing:

Black Box Testing attempts to find errors in following areas or categories,
incorrect or missing functions, interface error, errors in data structures,
performance error and initialization and termination error. Here all the input data
must match the data type to become a valid entry.

Unit Testing:
Unit testing is essentially for the verification of the code produced during the
coding phase and the goal is test the internal logic of the module/program. In the
Generic code project, the unit testing is done during coding phase of data entry
forms whether the functions are working properly or not. In this phase all the
drivers are tested they are rightly connected or not.

Integration Testing:
All the tested modules are combined into sub systems, which are then tested. The
goal is to see if the modules are properly integrated, and the emphasis being on the
testing interfaces between the modules. In the generic code integration testing is
done mainly on table creation module and insertion module.

Validation Testing:
This testing concentrates on confirming that the software is error-free in all
respects. All the specified validations are verified, and the software is subjected to
hard-core testing. It also aims at determining the degree of deviation that exists in
the software designed from the specification; they are listed out and are corrected.

WEB DEVELOPMENT TESTING:

HMS Page51
the applications that are hosted on web in which the application interfaces and
other functionalities are tested.

TESTING TECHNIQUES:
1. Functionality Technique: The below are some of the checks that are
performed but not limited to the below list:
• Verify there is no dead page or invalid redirects.
• First check all the validations on each field.
• Wrong inputs to perform negative testing.
• Verify the workflow of the system.
• Verify the data integrity.

2. Usability Testing: To verify how the application is easy to use with.

• Test the navigation and controls.
• Content checking.
• Check for user intuition
3. Interface Testing: Performed to verify the interface and the dataflow from
one system to other.
4. Compatibility Testing: Compatibility testing is performed based on the
context of the application.
• Browser compatibility
• Operating system compatibility
• Compatible to various devices like notebook, mobile, etc.

SYSTEM TESTING:

This testing is a series of different tests whose primary is to fully exercise the
computer based system. This involves

HMS Page52
Implementing the system in a simulated production environment and testing it.
Introducing errors and testing for error handling.

No. Test Case Title Description Expected Outcome Result

1 Successful User The login to the system Login should be Successful

Verification should be tried with the successful and the user
given email and password at should be able to see
the time of registration the dashboard.
2 Unsuccessful User Login to the system with a Login should fail with Successful
Verification due wrong email an error “Invalid
to wrong email username or password”

3 Unsuccessful Registration with a empty Registration halt with Successful

registration due to field an popup
a blank field “please fill out this
field”
4 Successful Email Validation of Proper Email Registration Should fail Successful
Validation while Registration is needed and display error
because further message ‘please
Communication is based on include an ‘@’ in the
Email email address”

CONCLUSION

Since we are entering details of the patients electronically in the” Hospital

Management System”, data will be secured. Using this application, we can
retrieve patient’s history with a single click. Thus processing information will

HMS Page53
be faster. It guarantees accurate maintenance of Patient details. It easily
reduces the book keeping task and thus reduces the human effort and increases
accuracy speed.

GANTT CHART
HOSPITAL MANAGEMENT SYSTEM
Start Date Duration
Task1( Analysis) 26-Aug 8
Task 2(Feasibility Study) 04-Sep 11
TASK3(Requirement Specification) 15-Sep 8

HMS Page54
TASK4(Design) 23-Sep 7
TASK5(Coding) 30-Sep 40
TASK6(Testing) 09-Nov 10
TASK7(Implementation) 19-Nov 10
TASK8(Maintenance) 29-Nov 3

92
TASK8(Maintenance)
TASK7(Implementation)
TASK6(Testing)
TASK5(Coding)
Start Date
TASK4(Design)
Duration
TASK3(RequirementSpecification)
Task 2(Feasibility Study)
Task1( Analysis)

03/Jun 23/Jul 11/Sep 31/Oct 20/Dec

HOME PAGE

HMS Page55
 PATIENT REGISTER

CONTACT US

HMS Page56
HMS Page57