KENDRIYA VIDYALAYA SAP

PEROORKADA

ACADEMIC YEAR: 2021-22

PROJECT REPORT ON- HOSPITAL MANAGEMENT

ROLL NO : 12218

NAME : ANANYA D R

CLASS : XII B

SUBJECT: COMPUTER SCIENCE

1|Page
ACKNOWLEDGEMENT

I would like to express my special thanks of gratitude

to my subject teacher Madam Deepa P R for her
stable guidance and support in completing my
project. I would also like to extend my gratitude to
our Principal Sir Jyothi Mohan N V for providing me
with all the facility that was required. I would like to
finally thank my parents and friends for helping me in
finalizing this project within the limited time frame.

SUBMITTED BY-
ANANYA D R

2|Page
CERTIFICATE
This is to certify that ANANYA D R Of Class XII B
have successfully completed the project entitled
HOSPITAL MANAGEMENT under the guidance
and supervision of Smt. Deepa P R during the
academic year 2021-22 for the partial fulfilment of
AISSCE CBSE board examination of Computer
Science. This project has been undertaken, prepared
and submitted as per CBSE guidelines.

Teacher-in-charge External Examiner

Principal School Seal

3|Page
 TABLE OF CONTENTS [ T O C ]

SER DESCRIPTION PAGE NO

01 INTRODUCTION 6

02 OBJECTIVES OF THE PROJECT 6

03 PROPOSED SYSTEM 7

04 SYSTEM DEVELOPMENT LIFE CYCLE (SDLC) 9

05 PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE 10

06 SOURCE CODE 20

07 OUTPUT 25

08 TESTING 27

09 HARDWARE AND SOFTWARE REQUIREMENTS 31

10 BIBLIOGRAPHY 32

4|Page
 PROJECT ON
HOSPITAL
MANAGEMENT
SYSTEM

SYNOPSIS

5|Page
INTRODUCTION

The Hospital Management System (HMS) is designed for Any

Hospital tore place their existing manual, paper-based system.
This System targets to provide complete solution for Hospital
and Health care services. This System can be used in any
Hospital, Clinic, Diagnostics or Pathology labs for maintaining
patient details and their test results. It integrates the entire
Resources of a Hospital into One Integrated Software
Application.

OBJECTIVES OF THE PROJECT

The objective of this project is to let the students apply the

programming knowledge into a real- world situation/problem

and exposed the students how programming skills helps in

developing a good software.

1. Write programs utilizing modern software tools.

2. Apply object-oriented programming principles effectively

when developing small to medium sized projects.

3. Write effective procedural code to solve small to medium

sized problems.

4. Students will demonstrate a breadth of knowledge in

computer science, as exemplified in the areas of systems,

theory and software development.

6|Page
 5. Students will demonstrate ability to conduct research or

applied Computer Science project, requiring writing and

presentation skills which exemplify scholarly style in

computer

PROPOSED SYSTEM

Today one cannot afford to rely on the fallible human

beings of be really wants to stand against today’s merciless

competition where not to wise saying “to err is human” no

longer valid, it’s outdated to rationalize your mistake. So, to

keep pace with time, to bring about the best result without

malfunctioning and greater efficiency so to replace the

unending heaps of flies with a much-sophisticated hard disk of

the computer.

One has to use the data management software. Software

has been an ascent in atomization various organizations. Many

software products working are now in markets, which have

helped in making the organizations work easier and efficiently.

Data management initially had to maintain a lot of ledgers and

7|Page
a lot of paper work has to be done but now software product on

this organization has made their work faster and easier. Now

only this software has to be loaded on the computer and work

can be done.

This prevents a lot of time and money. The work becomes

fully automated and any information regarding the organization

can be obtained by clicking the button. Moreover, now it’s an

age of computers of and automating such an organization gives

the better look.

8|Page
SYSTEM DEVELOPMENT LIFE CYCLE
(SDLC)

The systems development life cycle is a project management

technique that divides complex projects into smaller, more easily
managed segments or phases. Segmenting projects allows
managers to verify the successful completion of project phases
before allocating resources to subsequent phases.
Software development projects typically include initiation,
planning, design, development, testing, implementation, and
maintenance phases. However, the phases may be divided
differently depending on the organization involved.
For example, initial project activities might be designated
as request, requirements-definition, and planning phases, or
initiation, concept-development, and planning phases. End
users of the system under development should be involved in
reviewing the output of each phase to ensure the system is
being built to deliver the needed functionality.

9|Page
PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE

INITIATION PHASE
The Initiation Phase begins when a business sponsor identifies
a need or an opportunity.

The purpose of the Initiation Phase is to:

Identify and validate an opportunity to improve business

accomplishments of the organization or a deficiency
related to a business need.
Identify significant assumptions and constraints on
solutions to that need. Recommend the exploration of
alternative concepts and methods to satisfy the need
including questioning the need for technology, i.e., will a
change in the business process offer a solution?
Assure executive business and executive technical
sponsorship. The Sponsor designates a Project Manager
and the business need is documented in a Concept
Proposal. The Concept Proposal includes information
about the business process and the relationship to the
Agency/Organization.
Infrastructure and the Strategic Plan. A successful
Concept Proposal results in a Project Management
10 | P a g e
 Charter which outlines the authority of the project
manager to begin
The project.

Careful oversight is required to ensure projects support

strategic business objectives and resources are effectively
implemented into an organization's enterprise architecture. The
initiation phase begins when an opportunity to add, improve, or
correct a system is identified and formally requested through
the presentation of a business case. The business case should,
at a minimum, describe a proposal’s purpose, identify expected
benefits, and explain how the proposed system supports one of
the organization’s business strategies. The business case
should also identify alternative solutions and detail as many
informational, functional, and network requirements as possible.

11 | P a g e
SYSTEM CONCEPT DEVELOPMENT PHASE

The System Concept Development Phase begins after a business need

or opportunity is validated by the Agency/Organization Program
Leadership and the Agency/Organization CIO.

The purpose of the System Concept Development Phase is to:

Determine the feasibility and appropriateness

Identify basic functional and data requirements to satisfy the
business need. Establish system boundaries; identify goals,
objectives, critical success factors, and performance measures.
Evaluate costs and benefits of alternative approaches
Assess project risks
Identify and initiate risk mitigation actions, and Develop high-level
technical architecture, process models, data models, and a
concept of operations. This phase explores potential technical
solutions within the context of the business need.
It may include several trade-off decisions such as the decision to
use COTS software products as opposed to developing custom
software or reusing software components, or the decision to use
an incremental delivery versus a complete, onetime deployment.
Construction of executable prototypes is encouraged to evaluate
technology to support the business process. The System
Boundary Document serves as an important reference document
to support the Information Technology Project Request (ITPR)
process.
The ITPR must be approved by the State CIO before the project
can move forward.

12 | P a g e
PICTORIAL REPRESENTATION OF SDLC:

PLANNING PHASE

The planning phase is the most critical step in completing

development, acquisition, and maintenance projects. Careful planning,
particularly in the early stages of a project, is necessary to coordinate
activities and manage project risks effectively. The depth and formality of
project plans should be commensurate with the characteristics and risks
of a given project. Project plans refine the information gathered during
the initiation phase by further identifying the specific activities and
resources required to complete a project.
A critical part of a project manager’s job is to coordinate
discussions between user, audit, security, design, development, and
network personnel to identify and document as many functional,
security, and network requirements as possible. During this phase, a

13 | P a g e
plan is developed that documents the approach to be used and includes
a discussion of methods, tools, tasks, resources, project schedules, and
user input. Personnel assignments, costs, project schedule, and target
dates are established.
A Project Management Plan is created with components related to
acquisition planning, configuration management planning, quality
assurance planning, and concept
of operations, system security, verification and validation, and
systems engineering management planning.

REQUIREMENTS ANALYSISPHASE

This phase formally defines the detailed functional user

requirements using high-level requirements identified in the Initiation,
System Concept, and Planning phases. It also delineates the
requirements in terms of data, system performance, security, and
maintainability requirements for the system. The requirements are
defined in this phase to a level of detail sufficient for systems design to
proceed. They need to be measurable, testable, and relate to the
business need or opportunity identified in the Initiation Phase. The
requirements that will be used to determine acceptance of the system
are captured in the Test and Evaluation Master plan.

The purposes of this phase are to:

Further define and refine the functional and data requirements and
document them in the Requirements Document,
Complete business process reengineering of the functions to be
supported (i.e., verify what information drives the business
process, what information is generated, who generates it, where
does the information go, and who processes it),
14 | P a g e
 Develop detailed data and process models (system inputs, outputs,
and the process.
Develop the test and evaluation requirements that will be used to
determine acceptable system performance.

DESIGN PHASE

The design phase involves converting the informational, functional,

and network requirements identified during the initiation and planning
phases into unified design specifications that developers use to script
programs during the development phase. Program designs are
constructed in various ways. Using a top-down approach, designers first
identify and link major program components and interfaces, then expand
design layouts as they identify and link smaller subsystems and
Connections. Using a bottom-up approach, designers first identify and
link minor program components and interfaces, then expand design
layouts as they identify and link larger systems and connections.
Contemporary design techniques often use prototyping tools that build
mock-up designs of items such as application screens, database
layouts, and system architectures. End users, designers, developers,
database managers, and network administrators should review and
refine the prototyped designs in an iterative process until they agree on
an acceptable design. Audit, security, and quality assurance personnel
should be involved in the review and approval process. During this
phase, the system is designed to satisfy the functional requirements
identified in the previous phase. Since problems in the design phase
could be very expensive to solve in the later stage of the software
development, a variety of elements are considered in the design to
mitigate risk. These include:

15 | P a g e
Identifying potential risks and defining mitigating design
features. Performing a security risk assessment.
Developing a conversion plan to migrate current data to the new
system. Determining the operating environment.
Defining major subsystems and their inputs and
outputs. Allocating processes to resources.
Preparing detailed logic specifications for each software module.
The result is a draft System Design Document which captures the
preliminary design for the system.
Everything requiring user input or approval is documented and
reviewed by the user. Once these documents have been approved
by the Agency CIO and Business Sponsor, the final System
Design Document is created to serve as the Critical/Detailed
Design for the system.
This document receives a rigorous review by Agency technical and
functional representatives to ensure that it satisfies the business
requirements. Concurrent with the development of the system
design, the Agency Project Manager begins development of the
Implementation Plan, Operations and Maintenance Manual, and
the Training Plan.

16 | P a g e
DEVELOPMENT PHASE

The development phase involves converting design

specifications into executable programs. Effective development
standards include requirements that programmers and other project
participants discuss design specifications before programming
begins. The procedures help ensure programmers clearly understand
program designs and functional requirements. Programmers use
various techniques to develop computer programs. The large
transaction oriented programs associated with financial institutions
have traditionally been developed using procedural programming
techniques. Procedural programming involves the line-by-line
scripting of logical instructions that are combined to form a program.
Effective completion of the previous stages is a key factor in the
success of the Development phase. The Development phase consists
of:

Translating the detailed requirements and design into system

components. Testing individual elements (units) for usability.
Preparing for integration and testing of the IT system.

INTEGRATION AND TEST PHASE

Subsystem integration, system, security, and user acceptance

testing is conducted during the integration and test phase. The
user, with those responsible for quality assurance, validates that
the functional requirements, as defined in the functional
requirements document, are satisfied by the developed or modified
system. OIT Security staff assesses the system security and issue
17 | P a g e
 a security certification and accreditation prior to
installation/implementation.

Multiple levels of testing are performed, including:

Testing at the development facility by the contractor and possibly

supported by end users
Testing as a deployed system with end users working together with
contract personnel

Operational testing by the end user alone is performing all

functions. Requirements are traced throughout testing, a final
Independent Verification & Validation evaluation is performed and
all documentation is reviewed and accepted prior to acceptance
of the system.

IMPLEMENTATION PHASE

This phase is initiated after the system has been tested and
accepted by the user. In this phase, the system is installed to support
the intended business functions. System performance is compared to
performance objectives established during the planning phase.
Implementation includes user notification, user training, installation of
hardware, installation of software onto production computers, and
integration of the system into daily work processes. This phase
continues until the system is operating in production in accordance with
the defined user requirements.

18 | P a g e
OPERATIONS AND MAINTENANCE PHASE

The system operation is ongoing. The system is monitored for

continued performance in accordance with user requirements and
needed system modifications are incorporated. Operations continue as
long as the system can be effectively adapted to respond to the
organization’s needs. When modifications or changes are identified, the
system may re enter the planning phase.

The purpose of this phase is to:

Operate, maintain, and enhance the system.

Certify that the system can process sensitive information.
Conduct periodic assessments of the system to ensure the
functional requirements continue to be satisfied.
Determine when the system needs to be modernized, replaced, or
retired.

19 | P a g e
 SOURCE CODE
from sys import exit

import mysql.connector as sql

conn=sql.connect(host='localhost',user='root',passwd='',databa

se='project')

if conn.is_connected():

print('successfully connected')

c1=conn.cursor()

print('---------------------------------------------')

print("HOSPITAL MANAGEMENT SYSTEM")

print('---------------------------------------------')

print('"GOD WISHES YOU"')

print("1.LOGIN")

print("2.EXIT")

choice=int(input("ENTER YOUR CHOICE:"))

ifchoice==1:

u1=input("enter user name:")

pwd1=input("enter the password:")

while u1=='vasu'and pwd1=='vasu6072':

print('connected')

print("WELCOME TO HOSPITAL")

print("successfully connected")

print('1.RegisteringPatient details')

20 | P a g e
 print('2.RegisteringDoctor details')

print('3.RegisteringWorker details')

print("4.total patient details")

print("5.total doctor details")

print("6.total worker details")

print('7.Patient detail')

print('8.Doctor detail')

print('9.Worker detail')

print('10.Exit')

choice=int(input('ENTER YOUR CHOICE:'))

ifchoice==1:

p_name=input('Enter Patient Name:')

p_age=int(input('Enter Age:'))

p_problems=input('Enter the Problem/Disease:')

p_phono=int(input('Enter Phone number:'))

sql_insert="insert into patient_details

values(""'"+p_name+"',"+str(p_age)

+",'"+p_problems+"',"+str(p_phono)+")"

c1.execute(sql_insert)

print('SUCCESSFULLY REGISTERED')

conn.commit()

elifchoice==2:

d_name=input('Enter Doctor Name:')

d_age=int(input('Enter Age:'))

d_department=input('Enter the Department:')

21 | P a g e
 d_phono=int(input('Enter Phone number:'))

sql_insert="insert into doctor_details

values(""'"+d_name+"',"+str(d_age)

+",'"+d_department+"',"+str(d_phono)+")"

c1.execute(sql_insert)

print('successfully registered')

conn.commit()

elifchoice==3:

w_name=input('Enter Worker Name:')

w_age=int(input('Enter Age:'))

w_workname=input('Enter type of work:')

w_phono=int(input('Enter Phone number:'))

sql_insert="insert into worker_details

values(""'"+w_name+"',"+str(w_age)

+",'"+w_workname+"',"+str(w_phono)+")"

c1.execute(sql_insert)

print('successfully registered')

conn.commit()

elifchoice==4:

sql_w='select*from patient_details '

c1.execute(sql_w)

r = c1.fetchall()

for i in r :

print(i)

22 | P a g e
 elif choice==5:

sql_x="select*from doctor_details"

c1.execute(sql_x)

s=c1.fetchall()

for i in s:

print(i)

elif choice==6:

sql_y="select*from worker_details"

c1.execute(sql_y)

t=c1.fetchall()

for i in t:

print(i)

elif choice==7:

h=input("Enter the name:")

sql_w='select*from patient_details where

p_name=("{}")'.format(h)

c1.execute(sql_w)

u = c1.fetchall()

for i in u:

print(i)

elif choice==8:

d=input("Enter the name:")

23 | P a g e
 sql_d='select*from doctor_details where

p_name=("{}")'.format(d)

c1.execute(sql_d)

v=c1.fetchall()

for i in v:

print(i)

elif choice==9:

f=input("Enter the name:")

sql_f='select*from worker_details where

p_name=("{}")'.format(f)

c1.execute(sql_f)

w=c1.fetchall()

for i in w:

print(i)

elif choice==10:

exit()

break

else:

print('wrong username&password')

if choice==2:

exit()

24 | P a g e
 OUTPUT

Login output:

After login:

25 | P a g e
After choosing choice:

26 | P a g e
TESTING

Software Testing is an empirical investigation conducted to provide

stakeholders with information about the quality of the product or service
under test [1] with respect to the context in which it is intended to
operate. Software Testing also provides an objective, independent view
of the software to allow the business to appreciate an d u n d e r s t a n d
t h e r i s k s a t im p lem e n t a t ion o f t h e so f t w ar e . Test techniques
include, but are not limited to, the process of executing a program or
with the intent of finding software bugs.
It can also be stated as the process of validating and verifying that
a software program/application/product meets the business and
technical requirements that guided its design and development, so that it
works as expected and can be implemented with the same
characteristics. Software Testing, depending on the testing method
employed, can be implemented at any time in the development process,
however the most test effort is employed after the requirements have
been defined and coding process has been completed.

TESTING METHODS
Software testing methods are traditionally divided into black box
testing and white box testing. These two approaches are used to
describe the point of view that a test engineer takes when designing
test cases.

BLACK BOX TESTING

Black box testing treats the software as a "black box," without any
knowledge of internal implementation. Black box testing methods
include: equivalence partitioning, boundary value analysis, all-pairs
testing, fuzz testing, model-based testing, traceability matrix etc
27 | P a g e
SPECIFICATION-BASED TESTING

Specification-based testing aims to test the functionality of

software according to the applicable requirements.[16] Thus, the tester
inputs data into, and only sees the output from, the test object. This level
of testing usually requires thorough test cases to be provided to the
tester, who then can simply verify that for a given input, the output value
(or behavior), either "is" or "is not" the same as the expected value
specified in the test case. Specification-based testing is necessary, but it
is insufficient to guard against certain risks

28 | P a g e
ADVANTAGES AND DISADVANTAGES

The black box tester has no "bonds" with the code, and a tester's perception
is very simple: a code must have bugs. Using the principle, "Ask and you shall
receive," black box testers find bugs where programmers don't. But, on the other
hand, black box testing has been said to be "like a walk in a dark labyrinth without a
flashlight," because the tester doesn't know how the software being tested was
actually constructed.
That's why there are situations when (1) a black box tester writes many test
cases to check something that can be tested by only one test case, and/or (2) some
parts of the back end are not tested at all. Therefore, black box testing has the
advantage of "an unaffiliated opinion," on the one hand, and the disadvantage of
"blind exploring," on the other.

WHITE BOX TESTING

White box testing, by contrast to black box testing, is when the tester has
access to the internal data structures and algorithms (and the code that implement
these)

Types of white box testing:-

The following types of white box testing exist:
API testing - Testing of the application using Public and Private APIs.
Code coverage - creating tests to satisfy some criteria of code
coverage.
For example, the test designer can create tests to cause all statements in the
program to be executed at least once.
Fault injection methods.
Mutation testing methods.
Static testing - White box testing includes all static testing.

29 | P a g e
CODE COMPLETENESS EVALUATION

White box testing methods can also be used to evaluate the completeness of
a test suite that was created with black box testing methods. This allows thesoftware
team to examine parts of a system that are rarely tested and ensures that the most
important function points have been tested.

Two common forms of code coverage are:

Function Coverage: Which reports on functions executed and
Statement Coverage: Which reports on the number of lines executed
to complete the test.
They both return coverage metric, measured as a percentage

30 | P a g e
 HARDWARE AND SOFTWARE REQUIREMENTS

I. OPERATINGSYSTEM : WINDOWS 10 AND ABOVE

II. PROCESSOR : PENTIUM(ANY) OR AMD

ATHALON(3800+- 4200+ DUALCORE)

III. MOTHERBOARD : 1.845 OR 915,995 FOR PENTIUM 0RMSI

K9MM-V VIA K8M800+8237R PLUS

CHIPSET FOR AMD ATHALON

IV. RAM : 512MB+

V. Hard disk : SATA 40 GB OR ABOVE

VI. CD/DVD r/w multi drive combo: (If back up required)

VII. FLOPPY DRIVE1.44MB : (If Back up required)

VIII. MONITOR 14.1 or 15 -17inch

IX. Key board and mouse

X. Printer : (if print is required – [Hardcopy])

SOFTWARE REQUIREMENTS:

I. Windows OS
II. Python
III. MySQL

31 | P a g e
 BIBLIOGRAPHY

1. Computer science With Python -ClassXI By: SumitaArora

2. A Project Report on Blood Bank Management System(BBMS)
By: Praveen MJigajinni
3. Website:https://www.w3resource.com
4. Website: https://csip4.com

***

32 | P a g e
Thank
You…

33 | P a g e