Software Project Management (CS 800)

Group Project On: Phase 1: Group No.: Submitted on: Telemedicine Requirement analysis and specifications II 31/08/2012 Prepared By Name Arijit Mallik Murali K Anirban Chakraborty Roll No. 12CS05F 12CS14F 12CS04F Signature

Course: Branch: Semester: Institution:

M. Tech CSE I NITK Surathkal

Page | 1

1. Introduction
The purpose of this document is to present a detailed description of the Telemedicine system. It will explain the purpose and features of the system, the interfaces of the system, what the system will do, the constraints under which it must operate and how the system will react to external stimuli. This document is intended for both the stakeholders and the developers of the system.

2. Scope
This software system will be a Telemedicine System. Telemedicine may be defined as the use of computers and telecommunication technologies to provide and avail medical information and services from distant locations. More specifically, this system is designed to help eliminate distance barriers and to improve access to medical services that would often not be consistently available in distant rural communities. It is also used to save lives in critical care and emergency situations.

3. Minimum Requirements
3.1. Functional Requirements
Point to point video and/or audio conferencing facilities to enable the doctors to have a live interaction with the patients remotely. Central database for managing the patient records. Uploading facilities of the test results of the patients like ECG (in form of binary/SCPECG file format), BP, dialysis etc. Appropriate software modules to read the binary files and display it in appropriate form, e.g. viewing of ECG by interpreting the uploaded binary/SCP-ECG files. Facility to schedule appointments with experts from remote site. Online help in form of documents for doctors and hospital staffs who use the system directly. Facility to generate report regarding medical advices for the patient.

Page | 2

3.2. Non-Functional Requirements

Simple and elegant GUI. The system should support video/audio conferencing for a minimum of 3 users at a time. System should be compatible at least with web browsers such as IE and Mozilla.

4. Enhancements
Facility for the doctor to view, re-schedule or cancel the appointments. The central database must have backup facilities.

5. Simple Use-Case Diagram

Page | 3

6. Simple Flow Diagram

6.1. Local site
Patient In Patient gets OPD Local doctor checks up Patient Out

Referral needed?

No Patient gets local treatment only

Yes Appointment scheduled Patient data uploaded in database

6.1. Remote site

Patient 1 Patient 2 Patient 3 . . . Patient n Patient Queue Online audio/video conference takes place (Patient and local doctor at local site and expert doctor at remote site). All patient reports are uploaded as necessary.

Patient gets medical advice from expert doctor

Patient Out

**End of the SRS**

Page | 4