HOSPITAL MANAGEMENT SYSTEM

A Project Report

Submitted in partial fulfilment of the

Requirements for the award of the Degree of

BACHELOR OF SCIENCE (COMPUTER SCIENCE)

By
NAME: ADITYA VINAY PANDEY
T.Y.BSc.(COMPUTER SCIENCE)
PRN no. 2019016401118903
Under the esteemed guidance of
Mr. VIJAY VASTAVA
Assistant Professor
Submitted for
DEPARTMENT OF COMPUTER SCIENCE
K. M. AGRAWAL COLLEGE
(Affiliated to University of Mumbai)
KALYAN, 421301
MAHARASHTRA
2021-2022
SUBMITTED TO
UNIVERSITY OF MUMBAI

1
 K.M.AGRAWAL COLLEGE OF ARTS, COMMERCE
AND SCIENCE

KALYAN

NAAC ACCREDITED B++

CERTIFICATE
This is to certify that Mr./Ms. ADITYA VINAY PANDEY Exam Seat
No has satisfactorily completed the Project on

Hospital Management System for partial fulfillment of the 3 year Full

Time Course Bachelor of Computer Science (SEM-V) of the University of Mumbai for the year 2021-
2022.

PRN No : 2019016401118903

Place : K ALYAN Date : / /

Prof. In-Charge In-Charge External Examiner Signature

Self-Finance Department

2
 PROFORMA FOR THE APPROVAL PROJECT PROPOSAL

PRN No: 2019016401118903 Roll no:15

1. Name of the Student

Aditya Vinay Pandey
2. Title of the Project
Hospital Management System
3. Name of the Guide
VIJAY VASTAVA SIR
4. Teaching experience of the Guide
18 YEAR

5. Is this your first submission? Yes No

Signature of the Student Signature of the Guide

Date: ………………… Date: …………………….

Signature of the Coordinator

Date: …………………

3
 DECLARATION

I hereby declare that the project entitled, “HOSPITAL MANAGEMENT

SYSTEM” done at K. M. Agrawal College, Kalyan, has not been in any case
duplicated to submit to any other university for the award of any degree. To
the best of my knowledge other than me, no one has submitted to any other
university. The project is done in partial Fulfillment of the requirements for
the award of degree of BACHELOR OF SCIENCE (COMPUTER
SCIENCE) to be submitted as final semester project of our curriculum.
SR. CONTENT PAGE.

NO NO

1 INTRODUCTION 6

2 GOALS AND NEEDS 9

3 REQIUREMENT ANALYSIS 11

4 SYSTEM ANALYSIS 17

5 ACD(AECHITECTURAL CONTEXT 42
DIAGRAM)

6 DESIGN PHASE 68

7 DEVELOPMENT PHASE 72

8 TESTING PHASE 78

9 CONCLUSION 87

10 BIBLOGRAPHY 89
 1. INTRODUCTION

1.1. BRIEF OVERVIEW OF HOSPITAL MANAGEMENT SYSTEM

To develop a Hospital Management system, we take care of patient

registration, drug information and concerns such as drug enquiries and
complaints.

The current manual system is slow laborious and error prone to computerize the
same for quicker efficient results and customer satisfaction

1.1.1 ADVANTAGES TO BOTH END USERS & DEVELOPERS

The system is useful in various ways as the information about the patients
who are taking the free services from the Hospital all the details are already stored
in the database , so the service is done in no time . All the information about the
drugs are also maintained in the database

1.2 GOAL AND NEED:

GOAL: With every going day the need to be where the inflow of out patient request
exceeds that which can be handled manually. Hence computerization of OP
receipt request and maintenance of the drugs through the computerization brings
better satisfaction and service oriented ness.

Quicker processing of OPNO receipt would mean better service to the patients .
It would also help in the complexity of maintaining the records manually and thus
less time is wasted on rework. Proper maintenance of the drug information timely
dispatching of the drugs from the main stores to the pharmacy and also
maintenance of daily dispatching of the drugs to the out patients from the pharmacy
to the out patients . Towards this achievement the computerization of
the Health Center will help greatly in maintaining pf proper information about the
out patients who are eligible for the free services and the patients who are not
eligible for the free services , drug information , patients records ,and daily
dispatching of the drugs to various patients .

NEED: To develop a Heath Center Management system as from manual system

to computerized system, and to take care of Records of the various departments
in the health center.The current manual system is slow laborious and error prone
to computerize the same for quicker efficient results .

1.4 GENERAL METHODOLOGY IN DEVELOPING S/W PROJECT The general

methodology in developing a system is involved in different phases, which describe
the system’s life cycle model for developing software project. The concept includes
not only forward motion but also have the possibility to return that is cycle back to
an activity previously completed. This cycle back or feedback may occur as a
result of the failure with the system to meet a performance objective or as a result
of changes in redefinition of system activities. Like most systems, the life cycle of
the computer based system also exhibits distinct phases.
Those are,
1. REQUIREMENT ANALYSIS PHASE
2. DESIGN PHASE
3. DEVELOPMENT PHASE
4. CODING PHASE
1.4.1. REQUIREMENT ANALYSIS PHASE :

This phase includes the identification of the problem, in order to identify the
problem, we have to know information about the problem, the purpose of the
evaluation for problem to be known. We have to clearly know about the client’s
requirements and the objectives of the project.

SYSTEM ANALYSIS PHASE :

Feasibility analysis involves the benefits of various approaches and the

determination of the alternative approaches a\through methods like questionnaires
and interviews etc., different data about the project is collected and the data
through out the project is represented in the form of UML Diagrams.

1.4.2 DESIGN PHASE :

S/W design is a process through which the requirements are translated into
a representation of a s/w. One of the software requirements have been analyzed
and specified, the s/w design involves three technical activities : design, coding
generation and testing. The design of the system is in modular form i.e., the s/w is
logically partitioned into components that perform specific functions and sub
functions. The design phase leads to modules that exhibit independent functional
characteristics. It even leads to interfaces that reduce the complexity of the
connections between modules and with the external environment. The design
phase is of main importance because in this activity, decisions ultimately affect the
success of s/w implementation and maintenance.

1.4.3 DEVELOPMENT PHASE:

The development phase includes choosing of a suitable s/w to solve the

particular problem given. The various facilities and the sophistication in the
selected s/w give a better development of the problem.
1.4.4 CODING PHASE :

The coding phase is for translating the design of the system produced
during the design phase into code in a given programming language, which can
be executed by a computer and which performs the computation specified by the
design.

1.4.5 TESTING PHASE :

Testing is done in various ways such as testing the algorithm, programming

code, sample data debugging is also one of following the above testing.
 2. REQUIREMENT ANALYSIS
2.1 DATA COLLECTION:

Observation of the Existing System:

In the typical Hospital Management System is developed to make all the sections
computerized . The entire process is very time consuming and involves tones of
paper work- mostly manually, which is both error prone and time consuming.

The new system would have the patients are requesting for the receipts at
the Registration office by showing the ID given to the patients that are given at
there respected departments at the university level , Just by submitting the opno
to the database the person is confirmed that the person is eligible or not . If the
person is eligible the service is provided to the person. In the Drug Store the
maintenance of the drug information that how many drugs are there in the store
and how much is dispatched to the Pharmacy house and how many are in the
main stores and what content of the drugs are to be ordered? All this information
is in the drug store. The information that how many out- patients that have visited
the health center and how many patients are In-patients this information is stored
in the Case Records, and the daily dispatching of the drugs from the pharmacy
to the patients are maintained in the Daily Records.

2.2 SYSTEM REQUIREMENT SPECIFICATION DOCUMENT

What is SRS?

Software Requirement Specification (SRS) is the starting point of the software

developing activity. As system grew more complex it became evident that the goal
of the entire system cannot be easily comprehended. Hence the need for the
requirement phase arose. The software project is initiated by the client needs. The
SRS is the means of translating the ideas of the minds of clients (the input) into a
formal document (the output of the requirement phase.)
The SRS phase consists of two basic activities:

1) Problem/Requirement Analysis:

The process is order and more nebulous of the two, deals with
understand the problem, the goal and constraints.

2) Requirement Specification:

Here, the focus is on specifying what has been found giving analysis
such as representation, specification languages and tools, and checking the
specifications are addressed during this activity.

The Requirement phase terminates with the production of the

validate SRS document. Producing the SRS document is the basic goal of
this phase.

ROLE OF SRS:

The purpose of the Software Requirement Specification is to reduce

the communication gap between the clients and the developers. Software
Requirement Specification is the medium though which the client and user
needs are accurately specified. It forms the basis of software development.
A good SRS should satisfy all the parties involved in the system.

2.3 INTRODUCTION :

2.3.1 PURPOSE :

The purpose of this document is to describe all external

requirements for The Health Center. It also describes the interfaces for the
system.
 2.3.2 SCOPE :

This document is the only one that describes the requirements of

the system. It is meant for the use by the developers , and will also by the
basis for validating the final delivered system. Any changes made to the
requirements in the future will have to go through a formal change approval
process. The developer is responsible for asking for clarifications, where
necessary, and will not make any alterations without the permission of the
client.

2.3.1 PROJECT DEFINITION

The Hospital Management System project has been divided into four
modules. They are
1. Patient Registration
2. Appointment
3. Medication

Module-One - Registration
This module consists of the following sub modules viz.,
Inserting the Records of the persons sent from the different
departments
Viewing the Records

Module-Two- Appointment
Appointment consist of 2 Module
Username authentication
Password verification
Module Three - Medication
Medication consist of 2 Module
Availability of Medicine
Tracking of Medicine

Module-Four - Case Records

This module has been divided into three sub modules. They are
In-patient Record (Student)
In-patient Record (Employee)
Out-patient Record (Student & Employees)
Software Requirements:

Platform - Windows (2000/XP) /Unix/Solaris

Software - JSDK 5.0, Ms-Access.

Hardware Requirements:

Processor - Intel celeron class Processor with 2.0 GHz

RAM - 256 MB
Hard Disk - 40 GB
Keyboard - 101 keys
Mouse - Any pointing device

Design Constraints:

This Hospital Management System require huge resources as Hundreds of the

patients will require the services instantly, quick response time are needed. The
database should also be very large and robust to maintain very huge patients and
drugs data.
PRINCIPLES OF SYSTEM ANALYSIS:

PRINCIPLES:

 Understand the problem before you begin to create the analysis model.

 Develop prototypes that enable a user to understand how human machine

interaction will occur.

 Record the origin of and the reason for every requirement.

 Use multiple views of requirements like building data, function and

behavioral models.

 Work to eliminate ambiguity

System Analysis is a separation of a substance into parts for study and their
implementation and detailed examination.

Before designing any system it is important that the nature of the business and the
way it currently operates are clearly understood. The detailed examination
provides the specific data required during designing in order to ensure that all the
client's requirements are fulfilled. The investigation or the study conducted during
the analysis phase is largely based on the feasibility study. Rather it would not be
wrong to say that the analysis and feasibility phases overlap. High-level analysis
begins during the feasibility study. Though analysis is represented as one phase
of the system development life cycle (SDLC), this is not true. Analysis begins with
system initialization and continues until its maintenance. Even after successful
implementation of the system, analysis may play its role for periodic
maintenance and up gradation of
 the system. One of the main causes of project failures is inadequate
understanding, and one of the main causes of inadequate understanding of the
requirements is the poor planning of system analysis.

Analysis requires us to recall the objectives of the project and consider following
three questions:

• What type of information is required?

• What are the constraints on the investigation?

• What are the potential problems that may make the task more difficult?

Keeping the above questions in mind and considering the survey conducted to
determine the need of the system; the total system was designed and can be
described as under:

The three major parts of the system are:

Ø Providing Information:

The system is effectively used to provide large variety of information to the

interested customer. The major purpose of the site is to easily provide access to
records of various Job seekers & users of matrimonial such as resume & profile of
boys and girls those who want to search a life partner with quick update to latest
modifications in the records. This thing is not at all possible in printed material,
which are updated only once a few weeks. It also gives information about the
general usage of the system for first time visitors. The system itself works as a
information provider for company & life partner seekers.
 Preliminary Investigation

System development, a process consisting of two major steps of system analysis

and design, start when management or sometimes system development personnel
feel that a new system or an improvement in the existing system is required. The
system development life cycle is classically thought of as the set of activities that
analysts, designers and users carry out to develop and implement an information
system. The system development life cycle consists of the following activities:
 Preliminary investigation
 Determination of system requirements
 Design of system
 Development of software
 System testing
 Implementation, evaluation, and maintenance

A request to take assistance from information system can be made for many

reasons, but in each case someone in the organisation initiates the request is

made, the first system activity the preliminary investigation begins. This

activity has three parts:

1) Request clarification
2) Feasibility study
3) Request approval

Request clarification: Many requests from employees and users in the

organisations are not clearly defined, Therefore it becomes necessary that project
request must be eximined and clarified properly before considering systems
investigation.
FEASIBILITY STUDY:

The feasibility study proposes one or more conceptual solution to the problem set
of the project. In fact, it is an evaluation of whether it is worthwhile to proceed with
project or not.

1. Evaluation of feasibility of such solutions. Such evaluation often indicates

shortcomings in the initial goals. This step is repeated as the goals are adjusted
and the alternative solutions are evaluated.

Feasibility analysis usually considers a number of project alternatives, one that is

chosen as the most satisfactory solution. These alternatives also need to be
evaluated in a broad way without committing too many resources. Various steps
involved in feasibility analysis are:

2. To propose a set of solution that can realize the project goal. These solutions
are usually descriptions of what the new system should look like.

Four primary areas of interest in feasibility study are:

Economic Feasibility: An evaluation of development cost weighed against the

ultimate income of benefit derived from the development system of product. In
economic feasibility, cost benefit analysis is done in which expected cost and
benefits are evaluated.
COST AND BENEFIT ANALYSIS:

Developing an IT application is an investment. Since after developing that

application it provides the organization with profits. Profits can be monetary or in
the form of an improved working environment. However, it carries risks, because
in some cases an estimate can be wrong. And the project might not actually turn
out to be beneficial.

Cost benefit analysis helps to give management a picture of the cost, benefits and
risks. It usually involves comparing alternate investments.

Cost benefit determines the benefits and savings that are expected from the
system and compares them with the expected costs.

In performing cost and benefit analysis it is important to identify cost and benefits
factors. Cost and benefits can be categorized into the following categories:

1. Development Costs – Development costs is the costs that are incurred during
the development of the system. It is one time investment.
2. Operating Costs – Operating Costs are the expenses required for the day to
day running of the system. Examples of Operating Costs are Wages, Supplies
and Overheads.
3. Hardware/Software Costs – It includes the cost of purchasing or leasing of
computers and it’s peripherals. Software costs involves required S/W costs.
4. Personnel Costs – It is the money spent on the people involved in the
development of the system.
5. Facility Costs – Expenses that are incurred during the preparation of the
physical site where the system will be operational. These can be wiring,
flooring, acoustics, lightning, and air-conditioning.
6. Supply Costs – These are variable costs that are very proportionately with the
amount of use of paper, ribbons, disks, and the like.
q BENEFITS

We can define benefits as

Profit or Benefit = Income – Costs

Benefits can be accrued by:

 Increasing income, or
 Decreasing costs, or
 Both

TECHNICAL FEASIBILITY:

Technical Feasibility includes existing and new H/W and S/W requirements that
are required to operate the project using JSP. The basic S/W requirement is J2EE
in which the front end of the online hospital management project has been done.
The basic entry forms are developed in JSP and the data is stored in the MY SQL.

OPERATIONAL FEASIBILITY:

Operational feasibility is mainly concerned with issues like whether the system will
be used if it is developed and implemented. Whether there will be resistance from
users that will affect the possible application benefits? The essential questions that
help in testing the technical feasibility of a system are following:

 Does management support the project?

 Are the users not happy with current business practices? Will it reduce the
time considerably? If yes, then they will welcome the change and the new
system.
 Have the users involved in the planning and development of the project? Early
involvement reduced the probability of resistance towards the new system.
  Will the proposed system really benefit the organization? Does the overall
response increase? Will accessibility of information be lost? Will the system
affect the customers in considerable way?

Legal Feasibility:

A determination of any infringement, violation, or liability that could result from

development of the system. Legal feasibility tells that the software used in the
project should be original purchased from the legal authorities and they have the
license to use it or the software are pirated.

Alternatives:

An evaluation of alternative approaches to the development of system or product.

SYSTEM LIFE CYCLE:

System life cycle is an organizational process of developing and maintaining

systems. It helps in establishing a system project plan, because it gives overall list
of processes and sub-processes required for developing a system.

System development life cycle means combination of various activities. In other

words we can say that various activities put together are referred as system
development life cycle. In the System Analysis and Design terminology, the system
development life cycle means software development life cycle.

Following are the different phases of software development cycle:

• System study
• Feasibility study
• System analysis
• System design
 • Coding
• Testing
• Implementation
• Maintenance

The different phase of software development life cycle is shown below.

PRELIMINARY
INVESTIGATIONN

REVIEW RUNNING SYSTEM DETERMINATION OF

AND SYSTEM REQUIREMENTS
MAINTENANCE

DEVELOPMENT OF PROTOTYPE
SYSTEM

SYSTEM IMPLEMENTATIONN DESIGN OF SYSTEM

DEVELOPMENT OF
SYSTEM TESTING
SOFTWARE AND CODING
IDENTIFICATION OF NEED:

I have designed the given proposed system in the JSP to automate the process of
news sites. Many different people use Usenet, for many different reasons, ranging
from discussions of various topics, requests for help or to trade media, which is
often seen as the ‘dark side’ to Usenet — the abuse of public news groups to trade
copyrighted or offensive material. Thankfully however, those that use Usenet
responsibly far out weight the few who use it as a tool for piracy etc.

Many of the people using and contributing to Usenet are people who work with
computer technology. These people often use Usenet to seek help with a piece of
software or suggest improvements, indeed one of the early functions of Usenet
was to help users identify and report bugs found in software.

Unfortunately, the massive growth seen within Usenet has also made it a difficult
medium to keep track of, the great variety and number of articles can take
considerable time to filter through in order to find those of interest. There have
been a variety of software applications created to help deal with this problem and
many are freely available for personal use.

The following steps that give the detailed information of the need of proposed system are:

Performance: During past several decades, the records are supposed to be

manually handled for all activities. The manual handling of the record is time
consuming and highly prone to error. To improve the performance of the Company
system, the computerized system is to be undertaken. The computerized project
is fully computerized and user friendly even that any of the members can see the
report and status of the company.

Efficiency: The basic need of this website is efficiency. The website should be
efficient so that whenever a new user submit his/her details the website is updated
automatically. This record will be useful for other users instantly.
 Control: The complete control of the project is under the hands of authorized
person who has the password to access this project and illegal access is not
supposed to deal with. All the control is under the administrator and the other
members have the rights to just see the records not to change any transaction or
entry.

Security: Security is the main criteria for the proposed system. Since illegal
access may corrupt the database. So security has to be given in this project.

FACT FINDING TECHNIQUES:

The functioning of the system is to be understood by the system analyst to design

the proposed system. Various methods are used for this and these are known as
fact-finding techniques. The analyst needs to fully understand the current system.

The analyst needs data about the requirements and demands of the project
undertaken and the techniques employed to gather this data are known as fact-
finding techniques. Various kinds of techniques and the most popular among them
are interviews, questionnaires, record views, case tools and also the personal
observations made by the analyst himself.

 Interviews

Interview is a very important data gathering technique as in this the analyst directly
contacts system and the potential user of the proposed system.

One very essential aspect of conducting the interview is that the interviewer should
first establish a rapport with the interviewee. It should also be taken into account
that the interviewee may or may not be a technician and the analyst should prefer
to use day to day language instead of jargon and technical terms.
 The advantage of the interview is that the analyst has a free hand and the he can
extract almost all the information from the concerned people but then as it is a very
time consuming method, he should also employ other means such as
questionnaires, record reviews, etc. This may also help the analyst to verify and
validate the information gained. Interviewing should be approached, as logically
and from a general point of view the following guides can be very beneficial for a
successful interview:

1. Set the stage for the interview.

2. Establish rapport; put the interview at ease.
3. Phrase questions clearly and succinctly.
4. Be a good listener; a void arguments.
5. Evaluate the outcome of the interview.

The interviews are of the two types namely structured and

unstructured. I . S tructured Interview

Structured interviews are those where the interviewee is asked a standard set of
questions in a particular order. All interviews are asked the same set of questions.
The questions are further divided into two kinds of formats for conducting this type
if interview.

II. Unstructured Interview

The unstructured interviews are undertaken in a question-and-answer format. This

is of a much more flexible nature than the structured and can be very rightly used
to gather general information about the system.
 Questionnaires:

Questionnaires are another way of information gathering where the potential users
of the system are given questionnaires to be filled up and returned to the analyst.
Questionnaires are useful when the analyst need to gather information from a large
number of people. It is not possible to interview each individual. Also if the time is
very short, in that case also questionnaires are useful. If the analyst guarantees
the anonymity of the respondent then the respondent answers the questionnaires
very honestly and critically.

The analyst should sensibly design and frame questionnaires with clarity of it’s
objective so as to do just to the cost incurred on their development and distribution.

 Record Reviews

Records and reports are the collection of information and data accumulated over
the time by the users about the system and it’s operations. This can also put light
on the requirements of the system and the modifications it has undergone.
Records and reports may have a limitation if they are not up-to-date or if some
essential links are missing. All the changes, which the system suffers, may not be
recorded. The analyst may scrutinize the records either at the beginning of his
study which may give him a fair introduction about the system and will make him
familiar with it or in the end which will provide the analyst with a comparison
between what exactly is/was desired from the system and it’s current working.

 On-Site Observation

On-site observations are one of the most effectively tools with the analyst where
the analyst personally goes to the site and discovers the functioning of the system.
As a observer, the analyst can gain first hand knowledge of the activities,
operations, processes of the system on-site, hence here the role of an analyst is
of an information seeker. This information is very meaningful as it is unbiased and
has been directly taken by the analyst. This exposure also sheds some light on the
actual happenings of the system as compared to what has already been
documented, thus the analyst gets closer to system.
 This technique is also time-consuming and the analyst should not jump to
conclusions or draw inferences from small samples of observation rather the
analyst should be more patient in gathering the information. This method is
however less effective for learning about people’s perceptions, feelings and
motivations.

ANALYST’S INTERVIEW WITH HOSPITAL ADMINISTRATOR:

Analyst: Hi, I have come to talk to you regarding the functioning of

your hospital project.
Administrator: hello, do come in. I was expecting you.

Analyst: I’ll come straight to the point. Don’t hesitate, you can be as
much open you want. There are no restrictions.
Administrator: I’ll give you my whole contribution.

Analyst: Tell me are you excited about the idea of having an

automated system for your hospital?
Administrator: Yes, I do. Very much. After all it’s gonna reduce our loads of work.

Analyst: Will you elaborate on it?

Administrator: Major problem is managing the rooms and admission and
discharge of patients. There are so many of rooms and the
numbers of patients are admitted in the room. At the time of
discharging of a patient, it becomes more difficult to handle
the rooms condition, and re-admitting the patients in that
room.

Analyst: What do you think be ideal solution to this?

Administrator: All the information of rooms, patients and discharged
patients should be put into computer. It’ll be easy for us to
 rooms are not available and which patient has to be
allotted what room.

Analyst: Could you explain how?

Administrator: Look whenever a new patient is admitted he/she is allotted
a bed number and the bed is reserved for the patient till the
patient gets discharged. And when the patient is
discharged, the bed allotted to him/her is freed and now the
bed should again automatically ready for new patient to be
admitted.

Analyst: Do you have different patient categories?

Administrator: No, we don’t have any categorization for patients. All are
treated at par.

Analyst: How do you categorize your patients?

Administrator: By Bed number.

Analyst: Do you have any other expectations or suggestion for

the new system?
Administrator: It should be able to produce reports faster.

Analyst: Reports? I completely forgot about them. What reports you

people produce presently?
Administrator: Well first is for room status, another for patient’s list
being admitted and discharged patients and reports
for doctors.

Analyst: Do you have some format for them?

Administrator: Yes we do have and we want that the same format be
used by the new system.
Analyst: Yes we’ll take care of that. Any other suggestions?
Administrator: No. You have already covered all the fields.

Analyst: Thanks for your co-operation. It was nice talking to you.

Administrator: My pleasure. Bye.
QUESTIONNAIRES FOR HOSPITAL STAFF:

Instructions: Answer as specified by the format. Put NA for non-application situation.

1. What are your expectations out of the new system (computerized)? Rate the
following on a scale of 1-4 giving allow value for low priority.
(a) better cataloguing
(b) better managing of users
(c) better account and patients management
(d) computer awareness
(e) any other

2. How many users are you expecting?

3. How many rooms are there in the hospital?

4. How you want the patients to be categorized for searching (like by room
number, bed number)?

5. Is there any difference in the roles (privileges) of two or more

patients? Yes/No Please specify if Yes
 6. Do you have data of patients entered into some kind of
database? Yes/No

7. How do you want users to be categorized?

or

8. Would you like online registration for users rather than the printed
form? Yes/No

9. Do you already have some existing categorization of patients on the basis as

specified in question 4 above?
Yes/No

10. Any other specific suggestion/expectation out of the proposed system.

SOFTWARE REQUIREMENT SPECIFICATION (SRS):

1.1.1. What are the benefits of a SRS?

The IEEE 830 standard defines the benefits of a good SRS:

 Establish the basis for agreement between the customers and the
suppliers on what the software product is to do. The complete
description of the functions to be performed by the software specified in
the SRS will assist the potential users to determine if the software
specified meets their needs or how the software must be modified to
meet their needs. [NOTE: We use it as the basis of our contract with our
clients all the time].
 Reduce the development effort. The preparation of the SRS forces the
various concerned groups in the customer’s organization to consider
rigorously all of the requirements before design begins and reduces later
redesign, recoding, and retesting. Careful review of the requirements in
the SRS can reveal omissions, misunderstandings, and inconsistencies
early in the development cycle when these problems are easier to
correct.

 Provide a basis for estimating costs and schedules. The description of

the product to be developed as given in the SRS is a realistic basis for
estimating project costs and can be used to obtain approval for bids or
price estimates. [NOTE: Again, we use the SRS as the basis for our fixed
price estimates]

 Provide a baseline for validation and verification. Organizations can

develop their validation and Verification plans much more productively
from a good SRS. As a part of the development contract, the SRS
provides a baseline against which compliance can be measured.
[NOTE: We use the SRS to create the Test Plan].

 Facilitate transfer. The SRS makes it easier to transfer the software

product to new users or new machines. Customers thus find it easier to
transfer the software to other parts of their organization, and suppliers
find it easier to transfer it to new customers.

 Serve as a basis for enhancement. Because the SRS discusses the

product but not the project that developed it, the SRS serves as a basis
for later enhancement of the finished product. The SRS may need to be
altered, but it does provide a foundation for continued production
evaluation.

1.1.2. What should the SRS address?

Again from the IEEE standard:

The basic issues that the SRS writer(s) shall address are the following:.
 What is the software supposed to do?
 Our System aims at automating the manual system being used
in the hospital for maintaining the records of the patients &
employees of the Hospital.

 External interfaces.

How does the software interact with people, the system’s hardware,
other hardware, and other software?
 Our system uses various forms and reports through which users can
interact with the system.

 As we can have a centralized database so our system interact it

with database software through network and as network comes
in, it uses network peripheral likes switches etc.

1.2. Software Engineering Paradigm :

Software engineering paradigm can be defined as a development

strategy that encompasses the process, methods, tools layers and
generic phases such as definition phase, development phase and
support phase to solve real lives problems in an industry, research
institute etc used by software engineers or team of engineers.
The most useful software engineering paradigm that I incorporate in
developing my project is the “Spiral Model”. This process model is
suitable and useful for my project because the following reasons:
 The all requirements of the project are not well understood by me at the
beginning.

 Relatively small but too complex project.

 This project is a complete new research. No one has already

implemented the logics and all necessary factors governing the project.
  The target of this process model is that a complete system will be
developed after the number of refinement.

This approach to software development begins at the system level

and progresses towards through analysis, design, coding, testing
and support. The details discussion of these steps is beyond the
consideration of the project but all these steps have been applied
through out the SDLC of my project.

1.3. Process Logic

1. User verification Process :-

The module receives input from the user who logs on the system. The module
checks for the validity of the user from within the system itself. The module
generate the output, displaying the validity or non-validity of the user . the
module then grants access rights to the user depending on the level of the user.
The log file is updated after the user logs-on successfully.

2. OPD Registration Process :-

The module is operated on by the operational level user. The module receives
input from the patients, which includes their details. System will record these
details & generate a OPD No. and list of Doctors available in OPD on that day.
The output generated is the OPD Card No and patient is directed to the required
Doctor with that card. The revenue generated from OPD is recorded & updated
in the Master Revenue Database after every 24 hours.
 3. Admission Registration Process :-

This module receives input from two areas:-

(i) From the patient himself who has to get admitted to the Hospital. This
process record patient details and issues a Admission No. .This no. is
used as reference in other modules. The module generates a admission
slip as the output indicating the ward & Bed allotted to the patient.

(ii) The record input is received from the OPD Registration module, if the OPD
Doctor recommends patient for immediate admission to the hospital. The
Card No. taken as reference so that patient details do not required
entering again. The card no is now replaced by the admission no. and
output generated is same as in the case (i).

2. Duty Allocation Process :-

This module is operated by the super user in collaboration with top

management who together build-up the schedule for all employees of the
Hospital. The process receives input from the employee Master database and
the process prepares schedule for a period. The output of the process is the
schedule report for the period in the consideration.

3. Financial Activity Process :-

This process receives two types of inputs:-

(i) First input, which is received, is for the Patient. It receives input from the
admission-registration module, and test & treatment-undertaken module,
as
 well as the patient master database. It records & process all the financial
transactions taken place between the hospital and the patient and
generates the final bill as the output.

(ii) Second input, which is received, is for the employees of the hospital. It
receives input from the duty allocation process and the employee
database for the preparation of a salary-slip. The module records &
processes various calculations and generates the salary-slip as the
output.

4. Test and Treatment Undertaken Process :-

This module receives input in the form of prescription written by the doctor for
the types of tests and treatment to be undertaken by the patient. It records and
process, the various details about the test and generates the lab-report as the
output of the module. It also generates the receipt for the tests undertaken.
These receipts serve as one of the input to the financial-activity module.

5. Medical supply Process: -

This module is fairly independent of the other modules. It maintains the

inventory of the various medicines. It takes input in the form of prescription and
generates output in the form of bill containing the number of medicines
purchased and their respective rates, along with the total amount to be paid by
the patient. The module also maintains a database of the medicines and
provides a check for their availability and non-availability. In case of low
inventory of any medicine, a message is sent to the hospital, which replenishes
the inventory-level of that medicine.

6. Maintenance Process: -

This module is the most important module. It receives input from every other
module of the system, and its functionality is to maintain the working and
processing of other modules as well as the maintenance of the various
databases. Thus, it aims at the overall maintenance of the whole system.
 ACD (Architectural Context Diagram

Registration & Discharge

Access to system
User Login and
granted
User Login Security system
and Password
Access Denied

Registration
form
Opd system

Registration form
Admission system Admission
Granted

Admission
Prescription Test & Treatment system Rejected

Report +Result

Medicine Shop system

Receipt of
Payment

Discharge Slip Financial activity system

Receipt of
Payment

Verification & Validation

 PERTCHART

D (12) E (8)

2 5 7

D (0)
A (8)

B (12) F (8) J (10) K (8) L (5)

1
4 9 1 1 1
C
(5)
I (12)

G (12) H (5)
3 6 8

Critical Path

Activity

Dummy Activity

Node
A=Order computing Platform

B=Prepare site

C=Review Specification

D=Install equipment

E= Test hardware

F=Training

G=Write Programs

H=Test programs

I=Test software

J=Convent Systems

K=Implement follow

L= Accept
 E-R- DIAGRAM

Hospital Patients

Patient Admit
informatio
n

Room

Hospital Docto
doctor
r
record

Patient
Room
Discharge

Hospital
Appointme nt
 HOSPITALMANAGEMENT SYSTEM DATA FLOW DIAGRAM

Context Level DFD

Medical
Patient
Advice
Appointmen

HOSPITAL
MANAGEMENT PG
SYSTEM

Patient Carrier &

Status Bill Payment Job
Hospital
 DFD for Medical Advice

1. Read the 2. Search for

Patient Data from disease from
Knowledge
patient

Data base
3. Copy
Selecte
d

Output Unit
 DFD for patient Appointment

1. Read 2. Search
patient from Doctor
USER
reques Data base

Database
3. Give the
Time and
Number

Output UNIT
 DFD for PG Course

1. Accept 2. Search for

Doctor Seat
Data for
specializin

Database
3. Display the
Admission

status for PG

Output Unit
 DFD For Bill Payment

DATABASE

1. Read the
Patient
Data &
Accountant Treatment

2. Generate
the bill

Print Bill

Outpu Patient
t
Device
 DFD For Job Opportunity In hospital

User/
Search
Doctor Database
the
web

Apply Only

Get Online Id
 D FD For Online Searching For Patient

Read Data base

User Patien
t

Patient Data

CRT
 DFD For Searching a Doctors

Read the
Data of Doctor Data Base
User & Specialisation

Doctor’s
With Specialties

CRT
 D FD Online Medical Advice

Read Patient
Data and Data Base
User
Disease

Display the
Remedies &
Treatments

Output
 DFD For Login Of User

Read User Id
& Password Data Base
User

Authenticate
User & Login

Output
 DATA FLOW DIAGRAM RECORD
MODIFICATION

1
Read

USER

Scan Record

2
Show the FILE
Details of

Processing Updat

3
Modify
Details of
 D ATA FLOW DIAGRAM DISCHARGE OF
PATIENT

1 Scan the
patient
PATIENT

1.1 Display
Form
FILE

Process
Update Table

Patient Details

1.2 Get
1.4
Details
 DATA FLOW DIAGRAM LISTING OF
PATIENTS

FILE
Scan Record

2 Select 3 Copy
Record Selecte
1 from d
PATIENT
Read
the Bed
Processing

6 Copy
Selecte 4
d
Compute

Processing
Outpu

5 Select
Records

8
7
Generate
Compute
Final Output
To

OUTPUT
UNIT
 D ATA FLOW DIAGRAM LIST OF ALL
RECORDS

FILE
Scan All Record

MANAG 1 2 Select
Record
Read
EMENT from File
Processing

3 Copy
Selected
Record

7 Copy
Selecte 4
d
Compute

5
Outpu
Select
Processing

8
7
Generate
Compute
Final Output

To

OUTPUT
UNIT
SYSTEM ANALYSIS

Analysis is the detailed study of the various operations performed by a

system and their relationships within and outside of the system. A key question is:
What must be done to solve the problem? One aspect of analysis is defining the
boundaries of the system and determining whether or not candidate system should
consider other related systems. During analysis, data are collected on the
available files, decision points, and transactions handled by the present system.

3.1. MODULE DESCRIPTION

This section attempts to describe each module of the project in brief, and the
detailed description of each of these modules is spread throughout this document.

The Hospital Management System project has been divided into four
modules. They are
1 Registration
2 Drug stores
3 Case Records
4 Daily Entries

1. Registration
This module has been divided into two sub modules. They are
Inserting the new records
Retrieving the record

1.1. Inserting the new records

The information of the students and employees are send

from the different departments to provide the free service. All the records
 which are send from the departments are entered into the database and
each member is represented through the unique number known as the
opno. Inserting of the new records include the opno i.e which is allotted
uniquely for providing the free services, Name, Age, Sex, Address , Family
members of the employee and other Beneficiaries under the S.V. Health
Center.

1.2 Retrieving the details

The records which are entered into the database are

retrieved to check whether that person who has come to take the service at
the health center is eligible to take the service are not. This is done by
entering the opno that has allotted to the patient, if the data is retrieved from
the database the person is eligible to take the service and by this ,if person
is the employee then in some cases he/she is charged like wise the x-ray
charges and the bed charges for the employee. The students are not
charged in any cases all the services are provided for the free of the cost.

2 Drug Stores

This module is divided into three modules. They are

2.1 Drug Entry
2.2 Updating Drug Entry
2.3 Stock Details
2.1 Drug Entry
This is an entry done by entry operator after getting the stock from
the medical transcripters and the information is stored in the
database. The information is in the form starting with the Drug
name, in-stock, Expiry date1 and Expiry date2. The Drug name is
uniquely identified such that the database is maintained without any
complexity. Here the expiry date is represented in the form of
 month-year, but not in the form mm / dd / yy. The stock is first
stored in the main drug stores and every week it is shifted to the
pharmacy store by watching the stock at the pharmacy house.

2.2 Updating Drug Entry

This is an entry done by same entry operator after the drugs all
entered in the database. The drugs should be shifted to the
pharmacy house by checking the stock at the pharmacy house.
First the Main drug store maintains the stock and the drugs are
shifted to the pharmacy house periodically. This periodical shifting
of the drugs are updated such that the drug house knows how
much of the stock is present in the drug store, Here the drug stores
mainly considers the expiry date as the main criteria the drugs
which have the nearer expiry date are shifted to the pharmacy
house.
2.3 Stock Details
The stock details are so important such that we know how many
drugs are in the main store, what are the expiry dates of the drugs.
When the stock is taken it will minimum of two and maximum of five
expiry dates. So it is better to watch the expiry dates so that the
drugs are shifted to the pharmacy house according to the drugs
which are having the early expiry date.
3 Case Records
This module has been divided into three sub modules. They are
3.1 Students In-Patients Records
3.2 Employees & Beneficiaries In-Patients Records.
3.3 Out – Patients Records ( Students & Beneficiaries )

3.1 Students In-Patients Records

The information about the in-patients should be notified such
that the treatment for the patient is done in the proper way. The
 students who are in-patients are maintained separately because
everything to the student is served freely i.e there is no bed
charges, no charge for the scanning, no charge for the X-Rays and
every thing is supplied freely. There may be special cases that are
used for case studies how that disease has occurred and what are
the precautions are to be taken to overcome that disease. The
diseases that affect the other patients are shifted to the Isolation
ward such that disease is not affected to the other patients.
3.2 Employees & Beneficiaries In-patient Records
The employees and other beneficiaries are maintained
separately such that there are applicable for some charges .These
employees have the bed charges, X-Ray and Scanning charges.
These are calculated according to the days present in the hospital.
The medicines are freely served to the patient only in some special
cases the patient is charged.

3.3 Out-Patients Record

The patients are served for the common problems which are not
serious, the treatment to all the beneficiaries and students are
provided freely. There are separate wards for the ladies and gents
and in some special cases patients are sent to the chief doctor.

4 Daily Records
Daily records are then divided into two sub modules. They are

4.1 Pharmacy Daily Entries

Pharmacy daily entries are the entries which are given to the out-
patients and these are noted at the end of the day. Daily entries will give the
information about how many drugs are needed every day. This will then take the
sufficient number of drugs from the main stores to the Pharmacy house.
4.2 Nurse Daily Entries
Nurse daily entries that are entered with the operator when the drug
has been administered to the patient, The date, time what type of the
drugs applied to the patient are to be noted in certain period of time.

3.2 FEASIBILITY ANALYSIS

Feasibility study is an important phase in the software development process. It

enables the developer to have an assessment of the product being developed. It
refers to the feasibility study of the product in terms of outcomes of the product,
operational use and technical support required for implementing it.

Feasibility study should be performed on the basis of various criteria and

parameters. The various feasibility studies are:

 Economic Feasibility
 Operational Feasibility
 Technical Feasibility

1. Economic Feasibility: It refers to the benefits or outcomes we are deriving

from the product as compared to the total cost we are spending for developing the
product. If the benefits are more or less the same as the older system, then it is
not feasible to develop the product.

2. Operational Feasibility: It refers to the feasibility of the product to be

operational. Some products may work very well at design and implementation but
may fail in the real time environment. It includes the study of additional human
resource required and their technical expertise.

3. Technical Feasibility: It refers to whether the software that

is available in the market fully supports the present application. It studies the pros
and cons of using a particular software for the development and its feasibility. It
 also studies the additional training needed to be given to the people to make the
application work.

Implementation Plan:
The main plan for the system developed is to mimic the existing system as it is in
the proposed system.

Study of the Existing System

The existing system is very complex as every work is done manually.
By using the present system, work is done manually. So, each and every work
takes much time to complete. Whenever the doctor needs the information it is
very difficult for the employee to search for that particular opno details and the
drug information to be ordered. Every time we should search the records at the
shelves.
Disadvantages

1. The work is done manually so that it takes much time to recognize the
patient at the registration office.
2. More number of labors is needed.
3. We can’t asses the calculations accurately.
4. Amount of time is more needed when the more patients come to
registration counter. It counts time factor.
5. As there are thousands of patients records; Searching process is a
difficult task.

THE PROPOSED SYSTEM:

The present system has obvious problems, inhibiting growth and
more usage of man power. The present system which has been proposed is
very easy to work .The computerization of the every department in the health
 center will reduce the work that is done manually. The man power is reduced
to the maximum extent. The patients at the registration office are registered
within no time, because every time there is no need search for the particular
opno in the shelf’s .The drugs information are maintained without any
complexity and all the calculations are made automatically by this system
there is no need for the calculations

Advantages

1. A fast and more efficient service to all patients . As there are thousands
of patients records; Searching process is an easy task.
2. Saving in staff time in entering and manipulating data.
3. Easy input, deletion and manipulation of lot, patients details.
4. Simple correction of input errors and we can asses the calculations
accurately.

Disadvantage

1. Loss of data when electronic fluctuations occur.

Goals and Objectives

1. Service should be provided to patients in an efficient manner.

2. OPNO number receipt is issued instantly when patient apply for OP
receipt.
3. Enquiry details about the drugs are to be maintained in the proper way
etc.
4. Daily records are maintained such that the drugs are taken from the
MAIN STORES are dispatched in the proper way.
5. Each and every patient record should be maintained in systematic
manner so that the searching process will be easy.
 4.1 INTRODUCTION

Design is the first step in the development phase for any techniques and principles
for the purpose of defining a device, a process or system in sufficient detail to
permit its physical realization.

Once the software requirements have been analyzed and specified the software
design involves three technical activities design, coding, generation and testing
that are required to build and verify the software.

The design activities are of main importance in this phase, because in this activity,
decisions ultimately affecting the success of the software implementation and its
ease of maintenance are made. These decisions have the final bearing upon
reliability and maintainability of the system. Design is the only way to accurately
translate the customer’s requirements into finished software or a system.

Design is the place where quality is fostered in development. Software design is a

process through which requirements are translated into a representation of
software. Software design is conducted in two steps. Preliminary design is
concerned with the transformation of requirements into data.

4.2 FLOW CHARTS

Before solving a problem with the help of a computer, it is essential to plan the
solution in a step-by-step manner. Such a planning is represented symbolically
with the help of flow chart. It is an important tool of system analysts and
Programmers for tracing the information flow and the logical sequence in data
processing Logic is the essence of a flow chart.

A flow chart is the symbolic representation of step-by-step solution of a given

problem, and it indicates flow of entire process, the sequence of the data input,
operations, computations, decisions, results and other relevant information.
 Pertaining to a particular problem, a flow chart helps us in the complete
understanding of the logical structure of a complicated problem and in
documenting the method used. It would be seen that the flow chart is a very
convenient method of organizing the logical steps and deciding what, when and
how to proceed with various processes. The logic should be depicted in the flow
charts. Computerization of the data without a flow chart is like constructing the
building without a proper design and detailed drawings.

Kinds of the Flow Charts

1. System Flow Chart

The system analyst to describe data flow and operations for the data processing
cycle uses these. A system flow chart defines the broad processing in the
organizations, showing the origin of the data, filling structure, processing to be
performed, output that is to generate and necessity of the offline operation.

2. Program Flow Chart (or) Computer Procedure flow chart

The programmers to describe the sequence of operations and the decision of a

particular problem normally use these. A program flow chart plans the Program
structure and also serves the purpose of documentation for a program, which is to
be retained and used at a later date either by the original programmer or others.

Advantages:

Apart from, the DFDS the flow charts has been helping the programmer to develop
the programming logic and to serve as the documentation for a Completed
program, it has the following advantages
 1. They help for the easy understanding of the logic of a
Process or a procedure

2. It is a better communicating tool than writing in words.

3. It is easy to find the conditions, which are responsible

For the actions.

4. It is an important tool for planning and designing the

New system.
5. It clearly indicates the role-played at each level.

6. It provides an overview of the system and also

demonstrates the relationship between the various steps.

7. It facilitates troubleshooting.

8. It promotes logical accuracy.

Disadvantages:

1. Communication lines are not always easy to show.

2. The charts are sometimes complicated.

3. Reproduction is difficult.

4. They are hard to modify.

 DEVELOPMENT PHASE

FEATURES OF LANGUAGE PYTHON

Python is an interpreted high-level general-purpose programming language. Its design

philosophy emphasizes code readability with its use of significant indentation. Its language
constructs as well as its object-oriented approach aim to help programmers write clear,
logical code for small and large-scale projects.[30]
Python is dynamically-typed and garbage-collected. It supports multiple programming
paradigms, including structured (particularly, procedural), object-oriented and functional
programming. It is often described as a "batteries included" language due to its
comprehensive standard library.[31]
Guido van Rossum began working on Python in the late 1980s, as a successor to the ABC
programming language, and first released it in 1991 as Python 0.9.0.[32] Python 2.0 was
released in 2000 and introduced new features, such as list comprehensions and a garbage
collection system using reference counting. Python 3.0 was released in 2008 and was a
major revision of the language that is not completely backward-compatible. Python 2 was
discontinued with version 2.7.18 in 2020.[33]
Python consistently ranks as one of the most popular programming languages

PYTHON ADVANTAGES

Advantages of Python

1. Easy to Read, Learn and Write

Python is a high-level programming language that has English-like syntax. This makes it
easier to read and understand the code.
Python is really easy to pick up and learn, that is why a lot of people recommend Python to
beginners. You need less lines of code to perform the same task as compared to other major
languages like C/C++ and Java.
2. Improved Productivity

Python is a very productive language. Due to the simplicity of Python, developers can focus
on solving the problem. They don’t need to spend too much time in understanding
the syntax or behavior of the programming language. You write less code and get more
things done.
3. Interpreted Language

Python is an interpreted language which means that Python directly executes the code line
by line. In case of any error, it stops further execution and reports back the error which has
occurred.
Python shows only one error even if the program has multiple errors. This
makes debugging easier.
4. Dynamically Typed

Python doesn’t know the type of variable until we run the code. It automatically assigns the
data type during execution. The programmer doesn’t need to worry about declaring
variables and their data types.
5. Free and Open-Source

Python comes under the OSI approved open-source license. This makes
it free to use and distribute. You can download the source code, modify it and even
distribute your version of Python. This is useful for organizations that want to modify some
specific behavior and use their version for development.
6. Vast Libraries Support

The standard library of Python is huge, you can find almost all the functions needed for your
task. So, you don’t have to depend on external libraries.

But even if you do, a Python package manager (pip) makes things easier to import other
great packages from the Python package index (PyPi). It consists of over 200,000
packages.
7. Portability

In many languages like C/C++, you need to change your code to run the program on
different platforms. That is not the same with Python. You only write once and run it
anywhere.

DISADVANTAGE OF PYTHON

1. Slow Speed

We discussed above that Python is an interpreted language and dynamically-

typed language. The line by line execution of code often leads to slow execution.
The dynamic nature of Python is also responsible for the slow speed of Python because it
has to do the extra work while executing code. So, Python is not used for purposes where
speed is an important aspect of the project.
2. Not Memory Efficient

To provide simplicity to the developer, Python has to do a little tradeoff. The Python
programming language uses a large amount of memory. This can be a disadvantage while
building applications when we prefer memory optimization.
3. Weak in Mobile Computing

Python is generally used in server-side programming. We don’t get to see Python on the
client-side or mobile applications because of the following reasons. Python is not memory
efficient and it has slow processing power as compared to other languages.
4. Database Access

Programming in Python is easy and stress-free. But when we are interacting with the
database, it lacks behind.
The Python’s database access layer is primitive and underdeveloped in comparison to the
popular technologies like JDBC and ODBC.
Huge enterprises need smooth interaction of complex legacy data and Python is thus rarely
used in enterprises.
5. Runtime Errors

As we know Python is a dynamically typed language so the data type of a variable can
change anytime. A variable containing integer number may hold a string in the future, which
can lead to Runtime Errors.

FEATURES OF LANGUAGE
MYSQL
MySQL is an open-source relational database management system (RDBMS).[5][6] Its name
is a combination of "My", the name of co-founder Michael Widenius's daughter,[7] and "SQL",
the abbreviation for Structured Query Language. A relational database organizes data into
one or more data tables in which data types may be related to each other; these relations
help structure the data. SQL is a language programmers use to create, modify and extract
data from the relational database, as well as control user access to the database. In addition
to relational databases and SQL, an RDBMS like MySQL works with an operating system to
implement a relational database in a computer's storage system, manages users, allows for
network access and facilitates testing database integrity and creation of backups.
MySQL is free and open-source software under the terms of the GNU General Public
License, and is also available under a variety of proprietary licenses. MySQL was owned and
sponsored by the Swedish company MySQL AB, which was bought by Sun
Microsystems (now Oracle Corporation).[8] In 2010, when Oracle acquired Sun,
Widenius forked the open-source MySQL project to create MariaDB.[9]
MySQL has stand-alone clients that allow users to interact directly with a MySQL database
using SQL, but more often, MySQL is used with other programs to implement applications
that need relational database capability. MySQL is a component of the LAMP web
application software stack (and others), which is an acronym for Linux, Apache,
MySQL, Perl/PHP/Python. MySQL is used by many database-driven web applications,
including Drupal, Joomla, phpBB, and WordPress. MySQL is also used by many
popular websites, including Facebook,[10][11] Flickr,[12] MediaWiki,[13] Twitter,[14] and
YouTube.[15]
ADVANTAGES OF MYSQL
Advantages
Like other relational database system, MySQL database server also has its advantages and
disadvantages. Some of these advantages have been explained below.
Reduced Total Cost of Ownership
MySql one of the most popular open source database management system that allows you
to manage relational database. Since MySql open source, you can use MySql free and if you
want, you can tailor its source code according to your requirement. Most of the companies
prefer MySQL because they don't have to pay anything for this excellent product.
Portability
MySQL is cross platform database server. It can run on different plateform like Linux,Solaris
and Windows etc. It is good choice for those project that target multiple platforms particularly
web application. In fact, MySQL is a part of the famous LAMP (Linux Apache MySQL PHP)
server stack which is used worldwide for web application development. MySql support many
plateform with different languages like C, C++, PHP, PERL, JAVA, Python etc.
Seamless Connectivity
There are various secure and seamless connection mechanisms are available in order to
connect with MySQL server. These connections include named pipes, TCP/IP sockets and
UNIX Sockets.
Rapid Development and Round-the-Clock Uptime
MySQL comes with the assurance of 24x7 uptime and offers a wide range of high-availability
solutions, including specialized cluster servers and master/slave replication configurations.
MySQL has a very large developer community which releases regular patches and updates
for MySQL.
Data Security
MySQL is globally recognize the most secure and reliable database management system
used in popular web applications including WordPress, Drupal, Joomla, Facebook and
Twitter. Data protected via password and good thing about these passwords is that they are
stored in encrypted form and can not break these complex encryption algorithms.

DISADVANTAGE OF MYSQL
Disadvantages
MySQL database server has its disadvantages. Some of these disadvantages have been
explained below.

1. MySQL lower version (5.0 or less) doesn't support ROLE, COMMIT and stored
procedure.
2. MySQL does not support a very large database size as efficiently.
3. MySQL doesn't handle transactions very efficiently and it is prone to data corruption.
4. MySQL doesn't have a good developing and debugging tool compared to other
databases.
5. MySQL doesn't support SQL check constraints.
 LIFE CYCLE MODELS

The stage of planning the development process involves defining a define,

develop, test, deliver, operate, and maintain a software product. Different lifecycle
models emphasize different aspects of the lifecycle and no single lifecycle model
is suitable for all software products. A lifecycle model that is understood and
accepted by all concerned parties improves project communication and enhances
project manageability, resource allocation, cost control, and product quality.

The Phased Life Cycle Model

The phased lifecycle model represents software lifecycle as a series of

successive activities. Each phase requires well-defined input information, utilizes
well-defined processes and results in well-defined products. The phased model
consists of following phases.

Analysis, Design, Implementation, System Testing and Maintenance

This model is sometimes called the Waterfall Chart, the implication being
that the products cascade from one level to another in smooth progression.

ANALYSIS DESIGN Implementation System Maintenance

testing
Planning,
User needs
Definition Design
Details Code, debug
and Test Integration &
Acceptance Enhance, Fix
Adapt
 The Analysis Stage consists of Planning and Requirements definition
Major include understanding the customer’s problem, performing A feasibility
study, developing a recommended solution strategy, determining the acceptance
criteria and planning development process. The products of planning are a System
definition and a project plan.

The Software Design follows analysis. Design is concerned with its

software components, specifying relationships among components specifying
some structure, maintaining a record of design decisions and providing blueprint
implementation phase. Design consists of detailed design and Architectural
design.

The implementation phase of software development involves translation

design specification into source code, and debugging, documentation and unit
testing the source code. To enhance the quality of the software the methods are
structured control constructs, built in and user defined data types, secure type
checking, flexible scope rules exception handling mechanism, concurrency
constructs and separates compilation modules.

System Testing involves two kinds of testing integration testing and

acceptance testing. Developing a strategy for integrating the components of a
software system into a functioning whole requires careful planning so that modules
are available for integration when needed. Acceptance testing involves planning
and execution of various tests in order to demonstrate that the implemented
system satisfies the requirements document.

The Maintenance phase comes after the acceptance by the customer and
release of the system for production work. Maintenance activities include
enhancements of capabilities, adaptation of software to new processing
environments, and correction of software bugs.

This project follows the Phased Life Cycle Model or the Water Fall model
to a large extent.

The analysis stage consisted of listening to the needs and requirements of

all departments obtaining the required format of the system as desired by them,
taking the required data to be stored for future use etc., In the design stage the
 structure of the system was designed and all the required screens were formatted.
This was then shown to the medical officer’s approval and the system was built.
Implementation phase was also done at as they provided a computer with all the
required software and with required configuration. The coding and debugging was
done even after this stage certain changes were made as made as requested by
the guide. The testing was done to check for any errors or bugs or unwanted
behavior in the system. Individual modules as well as the whole system were
tested separately.

SOFTWARE TESTING

Software Testing is a critical element of software quality assurance

and represents the ultimate review of specification, design and coding, Testing
presents an interesting anomaly for the software engineer.

Testing Objectives include:

1. Testing is a process of executing a program with the intent of finding

an error
2. A good test case is one that has a probability of finding an as yet
undiscovered error
3. 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 a independent
third party
 TESTING STRATERGIES

A Strategy for software testing integrates software test cases into a

series of well planned steps that result in the successful construction of software.
Software testing is a broader topic for what is referred to as Verification and
Validation. Verification refers to the set of activities that ensure that the software
correctly implements a specific function Validation refers he set of activities that
ensure that the software that has been built is traceable to customer’s
requirements

Unit Testing:

Unit testing focuses verification effort on the smallest unit of software

design that is the module. Using procedural design description as a guide,
important control paths are tested to uncover errors within the boundaries of the
module. The unit test is normally white box testing oriented and the step can be
conducted in parallel for multiple modules.

Integration Testing:

Integration testing is a systematic technique for constructing the

program structure while conducting test to uncover errors associated with the
interfacing. The objective is to take unit tested methods and build a program
structure that has been dictated by design.

Top-down Integration:

Top down integrations an incremental approach to construction of

program structure. Modules are integrated by moving downward through the
control hierarchy, beginning with the main control program. Modules subordinate
to the main program are incorporated in the structure either in the breath-first or
depth-first manner.
Bottom-up Integration:

This method as the name suggests, begins construction and testing

with atomic modules i.e., modules at the lowest leveling the program structure.
Because the modules are integrated in the bottom up manner the processing
required for the modules subordinate to a given level is always available and the
need for stubs is eliminated.

Validation Testing:

At the end of integration testing software ids completely assembled

as a package. Validation testing is the next stage which can be defined as
successful when the software functions in the manner reasonably expected by the
customer. Reasonable expectations are those defined in the software
requirements specifications. Information contained in those sections form a basis
for validation testing approach.

System Testing:

System testing is actually a series of different tests whose primary

purpose is to fully exercise the computer-based system. Although each test has a
different purpose, all work to verify that all system elements have been properly
integrated to perform allocated functions.

Recovery Testing:

It is a system test that forces the system to fail in a variety of ways

and verities that the recovery is properly performed.

Security Testing:

Attempts to verify the protection mechanisms built into the system.

Performance Testing:

This method is designed to test runtime performance of software

within the context of an integrated system..Software testing is a critical element of
software quality assurance and represents the ultimate review of specification,
design and coding. Testing is the exposure of the system to trial input to see
whether it produces correct output.

Testing Phases:
Software testing phases include the following:
Test activities are determined and test data selected.
The test is conducted and test results are compared with the expected results.

There are various types of Testing:

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.
This project is thoroughly tested by exposing it to the various test cases
regarding correct event generation, as this project passed all the tests its
quality is completely assured.

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. On this project
integration testing is done mainly while implementing menus in a sample
application such as Browser for Mobiles.

System Testing:
It is mainly used if the software meets its requirements. The reference document
for this process is the requirement document.
 Acceptance Testing:
It is performed with realistic data of the client to demonstrate that the software
is working satisfactorily.

Testing Methods:
Testing is a process of executing a program to find out errors. If testing is
conducted successfully, it will uncover all the errors in the software. Any
testing can be done basing on two ways:

White Box Testing:

It is a test case design method that uses the control structures of the
procedural design to derive test cases. using this testing a software Engineer
can derive the following test cases:
Exercise all the logical decisions on either true or false sides. Execute all loops at their
boundaries and within their operational boundaries. Exercise the internal data structures
to assure their validity.

Black Box Testing:

It is a test case design method used on the functional requirements of the
software. It will help a software engineer to derive sets of input conditions that
will exercise all the functional requirements of the program. Black Box testing
attempts to find errors in the following categories:

Incorrect or missing functions

Interface errors
Errors in data structures
Performance errors
Initialization and termination errors
By Black Box Testing we derive a set of test cases that satisfy the following criteria:

Test cases that reduce by a count that is greater than one, the number of
additional test cases that must be designed to achieve reasonable testing.
Test cases that tell us something about the presence or absence of classes of
errors rather than errors associated only with a specific test at hand.

Test Approach :

Testing can be done in two ways:

Bottom up approach
Top down approach

Bottom up Approach:
Testing can be performed starting from smallest and lowest level modules and
proceeding one at a time. For each module in bottom up testing a short program
executes the module and provides the needed data so that the module is asked to
perform the way it will when embedded with in the larger system. When bottom
level modules are tested attention turns to those on the next level that use the
lower level ones they are tested individually and then linked with the previously
examined lower level modules.

Top down approach:

This type of testing starts from upper level modules. Since the detailed activities
usually performed in the lower level routines are not provided stubs are written. A
stub is a module shell called by upper level module and that when reached properly
will return a message to the calling module indicating that proper interaction
occurred. No attempt is made to verify the correctness of the lower level module.
CONCLUSION

The need for the Health Center to computerize the application processing and
servicing the Patients request through automated modules is most necessary and
now inevitable.

As we have already seen that the need cannot be emphasized for the further
development of this system is only timely and helpful to Health Center, the system
defined in the above script is up to date and caters to all kinds of request faced by
the Health Center employees requirements to provide the better service to the
patients, being developed in java it is also flexible modularized highly
parameterized and hence can be easily deployed by any other application because
of its componentized approach.

Based on the various parameters and properties files everything from the look and
feel to the functionalities can be customized. Thus this project is developed from
the beginning with reuse in mind and implicitly uses several design patterns. The
architecture of this project is such that it suits the diverse and distributed nature of
the Health Center Applications.

The features provided by the (Hospital Management System) are in no means

comprehensive but by all means full filling all important functionalities of Health
Center services. Inclusion of further functionalities as days go by can be easily
done because the project has been developed in a layered architecture.

Plug-in modules would easily add new features which change with the times and
being performance oriented the project will not face any issues. It is also extensible
and scalable as all applications should be thus it can be said that it will meet surges
of huge employee and patient requests that may come up in the near future.
\
BIBLIOGRAPHY

The following are the details of books and the sites which have details
regarding the Swings technology which is used in this project.

The Complete Reference,

https://www.wikipedia.org/

https://www.python.org/

https://www.mysql.com/

https://www.youtube.com/

https://www.google.co.in/