Professional Documents
Culture Documents
Software Requirements Specification - Hospital
Software Requirements Specification - Hospital
SPECIFICATION
HOSPITAL MANAGEMENT
SYSTEM
J.Manogna AP19110010153
K.MohananjaliAP19110010182
SK.HashithaAP19110010301
Table of
Contents
1. Introduction
1.1 Purpose 3
1.2 Scope 3
1.3 Definitions, Acronyms, and Abbreviations 3
1.4 References 4
1.5 Overview 5
2. The Overall Description
2.1 Product Perspective 20
2.2 Product Functions 5
2.3 User Characteristics 7
2.4 Constraints 7
2.5 Assumptions and Dependencies 8
3. External interface Requirements
3.1 User Interfaces 9
3.2 Hardware Interfaces 9
3.3 Software Interfaces 10
3.4 Communications Interfaces 10
4. System Features 10
5. Other Non-Functional Requirements 11
5.1 Performance Requirements 11
5.1.1 Capacity
11
5.1.2 Dynamic Requirements
5.1.3 Quality 12
5.2 Software System Attributes 12
3.6.1 Reliability 12
3.6.2 Availability 12
3.6.3 Security 13
3.6.4 Maintainability 13
5.3 Business Rules 14
1. Introduction
1.1 Purpose
The purpose of this project is to develop software which is user-friendly, cost effective
and fast. It deals with the collection of patient information, doctor information. The
main function of this is to store patients and doctor details and use them for later
purposes. The hospital management system can enter a username and password which
will be accessible by only the doctor, and admin.
1.2 Scope
The technology will be used to collect data from patients, doctors and store it for
later use. A paper-based method is now in use. It is inefficient and unable to supply
updated patient lists in a timely manner and it requires so much space to store the
data. If someone wants details of old patients and doctors, searching for those records
will be a huge task. The system's goals are to minimize overtime pay while also
increasing the number of patients who can be appropriately treated and doctors who
can treat more patients. There are functional and non-functional requirements
statements in this document
1.3 Definitions, Acronyms, and Abbreviations.
i. www.google.co.in
ii. www.winkipedia.com
1.4 Overview
Registration: When a patient is admitted, the staff checks to see if the patient
is already registered with the hospital. If the patient registration number is
entered into the computer or not Otherwise a new registration number is
given to the patient. The patient’s information such as date of birth, address
and telephone number is also entered into the computer system.
Patient check out. If a patient checks out, the administrative staff will delete
the patient's bed details from the system and the just evacuated bed is
included in available-beds list.
The system will be used in the hospital. The administrators and staff will be
the main users. Some users may not know how to use computers. So, some
users may have to be trained on using the system. The system is also designed
to be user-friendly. It uses a Graphical User Interface (GUI).
Staff:
All the staff will have general reception and secretarial duties. Every staff
member has some basic computer training. They are responsible for patient’s
check-in or notification of appropriate people .
Administrators:
They all have post-secondary education relating to general business
administration practices. Every administrator has basic computer training.
They are responsible for all of the scheduling and updating day/night
employee shifts.
Constraints
· It is assumed that the Hospital will have enough trained staff to take care of
the system.
Login module:
This module records only the user and password of the user.
Administration module:
This module enables the user to insert, update, view and delete the patient information.
Patient module:
This module is used to store information about patients who were admitted in the
hospital
→ Patient Id, disease, Doctor, Date of admitted, Date of discharge.
→ Updation like deletion and modification is done.
Doctor’s module:
doctors info such as appointment, doctor activity, no.of patients the doctor is handling,
add doctor, delete doctor is managed.
5.3Business Rules
6 Other Requirements
None.