Software Requirements Specification for PHMS System

Software Requirements Specification

   
for patient health management
system
     
16­12­2015

 Subject : Software requirement Engineering
 Submitted by:
 Afaq Cheema           6355
 Muneeb Alam Butt  6316
 Naqash Khan           6325
 Jawad Akhtar          6328
 Submitted to:
                           Sir Khuram Zeeshan.

GC University  Faislabad.
iSoftware Requirements Specification for PHMS System

                                Table of Contents
Table of Contents............................................................................................................................ 
1. Introduction..............................................................................................................................1
1.1 Purpose…………………………………………………………………………………………….1
1.2 Project scope………………………………………………………………………………………1
1.3   Document conventions…………………………………………………………………………….1
1.4 Intended Audience and Reading Suggestions……………………………………………………..1
1.5   Definitions, Acronyms, and Abbreviations………………………………………………………..2
    1.6    Overview…………………………………………………………………………………..2
    1.7    Refrence……………………………………………………………………………………2

2. Overall Description..................................................................................................................2
2.1 Product Perspective........................................................................................................................2
2.1.1 Hardware interfaces.......................................................................................................................2
2.1.1 Software interfaces........................................................................................................................2
2.2 Product Functions...........................................................................................................................3
2.3 User Characteristics........................................................................................................................3
2.4 Assumptions and Dependencies.....................................................................................................3
       
3.   Specific Requirements.............................................................................................................3
3.1 External Interfaces..........................................................................................................................4
3.1.1 User interfaces...............................................................................................................................4
3.1.2 Software Interfaces........................................................................................................................4
3.1.3 Hardware Interfaces.......................................................................................................................4
    3.1.4 Communication interfaces………………...………………………………………………………4

4. Functional Requirements........................................................................................................4
  
   

5.  Nonfunctional Requirements...................................................................................................6
5.1 Performance Requirements.............................................................................................................6
5.2 Logical database Requirement........................................................................................................6
5.3 Design Constraints..........................................................................................................................6
     5.4   Standards Compliance………………………………………………………………............6
     5.5   Reliability…………………………………………………………………………………………6 
     5.6    Availability………………………………………………………………………………………..7
     5.7   Security……………………………………………………………………………………………7
     5.8   Maintainability…………………………………………………………………………………….7
     5.9 Portability………………………………………………………………………………………….7

6. Change Management System..................................................................................................8
1Software Requirements Specification for Patient health management System

1. Introduction

1.1 Purpose

The software described in this document is the Patient health management system
website . This document seeks to provide the Software Requirements Specifications for
Patient health management system Website. The purpose of this document is to record
the requirements for the design and development of a Website.

1.2 Project Scope

The scope of the website is to provide a set of web pages that sufficient depth and
information about patient health management system for their viewers.

1. Software product name Patient health management system phms .

2. This software product will store the record of the patient as well as medicines
,food ,disease and the ultimate purpose is to generate the report
3. This software will be applicable in hospitals and clinics and it would ensure that the
record of the patient is maintained properly .
4. The system will be used to get the information from the patients and then storing
that data for future usage. The current system in use is a paper-based system. It is
too slow and cannot provide updated lists of patients within a reasonable
timeframe.The intentions of the system are to reduce over-time pay and increase
the number of patients that can be treated accurately. Requirements statements in
this document are both functional and non-functional.

Benefits for using the site should include:

• It would help the doctor by seeing his previous record and help doctor in making
certain estimates
• It would help the patients by generating supports

1.3 Document Conventions

 Ieee 830

1.4 Intended Audience and Reading Suggestions

Primary readers of this document are the web designers contributing to and testing of the
Organization website.

.
2Software Requirements Specification for Patient health management System

1.5 Definitions, Acronyms, and Abbreviations. 

PHMS – patient health management system

Srs –system requirement specification

1.6 Overview
The SRS is organized into two main sections. The first is The Overall Description
and the second is the Specific Requirements. The Overall Description will describe
the requirements of the PHMS from a general high level perspective. The Specific
Requirements section will describe in detail the requirements of the system.

1.6 References

IEEE/EIA 12207.1-1997, IEEE/EIA Guide for Information TechnologySoftware life cycle

processesLife cycle data; IEEE/EIA 12207.2-1997, IEEE/EIA Guide for Information
TechnologySoftware life cycle processesImplementation considerations

2 The Overall Description

Describes the general factors that affect the product and its requirements. This section
does not state specific requirements. Instead it provides a background for those
requirements, which are defined in section 3, and makes them easier to understand.

2.1 Product Perspective

The PHMS is an independent stand–alone system. It is totally self contained.

2.1.1 Hardware Interfaces

The PHMS system will be placed on nearly all PC’s .

2.1.2 Software Interfaces

All databases for the PHMS will be configured using php mysql . These databases
include all patient records. This can be seen by admin and doctor .

2.2 Product Functions

1. Registration: When a patient is admitted, the front-desk staff checks if
the patient is new one then all of his required information is taken and
that person is register and if its already registered it should be asked
before then there no need to register that person again
2. Patient check out: In this part doctor checks the patient and
recommend the food and medicine and if patient comes for recheck up
3Software Requirements Specification for Patient health management System

then also modify the medicine , food and it is also kept as record
(medicine and food and diagnosis ) for example if a person comes
three times for check up than nearly all time the recommendations may
also change so its record is also maintained
3. Report generation : In this part will show the whole record of the
patient and also its medicines ,diagnosis and food details in form of
report
4. View all : this part will show all patients which have been registered

2.3 User Characteristics

Educational level of person using PHMS software – Should know English and
should be a fully doctor should have how know of computer
Experience of PHMS software – None
Technical Expertise – Little

2.4 Assumptions and Dependencies

- The system is required to generated reports.
- maintain record
4Software Requirements Specification for Patient health management System

Specific Requirements
This section contains all the software requirements at a level of detail, that when
combined with the system context diagram, use cases, and use case descriptions, is
sufficient to enable designers to design a system to satisfy those requirements, and
testers to test that the system satisfies those requirements.

3.1 External Interfaces

The gcuf cargo system will use the standard input/output devices for a personal
computer. This includes the following:
 Keyboard
 Mouse
 Monitor
 Printer

3.1.1 User Interfaces

User will interact with the system through GUI like forms

3.1.2 Software Interfaces

The system shall interface with an php,mysql database.

3.1.3 Hardware Interfaces

The system shall run on a Microsoft Windows based system.
3.1.4 Communication Interfaces
Communication interfaces are local network protocol .
4 Functional Requirements
Functional requirements define the fundamental actions that system must
perform.
 Registration : add patient ,assign patient id
 Check up: doctor recomended medicine
 Report generation : information or report of patient
 Database : Patient Mandatory Information
 View all: this part will show the record if all patient
5Software Requirements Specification for Patient health management System

5 Nonfunctional Requirements
Functional requirements define the needs in terms of performance, logical database
requirements, design constraints, standards compliance, reliability, availability, security,
maintainability, and portability.

5.1 Performance Requirements

Performance requirements define acceptable response times for system functionality.
 The load time for user interface screens shall take no longer than two
seconds.
 Queries shall return results within five seconds.

5.2 Logical Database Requirements

The logical database requirements include the retention of the following data elements.
This list is not a complete list and is designed as a starting point for development.

5.4 Design Constraints

The PHMS shall be a web based system running in a Windows environment. The system
shall be developed using php and an mysql database.

5.5 Standards Compliance

There shall be consistency in variable names within the system. The graphical user
interface shall have a consistent look and feel.

5.6 Reliability
Specify the factors required to establish the required reliability of the software system at
time of delivery like it would not crash and would handle exception by alerts .

5.7 Availability
The system shall be available in online as it is website based .

5.8 Security
people will be asked to verify first before he can access the software
5.9 Maintainability
The PHMS is being developed in Php. Php is an scripting programming language and
shall be easy to maintain.

5.10 Portability
The PHMS shall run in any Microsoft Windows environment that contains Php Runtime
and the MYSQL database.
6Software Requirements Specification for Patient health management System

6 Change

Changes to this document may be made after approval from the project manager and the
client approval officer.