Online Diagnosis

Synopsis
for
BE Computer 8 sem
th

Submitted by

Mir Saqib
Mohd Shafi
Zubair Nisar
Sibti Mehdi
 INTRODUCTION

The learning process continues till one has life and he lives here for

discovering & inventing. The inventions in our mind give us real challenges and real

challenges are those that dare to dream us. The project which has been undertaken

by us is a web based application program known as " RESCUE ONLINE ”.

Hosipital Management is one of the largest service sectors

providing everyday Services to its users. With privatization of Hosipitals,

Hosipital Management is gaining popularity. With increasing usage of

networks, transferring data and information is easy. Both of these above-

mentioned technologies converge towards a common evolvement of online

Hosipital Management process, which not only helps to manage the Hosipitals

easily but also helps Administration access the Information rapidly. This

dummy project aims towards understanding the implementation of technology

in real world scenario. The client server architecture followed within the

project, which helps in having distributed environment with three tier logic and
thus implementing server and client side independently.

EXISTING SYSTEM

a) Existing system requires manual entry in to the following registries:

a. Patient Admission Register

b. Doctors on Duty Registry

c. Drugs in Stock Registry

d. Staff Service History Registers

e. Income Register

f. Expenditure registers

g. Staff Salary Register etc...

b) To keep record it requires large space for registries.

c) Locating a record is time consuming.

d) Redundant Data Entry.

e) Generation of Various Reports was Time consuming.

f) Communication between the different sections was time consuming

g) The administrator could not always within a fraction of time get the overview of the

working status of the system.

h) No system of feedback & response from the patient & the administration was

existing.

i) No Tension taking oppointmets to hospitals or clinics.

 OBJECTIVES OF THE PROPOSED SYSTEM

In the proposed system almost 90 percent of the manual and paper work replaced by

computerization I automation:

a. No redundant entry, entries only once per record of any type, in the add new form

b. To change entries no botheration of opening the registries, just go to the edit panel of

that item.

c. Support for online diagnosis

d. All the outputs printed on pre formatted unformatted (A4) paper.

e. No botheration of calculation for the reports.

f. No botheration to make files roam from one table to another table.

g. Quick search schemes also provided

h. Audit search panels also provided to trace any forgery.

i. Doctor’s communications made much faster and less interfering with the

administration work.

j. Feedback & suggestion facilities provided exclusively as an extra feature embedded

externally with the built in package.

k. Separate privileges provided for the different levels of the staff viz; administrator,

accountant & clerk.

l. Administration is given a clear view of the present working status of the system.
m. Account reports when regularly differentiated and studied provide a supervising

system of the treasury of the organization and the "Accountants Pocket".

n. Transferring of information from one hospital or from one clinic to another.

o. Doctors of any hospital can chat or discuss on any patients case.

p. people can give suggestions to higher officials of hospitals or clinics.

q. People can take appointments online and also can pay fee.

r. The main idea of the system is to provide a centralized database, client, and server

architecture. This project is a network based project, in which multiple terminals

communicate with the centralized database server.

THREE TIER ARCHITECTURE

<<>>
Authentication

UP a s s e s rw no ra d m e
LOG IN
<< Session >>

<< >>
Hello User
Inbox
Logged
Compose On
Sent DATABASE
Trash
Delete All
 Tools used in the Development Process

• ASP.NET

• Java script

• Visual Studio 2005

• Microsoft SQL Server 2005

• Internet Information Server (IIS)

• Macromedia flash CS4

• Photoshop CS4

• Coral Draw

• AJAX

Hardware requirement

Since the application is based on “THREE TIER ARCHITECTURE”, the following

hardware is required at:

1.CLIENT SYSTEM:-

1) Processor Pentium IV or higher.

2) 512 MB of RAM or more.

 3) 20GB Hard Disk or more.

4) Network Adapter or Modem.

5) Keyboard & Mouse.

2. SERVER SYSTEM: -

• Pentium-IV Processor or Above.

• RAM (at least) 1GB.
• LAN Card (Speed) 100mbps
• Hard Disk (20 GB)
• Keyboard & Mouse.

SOFTWARE REQUIRED:

CLIENT SYSTEM:-

1.) Operating systems: - “WIN-XP” / “WIN-98” / “WIN-2000 SERVER or ADVANCE

SERVER” / “WIN-2003 SERVER or ADVANCE SERVER”, LINUX etc.
2.) Web browser: - internet explorer, Netscape Navigator, Mozilla, Opera etc.

SERVER SYSTEM: -

a) Operating systems: - “WIN-XP” / “WIN-98” / “WIN-2000 SERVER or ADVANCE

SERVER” / “WIN-2003 SERVER or ADVANCE SERVER”, LINUX etc.

b) Web browser: - internet explorer, Netscape Navigator, Mozilla, Opera etc.

c) Internet Information Server ( IIS )

d) Visual Studio 2005.

e) .NET framework 2.0 or higher

f) Sql Server 2005.

 TESTING TECHNOLOGIES USED: -

The methodology that will be used for testing in the development of this proposed system is a
combination of “UNIT TESTING” and “INTEGRATION TESTING”. “INTEGRATION TESTING”
further includes both the “TOP-DOWN INTEGRATION” and the “BOTTOM-UP INTEGRATION”.
When we talk about the “UNIT TESTING” we have to take care of the each and every individual
module. This proposed system will be tested basically on this methodology. During the application of
the “INTEGRATION TESTING” initially we will opt for “BOTTOM-UP INTEGRATION” as all the
smallest modules of the proposed system are tested in order to achieve higher degree of
performance. The whole system will be divided into “Logical Clusters” on the basis of the
functionality. Hence making the clusters and then perform testing is the basic criteria under
“BOTTOM-UP TESTING” which is being applied to the testing phase during the development of this
system. In the “TOP-DOWN INTEGRATION” testing is being started from the main module i.e. the
“Control Program” or the “Main Program”. The various features of testing conclude to be the
following:-

I. Initially we will opt for the “UNIT TESTING” and the various types of activities that are
performed under it are as follows: -

a. Evaluation of the Testing Domain.

b. Defining desired test zones.
c. Prioritization of Test data.
d. Initialization & Verification of “UNIT TESTING” Plan.
e. Performing “UNIT TESTING”.
f. Removing encountered errors.
g. Retesting of misbehaving functions encountered.
h. Final Test Review.
i. Migrating to next test technology (if all errors removed).

II. The next option available out of the adopted testing techniques is “INTEGRATION
TESTING” and the various activities involved in it are as follows:-

a. Framing Testing Development Domain.

b. Dividing Test Code into clusters.
c. Application of “Bottom Up” Testing & removing Errors (if any).
d. Shifting Towards “Top Down” Testing & eliminating Errors encountered (if
any).
e. Considering Final Test output.
f. Delivering Validated Product.