Disease Diagnosis System

Software Requirement Specification (SRS)

Group ID: BCA-8650

Prepared By: SPSHM

Version 1.0 Approved

April 20th, 2017

 Revision History
Date Version Description Author
April 20th, 1.0 The main aim of this SSPHM
2017 project is to provide
better service to
people so that they
can cure their disease
by own. Using
powerful computer
resources will helps us
to diagnose there
common disease
which comes
seasonally. This will
saves the time of
many people too.
 Introduction

Aim:
The main aim of this project is to provide better service to people
so that they can cure their disease by own. Using powerful
computer resources will helps us to diagnose there common
disease which comes seasonally. This will saves the time of many
people too.

Future Aspects:
The main aim of this project is to provide better service to people
so that they can cure their disease by own. Using powerful computer
resources will helps us to diagnose there common disease which comes
seasonally. This will saves the time of many people too.

Scope:
This project is very much helpful in disease diagnosing for those
who got suffered from the common seasonal disease like: cold,
cough, blood pressure, diabetes.The main aim of this
project is to provide better service to people so that they can cure
their disease by own.
Product Functions:
The main aim of this project is to provide better service to people
so that they can cure their disease by own. Using powerful computer
resources will helps us to diagnose there common disease which comes
seasonally. This will saves the time of many people too.

References:
The main aim of this project is to provide better service to people
so that they can cure their disease by own. Using powerful computer
resources will helps us to diagnose there common disease which comes
seasonally. This will saves the time of many people too.
 SRS DOCUMENT

Scope of the Project

The first stage of information technologies (IT) product development process is
requirement agreement with customer in compliance with qualifying standards.
This paper focuses on design of disease diagnostic system. This project is about
identifying disease as per symptoms entered by the user . It will help people to
recognize their problem according to symptoms. It will always be very helpful
especially for the peoples living in the rural areas as they can identify their disease
without consulting the doctors and it will help them to know what next step they
have to take. Everyone can use this program after completion of this project . This
is a mobile application and we can simply use it. For identifying disease , firstly
users have to input all the symptoms which they noticed after getting ill for
example , if a user has a headache then the user have to input symptoms like how
much the pain is, in which area of head the pain occurs or it occur regular or not.
After input such symptoms the name of a disease ( according to the entered
symptoms) are displayed on user screen.
Functional & Non-Functional Requirements

Functional Requirements
Feature requirements define functions and services which system
should perform on the system or user level.

Graphical User Interface (GUI) requirements define presence,

appearance, functionality and behavior of applications GUI
elements

Usability requirements define all human factor-concerned

requirements like ergonomic, clearness, simplicity and consistency.

Data requirements define input and output data for the system,
format of the data, what data should be saved.

Security requirements define access permissions to the system

functionality and stored data.

Performance requirements define performance parameters for the

system such as: scalability; synchronization of parameters for
application.

Interface requirements define interaction of the system with other

system/environment.
 Non-Functional Requirements

Reliability requirements define parameters like average/maximum

frequency of failures, mean time between failures, and failures
distribution.

Documentation requirements define all kinds of documentation which

should or should not be present for the system.

Implementation requirements define any constraints as well as

industry, quality or other standards which the system should confirm
to.

Supportability requirements define how the product is supported,

what are the ways of getting licenses, technical support & delivery of
new version.

Diagram
 User Case Diagram
START

PATIENT HAS
HEADACHE

LOW MILD HIGH

MILD

EXCRETA PRB NO COUGH CHEST PAIN

& VISION
VOMITTING SNEEZING PRB

YES YES YES

COLD HIGH B.P.

STOMACH MILD MILD

ACHE
NO
WEAKNESS

NO
FAINT
YES
FOOD INC. THIRST
POISIONING
PATIENT HAS
DIARRHEA YES
LOW B.P.
NO
MILD
DIZZINESS

MUSCLE PAIN

YES
HEAT STROCK
 YES RASHES NO

FEVER

CHICKEN POX
HIGH FEVER

DIARRHEA

NO YES
MALARIA

AB. PAIN

CONSTIP.

YES

TYPHOID
 START

PARENTS HISTORY AT THE TIME OF YOUR BIRTH

NO
WEAKNESS CHEST PAIN
GLC. IN BLD. BLD. CLOT

YES
YES
DIABATES HEART DISEASE

NO
NO

NERVES
DAMAGED
IRR.
BLEEDING

YES
YES

POLIO
TUMOR
Usage Scenario

Analysis
Requirement

Planning
Phase

Decision
Phase-1

Decision
Phase-2

Developement
Phase

Final Report