Software Engineering

SRS

NED University of Engineering & Technology Department of Computer & Information Systems Engineering

Software Requirements
Specification
for

HOSPITAL MANAGEMENT
DATABASE
Version 1.1

Prepared by

Group ID: 22
ALISHBA ALI
HAJRA AHMED
HAFIZA RIDA RAO

CS-073
CS-107
CS-110

Instructor:

[email protected]
[email protected]
[email protected]

SIR KASHIF ASRAR

SEPTEMBER 7TH , 2015

Software Engineering

SRS

NED University of Engineering & Technology Department of Computer & Information Systems Engineering

Contents
REVISIONS.................................................................................................................................................................II
1

INTRODUCTION............................................................................................................................................1-3
1.1
1.2
1.3
1.4
1.5
1.6

OVERALL DESCRIPTION............................................................................................................................4-8
2.1
2.2
2.3
2.4
2.5
2.6
2.7

EXTERNAL INTERFACE REQUIREENTS.................................................................................................. 9

FUNCTIONAL REQUIREMENTS......................................................................................................... 9-10
BEHAVIOUR REQUIREMENTS.............................................................................................................. 11

OTHER NON-FUNCTIONAL REQUIREMENTS..................................................................................12-13

4.1
4.2
4.3

PRODUCT PERSPECTIVE...................................................................................................................... 4
PRODUCT FUNCTIONALITY................................................................................................................... 5
USERS AND CHARACTERISTICS........................................................................................................ 5-6
OPERATING ENVIRONMENT.................................................................................................................. 6
DESIGN AND IMPLEMENTATION CONSTRAINTS......................................................................................7
USER DOCUMENTATION.................................................................................................................... 7-8
ASSUMPTIONS AND DEPENDENCIES..................................................................................................... 8

SPECIFIC REQUIREMENTS.....................................................................................................................9-11
3.1
3.2
3.3

DOCUMENT PURPOSE.......................................................................................................................... 1
PRODUCT SCOPE................................................................................................................................ 1
INTENDED AUDIENCE AND DOCUMENT OVERVIEW ...............................................................................1
DEFINITIONS, ACRONYMS AND ABBREVIATIONS.................................................................................1-2
DOCUMENT CONVENTIONS.................................................................................................................. 3
REFERENCES AND ACKNOWLEDGMENTS.............................................................................................. 3

PERFORMANCE REQUIREMENTS........................................................................................................ 12
SAFETY AND SECURITY REQUIREMENTS.......................................................................................12-13
SOFTWARE QUALITY ATTRIBUTES...................................................................................................... 13

OTHER REQUIREMENTS.............................................................................................................................14

APPENDIX A DATA DICTIONARY....................................................................................................................14-

ii

Software Engineering

SRS

NED University of Engineering & Technology Department of Computer & Information Systems Engineering

Revisions
Version

Primary Author(s)

Description of Version

Draft Type
and
Number

Full Name

Information about the revision. This table does

not need to be filled in whenever a document is
touched, only when the version is being
upgraded.

Date Completed
00/00/00

<In this template you will find text bounded by the <> symbols. This text appears in italics and
is intended to guide you through the template and provide explanations regarding the different
sections in this document. There are two types of comments in this document. These
comments that are in black are intended specifically for that course. These comments that are
in blue are more general and apply to any SRS. Please, make sure to delete all of the
comments before submitting the document.
The explanations provided below, do not cover all of the material, but merely, the general
nature of the information you would usually find in SRS documents. It is based on the IEEE
requirements. Most of the sections in this template are required sections, i.e. you must include
them in your version of the document. Failure to do so will result in marks deductions. Optional
sections will be explicitly marked as optional.>

iii

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page1

1 Introduction
1.1 Document Purpose
Every organization requires a database to maintain the record of the timely activities that
are associated with its members. Online access to this record provides ease to the clients
by allowing them the services of searching information and contact the dealers.
HOSPICE+ is an online website that will serve its patients the same way. It will allow
patients to take online suggestion from the doctors. Surgeons will write blogs regarding
the new researches made. Patients will make online appointments by checking availability
of the particular doctors.

1.2 Product Scope

The software is for computerizing the working in a hospital. It takes care of all the
requirements of an average hospital plus covers some extra requirement that are capable
of providing easy and effective storage of information related to all the patients taking
services form that hospital. It can be used for any hospital or clinic for maintaining the
details of patients (their bio data), doctors (their details and appointments) and staff
(nurse on duty, receptionist and accountant).

1.3 Intended Audience and Document Overview

The intended audience is the subject teacher taking it as a project for now and then all the
administrative staff, doctors, nurses, surgeons and developers when converted into a final
product.
This SRS document describes the functions, goals and tasks perform by the system along
with the scope of the project and to plane for the systems design and eventual
implementation

1.4 Definitions, Acronyms and Abbreviations

ASP.NET(Active Server Page)

SRS( Software Requirement Specification)
VS(Visual Studio)
SQL(Structured Query Language)
HTTP (Hyper Text Transfer Protocol) [1]
RMO (Regular Medical Officer)
PHN (Patient Health Number)

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page2

SRS:

A software requirements specification (SRS) is a comprehensive description of the

intended purpose and environment for software under development. The SRS fully
describes what the software will do and how it will be expected to perform.
ASP.NET:
A Microsoft server-side Web technology. ASP.NET takes an object-oriented programming
approach to Web page execution. Every element in an ASP.NET page is treated as an
object and run on the server. An ASP.NET page gets compiled into an intermediate
language by a .NET Common Language Runtime-compliant compiler. Then a JIT compiler
turns the intermediate code to native machine code, and that machine code is eventually
run on the processor. Because the code is run straight from the processor, pages load
much faster than classic ASP pages, where embedded VBScript or JScript had to be
continuously interpreted and cached.ASP.NET is used to create Web pages and Web
services and is an integral part of Microsoft's .NET vision.
VISUAL STUDIO:
Microsoft Visual Studio is an integrated development environment (IDE) from Microsoft. It
is used to develop computer programs for Microsoft Windows, as well as web sites, web
applications and web services.
SQL SERVER:
SQL Server is a relational database management system (RDBMS) from Microsoft that's
designed for the enterprise environment. SQL Server runs on T-SQL (Transact -SQL), a
set of programming extensions from Sybase and Microsoft that add several features to
standard SQL, including transaction control, exception and error handling, row
processing, and declared variables.
WEB BASED APPLICATIONS:
A Web-based application refers to any program that is accessed over a network
connection using HTTP, rather than existing within a devices memory. Web-based
applications often run inside a Web browser. However, Web-based applications also may
be client-based, where a small part of the program is downloaded to a users desktop, but
processing is done over the Internet on an external server. Web-based applications are
also known as Web apps.
HTTP:
The HTTP [1] is an application protocol for distributed, collaborative, hypermedia
information systems. HTTP is the foundation of data communication for the World Wide
Web. Hypertext is structured text that uses logical links (hyperlinks) between nodes
containing text.

SERVER:
2

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page3

A computer or computer program which manages access to a centralized resource or

service in a network.

1.5 Document Conventions

This document follows the IEEE formatting requirements. Use Arial font size 11, or 12
throughout the document for text. Use italics for comments. Document text should be
single spaced and maintain the 1 margins found in this template. For Section and
Subsection titles please follow the template. Describe any standards or typographical
conventions that were followed when writing this SRS, such as fonts or highlighting that
have special significance. Sometimes, it is useful to divide this section to several sections,
e.g., Formatting Conventions, Naming Conventions, etc.

1.6 References and Acknowledgments

[1] Hyper Text Transfer Protocol.
http://www.slideshare.net/iffi910/hospital-management-systemdatabase
http://docslide.us/documents/srs-for-hospital-management-system.html

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page4

2 Overall Description

2.1 Product Perspective

This HOSPICE+ is a self-contained system that manages activities of the hospital as bed
assignment, operations scheduling, personnel management and administrative
issues.
It can be used for any hospital for maintaining the details of patients treatments,
consultation timing of doctors and surgeons and on duty nurses and ward boys.
The intentions of the system are to reduce over-time pay and increase the number of
patients that can be treated accurately.

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page5

2.2 Product Functionality

Register:
In this module we basically create a new ID on the website for the person who
Is new to this system using his unique id and a password.
Login:
If a person has an account then he /she can enter through their id and password and
perform the tasks they want.
Add patients, doctors and staff:
A persons record is added when he/she has registered.
Modify patients, doctors and staff:
A persons record is modified as per the requirements.
Search patients, doctors and staff:
A persons record can be searched by their names, ids and designation.
Delete patients, doctors and staff:
If the person checks out, the administrative staff must delete his entry from the system.

2.1 Users and Characteristics

The system will be mainly used in the hospital by the administrative staff, front-desk staff
and then by doctors and surgeons. End users also include patients and who ever visit the
website.
Front end staff:
They are responsible for patients check in or notification of appropriate people.
Administrative staff:
They are responsible for scheduling and updating day/night employee shifts.
Doctors and Surgeons:
Doctors may manage their information and post blogs for patients based on different
researches
Patients and other users:
5

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page6

Whoever (Patients or others) visits the website will be allowed to read all the blogs and
limited information of particular doctors and surgeons.

2.2 Operating Environment

Hardware Requirements:
Computer that has a 1.6GHz or faster processor.
1 GB (32 Bit) or 2 GB (64 Bit) RAM (Add 512 MB if running in a virtual machine).
3GB of available hard disk space.
5400 RPM hard disk drive.
Software Requirements:
Windows XP ,Vista , 7, 8 , 8.1
Visual Studio 2010 or 2013
SQL Server 2008 edition

2.3 Design and Implementation Constraints

Both the hospital and physician database will need large storage capabilities and a
process to archive outdated data.
The time may limit some of the functionalities of the system.
Hardware, software, and data communication elements must be sourced within
budgetary constraints.
Project involves the use of new languages. (Lack of skilled members).
Lack of dedicated Product Manager to make critical trade off decisions about the
conflicting requirements.

2.4 User Documentation

For Front end staff:
Go to the search menu on the top and enter the required password. No need to register
since they can only search if the rooms and bed are available.
6

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page7

For Administrative staff:

Go to the login menu and login as admin. You can manage staff members, doctors and
patients there. You can also edit the overall information of hospital like editing the contacts
etc.
For Doctors and Surgeons:
Go to the registration menu from the menus at the top.
Sign In page will be opened. In order to sign in enter username and password to
appropriate fields and click Sign In button.
Right after login you will be presented with a user account home page where you can
manage your account by adding, deleting and modifying your professional and personal
information, write blogs and reply to the patients who ask for your suggestions.

For Patients:
If you want to make an appointment then first register yourself as a patient and for that go
to the registration menu at the top.
Sign In page will be opened. In order to sign in enter username and password to
appropriate fields and click Sign In button.
Right after login you will be presented with a user account home page where you can read
different research based blogs by specialist doctors or consultants. You can also ask for a
suggestion from the respective doctors and then make appointments by checking their
availability.

2.5 Assumptions and Dependencies

The system shall use SQL Server 200 database.

The development environment shall be windows 7, Vista, 8, 8.1.
The system shall be a web based application supporter.
It is assumed that Hospital will have enough trained staff to take care of the system.
Only two categorised of doctors are covered i.e. consultants and RMOs.
Only the consultant doctors are allowed to write blogs.
The module does not depend on any external services.

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page8

3 Specific Requirements
3.1 External Interface Requirements
3.1.1 User Interfaces
The software provides good graphical interface for the user. Any administator can operate
on the system performing the required task such as create, update and viewing the details
of the appointment.
3.1.2 Hardware Interfaces
Hard disk: 40 GB
RAM : 25MB6
Processor: Pentium dual core and onwards
3.1.3 Software Interfaces

ASP.Net
SQL Server 2008
Visual studio 2010
Operating system : windows

SoftwareRequirementsSpecificationforHospitalManagementDatabase
Page9

3.1.4 Communications Interfaces

3.2 Functional Requirements

Register:
When a patient is admitted, the font desk staff checks to see if the patients is already
registered with the hospital. If his/her personal health number (PHN) is entered into the
system otherwise a new PHN is given to this patient. The patient information such as
Name, age ,gender, date of birth, address, telephone no., date of admission and
discharge, type etc. is entered into the system
Login:
If a person has an account then he /she can enter through their id and password and
perform the tasks they want.
Add patients, doctors and staff:
A persons record is added when he/she has registered. Patients record include persons
name, PHN, age ,gender, date of birth, address, telephone no., date of admission and
discharge, type etc. patients are categorized as OPD or WARD patients wheras doctors
can be categorized as MOs and CONSULTANTS.salary is an additional attribute for the
staff members and doctors.
Modify patients, doctors and staff:
A persons record is modified as per the requirements. Patients record such as
address,tel no., date of discharge can be modified.
Search patients, doctors and staff:
A persons record can be searched by their names, PHN and designation.
Delete patients, doctors and staff:
If the person checks out, the administrative staff must delete his entry from the system.
A doctors / staff members entry is deleted,if he leaves the hospital.

SoftwareRequirementsSpecificationforHospitalManagementDatabase

Page10

3.3 Behaviour Requirements

3.3.1 Use Case View

10

SoftwareRequirementsSpecificationforHospitalManagementDatabase

Page11

11

SoftwareRequirementsSpecificationforHospitalManagementDatabase

Page12

4 Other Non-functional Requirements

4.1 Performance Requirements
Response Time:
The system shall give response in 1 second after checking the patients
information.
Capacity:
System must support 1000 people at a time at maximum.
User Interface:
The user interface screen shall respond within 5 seconds.

4.2 Safety and Security Requirements

Login ID:
A user who uses the system shall have a login Id and password.
Administrators rights:
Administrator shall be able to view , modify , add and delete any information .
Patients Rights:
Patients can view filtered data of the consultants for the appointment purpose.
Patients identification:
The system requires the patient to identify himself/herself using PHN.
Modification:
Any modification (insert, delete, update) for the database shall be synchronized
and only by the administrator.
Front Desk staff rights:

12

SoftwareRequirementsSpecificationforHospitalManagementDatabase

Page13

Front desk staff shall be able to view all information in hospitals but shall not be
able to modify any information in it.

Doctors/Surgeons rights:
Doctors can edit their personal information on website, write blogs and give
suggestions to the patients.

4.3 Software Quality Attributes

Availability:
The system shall be available all the time.
Safety:
Humans are error prone, but the negative effects of common errors should be
limited. For example, users should realize that a given command will delete data,
and be asked to confirm their intent.
Software Quality:
Good quality of the framework will produce bug free software which contains all
necessary requirements Customer satisfaction..
Reusability:
Produce simple and independent code modules that can be reused.
Understandability:
The code must be clear for the developer to keep track of the maintenance easily.
Portability:
Software is compatible enough to support certain versions of the tools used.

13

SoftwareRequirementsSpecificationforHospitalManagementDatabase

Page14

5 Other Requirements
Not applicable for our project.

Appendix A Data Dictionary

A:
Audience ______________________________________________________________ 1
Acronym ______________________________________________________________ 1
Abbreviation____________________________________________________________ 1
ASP.Net ______________________________________________________________ 1
Acknowledgement _______________________________________________________ 3
Administrative staff ______________________________________________________ 5
Assumptions ___________________________________________________________ 8
Administrator ___________________________________________________________ 9
Appointment ___________________________________________________________11
Availability_____________________________________________________________13
Attributes _____________________________________________________________13

C:
Convention ___________________________________________________________ 3
Characteristics ________________________________________________________ 5
Computer ____________________________________________________________ 6
Constraints ___________________________________________________________ 7
Communication _______________________________________________________ 9
Consultant ___________________________________________________________ 10
Capacity _____________________________________________________________ 12

D:
Document ____________________________________________________________ 1
Delete _______________________________________________________________ 5
Design _______________________________________________________________ 5
14

SoftwareRequirementsSpecificationforHospitalManagementDatabase

Page15

Dependency ___________________________________________________________ 8

E:
External ______________________________________________________________ 9
Environment ___________________________________________________________ 6

F:
Front _________________________________________________________________ 7
Functional _____________________________________________________________ 9

H:
Hospice+ ____________________________________________________________
Hospital ______________________________________________________________
HTTP ________________________________________________________________
Hardware _____________________________________________________________

1
1
1
9

I:
Intended ______________________________________________________________ 1
ID ___________________________________________________________________12
Interface ______________________________________________________________12

L:
Login _________________________________________________________________ 4

M:
Modify ________________________________________________________________10

O:
Overview ______________________________________________________________ 1
Overall ________________________________________________________________ 4
Operating _____________________________________________________________ 6

P:
Purpose ______________________________________________________________ 1
Product _______________________________________________________________ 1
PHN _________________________________________________________________ 1
Perspective ___________________________________________________________ 4
Patient _______________________________________________________________ 6
Performance __________________________________________________________ 12
Portability ____________________________________________________________ 13

Q:
15

SoftwareRequirementsSpecificationforHospitalManagementDatabase

Page16

Quality _______________________________________________________________ 12

R:
Register ______________________________________________________________ 9
Requirement __________________________________________________________ 9
Response ____________________________________________________________ 12
Reuseability __________________________________________________________ 13

S:
Scope _______________________________________________________________ 1
SRS _________________________________________________________________ 1
SQL _________________________________________________________________ 1
Software ______________________________________________________________1
Server ________________________________________________________________2
Search _______________________________________________________________ 4
Security ______________________________________________________________ 12

U:
User _________________________________________________________________ 5
Understandability _______________________________________________________13

V:
Visual studio ___________________________________________________________ 1
View _________________________________________________________________11

W:
Web _________________________________________________________________ 2

16

SoftwareRequirementsSpecificationforHospitalManagementDatabase

Page17

17