0% found this document useful (0 votes)
283 views40 pages

Project Report

This document is a project report submitted for the partial fulfillment of a Bachelor of Technology degree in Information Technology. It discusses the development of a disease diagnosis application through symptom checking. The report contains sections on introduction, literature review, proposed methodology, results analysis, and conclusions. It was created by two students under the guidance of a project supervisor to diagnose diseases based on entered symptoms.

Uploaded by

Anamika Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
283 views40 pages

Project Report

This document is a project report submitted for the partial fulfillment of a Bachelor of Technology degree in Information Technology. It discusses the development of a disease diagnosis application through symptom checking. The report contains sections on introduction, literature review, proposed methodology, results analysis, and conclusions. It was created by two students under the guidance of a project supervisor to diagnose diseases based on entered symptoms.

Uploaded by

Anamika Singh
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 40

DDS

PROJECT REPORT

On

“DISEASE DIAGNOSIS THROUGH SYMPTOMS”

Submitted for partial fulfillment of award of

BACHELOR OF TECHNOLOGY

In

INFORMATION TECHNOLOGY

(2020)

Submitted by

ANAMIKA SINGH(1712213015)

ANSHI SRIVASTAVA(1712213018)

Under the guidance of

Mr. Amit Kr. Sachan

SHRI RAMSWAROOP MEMORIAL GROUP OF

PROFESSIONAL COLLEGES

LUCKNOW Affiliated to

Dr. APJ ABDUL KALAM TECHNICAL UNIVERSITY,

LUCKNOW

1
DDS

DEPARTMENT OF INFORMATION TECHNOLOGY


SRMGPC
CERTIFICATE
Certified that the project entitled “Disease Diagnosis through Symptoms” submitted by
Anamika Singh (1712213015) and Anshi Srivastava (1712213018)in the partial
fulfilment of the requirements for the award of the degree of Bachelor of Technology
(Information Technology) of DR. A.P.J ABDUL KALAM TECHNICAL UNIVERSITY,
is a record of student’s own work carried under our supervision and guidance. The
project report embodies results of original work and studies carried out by students and
the contents do not form the basis for the award of any other degree to the candidate or to
anybody else.

Mr. Amit Kumar Sachan Prof. A.K.Srivastava

Assistant Professor Head of Department

(Project Guide) IT, SRMGPC

2
DDS

DEPARTMENT OF INFORMATION TECHNOLOGY


SRMGPC

DECLARATION

We hereby declare that the project entitled “Disease Diagnosis through Symptoms”
submitted by us in the partial fulfillment of the requirements for the award of the
Bachelor Of Technology (Information Technology) of Dr. APJ Abdul Kalam University
is record of our own work carried under the supervision and guidance of the Mr. Amit
Kumar Sachan. To the best of our knowledge this project has not submitted to Dr. APJ
Abdul Kalam Technical University or any University or Institute for the award of any
degree.

ANAMIKA SINGH ANSHI SRIVASTAVA

(1712213015) (1712213018)

3
DDS

DEPARTMENT OF INFORMATION TECHNOLOGY


SRMGPC
ACKNOWLEDGEMENT
We are extremely grateful and remain indebted to our Project Guide. Mr. Amit Kumar
Sachan a source of inspiration and for his constant support in the design, implementation
and evaluation of this project. We are thankful for his constant constructive and valuable
suggestion which benefited us a lot in developing this project. Through this column it
would be our utmost pleasure to express gratitude to her encouragement, corporation and
consent without which it would have impossible to accomplish this project. We are
sincerely grateful to our Head of Department Prof. Ajay Kumar Srivastava for his
assistance and continued guidance throughout this study. In addition to this, we are
grateful to the management of Shri Ramswaroop Memorial Group of Professional
Colleges which encouraged to move in right direction through which we could achieve to
this extent.

Anamika Singh Anshi Srivastava

(1712213015) (1712213018)

4
DDS

PREFACE
The project report has been divided into 6 chapters. The topics covered under each are as
follows:

Chapter 1 - This chapter gives our problem definition along with the aims and
objectives. This part also includes a section on System Analysis which gives information
about the Technical, Economical and Operational Feasibility of our project.

Chapter 2 - A detailed literature survey is done of the convolutional codes and various
parameters related to it.

Chapter 3 - The methodology proposed to develop the project is explained containing the
description of the various modules and the designing section.

Chapter 4 - It deals with software/hardware requirement of the project and the


specifications of the simulator used.

Chapter 5 -It gives the implementation of our entire work and the coding done. It
contains the results obtained after the simulation is done. It also deals with the testing of
the structure using modalism simulator. Gives various advantages, limitation and
application and conclusion of the project.

Chapter 6 - Give the future scope of the project.

5
DDS

ABSTRACT
We have faced issue in this critical time in which diseases could not be find out
easily due to lockdown. The health care industries collect huge amounts of data that
contains some hidden information, which is useful for making effective decisions.

6
DDS

TABLE OF CONTENTS

Title Page (i)

Certificate (ii)

Declaration (iii)

Acknowledgement (iv)

Preface (v)

Abstract (vi)

Table of Contents (vii-ix)

1. INTRODUCTION
1-3

1.1 Overview of Project 1

1.2 Structure 1

1.3 Software Requirements 1

1.4 Hardware Requirements 2

1.5 Feasibility Study 2-3

2. LITERATURE REVIEW 4-11

2.1 Android 4-7

2.1.1 History of Android

2.1.2 Development

2.2 Android Studio 7-10

7
DDS

2.2.1 Features of Android Studio

2.3 Firebase 10-11

2.3.1 Advantages

2.3.2 Some Benefits of Using Firebase

3. PROPOSED METHODOLOGY 12-30

3.1 Problem Definition 12

3.2 Project Objective 12

3.3 Methodology Used 13-16

3.4 Theory 16-17

3.5 Software and Hardware 17-18 And Requirement specification

3.6 Module Description 18-19

3.6.1 Login Module

3.6.2 Admin Module

3.6.3 Corruption Module

3.6.4 Traffic Module

3.6.5 Accident Module

3.7 Area of Work 19

3.8 Proposed Title 19-20

3.9 Diagram of Model 20-22

3.9.1 Data Flow Diagram

3.9.2 Use Case Diagram

3.10 Screenshots 23-30

8
DDS

3.10.1 Application

3.10.2 Database

4. RESULT ANALYSIS AND DISCUSSION 31-33

4.1 Testing 31-33

4.2 Test Case 33-359

4.3 Application, Advantages and 35-36 Limitation of the Project

5. CONCLUSION 37

6. FUTURE SCOPE OF THE PROJECT 38

Appendices (x-xii)

1. LIST OF FIGURES

2. REFERENCES

9
DDS

APPENDICES

APPENDIX 1: LIST OF FIGURES

Serial No. Description Page No.

2.1 Android Versions 5

3.1 Iterative Waterfall Model 13

3.2 O-Level DFD 20

3.3 Use Case Diagram 21

3.4 Class Diagram 22

3.5 User First Page 23

3.6 User Home 24

3.7 Report Page 24

3.8 User FeedBack 25

3.9 Admin Front 25

3.10 Admin Home 26

3.11 View Page 26

3.12 View Content 27

10
DDS

REFERENCES

 https://developer.android.com/reference/android/car/classes

 https://developer.android.com/courses

 https://www.dummies.com/programming/java/10-useful-classes-and-interfacesin-the-
android-api

 https://www.mayoclinic.org/symptom-checker/select-symptom/itt-20009075
 https://symptomate.com/diagnosis/#0-66
 https://www.everydayhealth.com/symptom-checker/
 https://www.medicinenet.com/symptoms_of_serious_diseases_and_health_pr
oblems/article.htm
 https://www.nhsinform.scot/illnesses-and-conditions/

11
DDS

CHAPTER 1
INTRODUCTION
1.1 OVERVIEW OF PROJECT:
The main aim of this project is to provide a platform to the public where they can
See their basic diseases according to symptoms or vice versa. It is for the users
who face challenges while trying to determine the diseases.
Users can use this application without internet connection. Users can get knowledge
about diseases and their symptoms. They can quiz themselves added features. Users
can find out the causes of diseases, they can get knowedage about test and
medicines.
It also tells about how to prevent that disease from happening. It can also help when
to go to hospital.
We hope that this project will encourage the public to take active part and make this
place a better place to live in.

1.2 STRUCTURE:

 Front End : Android

 Back End: Java

12
DDS

1.3 SOFTWARE REQUIREMENTS:


 Windows 10
 Android Studio

1.4 HARDWARE REQUIREMENTS:


 i3 Processor Based Computer
 3 GB-RAM
 80 GB Hard Disk
 Android Device

1.5 FEASIBILITY STUDY:


In this phase our aim is to determine that whether it would be
technically and financially feasible to develop the desired Project.
Since android is an open source platform so the cost of the project in
monetary terms in nil. Technically as android supports sharing of
various contents it became possible for us to implement our objectives.
Three key consideration are involve in the feasibility analysis:
Technical, Operational and Economical.

 Technical Feasibility
A technical feasibility is done on our project to ensure that our
project is both technically an legally feasible. Our project is
technically feasible as all the technology for this project i.e. the
software and the hardware specifications required to develop

13
DDS

and use this project is easily available and free of cost. ADT
bundle used for developing Android application including
Android SDK Tools, Android Platform-tools the latest Android
platform, the latest Android image for the emulator is an open
source technology. Open

source allows one to download the software for usage without


paying software cost.

 Operational Feasibility
The Operational feasibility assessment focuses on the degree
to which the our proposed development projects fits in with the
existing business environment and objectives with regard to
development schedule , delivery date, corporate culture and
existing business processes. Our application is very easy to use
and interactive. The interface of the application is simple and
efficient. Hence we conclude that this project is operationally
feasible.

 Economical Feasibility
It is also known as cost benefit analysis. It basically is cost
outlook for a business project or proposed project. We are
investing only our knowledge and time in this project so it is
economically feasible. We will not only be benefited with our
project but can also use our experience and knowledge while
making other project in future. It can be well understood and
can be used in some other technologies or development. Hence
we conclude that this project is operationally feasible.

14
DDS

CHAPTER 2
LITERATURE REVIEW
2.1 ANDROID:
Android is a mobile operating system developed by Google. It is based on
a modified version of the Linux kernel and other open source software,
and is designed primarily for touchscreen mobile devices such as
smartphones and tablets. In addition, Google has further developed
Android TV for televisions, Android Auto for cars, and Wear OS for wrist
watches, each with a specialized user interface. Variants of Android are
also used on game consoles, digital cameras, PCs and other electronics.
Initially developed by Android Inc., which Google bought in 2005,
Android was unveiled in 2007, with the first commercial Android device
launched in September 2008. The operating system has since gone 17
through multiple major releases, with the current version being 9 "Pie",
released in August 2018. Google released the first Android Q beta on all
Pixel phones on March 13, 2019. The core Android source code is known
as Android Open Source Project (AOSP), and is primarily licensed under
the Apache License.

15
DDS

Android is also associated with a suite of proprietary software developed


by Google, called Google Mobile Services GMS) that very frequently
comes pre-installed in devices, which usually includes the Google Chrome
web browser and Google Search and always includes core apps for
services such as Gmail, as well as the application store and digital
distribution platform Google Play, and associated development platform.
These apps are licensed by manufacturers of Android devices certified
under standards imposed by Google, but AOSP has been used as the basis
of competing Android ecosystems, such as Amazon.com's Fire OS, which
use their own equivalents to GMS.
Android has been the best-selling OS worldwide on smartphones since
2011 and on tablets since 2013. As of May 2017, it has over two billion
monthly active users, the largest installed base of any operating system,
and as of December 2018, the Google Play store features over 2.6 million
apps.

2.1.1 History of Android


The history and versions of android are interesting to know. The code
names of android ranges from A to J currently, such as Aestro, Blender,
Cupcake, Donut, Eclair, Froyo, Gingerbread, Honeycomb, Ice Cream
Sandwitch, Jelly Bean, KitKat and Lollipop. Let's understand the android
history in a sequence.
1) Initially, Andy Rubin founded Android Incorporation in Palo Alto,
California, United States in October, 2003.
2) In 17th August 2005, Google acquired android Incorporation. Since 18
then, it is in the subsidiary of Google Incorporation.
3) The key employees of Android Incorporation are Andy Rubin, Rich
Miner, Chris White and Nick Sears.
4) Originally intended for camera but shifted to smart phones later
because of low market for camera only.
5) Android is the nick name of Andy Rubin given by coworkers because
of his love to robots.

16
DDS

6) In 2007, Google announces the development of android OS.


7) In 2008, HTC launched the first android mobile.

2.1.2 Development
Android is developed by Google until the latest changes and updates are
ready to be released, at which point the source code is made available to
the Android Open Source Project (AOSP), an open source initiative led by
Google. The AOSP code can be found without modification on select
devices, mainly the Nexus and Pixel series of devices. The source code is,
in turn, customized and adapted by original equipment manufacturers
(OEMs) to run on their hardware. Also, Android's

source code does not contain the often proprietary device drivers that are
needed for certain hardware components. As a result, most Android
devices, including Google's own, ultimately ship with a combination of
free and open source and proprietary software, with the software required
for accessing Google services falling into the latter category.

17
DDS

Figure 2.1: Android Versions

2.1.3 Firebase
Firebase is a technology that allows you to create web applications
without server-side programming, making development faster and easier.
It supports Web, iOS, OS X and Android clients. Apps that use Firebase
can use and control data without thinking about how data is stored and
synchronized across different instances of the application in real-time.
Working with Firebase from a developer's perspective is a wonderful
benefit, as they are the core technology of development.
2.1.3.1 Advantages:
 Authentication. Firebase authentication includes a built-in
email/password authentication system. It supports OAuth2 for Facebook,
Google, Twitter and GitHub. Additionally, the Firebase standard
integrates directly into the Firebase database so that you can use it to
control access to your data.

18
DDS

 Hosting. Firebase comes with an easy-to-use hosting service for all your
static files. It works from a global CDN with HTTP / 2.
 Real-time synchronization of data across all clients, be it Android, iOS
or the Web, is very useful. With minimal code, you can notify users of
chat boxes, live news feeds, new posts or friend requests, and more.
 The code for AJS is straightforward in any way. From querying data to
integrating Twitter, Facebook and Google+ logins, you can implement it
very quickly with some nice features.
 With automatic update notifications, it can sync both systems without
manual messaging, Web Sockets, etc.
 Allows you to consider data streams to create more scalable
applications.
2.1.3.2. Some benefits of using Firebase
 Firebase Real-Time Database
 Firebase standard
 Firebase storage

 Firebase Cloud Message


 Firebase notification
 Firebase Remote Configuration
 Firebase Crash Report
 Firebase Application Index
 Firebase Analytics
 Firebase Test Lab for Android

19
DDS

2.2 ANDROID STUDIO:


Android Studio is the official integrated development environment (IDE)
for Android application development. It is based on the IntelliJ IDEA, a
Java integrated development environment for software, and incorporates
its code editing and developer tools.
To support application development within the Android operating system,
Android Studio uses a Gradle-based build system, emulator, code
templates, and Github integration. Every project in Android Studio has
one or more modalities with source code and resource files. These
modalities include Android app modules, Library modules, and Google
App Engine modules.
Android Studio uses an Instant Push feature to push code and resource
changes to a running application. A code editor assists the developer with
writing code and offering code completion, refraction, and analysis.
Applications built in Android Studio are then compiled into the APK
format for submission to the Google Play Store.
The software was first announced at Google I/O in May 2013, and the first
stable build was released in December 2014. Android Studio is available
for Mac, Windows, and Linux desktop platforms. It replaced Eclipse
Android Development Tools (ADT) as the primary IDE for Android
application development. Android Studio and the Software Development
Kit can be downloaded directly from Google.

2.2.1 Features of Android Studio


Instant App Run
It is an advanced technology in which it cleverly understands the
transmutations done in the applications and deliver it instantly without
taking time to rebuild the apk and installations make. So, quick that you
can see the changes in app immediately. This is done by launching the

20
DDS

URL on Android application installing the native libraries with Android


Instant apps. Instant App sometimes is known as " New Module Wizard".
Visual Layout Editor
Layout editor helps to build the layout quickly by adding different
attributes either by hard-code or drag and drop. The preview of the codes
can be seen easily on the visual editor screen and changes can be made
accordingly by resizing it dynamically. This will make testing the
application process more facile and more exhaustive.
Fast Emulator
Android has a great feature of Emulator which is exactly like the android
phones to test how the application looks like in physical devices. It gives
real-time experience to the Android applications. It allows you to test your
applications faster and on different-different configuration devices like
tablet, android phone etc. It helps you to make your application
development life cycle shorter and more efficient.
Intelligence Code Editor
Android Studio provides you with the intelligent and quick code editor.
This will help you and guide you with the accurate code. It helps you to
complete code in advance and analyze your code in advance before
building. Android studio has the special feature of the development of
code by the drop-down list with suggesting the code you can integrate.
Addition of New Activity as a Code Template
Yes, Android also has the feature of templates built-in. If you know to
build that accordingly that makes your task easier. it has both pros and
cons, you don't find every template in Android Studio. It's an additional
feature which helps the developer to build an application efficiently and
effectively which provide effective solutions.
Help to Build Up App for All Devices
Android studio builds applications for every screen size, for wear and gear
devices etc. It also can stimulate the various type of features which a
hardware has like GPS location tracker, multi-touch.

21
DDS

Help to Connect with Firebase

Android Studio helps to give real-time experience with IOT based project
development with dynamic upgrades in the application.
Firebase connectivity help to create direct updates and provide databases
connectivity. To build high-quality applications we must use Firebase
connectivity it helps to build the scalable infrastructure for building the
application. You can create chat applications by using firebase
connectivity it helps you to do happy chat experience.
Support KOTLIN
Kotlin the official language can be considered for Android. It is a
language without having any new restrictions and has various advantages
in it. The great feature of Kotlin is it run without any disturbances in older
android versions as well that means no issues of specific android versions.
It runs fast and equivalent to Java. Java developers can easily hands-on
Kotlin with no-issues because it is based on automated java.

22
DDS

CHAPTER 3
PROPOSED METHODOLOGY
3.1 PROBLEM DEFINITION:

3.2PROJECT OBJECTIVES:
1. Identify symptoms that enable you to understand how to address any disease.

2. Identify common diseases for the customer.

23
DDS

3. Discover opportunities to optimize their customer health details.

4. Store the customer report.

5. Drawing an association between symptoms and illness.

3.3 METHODOLOGY USED:

Figure 3.1: Iterative Waterfall Model

24
DDS

Iterative Waterfall Model is used to develop the project. The Iterative Waterfall Model
follows the same approach as the Waterfall Model except that it also provides an iterative
approach to do any kind of modification needed even if the Phase of the Software
Development Life Cycle is complete.

SDLC, Software Development Life Cycle is a process used by software industry to


design, develop and test high quality software’s. The SDLC aims to produce a high
quality software that meets or exceeds customer expectations, reaches completion within
times and cost estimates.

customer expectations, reaches completion within times and cost estimates.

 SDLC is the acronym of Software Development Life Cycle.

 It is also called as Software development process.

 The software development life cycle (SDLC) is a framework defining tasks performed
at each step in the software development process.

 ISO/IEC 12207 is an international standard for software life-cycle processes. It aims to


be the standard that defines all the tasks required for developing and maintaining
software.

A typical Software Development life cycle consists of the following stages:

 Stage 1: Planning and Requirement Analysis

 Stage 2: Defining Requirements


 Stage 3: Designing the product architecture

 Stage 4: Building or Developing the Product

 Stage 5: Testing the Product

Reason to Choose Iterative Waterfall Model

25
DDS

We have used this model in our project (Lucknow Metro World) android application
because of the following factors:

 We have complete knowledge of the requirements of the user and the system needs.

 We as beginners opted for iterative waterfall model over other models because we
decided to release our projects in builds.

 This project involves only two members so iterative waterfall model was the best
choice as this model is used where less number of people are involved in the project.

 For a very small time span at least core product can be delivered.28 Our project is an
android application so we decided to update it frequently according to the market needs.

 This model manages the technical risk with each update.

The phases of the Model are

 Feasibility Study: In this phase our aim is to determine that whether it would be
technically and financially feasible to develop the desired Project. Since android is an
open source platform so the cost of the project in monetary terms in nil. Technically as
android supports sharing of various contents it became possible for us to implement our
objectives.

 Requirement Analysis and Specification: In this phase we mainly prepared the


Software Requirement Specification document which contained mainly Architecture
diagram, Use Case Diagram and Sequential Diagram and an overview of the project.

 Design: In this phase we mainly concentrated on converting the requirement as


described in the Software Requirement Specification document into an interactive
application by making the basic architecture of the project.

 Coding: In this phase we mainly worked to translate the software design into source
code. Here the various features like playing audio and video files on a single station in a
very comprehensive manner.

26
DDS

 Testing: In this phase we mainly worked to remove all the errors form our project. The
testing of the project was done in two ways:

 Unit Testing: In this each module was unit tested to determine the correct
working of all the individual module. We have used Toasts as a mean of visual
display to know the proper working of a module. Along with it we have used
Toast pop-ups to inform whether it is the first or last song in the list.

 Integration Testing: In this integration of different modules is undertaken. All


the different modules are combined together and tested weather they are working
together correctly or not

 Maintenance: Maintenance phase mainly involves any change to be made to


the software project after it had been delivered to the customer. We will remove
any bugs or errors coming in the practical implementation of the project. And will
be releasing updates of the project with proceed in technology, more custom made
backgrounds will be given. We will try to improve the user interface by using new
sliding and widget features.

3.4. THEORY:

Technology used

Android is a software package and Linux based operating system for mobile
devices such as tablet computers and smartphones. It is developed by Google and
later the OHA (Open Handset Alliance). Java language is mainly used to write the
android code even though other languages can be used.

27
DDS

The goal of android project is to create a successful real-world product that


improves the mobile experience for end users.

There are many code names of android such as Lollipop, Kitkat, Jelly 30 Bean,
Ice cream Sandwich, Froyo, Eclair, Donut etc. which is covered in next page.

Open Handset Alliance (OHA)

It's a consortium of 84 companies such as Google, Samsung, AKM, synaptics,


KDDI, Garmin, Teleca, Ebay, Intel etc. It was established on 5th November,
2007, led by Google. It is committed to advance open standards, provide services
and deploy handsets using the Android Platform.

3.5 SOFTWARE AND HARDWARE REQUIREMENTS AND SPECIFICATION:

 Microsoft Windows 7/8/10 (32-bit or 64-bit)

 2 GB RAM minimum, 8 GB RAM recommended

 2 GB of available disk space minimum, 4 GB Recommended (500 MB for IDE + 1.5 GB


for Android SDK and emulator system image)

 1280 x 800 minimum screen resolution

 JDK 8

 For accelerated emulator: 64-bit operating system and Intel processor with support for
Intel VT-x, Intel EM64T (Intel 64), and Execute Disable (XD) Bit functionality

Software Requirements

 Windows 10

 Android Studio  Java

Hardware Requirements

Hard Disk – 2 GB31

28
DDS

RAM – 3 GB

Storage – min 500 MB

Smart phone – android version above 5.

3.6MODULE DESCRIPTION

3.6.1 Welcome Module

3.6.2 Symptoms Module

3.6.3 Diseases Module

3.6.3 Quiz Module

3.7 AREA OF WORK

The project is basically aimed at providing a platform where users can see diseases according to
symptoms and also provide first aid.

User can also see all details of diseases and also precautions of that diseases. User can see risk
factors and treatment and how they can care for self.

User can see only diseases which is not according to symptoms and also take advice of risk
factor, treatment and selfcare.

User can take quiz for knowing knowledge of diaseases.

29
DDS

3.8 PROPOSED TITLE:

Disease Diagnosis through Symptoms

To conclude,

 All Diseases

 All Symptoms

 Services

Advice

3.9 DIAGRAM OF THE MODEL:

3.9.1 Data Flow Diagram

Context Diagram. A context diagram is a top level (also known as "Level 0") data flow diagram. It
only contains one process node ("Process 0") that generalizes the function of the entire system
in relationship to external entities.

DFD Layers- Draw data flow diagrams can be made in several nested layers. A single process
node on a high level diagram can be expanded to show a more detailed data flow diagram. Draw
the context diagram first, followed by various layers of data flow diagrams.

DFD Levels- The first level DFD shows the main processes within the system. Each of these
processes can be broken into further processes until you reach pseudo code.

Level-0 DFD :

30
DDS

3.9.2 Use Case Diagrams

31
DDS

3.10 SCREENSHOTS

3.10.1 Application:

User

Splash Screen:

32
DDS

Home Page

33
DDS

CHAPTER 4

RESULT, ANALYSIS AND DISCUSSION

4.1 TESTIN

Our application Disease Diagnosis through Symptoms is tested ensuring that it meets all the
objectives and fulfill user requirement.

We have performed 4 types of testing in our project –

 Unit Testing
 Integration Testing
 System Testing
 Device testing

 Unit Testing

Unit testing is a level of software testing where individual units / components of a software are
tested. The purpose is to validate that each unit of the software performs as in the application
we have performed unit testing by running our code after every build. This will verify that the
logic of individual unit is correct. Running unit tests after every build helps us to quickly catch
and fix software regression introduced by code changes to your app. For every submodule
made, we run that application to see if there is any error. If any error, it appear in the run
window of android studio.

 Integration Testing

Integration testing (sometimes called integration and testing, abbreviated I&T) is the phase in
software testing in which individual software modules are combined and tested as a group.
Integration testing is conducted to evaluate the compliance of a system or component with
specified functional requirements. It occurs after unit testing and before validation testing.
Integration testing takes as its input modules that have been unit tested, groups them in larger

34
DDS

aggregates, applies tests defined in an integration test plan to those aggregates, and delivers as
its output the integrated system ready for system testing

Figure 4.1: Testing

 System Testing

It is testing conducted on a complete integrated system to evaluate the system's compliance


with its specified requirements.

35
DDS

System testing takes, as its input, all of the integrated components that have passed integration
testing. The purpose of integration testing is to detect any inconsistencies between the units
that are integrated together (called assemblages). System testing seeks to detect defects both
within the "inter-assemblages" and also within the system as a whole. The actual result is the
behavior produced or observed when a component or system is tested System testing is
performed on the entire system in the context of either functional requirement specifications
(FRS) or system requirement specification (SRS), or both. System testing tests not only the
design, but also the behaviour and even the believed expectations of the customer. It is also
intended to test up to and beyond the bounds defined in the software or hardware
requirements specification(s).

 Device Testing

We have made Disease Diagnosis through Symptoms application flexible enough such that it
can be used in different device. Minimum requirement of Android version is 6.0 (Marshmallow).
It includes Relative Layout thus making it adaptable to different mobile phone’s screen sizes. We
have made our application to run various android devices to see if the application is working
properly in different environment.

4.2 TEST CASES

Test Cases In addition to functionality based test cases, Mobile application testing requires
special cases which should cover following scenarios

 Battery usage

It's important to keep a track of battery consumption while running application on the mobile
devices. Our application does not consume much battery

 Speed of the application

The response time on different devices with different memory parameters with different
network types etc. The app works smoothly and efficiently only the functionality that required
internet can work slowly when the network or internet connection is poor.

36
DDS

 Data requirements

For installation one does not require any data plan the application is only of size 2 MB so it can
be easily downloaded by the user with limited data plan

 Memory requirement

It is important to know the memory that has been used for installing the application Too big
application are not much handy or useful The application is downloaded again to analyze if it’s
still running smoothly without any bug

 Functionality of the application

We have made sure that application is not crashing due to network failure or anything else. The
functionality that require internet will not work if the internet is not present or any network
failure all the other functionality offline objective) will still work smoothly

 Maintenance We

will maintain the project by releasing new updates of the project As per the and new
requirements of the user, new functionality will be 50 added to the New update can also include
many more emotions to be judged.

 Cost/Benefit Analysis

Cost Benefit analysis performed to ascertain whether the cost in the system match with the
benefits it will provide. Various cost that incur in one project is cost-There is no extra cost
incurred in sassing this project except requirement of smart phone Our application is free and
can be easily download from the Google play store Software cost-There is no cost required to
make this project apart from the effort and knowledge.

 Cost Estimation

The objective of the cost estimation is to enable the client or developer to perform a cost-
benefit analysis and for project monitoring and control. The accuracy of the estimate depends
on the amount of reliable information about the final product. When the product is delivered,

37
DDS

the cost can be accurately determined, as all the dates about the project and the resource spent
can be fully known by then.

 COCOMO Model

We have performed cost estimation of this project through Basic COCOMO model since all the
requirements are already known. Now given below is the detailed description of Basic COCOMO
model that will helps to understand the cost estimation of the app better.

Basic COCOMO Model computes:

 Software development effort (and cost) as a function of program size51

 Program size is expressed in estimated thousands of source lines of code (SLOC, KLOC)

 Development Time for Application.

 People required to make the application.

4.3 APPLICATION, ADVANTAGES AND LIMITATION OF THE PROJECT

Applications

 Provides the facility to report accidents.

 Provides the facility to report incidents of corruption.

 Provides the facility to report traffic.

 Provides the facility to user to share their stories, incidents, experiences on public platform on
above mentioned topics.

 It tracks the location of user and sends to associated authorities so that immediate action can
take place.

Advantages:
The main advantage of such a system is to:
1) It helps to know about your medical health.
38
DDS

2) It helps to know about any illness.


3) It helps to find the medicine for any specific illness.
4) It helps to find any specific hospital.
5) It helps to keep record of your searched data.
6) It helps to find phone number of any specific doctor.

Limitations

 It requires proper internet connectivity.

 May not be accessible to people in remote or rural areas.

 People may take ill benefit by reporting false incidents of corruption

CHAPTER 5

CONCLUSION

 Using mobile application as a means of service management, giving people convenience


to report cases online.
 This application has varieties of features such as public review,discussions,sharing
incidents.
 This application also helps the government to keep an eye on such evil incidents taking
place in the society.
 This app is providing an platform to give honour to those who has fight against
corruption cases by reporting them.
 The citizen can get immediate help in case of accidents and traffic.
 Hence this project helps to strengthen and form an transparent relationship between
the people of the country and the government.

39
DDS

CHAPTER 6
FUTURE SCOPE OF THE PROJECT
 The disease diagnosis is used to diagnose any specific disease through its symptoms and
vice versa.
 This project will help people to diagnose any illness from anywhere.
 It will also tell whether the user will need to get test to get confirm result of their
disease.
 It tells users about precautions of disease. It also finds appropriate medicine for the
illness.
 It also helps find specific hospitals and specialist for disease. It also finds the contact
details of hospitals and doctors.

40

You might also like