1 INTRODUCTION:

1.1 Purpose:

The Hospital Management System (HMS) is a application software

for LIFE-CARE Hospital,Kolhapur.The version of application is 1.0.
This specification document provides complete overview of HMS
including definition,goals,objectives & major capabilities.

1.2 Document conventions:

HMS: HOSPITAL MANAGEMENT SYSTEM.

LIFE-CAREHP: LIFE-CARE Hospital Kolhapur.

1.3 Intended Audiences:

This includes:-

Employees of LIFE-CARE:
- Managers.
- Doctors.
- Other staff(Worker).
Project Incharge:
- Project managers
- Hardware engineers.
- Programmers
- Usability engineers

1.4 References:

1. Software engineering-practitioner’s approach – Roger

Pressman.
2. SRS TEMPLATES.
3. Software engineering fundamentals – Fedrick Hudson.

2 Overall description:

2.1 SCOPE:
HMS is restricted to LIFE-CARE Hospital.
This software provides a medium
to access Manager directly for all staff’s & Patient’s
current live Information
New Staff or Patient records are added to database.
 It does not serve as a database for employees’ official
documents.
Goals:
Reduce overhead of HMS dept head.
New data’s storage.

Benefits:
1. It Provides necessary & current information regarding
Doctor, worker, Patient to Chairman or head authority
So it is not necessary to go HMS head
2. New data’s easily available in database

2.2 Product perspective.:

HMS is self-contained product. It is interactive software

for managing data of new employees in LCHP.

2.3Operating environment :

Operating system: Windows 98,Windows XP and other versions

Of Microsoft Windows.
Software component: SQL server.

2.4 Assumptions & Dependencies:

Software interface of HMS will change depending on future

decisions to maintain any more data about hospital employees.

3 External interface requirements:

3.1 User interface:

Main interface of HMS is a GUI window linked to different

Functions such as to retrieve option that performs search for Staff
Or Patient data’s in database and return relevant records.

3.2 Software interface :

s/w name : SQL server.

Version: 8i
Vendor: Microsoft Corp.
External: server system.

3.3 Hardware interface:

Workstations: Personal computers used by employees in LCHP.

3.4 Memory constraints:

Memory size required depends on number of employee records/

Data’s.

3.5 Communication interface :

Local Area Network, which is internal to LCHP, used for

communication among employees & HRM.
4 Functional requirements :

This section of SRS specifies functional requirements of HMS in terms of

Use cases.

1 Employees of LCHP:

- Reads operating help.

- Access status of leaves.
- Apply for leaves.
- HMS gives result to application of leave.

2 Human resource dept. :

- Login through user interface.

- Add new applicants data’s.
- Delete specific data’s.
- Access status of particular Staff Or Patient.
- Updates database.

5 Other nonfunctional requirements :

5.1 Performance requirement :

This is a multi-user database application. It handles about

10000 Patient & employee records of LCHP.

Response time : All system responses shall occur within

Less than 30 seconds.

5.2 Safety requirements:

The system does not cause any accidental damage to

employee records.
HMS shall:
- Not accidentally loose employee Or Patient
information.
- Accurately maintains leave records.

5.3 Security requirements:

 Important features of HMS are restricted to administrator
mode only. Security is provided through password protection
to avoid any damage to records of employees Or Patients.

Identification / Authentication:

HMS shall identify employees & administrator before

Interacting with them.

5.4 Software quality attributes :

Online leave sanctioning is available from any computer in LCHP.

Maintainability:

Software is divided into easy- to –maintain tables that can be

modified in future to add /delete some attributes of
employees Or Patients.