for

Hospital
Prepared by :

Roll No. Name of the Student Email ID

38 Janvi Ramesh Mungekar [email protected]

60 Mandar Purushottam Raorane [email protected]
44 Poorva Anand Palkar [email protected]
13 Rahul Baban Ghadshi [email protected]
49 Prathamesh Uttam Parsekar [email protected]

Instructor: Prof. Priyanka Bandagale

Course: Software Engineering
Date: 18-Aug-2022
Table of Contents ii
Revision History ii
1. Introduction 1
1.1 Purpose 1
1.2 Product Scope 1

2. Description 2
2.1 Product Perspective 2
2.2 Product Features 2
2.3 Design and Implementation Constraints 2
2.4 Assumptions and Dependencies 3
3. External Interface Requirements 3
3.1 User Interfaces 3
3.2 Hardware Interfaces 3
3.3 Software Interfaces 3
3.4 Communications Interfaces 3
4. Functional Requirement 4
4.1 Description 4
4.2 Technical issues 4
5. Software Requirement Analysis 4
5.1 Define Problem 4
5.2 Define Module and Functionality 5
Database design 5
6. Non Functional Requirements
6.1 performance
6.2 Security
6.3 Reliability
6.4 Availiability
6.5 Safety
6.6 Software quality
6.7 Reusability
6.8 Maintainability
 ose

The project is about to handle all the information of the student regarding admission and
tion. Also it manages resources which were managed and handled by manpower previously. The
pose of the project is to integrate distinct sections of the organization into consistent manner so that
functions can be handled smoothly by any technical or non-technical persons.
ect aims at the following matters:
To manage information of student, faculty and courses.
Consistently update information of all the students.
n purpose of the Admin Module is to introduce new things and configure important aspects. For e.g.
min is authorized to introduce quota, board, subject, category, etc. and only admin is allowed to
e exam and set fees structure. So the master screens for all these are visible to only admin role. This
by the Admin Module.
 1.2 Product Scope
The scope of the project includes the following:

 Any college can use this system as it is not client centric.

 All admission and examination related

work for the student can be done using this system.

 Deliver Electronic Workplace

 Provide Bi-lingual support

 Application Support & Maintenance after deployment to production

 The Admin Module can be reused for

projects as well which have many users with different rights.
Hence it is reusablefunctional.

1.3

 This Software Requirement Specification (SRS) is the requirements work

product that formally specifies Hospital Management System(HMS).
 It includes the results of both business analysis and systems analysis efforts
Various technique were used to elicit the requirement and we have identified
your needs, analyzed refined them.
 The objective of this document therefore is to formally describes the system’s
high level requirements including functional requirements, non-functional
requirements and business rules and constraints. The detail structure of this
document is organized as follows:
 Section 2 of this document provides an overview of the business domain that
the proposal Hospital Management System(HMS) will support .
 These includes a general description of the product, user characteristics
,general constraints , and any assumptions for this system.
 This model demonstrates the development team’s understanding of the
business domain and serves to maximize the team’s ability to build a system
that truly does support the business. Section 3 presents the detail
requirement ,which comprise the domain model.

 Urine Test
 X-ray
 Stool Test
 Sonography Test
 Gastroscopy Test
 Blood Test
 Biochemistry Test
  Maintaining patient’s injection entry records

2.1 Product Perspective

 This Hospital Management System is a self-contained system that manages
activities of the hospital as patient Info. Various stakeholders are involved in
the hospital patient info system.

2.2 Product Features

The system functions can be described as follows:

 Registration: When a patient is admitted , the front-desk staff checks to see if the
patient is already registered with the hospital.

 If he is, his/her Personal Health Number(PHN) is entered into computer.

Otherwise a new Personal Health Number is given to this patient.
 The patient’s information such as date of birth, address and telephone number
is also entered into computer system.

Patient check out: If the patient checks out , the administrative staff shall delete his
PHN from the system and the just evacuated bed is included in available-beds list.

Generation: The system generates reports on the following information : list of detailed
information regarding the patient who has admitted in the hospital.

2.3
 Database: The system shall use the SQL, Database, which is open source and free.
 Operating system: The development environment shall be windows 2000.
 Web-based: The system shall be a Web-based application.

2.4 Assumptions and Dependencies

It is assumed that 100 IBM compatible computers will be available before the
system is installed and tested.
 It is assumed that the hospital will have enough trained staff to take care of the
system.

3 Functional Requirements
2.5 User Interfaces
User interface is designed in a user friendly manner and the user,in another end he has to give
the order,for that he will interface with keyboards and mouse.

2.6 Hardware Interfaces

 Operating system: windows
 Hard disk:40 GB
 RAM :256 MB
  Processor: Pentium (R)Dual-core CPU

2.7 Software Interfaces

 Java language.
 Net beans IDE 7.0.1
 MS SQL server 2005

2.8 Interfaces
Windows

3.1 Description:

 The HMS shall allow front-desk staff to add new patients to the
system.
ID:

 The HMS shall allow front-desk staff to give each patient a ID and
add it to the patients records. This ID shall be used by the patient
throughout his/her stay in the hospital

 The administrative staff in the ward shall be allowed to delete the ID

as the patient from the system when the patient checks out.

list:

 The administrative staff in the ward shall be allowed to put the beds
just evacuated in bed-available lists

Report Generation:

Patient information:

 The HPIMS shall generate reports on patients about the following

information:
  Patients PHN , Patients name , Ward name , Bed number and the
Doctors name which was assigned.

 The HPIMS shall generate reports on bed availability about the

following information: Ward name, Bed number occupied/unoccupied.

 Each patient shall have the following mandatory information: First

name, last name , phone number , PHN , address , Postal code, City,
Country , Patient identification number.

 The HPIMS shall allow the user to update any of the patient information
has described in SRS 007 .
: 3.2 issues

 The system shall use the My SQL database , which is open source and
free.

 The development environment shall be windows 2000.

Web Based:

 The system shall be a Web-based application.

 Software
a. Define Problem:

 We develop the Hospital Management system for the hospital staff and other
department that for record for all the user .

b.

 The system functions can be described as follows :

Registration: When a patient is admitted , the front-desk staff checks to see if the
patient is already registered with the hospital. If he is , his/her Personal Health
Number(PHM) is entered into the computer. Otherwise a new PHN is given to this
patient . The patient information such as date of birth, address and telephone numberis
also entered into computer system.

Patient check out: If a patient checks out, the administrative staff shall delete his PHN
from the system and the just evacuated bed is included in available-beds list

5 Database Design
5.1.1
SoftwareRequirementsSpecifcationfor<Project> Page8
6 Non Functional
6.1 Performance:

 Response Time:
The system shall give responses in one second after checking the patients
information.

 Capacity:
The system must support 1000 people at a time .

 User Interface:
The user interface screen shall respond within 5 seconds .

 Conformity:
The systems must confirm to the Microsoft accessibility.

 Patient Identification:
The system requires the patient to identify himself/herself using PHN .

 Logon ID:
Any user who uses the system shall have a logon ID and password.

 Modification:
Any modification (insert, delete, update) for the database shall be synchronized andonly
by the administrator in the ward .

 Front Desk
Front desk staff shall be able to view all information in HPIMS , add new patients to
HPIMS but shall not able to modify any information in it.

 Administrators rights :
Administrator shall be able to view and modify all information in HPIMS .

6.3 Reliability:
 How general the form generation language its simplicity vs. functionality of the
form language = speeds up form development but does not limit functional .

6.4 Availability:
 The system shall be available all the time.
 6.5 Safety:
 Humans are error-prone , but the negative effects of common errors should be
limited. E.g Users should realize that a given command will deleted data , and we
ask to confirm there intend or have the option to undo.

6.6 Software Quality:

 Good quality of the framework =produces robust , bug free software which contains
all necessary requirements customer satisfaction.

6.7 Reusability:
 Is part of the code going to be used elsewhere = produces simple and independent
code modules that can be reused.

6.8 Maintainability:
 Back up: The system shall provide the capability to back up the data.
 Errors: The system shall keep a log of all the errors.

7
This SRS document is used to give details regarding Hospital patient info
management system . in this all the functional and non functional requirements are
specified in order to get a clear cut idea to develop a project.