Software Requirements Specifications

<Online Hospital Management System>

Project Code:

Internal Advisor:

Dr Muhammad

External Advisor:

Project Manager:

Project Team:

Submission Date:

__________
___________
Project Managers
SignatureDocument

<Project code>
<Version x>

Software Requirements Specifications

Document Information
Category

Information

Customer
Project
Document
Document Version
Identifier
Status
Author(s)
Approver(s)
Issue Date
Document Location

FAST-NU
<Project Title>
Requirement Specifications
1.0
PGBH01-2003-RS
Draft
<Names of all the authors of this document>
PM
Sept. 15, 2003

Distribution

1.
2.
3.

Advisor
PM
Project Office

Definition of Terms, Acronyms and Abbreviations

This section should provide the definitions of all terms, acronyms, and abbreviations required to interpret
the terms used in the document properly.
Term
ASP
RS

Sept. 15, 2003

10

Description
Active Server Pages
Requirements Specifications

Page 2 of2

<Project code>
<Version x>

Sept. 15, 2003

10

Software Requirements Specifications

Page 3 of3

<Project code>
<Version x>

Software Requirements Specifications

Table of Contents
1.INTRODUCTION..................................................................................................................6
Purpose of Document .................................................................................................6
Project Overview.........................................................................................................6
web project of hospital management system...............................................................6
Two user levels:...........................................................................................................6
Administrative..............................................................................................................6
users.............................................................................................................................6
System has following functionalities:..........................................................................6
Reception Managent....................................................................................................6
Patient Registration(outdoor & indoor)......................................................................6
Out Patient Management ............................................................................................6
Outdoor Patient billing................................................................................................6
Indoor patient Management........................................................................................6
Indoor Billing..............................................................................................................6
Store.............................................................................................................................6
Financial Accounting..................................................................................................6
Payroll.........................................................................................................................6
Password Recovery for user by asking question.........................................................6
Precscription, Precautions and diet advice will be automatically updated to database
.....................................................................................................................................6
Patient detailed report Precscription and Billing report can be generated as user wants
.....................................................................................................................................7
....................................................................................................................................7
Scope............................................................................................................................7
2.OVERALL SYSTEM DESCRIPTION..........................................................................................7
User characteristics.....................................................................................................7
Operating environment................................................................................................7
System constraints.......................................................................................................7
3.EXTERNAL INTERFACE REQUIREMENTS..................................................................................8
Hardware Interfaces....................................................................................................8
Software Interfaces......................................................................................................8
Communications Interfaces.........................................................................................8
4.FUNCTIONAL REQUIREMENTS...............................................................................................9
5.NON-FUNCTIONAL REQUIREMENTS.......................................................................................9
Performance Requirements.........................................................................................9
2 Safety Requirements.................................................................................................9
Security Requirements.................................................................................................9
8.5 Business Rules.......................................................................................................9

Sept. 15, 2003

10

Page 4 of4

<Project code>
<Version x>

Software Requirements Specifications

List any operating principles about the product, such as which individuals or roles can
perform which functions under specific circumstances. These are not functional
requirements in themselves, but they might imply certain functional requirements to enforce
the rules. Mention all users who will be accessing the software and describe their
respective rights...........................................................................................................9
User Documentation....................................................................................................9
6.ASSUMPTIONS AND DEPENDENCIES.......................................................................................9
7.REFERENCES...................................................................................................................10
8.APPENDICES....................................................................................................................10

Sept. 15, 2003

10

Page 5 of5

<Project code>

Software Requirements Specifications

<Version x>

Section

1. Introduction

Purpose of Document

This is online project of hospital management system.

System has two user levels :
Administrative
Users
Frontend users
Back end users related to hospital
The system has some facilities given below:
Overall patient details
Billing facility
Improve work efficency
Enhance patient care
Help in efficient management of hospital
Project Overview
web project of hospital management system
Two user levels:

Administrative
users
System has following functionalities:
Reception Managent
Patient Registration(outdoor & indoor)
Out Patient Management
Outdoor Patient billing
Indoor patient Management
Indoor Billing
Store
Financial Accounting
Payroll
Password Recovery for user by asking question
Precscription, Precautions and diet advice will be automatically updated to database
Sept. 15, 2003

Page 6 of 10

<Project code>

Software Requirements Specifications

<Version x>

Patient detailed report Precscription and Billing report can be generated as user
wants

Scope

This system will provide separate billing method for indoor and outdoor patients.
It can be used in any hospital,labs,dispensary and clinics for maintaining patient record.
Online project is very useful as compared to desktop application.

Administrator will check condition of hospital environment by internet at any time any place anywhere.
Also provide facility to developer in case of any error may cause in system. Developer will solve
problem by correcting backup which is on domain.
It is usefull to many user which belong to hospital or not. Front end of system has just information about
hospital events. and backend have information which is only useful for administrator

2. Overall System Description

Describe the environment, in which the system will be developed and used, the anticipated users of the system and the
known constraints, assumptions and dependencies.

User characteristics
Every user must have:
Comfortable of working with computer
He must have knowledge in medical field
He must have also have basic knowledge of English.
Know about internet

Operating environment
This project is online application to be developed in php having mysql as database

Database design (MYSQL)

Interface Design (PHP)
Coding (PHP)

System constraints
System constraints have following constraints:

Software constraints
Operating system
Win-98, Win-XP, or any other

Data Base
Xammp(Mysql)

higher version
Sept. 15, 2003

Page 7 of 10

<Project code>

Software Requirements Specifications

<Version x>

Hardware constraints
Processor
Pentium III,
Pentium IV or
higher

RAM
128
MB
Higher

or

Cultural constraints

English will be primary language.

Legal Constraints:

User should follow website policy and rules.

Environmental constraints

(e.g., the environment where the software will be installed, It could be a noisy environment, which may require
that there is no sound event in the project).

User constraints
Different types of user used this system like patients,doctors,health care person,or anyother.
But patients and doctors are most prominent user of this system

3. External Interface Requirements

This section is intended to specify any requirements that ensure that the new system will connect properly to external
components. Place a context diagram showing the external interfaces at a high level of abstraction.

Hardware Interfaces
Describe the characteristics of each interface between the software and hardware components of the system. This
description might include the supported device types, the nature of the data and control interactions between the
software and the hardware.

Software Interfaces
Describe the connections between this system and other external software components (identified by name and version),
including databases, operating systems, tools, libraries, and integrated commercial components. Identify and describe
the purpose of the data items or messages exchanged among the software components. Describe the services needed and
the nature of the inter-component communications. Identify data that will be shared across software components.

Communications Interfaces
Sept. 15, 2003

Page 8 of 10

<Project code>

Software Requirements Specifications

<Version x>

Describe the requirements associated with any communication functions the system will use, including e-mail, web
browser, network communications standards or protocols, electronic forms, and so on. Define any pertinent message
formatting. Specify communication security or encryption issues, data transfer rates, and synchronization mechanisms.

4. Functional Requirements
This section should contain a textual description of the requirements related to the customers business. This should
contain a list of all the business events related to the business process.

5. Non-functional Requirements

Performance Requirements
The performance characteristics of the system that are required by the business should be outlined in this section.
Performance characteristics include the speed, precision, capacity, safety, and reliability of the software. These
characteristics define the performance of the project.

2 Safety Requirements
Specify the requirements that are concerned with possible loss, damage, or harm that could result from the use of the
system. Define any safeguards or actions that must be taken, as well as potentially dangerous actions that must be
prevented. Identify any safety certifications, policies, or regulations to which the system must conform.

Security Requirements
Specify any requirements regarding security, integrity, or privacy issues that affect the use of the system and protection
of the data used or created by the system. Define all user authentication or authorization requirements, if any. Identify
any security or privacy policies or certifications the system must satisfy.

8.5 Business Rules

List any operating principles about the product, such as which individuals or roles
can perform which functions under specific circumstances. These are not functional
requirements in themselves, but they might imply certain functional requirements to
enforce the rules. Mention all users who will be accessing the software and describe
their respective rights.

User Documentation
List the user documentation components that will be delivered along with the software, such as user manuals, online
help, and tutorials.

6. Assumptions and Dependencies

List any assumed factors that could affect the stated requirements. These factors are not system constraints, but areas
where future changes might drive changes in the requirements. The project could be affected if these assumptions are
incorrect, are not shared, or changed.

Sept. 15, 2003

Page 9 of 10

<Project code>

Software Requirements Specifications

<Version x>

Also, identify any dependencies the project has on external factors. For example, if you expect to integrate into the
system some components that are being developed by another project, you are dependent upon that project to supply the
correctly operating components on schedule.

7. References
This section should provide a complete list of all documents referenced at specific point in time. Each document should
be identified by title, report number (if applicable), date, and publishing organization. Specify the sources from which
the references can be obtained. (This section is like the bibliography in a published book).
Ref. No.
PGBH012003Proposal

Document Title
Project Proposal

Date of Release/ Publication

Oct 20, 2003

Document Source
<Give the path of your
Project repository/Folder>

8. Appendices
This section should include supporting detail that would be too distracting to include in the main body of the document.

Sept. 15, 2003

Page 10 of 10