VELAMMAL VIDYALAYA

ACADEMIC YEAR: 2024-25

PROJECT REPORT ON
HOTEL MANAGEMENT SYSTEM

ROLL NO : 2232071

NAME : Kanisha.S

CLASS : XII

SUBJECT : COMPUTER SCIENCE

PROJECT GUIDE: Ms.ELAMATHI

VELAMMAL VIDYALAYA

MELAYANAMBAKKAM

CHENNAI
ACKNOWLEDGEMENT

Firstly I would like to thank the almighty as this project

“ Hospital Management System”was a successful one. I
hereby express my gratitude towards my school “Velammal
Vidyalaya” for having given me the opportunity to complete
this project. I would also like to thank my benevolent teacher
Ms.Elamathi.E for having given me moral support and for
being the backbone of this project. Finally I would like to
thank my parents for their support and encouragement.
CERTIFICATE
This is to hereby certify that the Computer Science project
had been solely , sincerely and satisfactorily completed by
Kanisha.S of class XII for the practical examination of Central
Board of Secondary Education (CBSE) in the academic year
2024-25

Internal Examiner External Examiner

TABLE OF CONTENTS
TITLE PAGE.
NO
INTRODUCTION 1
PROPOSED SYSTEM 2
EXISTING SYSTEM 2
SYSTEM DEVELOPMENT LIFE CYCLE(SDLC) 3
PLANNING PHASE 5
REQUIREMENT ANALYSE PHASE 6
DESIGN PHASE 6
DEVELOPMENT PHASE 7
INTEGRATION AND TEST PHASE 8
IMPLEMENTATION PHASE 8
OPERATION AND MAINTENANCE PHASE 8
PROGRAM 9
OUTPUT 13
HARDWARE AND SOFTWARE REQUIREMENTS 16
BIBLIOGRAPHY 17
INTRODUCTION:-
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 Integrate the entire Resources of a Hospital into One Integrated
Software Application.

PROPOSED SYSYTEM:-
ADVANTAGES OF HMS:
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 organisations. 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
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.

DISADVANTAGES OF HMS:
1. Lack of privacy

2. Risk in the management of the data.

3. Less security

4. Less user-friendly

5. Accuracy nor guaranteed

6. Not in reach of distant users.

7. There is no storage and automation if users have some enquiry.

EXSISTING SYSTEM:-
In today's world if someone wants to book a Doctor's Appointment we need to call in
clinic or personally go to that place and book the appointment.

This consumes precious time of the patient. Also if the doctor cancels his/her
schedule, the patient does not come to know about it unless he/she goes to the clinic.

SYSTEM DEVELOPED LIFE CYCLE:-

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
functionality.

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 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 validation, and systems engineering
management planning.

REQUIRMENT ANALYTICAL 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 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:
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.

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 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.

OPERATION AND MAINTAINACE 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 reenter 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.