A

PROJECT REPORT

ON

“HOSPITAL MANAGEMENT”

In partial fulfillment of

Diploma II year (Computer Science & Engineering)

Session 2023-2024

Submitted To: Submitted by:

Mr. Bhagaram patel Raju Kumar

(Assistant Lecturer) Diploma 2nd year, 4th sem

CSE

Department of Computer Science & Engineering

GOVERNMENT POLYTECHNIC COLLEGE JALORE
(RAJASTHAN)
 CERTIFICATE
This is to certify that the CSE project entitled “Hospital Management” has been
carried out by the student/team of college GOVERNMENT POLYTECHNIC
COLLEGE JALORE,(RAJ) under my guidance and supervision in partial
fulfillment of the degree of Bachelor of Engineering in Information
Technology/Computer Science & Engineering of Rajasthan Technical University,
Kota during the academic year 2022-2023.

Student:
1.Raju Kumar

Date:

Place: GPC, JALORE

----------------------------------- --------------------------------------

Mr. Bhagaram patel Mr. Ramkaran patel

Assistant Lecturer Head of Department,

Department of CSE,GPC Department of CSE,GPC

 TABLE OF CONTENTS
SER DESCRIPTION PAGE NO
01. ACKNOWLEDGEMENT 04

02. ABSTRACT 05

03. INTRODUCTION 05

04. OBJECTIVES OF THE PROJECT 05

05. PROPOSED SYSTEM 06

06. SYSTEMDEVELOPMENT LIFE CYCLE (SDLC) 07
07. PHASES OF SYSTEMDEVELOPMENT LIFE CYCLE 08
08. FLOW CHART 15
09. SOURCE CODE 16
10. OUTPUT 19
11. TESTING 20
12. HARDWARE AND SOFTWARE REQUIREMENTS 23
13. BIBLIOGRAPHY 24
 ACKNOWLEDGEMENT

I take this opportunity to express my profound gratitude and deep regards to my

guide (Bhagaram patel) for his exemplary guidance, monitoring and constant
encouragement throughout the course of this thesis. The blessing, help and
guidance given by him time to time shall carry me a long way in the journey of life
on which I am about to embark.

I also take this opportunity to express a deep sense of gratitude to Bhagaram patel,
Assistant Lecturer , GPC, for his/her cordial support, valuable information and
guidance, which helped me in completing this task through various stages.

I am obliged to staff members of (GPC, JALORE), for the valuable information

provided by them in their respective fields. I am grateful for their cooperation
during the period of my assignment.

Lastly, I thank almighty, my parents, brother, sisters and friends for their constant
encouragement without which this assignment would not be possible.

Raju Kumar

Date:
 ABSTRACT

Fast. Accurate and relevant hotel services have been a great demand in a progressive place. This
is because many investors or travelers from faraway places seek to find comfort in terms of their
accommodation and stay in their certain destination. Because of this; the modern technology
world of hotel accommodation has gone into various level-up stages. There must be a system that
will work out to make transactions fast. Accurate and convenient to clients. This system will
accept large scale of data without any inconveniences. Hassle-free as it must, the customer and at
the same time the management can enjoy the chance of being free from complains when it comes
to service provision, in its most accurate way.

PURPOSE AND DESCRIPTION

Hotel Reservation system is designed to be user friendly that provides flexible accommodation
of wide range of requirements. Hotel Reservation system is created to speech up transaction, and
is designed for faster and easy booking online, lesser manpower, and less effort of the clients.

OBJECTIVES

The main objectives of the study focus on three different scenario; 1. To alleviate the need of
having a system that caters hotel reservation. 2. To provide fast and accurate service to clients. 3.
To speed up transactions among clients.

SIGNIFICANCE OF THE STUDY

The relevance of the study does not only benefit clients but tellers or the management as well.
The system can be an efficient...

PROJECT ON HOSPITAL MANAGEMENT SYSTEM

INTRODUCTION
1.The Hospital Management System(HMS) is designed for Any Hospital to replace
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

1. Write programs utilizing modem software tool.

2. Apply object oriented programming principals 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.

5. Students will demonstrate ability to conduct a research or applied computer

science project requiring writing and presentation skills which exemplify
scholarly style in computer science.

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 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 a lot of
paperwork has be done but now software production this organization has mode
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 can 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.

SYSTEM DEVELOPMENT LIFE CYCLE (SDLC)

 The system 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 allocation 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.

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 a 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 Charter which outlines the authority of the project
manager to begin the project.
 Careful oversight is required to ensure project 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 connect 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 solution and detail as many
informational, functional, and network requirements as possible.

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 of the alternatives.

 Identify system interfaces.
 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 to satisfy the basic
functional requirements
 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.
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 risk 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 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, concept
of operations, system security, verification, and systems engineering management
planning.

REQUIREMENTS ANALYSIS PHASE

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),
 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 to-
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 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:

 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

function representatives to ensure that it satisfies the business
requirement Concurrent with the development of the system design, the
Agency Project Manager begins development of the Implementation
Plan, Operations are Maintenance Manual, and the Training Plan.

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 assess the system security
and issue 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 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 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.

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.

FLOW CHART
SOURCE CODE
OUTPUT

Login output:

After login:

After choosing choice:

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 and understand the risks at implementation of the software.
Test techniques include, but are not limited to, the process of executing a program
or application 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 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, exploratory testing and specification-
based testing.

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

ADVANTAGES AND DISADVANTAGES

The black box tester has “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 or 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.