1.

PRELIMINARY INVESTIGATION
AND INTRODUCTION

1
1.1 PROJECT OVERVIEW

Disease Analysing Centre is situated at Nerul, Navi Mumbai. This centre was established in
the year 2000. It is one of the popular diagnostic centre.

In this Analysing Centre Various Facilities are provided to the patients. All types of X-Rays,
Sonographies, and various types of Pathology tests are Available. All types of Specialized
Doctors and highly qualified employee staff is working in this centre.

The existing system does not support much functionality deals with reporting and it is
partially automated. It is very time consuming.

The Patient has to visit the centre to check availability of tests and book appointment. The
centre does not support much functionality deals with reporting and it is partially automated.
It is very time consuming. The all transaction is done manually. It becomes very difficult to
handle Patient details and maintain all transaction records.

2
1.2 DESCRIPTION OF SYSTEM
Disease Analysing Centre is web based application which is helpful for all the patients
as well as ailment patient. The existing system does not support much functionality deals
with reporting and it is partially automated. It is very time consuming. The main objective of
the project is to book an appointment for a particular test or x-ray or sonography at their
home, so that patient does not often require coming to the centre very early in the morning
and waiting for a doctor in case of emergency and finally they are wasting their 3 to 4 hours.

As the proposed system is user-friendly it allows user to book their appointment by login
their account, and they will get all the information about which required instructions they
have to follow for a particular test or x-ray or sonography.The success of the system depends
largely on how clearly the problem is defined, thoroughly investigated and properly carried
out through the choice of solution.

3
 1.3 LIMITATION OF PRESENT SYSTEM

DISADVANTAGES:
The following are the disadvantages of the existing system:

 Existing system is not a fully computerized system.

 Work load is more.
 Time consuming.
 All reports are done manually.
 Information is not secure.
 Data redundancy is more and data and information are not arranged in proper
structure and way.

4
1.4 PROPOSED SYSTEM AND ADVANTAGES
The proposed system is web based application, where user can book their appointments for a
particular test or for an X-Ray or for a sonography by login their account. Here user will get
all the information about the tests, that is which instructions they have to follow to do any test
and this will get by clicking on respective test. If user wants to cancel an appointment, they
can cancel it but only before one day. So this proposed system will help to the users in all
above mentioned facilities and they can access this website at their home or at anywhere.

Objective of the System

The objective of Disease Analysing Centre is to provide better information of all pathalogy
tests provided by the pathology lab for the patients, all details of digital X-Rays and
sonographies. Easily they can register and book appointments for any tests from anywhere
without facing any difficulty, and if they want to cancel, they cancel it. So that patient does
not often require to come to the diagnostic centre to book an appointment for a particular test,
to see test details and required instructions in case of emergency.

Advantages of Proposed System:

 This website is easy to use and user-friendly.
 Paperless work environment.
 The system allows automate diagnosis system.
 Allows faster services.
 Work-load of staff will be reduced.
 Time will be saved.
 Information at mouse click.
 There will not be any chances to lost information and of the patient.
 Beneficial for ailment patients.

5
 1.5 BASIC MODULES OF PROPOSED SYSTEM
There are mainly 3 modules in this software, Patient module, Doctor Module and Employee
Module. A Patient can register himself and can book an appointment online. The doctor can
add, update, delete and view the patient appointments, doctor details and employee details.

Modules:
This project involves mainly three modules.

Patient module
Doctor module
Employee module

Modules Description:
1. Patient module:
In this module patient can visit website and view details regarding tests. patient
can register himself online. patient can also book appointment online. Patient can
cancel appointmentbefore one day.
2. Doctor module:
In this module doctor can add, update appointment details dynamically. Doctor
can also maintain employee details. Doctor had right to update employee details.
He can add other doctors for doing diagnosis.
Doctor can also generate report of various details.
3. Employee module:
In this module employee can add, update, and delete patient details dynamically.
Employee can also maintain test details. Employee had right to view and update
appointment details.
Employee can also generate report.

6
1.6 GANT CHART

7
2. SURVEY OF TECHNOLOGY

8
2.1 FEASIBILITY STUDY

Feasibility study is conducted once the problem is clearly understood. Feasibility

study is a high level capsule version of the entire system analysis and design process.
The objective is to determine quickly at a minimum expense how to solve a problem.
The purpose of feasibility is not to solve the problem but to determine if the problem
is worth solving.
The system has been tested for feasibility in the following points.

1. Technical Feasibility
2. Economical Feasibility
3. Operational Feasibility.

1. Technical Feasibility

The technical feasibility is frequently the most difficult are encountered at this stage.
It is essential that the process of analysed definition be conducted in parallel with an
assessment to technical feasibility. It centers on the existing computer system
(hardware and software etc.) and to what extent it can support the proposed system.
It provides the high level of graphical user interface, reliability, availability and
compatibility, excellent reporting features, platform independent.

2. Economical Feasibility
The computerized system will help in automate the selection leading the profits and
details of the organization. With this software, the machine and manpower utilization
are expected to go up by 80-90% approximately. The costs incurred of not creating
the system are set to be great, because precious time can be wanted by manually. The
proposed system will give the minute information, as a result the performance is
improved which in turn may be expected to provide increased profits.

9
3. Operational Feasibility
It is mainly related to human organizations and management. The points to be
considered are:
 What changes will be brought with the system?
 What organization structures are disturbed?
 What new skills will be required? Do the existing staff members have these skills? If
not, can they be trained in due course of time? The system is operationally feasible as
it very easy for the End users to operate it.

10
2.2 METHODOLOGY

Waterfall model

Sometimes also called as classic life cycle or the linear sequential model suggests a
systematic, sequential approach to software development that begins at the system level and
progresses through analysis, design, coding, testing, and maintenance. Above Figure
illustrates the linear sequential model for software engineering.

System/Software Requirements:
Because software is always part of a larger system (or business), work begins by establishing
requirements for all system elements and then allocating some subset of these requirements to
software. This system view is essential when software must interact with other elements such
as hardware, people, and databases. System engineering and analysis encompass
requirements gathering at the system level with a small amount of top level design and

11
analysis. Information engineering encompasses requirements gathering at the strategic
business level and at the business area level.

Analysis: The requirements gathering process is intensified and focused specifically on

software. To understand the nature of the program(s) to be built, the software engineer
("analyst") must understand the information domain for the software, as well as required
function, behavior, performance, and interface.

Design: Software design is actually a multistep process that focuses on four distinct attributes
of a program: data structure, software architecture, interface representations, and procedural
(algorithmic) detail. The design process translates requirements into a representation of the
software that can be assessed for quality before coding begins.

Coding:The design must be translated into a machine-readable form. The code generation
step performs this task. If design is performed in a detailed manner, code generation can be
accomplished mechanistically.

Testing: Once code has been generated, program testing begins. The testing process focuses
on the logical internals of the software, ensuring that all statements have been tested, and on
the functional externals; that is, conducting tests to uncover errors and ensure that defined
input will produce actual results that agree with required results.

Maintenance: Software will undoubtedly undergo change after it is delivered to the customer
(a possible exception is embedded software). Change will occur because errors have been
encountered, because the software must be adapted to accommodate changes in its external
environment. Software support/maintenance reapplies each of the preceding phases to an
existing program rather than a new one.

12
2.3SOFTWARE AND HARDWARE REQUIREMENTS

Hardware Requirements:

This system requires following hardware for making it:

Processor Minimum: Intel P4.

Recommended: Core i3 Duo or higher.

Processor speed 1 GHz or higher

Hard disk 160 GB or more

Software Requirements:

This system requires following software for making it:

Operating System Windows xp or higher, Linux

Browser Google Chrome

Language Java Programming Languages

Database MySql

13
2.4 DEVELOPMENT TOOLS AND TECHNOLOGY

2.4.1 Front End

 Jsp (JavaServer Pges)

 HTML (Hyper Text Markup Language )
 JavaScript
 AJAX(Asynchronous JavaScript and XML)
 CSS(Cascading Style Sheet)

2.4.2 Back End

 MySql

2.4.3 Development Environment

 NetBeans

14
3. REQUIREMENTS AND
ANALYSIS

15
3.1 E-R Diagram

The Entity-Relationship (ER) model was originally proposed by Peter in 1976 as a

way to unify the network and relational database views. Simply stated the ER model is a
conceptual data model that views the real world as entities and relationships. A basic
component of the model is the Entity-Relationship diagram which is used to visually
represent data objects. Since Chen wrote his paper the model has been extended and today it
is commonly used for database design for the database designer, the utility of the ER model
is:

 It maps well to the relational model. The constructs used in the ER model can easily
be transformed into relational tables.
 It is simple and easy to understand with a minimum of training. Therefore, the model
can be used by the database designer to communicate the design to the end user.

In addition, the model can be used as a design plan by the database developer to
implement a data model in specific database management software.

Connectivity and Cardinality

The basic types of connectivity for relations are: one-to-one, one-to-many, and many-to-
many.

 A one-to-one (1:1) relationship is when at most one instance of a entity A is

associated with one instance of entity B.
For example, "employees in the company are each assigned their own office. For each
employee there exists a unique office and for each office there exists a unique employee.

 A one-to-many (1:N) relationships is when for one instance of entity A, there are zero,
one, or many instances of entity B, but for one instance of entity B, there is only one
instance of entity A.

16
 An example of a 1:N relationships is a department has many employees each employee is
assigned to one department

 A many-to-many (M:N) relationship, sometimes called non-specific, is when for one

instance of entity A, there are zero, one, or many instances of entity B and for one
instance of entity B there are zero, one, or many instances of entity A. The
connectivity of a relationship describes the mapping of associated.

E R Notation

There is no standard for representing data objects in ER diagrams. Each modeling

methodology uses its own notation. The original notation used by Chen is widely used in
academics texts and journals but rarely seen in either CASE tools or publications by non-
academics. Today, there are a number of notations used; among the more common are
Bachman, crow's foot, and IDEFIX.

All notational styles represent entities as rectangular boxes and relationships as lines
connecting boxes. Each style uses a special set of symbols to represent the cardinality of a
connection. The notation used in this document is from Martin. The symbols used for the
basic ER constructs are:
 Entities are represented by labeled rectangles. The label is the name of the entity.
Entity names should be singular nouns.

 Relationships are represented by a solid line connecting two entities. The name of the
relationship is written above the line. Relationship names should be verbs

 Attributes when included, are listed inside the entity rectangle. Attributes which are
identifiers are underlined. Attribute names should be singular nouns.

 Cardinality of many is represented by a line ending in a crow's foot. If the crow's

foot is omitted, the cardinality is one.

 Existence is represented by placing a circle or a perpendicular bar on the line.

Mandatory existence is shown by the bar (looks like a 1) next to the entity for an
instance is required. Optional existence is shown by placing a circle next to the entity
that is optional

17
18
3.2 Use Case Diagram

Actor: A coherent set of roles that users of use cases play when interacting with the use cases.

Use case: A description of sequence of actions, including variants, that a system performs
that yields an observable result of value of an actor.

UML stands for Unified Modeling Language. UML is a language for specifying,
visualizing and documenting the system. This is the step while developing any product after
analysis. The goal from this is to produce a model of the entities involved in the project
which later need to be built. The representation of the entities that are to be used in the
product being developed need to be designed.

Use case diagrams model behaviour within a system and helps the developers
understand of what the user require. The stick man represents what’s called an actor. Use
case diagram can be useful for getting an overall view of the system and clarifying that can
do and more importantly what they can’t do. Use case diagram consists of use cases and
actors and shows the interaction between the use case and actors.

19
  The purpose is to show the interactions between the use case and actor.
 To represent the system requirements from user’s perspective.
 An actor could be the end-user of the system or an external system.

A Use case is a description of set of sequence of actions graphically it is rendered as

an ellipse with solid line including only its name. Use case diagram is a behavioural diagram
that shows a set of use cases and actors and their relationship. It is an association between the
use cases and actors. An actor represents a real-world object.

20
21
3.3 Sequence Diagram/Collaboration Diagram

A sequence diagram is an interaction diagram that shows how processes operate with one
another and in what orders sequence diagram emphasizes on time sequence of messages.

A sequence diagram shows as parallel, vertical lines different processes or objects that
live simultaneously and as horizontal arrows, the message exchanged between them in order
in which they occur. An important characteristic of a sequence diagram is that time passes
from top to bottom.

22
23
3.4 Class Diagram

The class diagram is a static diagram. It represents the static view of an application. Class
diagram is not only used for visualizing, describing and documenting different aspects of a
system but also for constructing executable code of the software application.

The class diagram describes the attributes and operations of a class and also the
constraints imposed on the system. The class diagrams are widely used in the modelling of
object oriented systems because they are the only UML diagrams which can be mapped
directly with object oriented languages. The class diagram shows a collection of classes,
interfaces, associations, collaborations and constraints. It is also known as a structural
diagram.

24
25
3.5 Object Diagram

26
3.6 Activity Diagram

3.6.1 For Patient

Search For a Test

X-Ray Sonography Pathology

Login

No Register

Yes

Booking Appointment

Cancel Appointment

Yes
Cancel

No

Logout

27
3.6.2 For Doctor

Login

View Appointment

Diagnosis

Payment

Acknowledement

Logout

28
3.6.3 For Employee

Login

Manage Tests

View & Update Appointment Status

Get Payment

Acknowledement

Logout

29
4. SYSTEM DESIGN

30
4.1 Data Dictionary (Table List)

1. Register Table

Attributes Datatype Constraint

p_id int Primary
f_name varchar not null
m_name varchar not null
l_name varchar not null
p_add varchar not null
p_mob varchar not null
p_gender varchar not null
p_dob varchar not null
p_age int not null
p_bgroup varchar not null
p_email varchar not null
ref_doc varchar not null
City varchar not null
State varchar not null
Pin int not null
User varchar not null
Pass varchar not null
sec_qn varchar not null
sec_ans varchar not null
p_photo longtext not null

2. Appoint Table

Attributes Datatype Constraint

p_id varchar not null
p_name varchar not null
t_id varchar not null
t_type varchar not null
t_name varchar not null
t_cost varchar not null
app_no int not null
date1 varchar not null
time1 varchar not null
confirm varchar not null

31
 3. Test1 Table

Attributes Datatype Constraint

t_id varchar Primary
t_type varchar not null

4. Test2 Table
Attributes Datatype Constraint
t_id varchar Foreign
t_name varchar not null
t_cost varchar not null
r_day varchar not null

5. Doctor_details
Atrributes Datatype Constraint
d_id varchar Primary
d_name varchar not null
d_mobi varchar not null
d_add varchar not null
d_specialize varchar not null
d_email varchar not null
d_photo longtext not null
joining_date varchar not null
user varchar not null
Pass varchar not null

6. Emp_det Table
Attrbutes Datatype Constraint
e_id Int primary
e_name varchar not null
e_mob varchar not null
e_add varchar not null
e_qualific varchar not null
e_des varchar not null
e_join_date varchar not null
e_photo longtext not null
e_salary Int not null
user varchar not null
pass varchar not null

32
 7. Cancelbooking Table
Attributes Datatype Constraint
ddate Date not null
pid varchar not null
appid varchar not null
ttime varchar not null

8. Empsalary_detail Table
Attrbutes Datatype Constraint
esal_id Int primary
esal_name varchar not null
esal_salary Int not null
month varchar not null
esal_attendance int not null
esal_bal varchar not null
esal_incen Int not null
esal_total longtext not null
esal_status Int not null
esal_dop varchar not null
salary_id varchar not null

9. Attendance Table
Attributes Datatype Constraint
eid Int not null
ename varchar not null
date varchar not null
status varchar not null

10.Feedback Table
Attributes Datatype Constraint
id Int not null
feedback varchar not null

33
 4.2 Test Cases

Test id Test Cases Test Data Actual Expected Status

Login Form
1 Open Login doctor Open Open Pass
page of doctor doctor doctor
Enter username 123 Page Page
Enter Password Or Or
Click login Invalid user Invalid user
name and name and
password password
page page
2 Open Login emp Open login Open login Pass
page of Successful Successful
employee 12345 page page
Enter username Or Or
Enter Password Invalid user Invalid user
Click login name and name and
password password
page page
Registration
for Patient

1 Enter Valid details User User Pass

registration registered registered
details
Click submit
2 Enter Invalid details User Try again Fail
registration registered
details
Click submit
3 Patient Login Open Open Pass
Enter Username XYZ Appointment Appointment
Enter Password XYZ@1 booking page booking page
Click Login Or Or
Invalid Invalid Fail
username & username &
password password
page page
Appointment
Booking
1 Enter Valid details Appointment Appointment Pass
appointment booked booked
details and click
on book
appointment
2 Enter Invalid details Appointment Appointment Fail
appointment not booked not booked
34
 details and click
on book
appointment
3 To view details View Patient Patient Pass
& cancel details are details are
appointment viewed and viewed and
click on View appointment appointment
has been has been
cancelled(1 cancelled(1
day before). day before).
4 To view details View Patient Patient Fail
& cancel details are details are
appointment viewed and viewed and
click on View appointment appointment
has not been has not been
cancelled(1 cancelled(1
day before). day before).
Feedback Page

1 Login and then Feedback Feedback Feedback Pass

give feedback submitted submitted
Enter Details
By employee

1 Open test details Valid test Tests added, Tests added, Pass
page and enter details updated and updated and
test details click displayed on displayed on
on add modify respective respective
or view display page display page
2 Open test details Valid test Tests not Tests not Fail
page and enter details added, not added, not
test details click updated and updated and
on add modify not displayed not displayed
or view on respective on respective
display page display page
3 Open diagnosis View diagnosis After After Pass
details page and details & diagnosis diagnosis
update payment payment details payment payment
details status has status has
been updated been updated
4 Open test details View diagnosis Without Without Fail
page and enter details & diagnosis diagnosis
test details click payment details payment payment
on add modify status has not status has not
or view been updated been updated
Enter
Employee
Details By
Doctor

35
1 Open employee Valid Details are Details are Pass
details page and employee submitted submitted
click on submit details
2 Open employee Valid Details are Details are Fail
details page and employee not submitted
click on submit details submitted
Enter
Employee
salary Details
By Doctor

1 Open employee Valid Details are Details are Pass

salary details employee submitted submitted
page and click salary details
on submit
2 Open employee Valid Details are Details are Fail
salary details employee not submitted
page and click salary details submitted
on submit
Enter
Employee
attendance
Details By
Doctor

1 Open employee Valid Details are Details are Pass

attendance employee submitted submitted
details page and attendance
click on submit details
2 Open employee Valid Details are Details are Fail
attendance employee not submitted
details page and attendance submitted
click on submit details
Report
Generation
1 Click on report Select report Same report Same report Pass
you want to you want to is generated is generated
generate generate
2 Click on report Select report Report is not Same report Fail
you want to you want to generated is generated
generate generate
Click on report Select report Different Same report Fail
you want to you want to report is not is generated
generate generate generated

36
37
38