Software Requirements Specification

for

Hospital Management

Version 1.0 approved

Lakshmi Niranjan

LIBA Maveric 11-a

11-07-2014

Software Requirements Specification

Table of Contents

1. Introduction

1.1 Purpose 1.2 Scope 1.3 Definitions, Acronyms, and Abbreviations 1.4 References 5. Overview

2. General Description

2.1 Product Perspective 2.2 Product Functions 2.3 User Characteristics

3. Specific Requirements

3.1 Functional Requirements 3.2 Performance Requirements 3.3 Non-Functional Requirements 3.4 Design Constraints

Appendix

A. 1 Hospital Management Process Diagram

1. Introduction

1. Purpose

Basic Description of Problem

The Administrator and staff of a hospital have been experiencing major headaches in organising and managing patients, beds, and nurses. There have been reports of missing patient information, lack of security and privacy on patient medical history, and confusion in bed allocations. Nurses have complained about mistakes in nurse allocation to patients, and bed management for waiting patients. The manual systems can not handle current demands on hospital staff.

2. Scope

The purpose of this specification is to document requirements for a system to manage the hospital. The specification identifies what such a system is required to do. The specification is written in a format conforming to the IEEE Standard 830-1984. Subject to approval, the specification will complete the Requirements phase and will be followed by detailed design, implementation, and testing.

The product will be labelled the Hospital Management System (HMS). The Hospital Management System will manage a waiting list of patients requiring different treatment. The availability of beds will be