Project Name: Hospital Management System Academic Year: 2019-2020

Subject Name: Software Engineering Semester: Fourth

[ college logo ]
A STYDY ON

Hospital Management System

MICRO PROJECT REPORT

Submitted in March 2020 by the group of 4 Students
Sr. Roll No Enrollment Seat No
Full name of Student
No (Sem- No (Sem-
iv) iv)
1 0
2
3
4

Under the Guidance of

[ your guide name ]
in
Three Years Diploma Program in Engineering & Technology of Maharashtra
State Board of Technical Education, Mumbai (Autonomous)
ISO 9001:2008 (ISO/IEC-27001:2013)
at

[ your collge name ]

1
 MAHARASHTRA STATE BOARD OF TECHNICAL
EDUCATION, MUMBAI

Certificate
This is to certify that Mr. /Mrs.

Roll No: of Fourth Semester of Diploma

in Engineering & Technology at [ your college name ] , has completed the Micro

Project satisfactorily in Subject SEN in the academic year2019-2020 as per the

MSBTE prescribed curriculum of I Scheme.

Place: Pune Enrollment No:

Date: / /2020 Exam Seat No:

Project Guide Head of the Department Principal

2
 INDEX

Sr. Title Page No.

Abstract 4
1. Introduction 5
2. Literature Survey 6
3. Problem Statement 7
4. Process Model 8-10
5. Application Requirements 11
6. SRS 12-14
7. Use Case Diagram 15
8. DFD 16-17
9. Class Diagram 18
10. Preparation of RMMM 19-20
11. Timeline Chart 21
12. SQA Plan 22
13. Conclusion 23
14. References 23

Abstract

3
The Hospital Management System is designed for any hospital to replace their existing manual
paper-based system. The project Hospital Management System includes registration of patients,
storing their details into the system, and also computerize billing in the pharmacy, and labs. The
purpose entitled as “Hospital Management System” is to computerize the Front Office
Management of Hospital to develop software which is user friendly, simple, fast, and cost-
effective. The new system is to control the information of the patients. Room availability, staff
and operating room schedules and patient invoices. The proposed system gives the information
about the day-to-day activities of the Hospital like, Room activities, Admissions of new patient,
Discharge of patients, assign a doctor, and finally compute the bill etc.
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. These services are to be provided in an
efficient, cost effective manner, with the goal of reducing the time and resources required for
such tasks.

4
 Introduction

“Hospital Management System” is developed to computerize the following functions that are
performed by system:
Using this hospital management System user can take online appointments with the doctors:
Admin can register new patient through this system.
Admin can also check the Discharge Detail of a patient from discharge report generated by the
system. Admin can discharge the patient through the system and this information will display to
other users like receptionist and accountant.
This system also keeps record of Patient’s Disease. Admin can also check the report of admitted
patient or admitted patient’s time.
Hospital Management System provides the benefits of streamlined operations, enhanced
administration & control, superior patient care, strict cost control and improved profitability.
The software has the facility to give a unique id for every patient and stores the details of every
patients and the staff automatically. It deals with the collection of patient’s information,
diagnosis details, etc. Traditionally, it was done manually. It includes a search facility to know
the current status of each room. User can search availability of a doctor and the details of a
patient using the id.
The main function of the system is register and store patient details and doctor details and
retrieve these details as and when required. The manual handling of the record is time consuming
and highly prone to error. Hospital Management System is powerful, flexible, and easy to use.
Hospital Management System can be entered using a username and a password. To improve the
performance of hospital management system, the computerized hospital management system
needs to be undertaken. It is accessible either by an administrator or a receptionist. Only they can
add the data into the database. The data can be retrieved easily. Hospital Management System is
designed for multispecialty hospitals, to cover a wide range of hospital administration and
management processes.

5
 Literature Survey

Title of the book Author Publication

A Handbook of Agile
Software Craftsmanship Robert C. Martin Paperback

Elements of Reusable
Object-Oriented Software Erich Gamma Hardcover
Driven Design: Tackling
Complexity in the Heart of Eric Evans Hardcover
Software (Hardcover)
People ware: Productive Tom DeMarco
Projects and Teams Paperback
Extreme Programming Kent Beck
Explained: Embrace The XP Series
Change

6
 Problem Statement

The problem statement is the initial starting point for a project. It is basically one to three pages
statement that everyone on the project agrees with that describes what will be done at a high
level. The problem statement is independent for a broad audience and should be written in non-
technical terms. It helps the non-technical and technical person communicate by providing a
description of a problem.

The project entitled Hospital Management System provides the basic functionalities needed to
be handled in a hospital management environment.

7
 Process Model
The Waterfall Model was the first Process Model to be introduced. It is also referred to as a
linear-sequential life cycle model. It is very simple to understand and use. In a waterfall model,
each phase must be completed before the next phase can begin and there is no overlapping in the
phases. The Waterfall model is the earliest SDLC approach that was used for software
development.

Waterfall Model - Design

Waterfall approach was first SDLC Model to be used widely in Software Engineering to ensure
success of the project. In "The Waterfall" approach, the whole process of software development
is divided into separate phases. In this Waterfall model, typically, the outcome of one phase acts
as the input for the next phase sequentially.

The following illustration is a representation of the different phases of the Waterfall Model.

Fig. Waterfall Model

The sequential phases in Waterfall model are –

8
Requirement Gathering and analysis − All possible requirements of the system to be
developed are captured in this phase and documented in a requirement specification document.

System Design − the requirement specifications from first phase are studied in this phase and
the system design is prepared. This system design helps in specifying hardware and system
requirements and helps in defining the overall system architecture.

Implementation − with inputs from the system design, the system is first developed in small
programs called units, which are integrated in the next phase. Each unit is developed and tested
for its functionality, which is referred to as Unit Testing.

Integration and Testing − All the units developed in the implementation phase are
integrated into a system after testing of each unit. Post integration the entire system is tested for
any faults and failures.

Deployment of system − Once the functional and non-functional testing is done; the product
is deployed in the customer environment or released into the market.

Maintenance − There are some issues which come up in the client environment. To fix those
issues, patches are released. Also to enhance the product some better versions are released.
Maintenance is done to deliver these changes in the customer environment.

9
 Application Requirements
Functional Requirements: The functional requirements are organized in two sections,
requirements of portal and requirements of management computer.

1. Requirements of the Attendance Tracking System-

 Authorization Process
 Tracking Process
 Submit Records

2. Requirements of the Management Computer-

 Tracking
 Record Management

10
  Push Notification

Non-functional Requirements: The system has to be available 24 hours a day, so that the
doctors can keep the information of the patients.

Each computer in different department may processing from several systems at the same time.
The system must be able to use several formats according to the data formats that are provided
by the database of different systems.

Software Requirement Specification (SRS)

1) Introduction

Hospital Management System is developed to computerize the following functions that are
performed by the system:
Using this hospital management system user can take online Appointments with the doctors.
Admin can also check the information about the admitted patient and the patient taking
discharge, like the total number of patients admitted and discharged in the given time in the
hospital.
This helps the admin in the billing process.
This system also keeps the record of the Patient’s disease.
Administrator can also add new doctors in the system and can also check all the list of the
doctors of the hospital.

Purpose

This SRS defines external interface performance and software system attributes requirements of

11
Android Advance Attendance and Tracking Control System. This document is intended for
following group of people:
- Administrative department of the Hospital to keep records of the patients.
- Doctors can have all the information about the patients.
- Doctors keep tracking their patients in case any interruption happens.

2) The Overall Description

Product Perspective

- The Hospital Management System is a single functional unit consisting of various sub
components.
- This system allows the admin, doctors and receptionist to access their patients details
remotely.
- This system allows various other functions apart from just accessing their patient’s
records

Product Functions

The major functions that performs in this system are described as follows:
1. Language Selection: After the user has logged in, the display provides him / her with the
list of departments from which he/she can select any one in order to interact with the
system throughout the session.

2. Account Maintenance: The various functions that a user can perform with his/her
account are as follows – Pupations, Addition and Deletion of data.

3. Cancelling: The user shall abort a record with the press of Cancel key’s

12
3) External Interface Requirements

User Interface Requirements

The interface provided to the user should be a very user friendly one and it should provide an
optional Interactive help each of the functionalities listed. The Interface provided is the menu
driven one and the following screens will be provided:
1. The login screen is provided in the begging for entering the required user name.
2. An unsuccessful login leads to a reattempt screen for again entering the same
information.
3. In case of administrator, a screen will be shown having options to reboot system,
shutdown system, block system and disable any functions.
4. In case of reboot, shutdown, a screen will be displayed to users will to reboot and also
allow the user any backup needed.

4) System Features

- Validity Checks
- In order to gain access to the system the user is required to enter his/her correct user id or
pin number and details filling.
- The user can access only one account at a time.

13
Use Case Diagram

14
Fig. Use Case Diagram for Hospital Management System

Data Flow Diagram (DFD)

15
Fig. Level 0 DFD for Hospital Management System

16
Fig. Level 1 Data flow diagram for Hospital Management System

17
Fig. Class Diagram for Hospital Management System

18
 Preparation of RMMM Plan

The goal of the risk mitigation, monitoring and management plan is to identify as many potential
risks as possible. To help determine what the potential risks are, Game Forge will be evaluated
using the checklists found in section 6.3 of Roger Pressman’s Software Engineering, A
Practitioner’s Approach [Reference is the SEPA, 4/e, see risk checklists contained within this
Web site]. These checklists help to identify potential risks in a generic sense. The project will
then be analyzed to determine any project-specific risks.

THE RISK MANAGEMENT:

The risk management process can be broken down into two interrelated phases, risk assessment
and risk control, as outlined in Figure 1. These phases are further broken down. Risk assessment
involves risk identification, risk analysis, and risk prioritization. Risk control involves risk
planning, risk mitigation, and risk monitoring. It is essential that risk management be done
iteratively, throughout the project, as a part of the team’s project management routine.

19
RISK IDENTIFICATION:

In the risk identification step, the team systematically enumerates as many project risks as
possible to make them explicit before they become problems. There are several ways to look at
the kinds of software project risks, as shown in Table 1. It is helpful to understand the different
types of risk so that a team can explore the possibilities of each of them.

RISK MITIGATION:

Related to risk planning, through risk mitigation, the team develops strategies to reduce the
possibility or the loss impact of a risk. Risk mitigation produces a situation in which the risk
items are eliminated or otherwise resolved. Risky feature.
Accrued by the risk management steps outweigh the costs associated with implementing them

RISK MONITORING:

After risks are identified, analyzed, and prioritized, and actions are established, it is essential that
the team regularly monitor the progress of the product and the resolution of the risk items, taking
corrective action when necessary. This monitoring can be done as part of the team project
management activities or via explicit risk management activities. Often teams regularly monitor
their “Top 10 risks.”
Risks need to be revisited at regular intervals for the team to reevaluate each risk to determine
when new circumstances caused its probability and/or impact to change. At each interval, some
risks may be added to the list and others taken away.

20
 Timeline Chart / Gantt chart

Fig. Timeline chart for Hospital Management System

SQA Plan

SQA is a concept that spans across the entire software development process. It focuses on

21
improving the process of development of software so that problems can be prevented before they
become a major issue. SQA also involves continuous monitoring of the process and making sure
those agreed-upon standards and procedures are followed all along in the development process.

The SQA process usually consists of the following tasks:

1. Process implementation: In this task, the design team in consultation with the
development team and the SQA team prepares a (quality assurance) process for the
development of the software (project). This process is then synchronized with the related
verification and validation, joint review, and audit processes that run concurrently. A plan
is then prepared for the quality assurance process activities/tasks, which is documented
and stored (for the life of the contract of the project).
2. Product assurance: In this task, all plans and tasks are documented including their
execution so that one can assure that all contractual obligations have been fulfilled.
3. Process assurance: In this task, assurance is provided that the software (project) process
complies with all the provisions of the contract and the plans for the process of
development.
4. Assurance of quality systems: In this task, the SQA team monitors the development
process and measures parameters of the software (project), based on which a decision on
the assurance of the software is provided.

Conclusion
In this project we learnt to make Use Case Diagram, Data Flow
Diagram, Class Diagram and Timeline Chart for Hospital
Management System.

22
 References:
MSBTE
MSBTE, Mumbai
Google.com

23
24