Anda di halaman 1dari 85

Paediaroid: Toddlers Healthcare and

Emergency App
Mid Review Report
Project ID: 10

Submitted to
Sri Lanka Institute of Information Technology

In partial fulfillment of the requirements for the


Degree of Bachelor of Science in Information Technology

September, 2015

Declaration
We hereby declare that the project work entitled Paediaroid Toddlers healthcare and
emergency app, submitted to the Sri Lanka Institute of Information Technology is a record
of an original work done by us, under the guidance of our Supervisor Mr. Ivantha Guruge.
This project work is submitted in the partial fulfillment of the requirement for the award of
the degree of Bachelor of Science in Information Technology. The results embodied in this
report have not been submitted to any other University or Institution for the award of any
degree or diploma. Information derived from the published or unpublished work of others has
been acknowledged in the text and a list of references is given.
Project Title

: Paediaroid Toddlers healthcare and emergency app

Project ID

: 10

Names of the authors

Student ID

Student Name

IT 13 0917 12

L V Jayasinghe

IT 13 2331 36

B M Lasantha Ranjana Bandara

IT 13 2454 98

L M C Jayasinghe

IT 13 2380 18

C S Dissanayake

Signature

Date of Submission: 01st of September 2015


Internal Supervisor:
Mr. Ivantha Guruge
Name

Signature

Date

Signature

Date

Acceptance by Lecture in charge:


Ms. Gayana Fernando
Name

Acknowledgement
The Paediaroid team would like to express our sincere sense of gratitude to our institution;
Sri Lanka Institute of Information Technology (SLIIT). We are deeply indebted to our
Lecturer in charge for the subject Comprehensive Design/Analysis Project Ms. Gayana
Fernando, whose help, stimulating suggestions, knowledge, experience and encouragement
helped us in all the times of study and analysis of the project in the pre and post research
period. We are also grateful to our supervisor Mr. Ivantha Guruge who helped us in many
ways to a great extent in the project. Also very special thanks to the lecture panel as well as
our seniors for their endless support given at times of difficulty. The completion of this
undertaking could not have been possible without the participation and assistance of so many
people whose names may not all be enumerated.

II

Abstract
This document describes the research based upon the android system which is developed for disease diagnosing,
predicting, and provision of solutions for toddlers and infants. The system consists of a mobile application
developed for the android platform and a web based service application to provide much faster processing
solutions rather processing the data interrupting the performance the mobile. Emergence of wireless and mobile
technologies plays a key role in the global IT boost, unfolding a new era of communication technology.
Similarly, different efforts have been taken to develop applications for patients; specially on diagnosing medical
conditions of infants, by replacing the diagnosis part of a doctor. The proposed system would play a significant
and a unique asset for android users. In addition to providing real time presentation, the integrated system will
provide voice instructions through the applications. On the other hand the application integrates data mining
algorithms which in return results for future predictions on the disease conditions of the user. The system will be
developed using the prototype methodology as a concept and the findings of the research. As a research project,
a number of available technologies will be studied and evaluated in order to maintain the scope, cost and time
more effective in developing the system as well as its use and maintenance.
Keywords: Toddlers, Patients, Infants, Android, Data Mining Algorithms, Medical Diagnosis, Predictions

III

Table of Contents
1

Introduction ................................................................................................................... 1
1.1

Background Context ............................................................................................... 1

1.2

Research Problem to be Addressed.......................................................................... 4

1.3

Research Questions ................................................................................................. 4

1.4

Research Objectives ................................................................................................ 5

1.5

Scope of the Research ............................................................................................. 5

1.6

Research Contribution ............................................................................................. 6

1.7

Structure of the Report ............................................................................................ 6

Literature Review .......................................................................................................... 7


2.1

Addressing the Literature ........................................................................................ 7

2.1.1

Colorectal smartphone apps: Opportunities & risks. ......................................... 7

2.1.2

Mobile personal health records An evaluation of features and functionality. .. 7

2.1.3

A Comprehensive Ubiquitous Healthcare Solution on an Android Mobile


Device. ............................................................................................................ 7

2.1.4

Smartphone applications for pain management. ................................................ 7

2.1.5

EpiCollect - Linking smartphones to web applications for epidemiology,


ecology and community data collection. ........................................................... 7

2.1.6

Review of Infectious Diseases Applications for iPhone/iPad and Android: From


Pocket to Patient. ............................................................................................. 8

2.1.7

Mobile Phone Based Clinical Microscopy for Global Health Applications. ...... 8

2.2

Research Findings ................................................................................................... 8

2.3

Research Gap .......................................................................................................... 8

Methodology ................................................................................................................. 9
3.1

Initiation & System Concept Development ............................................................ 10

3.2

Planning ................................................................................................................ 10

3.3

Analysis ................................................................................................................ 12

IV

3.4

3.4.1

Software Resources........................................................................................ 14

3.4.2

Hardware Resources ...................................................................................... 15

3.5

Integration and Test .............................................................................................. 16

3.6

Implementation ..................................................................................................... 16

3.7

Operation and Maintenance ................................................................................... 17

Results and Discussion ................................................................................................ 18


4.1

Evidence ............................................................................................................... 18

4.1.1

Interfaces ....................................................................................................... 18

4.1.2

Coding ........................................................................................................... 21

4.1.3

Test Cases and Test Results ........................................................................... 22

4.2
5

Design and Development ...................................................................................... 13

Discussion............................................................................................................. 25

Conclusion .................................................................................................................. 26
5.1

Importance of Outcome ......................................................................................... 26

5.2

Limitations ............................................................................................................ 26

5.3

Recommendations ................................................................................................. 26

5.4

Future Work.......................................................................................................... 27

References ................................................................................................................... 28

Appendices .................................................................................................................. 29
7.1

Appendices A ....................................................................................................... 29

7.1.1

Use Case Diagram ......................................................................................... 29

7.1.2

Class Diagram................................................................................................ 30

7.1.3

Entity Relationship Diagram (ER) .................................................................. 31

7.2

Appendices B ........................................................................................................ 32

7.2.1

Interfaces ....................................................................................................... 32

7.2.2

Test Cases and Test Results ........................................................................... 39

7.3

Appendices C ........................................................................................................ 71

7.3.1

Definitions, Acronyms, and Abbreviations ..................................................... 71

7.3.2

Questionnaire ................................................................................................. 72

VI

List of Figures
Figure 1 : Sri Lankan Mobile Handsets Market Share Q3-2014 ............................................. 2
Figure 2 : High Level Architecture of the System .................................................................. 3
Figure 3 : System Development Life Cycle ......................................................................... 10
Figure 4 : Welcome Page interface ...................................................................................... 18
Figure 5 : User Register interface ........................................................................................ 19
Figure 6 : Patient Register Interface .................................................................................... 20
Figure 7 : Use Case Diagram ............................................................................................... 29
Figure 8 : Class diagram ...................................................................................................... 30
Figure 9 : Entity Relationship Diagram ............................................................................... 31
Figure 10 : Guardian register interface ................................................................................ 32
Figure 11 : Doctor Register interface ................................................................................... 33
Figure 12 : Doctor Work Place Register interface ................................................................ 34
Figure 13 : Symptoms interface ........................................................................................... 35
Figure 14 : Prediction interface ........................................................................................... 36
Figure 15 : Precautions interface ......................................................................................... 37
Figure 16 : Emergency interface .......................................................................................... 38

VII

List of Tables
Table 1 : Statistics of Sri Lankan Mobile Handsets Market Share Q3-2014 ........................... 2
Table 2 : Login Validation test case 01 ................................................................................ 22
Table 3 : Login Validation test case 02 ................................................................................ 22
Table 4 : Login Validation test case 03 ................................................................................ 23
Table 5 : Login Validation test case 04 ................................................................................ 23
Table 6 : Login Validation test case 05 ................................................................................ 24
Table 7 : Login Validation test case 06 ................................................................................ 24
Table 8 : User Register Validation test case 01 .................................................................... 39
Table 9 : User Register Validation test case 02 .................................................................... 40
Table 10 : User Register Validation test case 03 .................................................................. 41
Table 11 : User Register Validation test case 04 .................................................................. 42
Table 12 : User Register Validation test case 05 .................................................................. 43
Table 13 : User Register Validation test case 06 .................................................................. 44
Table 14 : User Register Validation test case 07 .................................................................. 45
Table 15 : User Register Validation test case 08 .................................................................. 46
Table 16 : User Register Validation test case 09 .................................................................. 47
Table 17 : User Register Validation test case 10 .................................................................. 48
Table 18 : User Register Validation test case 11 .................................................................. 49
Table 19 : Patient Register Validation test case 01............................................................... 50
Table 20 : Patient Register Validation test case 02............................................................... 51
Table 21 : Patient Register Validation test case 03............................................................... 52
Table 22 : Patient Register Validation test case 04............................................................... 53
Table 23 : Patient Register Validation test case 05............................................................... 54
Table 24 : Patient Register Validation test case 06............................................................... 55
Table 25 : Patient Register Validation test case 07............................................................... 56
Table 26 : Patient Register Validation test case 08............................................................... 57
Table 27 : Patient Register Validation test case 09............................................................... 58
Table 28 : Guardian Register Validation test case 01 ........................................................... 59
Table 29 : Guardian Register Validation test case 02 ........................................................... 59
Table 30 : Guardian Register Validation test case 03 ........................................................... 59
Table 31 : Guardian Register Validation test case 04 ........................................................... 60
Table 32 : Family Doctor Register Validation test case 01 ................................................... 60

VIII

Table 33 : Family Doctor Register Validation test case 02 ................................................... 61


Table 34 : Family Doctor Register Validation test case 03 ................................................... 61
Table 35 : Family Doctor Register Validation test case 04 ................................................... 62
Table 36 : Family Doctor Register Validation test case 05 ................................................... 62
Table 37 : Family Doctor Register Validation test case 06 ................................................... 63
Table 38 : Family Doctor Work Place Register Validation test case 01 ................................ 64
Table 39 : Family Doctor Work Place Register Validation test case 02 ................................ 64
Table 40 : Family Doctor Work Place Register Validation test case 03 ................................ 65
Table 41 : Family Doctor Work Place Register Validation test case 04 ................................ 65
Table 42 : Family Doctor Work Place Register Validation test case 05 ................................ 66
Table 43 : Family Doctor Work Place Register Validation test case 06 ................................ 66
Table 44 : User checks for the Disease Condition test case 01 ............................................. 67
Table 45 : User checks for the Disease Condition test case 02 ............................................. 67
Table 46 : User checks for the Precaution test case 01 ......................................................... 68
Table 47 : User checks for the Precaution test case 02 ......................................................... 68
Table 48 : User checks for the Precaution test case 03 ......................................................... 69
Table 49 : User checks on the Emergency test case 01......................................................... 69
Table 50 : User checks on the Emergency test case 02......................................................... 70
Table 51 : User checks on the Emergency test case 03......................................................... 70
Table 52 : Definitions, Acronyms, and Abbreviations ......................................................... 71

IX

1 Introduction
1.1 Background Context
Substantial efforts have been spent upon developing disease diagnosing, predicting, and
providing solutions for the android application users to handle day to day situations.
Emergence of wireless and mobile technologies plays a key role in the global IT boost,
unfolding a new era of communication technology. Similarly, different efforts have been
taken to develop applications for patients; specially on diagnosing medical conditions of
infants, by complimenting the diagnosis part of a doctor using new technologies. The
proposed research problem domain runs around the disease prediction regarding the pediatric
field. When considering the current development of android applications regarding disease
diagnosing, the trends must be steered towards much extensive curves and drifts. When
considering the overview of the project; the application has been developed focusing mainly
upon the toddlers, which is operated by their guardians. The research team has intended to
achieve specific requirements and alternatives in developing the proposed system. Advancing
the application with the rendering of voice instructions will be much more helpful for the
users to ease their operations, which will lead in facilitating the users a better experience. In
the main aspects of the research, an enhanced methodology will be used throughout the entire
course of the project in order to have a system in place for the users convenience at an early
stage, and to quickly refine real requirements and to reassure the requirements. When
sheering down these trends towards the Sri Lanka, the tendency in using android applications
has become much higher, encompassing a huge domain. Even mobile oriented services have
drastically taken more advanced steps in providing much better and accurate selections.
Despite the replacement of the component-role of a doctor through this application, a
technology revolution is fast replacing human beings with machines in virtually every sector
and industries globally.
The current statistics of the Mobile Handsets Market Share in Sri Lanka are as follows.
(According to the statistics of Sri Lanka: Mobile Handsets Market Review) [1].
A total of 1Million mobile handsets were shipped into Sri Lanka during the 3rd
quarter of 2014.
Compared to 0.9 Million mobile handsets shipped during Q2 2014, this is a Quarter
over Quarter growth of 11%.

Smart phone shipments have doubled during Q3 - 2014 (0.2 Million units), compared
to shipments during Q2 2014 (0.1 Million units).
Sri Lankan Mobile Handsets Market Share Q3-2014

Micromax
19%

Nokia
22%

E-tel
12%
Others (Samsung/Apple/Sony
etc.)
47%

Nokia

Others (Samsung/Apple/Sony etc.)

E-tel

Micromax

Figure 1 : Sri Lankan Mobile Handsets Market Share Q3-2014

The statistics can be summarized as follows,


Table 1 : Statistics of Sri Lankan Mobile Handsets Market Share Q3-2014

Brand

Operating System

Percentage of Market share

Nokia

Windows / Symbian

22 %

Others (Samsung/Apple/Sony etc.)

Android / iOS

47 %

E-tel

Java

12 %

Micromax

Java

19 %

Accordingly, there is a higher percentage of the market share of android and iOS operated
mobile phones which in return provide a bigger trend for the proposed application to be
developed under Android platform.
The following figure depicts the high level architecture of the system which is to be
implemented during the proceedings of the project steps.

Figure 2 : High Level Architecture of the System


The User logs in to the system
with the username and the password. The user selects the

symptoms of the toddler and the system will predict the disease condition for you. If the
disease condition is an emergency situation, the user is allowed to inform the Guardian and
the doctor via a text message. And also the user is eligible to view his/her current location in
an emergency situation. More over the user can check for the nearest hospitals based on the
current location as well. On the other hand the user can listen to the precautions that should
be given for the particular disease condition.

1.2 Research Problem to be addressed


The main research problem is based upon the disease prediction upon the pediatric field,
where the symptoms of kids and babies will be used in predicting the precautions that a
guardian should follow through in an event of a disease condition. In the process of
identifying a disease condition of a child, guardians or parents might not have an idea of
performing several required precautions before they consult a doctor or acquiring the help of
a hospital. If the area they live becomes new, they might not have the utmost courage to
locate a doctor or a hospital in an emergency situation. Even they might not have the time to
be spent upon reading instructions or precautions to be taken at such an event while handling
functionalities of the mobile. And also, contacting their family members (the guardians as
mentioned in the application) will leave a blank space. Even the patient might not be able to
predict the future events regarding the current situation of his disease condition. This will
result in several major problems, as well as it leads the guardians in unmanageable
circumstances. The currently proposed system will contribute in providing several solutions
for the above mentioned problem areas.

1.3 Research Questions


How to identify the disease using the symptoms provided by the user?
How to provide the accurate predictions and precautions for the disease?
How to provide better future predictions to the uses?
How can we provide a communication interface among guardians and family doctors
through the application?
How to provide information regarding specialized and common disease conditions?

1.4 Research Objectives


The Research objective was to design and implement an android application where the
disease can be predicted with physically identified symptoms. The following objectives were
achieved.
1. To provide accurate instructions to guardians
2. Send a text message to the guardian about toddlers situation in an emergency
situation
3. Providing a well identified and a wide range of disease diagnosing expertise in
predicting the symptoms of common infant diseases
4. Acquire a good guidance by providing accurate instructions for taking the necessary
precautions
5. Establishing a communication interface with the guardians and the family doctor for
better safety
6. Providing locations of the nearby hospitals through a location based service
7. Supporting any emergency situational conditions
8. To provide voice instructions rather reading the instructions precautions that should
be taken, through the phone

1.5 Scope of the Research


The main scope of the Paediaroid research project runs around the disease prediction
pediatric field, where the symptoms of kids and babies will be used in predicting the
precautions that a guardian should follow through in an event of a disease condition. When
considering the overview of the project; the application has been developed focusing mainly
upon the toddlers, which is operated by their guardians. The research team has intended to
achieve specific requirements and alternatives in developing the Android based application
which communicates with a service application covering the server and the predicting
internal application.

1.6 Research Contribution


The main contribution of the Paediaroid application engages in providing an interface for the
guardians of toddlers, in achieving much accurate precautions at an event of a disease
condition of any specific toddler. A limited number of disease conditions will be
implemented with the commencing of the development of the application as a start. The
Paediaroid team targets to achieve the objectives through the Paediaroid android application,
which in return benefits the parents and guardians of toddlers.

1.7 Structure of the Report


The structure of this report is as follows and provides the following information regarding the
Paediaroid application and the research.
Chapter 1-Introduction
This contains the background of Paediaroid, the problems that are identified, the scope of the
project and the benefits which can be achieved through implanting the proposed solution
system.
Chapter 2- Literature Review
This contains the past review for the Paediaroid project, the team sought out and studied
various patents, research papers, documents, and newspaper and magazine articles from
various sources. A summary of the findings and research gap was contains this section.
Chapter 3-Methodology
This includes how the system was developed step by step using the Software Development
Life Cycle, System diagrams which gives an overview of the project from inception to the
final stage of completion. Further it contains the rationale for the softwares and the
technologies used.
Chapter 4- Results & Discussion
Under this section the final achievements of the proposed system and its unique features are
described using the main tasks of the web site.
Chapter 5-Conclusion
This chapter gives an evaluation of the project. The final outcomes achieved, problems
encountered, and suggestions for further development and enhancements of the system are
stated at the end of the document.

2 Literature Review
2.1 Addressing the Literature
In the literature review of the Paediaroid project, the research team sought out and studied
various patents, research papers, documents, and newspaper and magazine articles from
various sources. The following section comprises of an overview of the researches that had
conducted regarding the standardized problem domain.
2.1.1 Colorectal smartphone apps: Opportunities & risks.
S. ONeill and R. R. W. Brady have reviewed

[2]

contemporary medical apps specifying

colorectal diseases and assess levels of medical professional involvement in their design and
content. The paper concluded stating the lack of involvement of the guidance of doctors, and
the offset of the benefits of colorectal specialization.
2.1.2 Mobile personal health records An evaluation of features and functionality.
Hadi Kharrazi et al.

[3]

evaluated stand-alone mobile personal health record applications for

iOS, BlackBerry, and Android assessing each for product characteristics, data elements, and
features.
2.1.3 A Comprehensive Ubiquitous Healthcare Solution on an Android Mobile Device.
Pei-Cheng Hii and Wan-Young Chung [4], have proposed the smart phone device as a mobile
monitoring terminal to observe and analyze ECG (Electrocardiography) waves from wearable
ECG devices in real time under the coverage of a wireless sensor network (WSN).
2.1.4 Smartphone applications for pain management.
Benjamin A Rosser and Christopher Eccleston [5] conducted a research regarding the apps on
generic pain conditions on five major mobile platforms. The results concluded the limitations
and the requirements of proper guidance and appropriate expertise.
2.1.5 EpiCollect - Linking smartphones to web applications for epidemiology, ecology
and community data collection.
Aanensen DM et al. [6] describes an android application which was developed as a framework
allowing allows multiple epidemiological data records to be entered on a mobile phone and
synced to a centralized web database as well as the web application in return allows the
mapping, visualization and analysis according to the database records.

2.1.6 Review of Infectious Diseases Applications for iPhone/iPad and Android: From
Pocket to Patient.
This research paper

[7]

includes review of applications on Apple and Google Play app stores.

The review declares the lack of standards to guide accuracy or reliability of medical apps
content, and the identification of several comprehensive applications.
2.1.7 Mobile Phone Based Clinical Microscopy for Global Health Applications.
Breslauer DN et al.

[8]

pioneered in building a mobile phone-mounted light microscope

demonstrating its potential for clinical use; substantially resulted in a platform for highresolution clinical light microscopy.

2.2 Research Findings


Our research team provided application on the patients, especially on diagnosing medical
conditions of infants, providing instructions, precautions and predicting the future.
Toddlers application healthcare provide a well identified and a wide range of disease
diagnosing expertise in predicting the symptoms of common infant diseases.
Application were established a communication interface with the guardians and the
family doctor for better safety.
Provide locations of the nearby hospitals through a location based service
Paediaroid application supports any emergency situational conditions.
This provides voice instructions rather reading the instructions precautions that should
be taken, through the phone.

2.3 Research Gap


The unique solutions which are provided by the application are as follows.
Identification of the exact disease condition using the symptoms.
Providing the accurate predictions and precautions for the disease.
Leading reliable future predictions.
Acquiring a communication interface among guardians and family doctors in case of
an emergency.
Providing information regarding specialized and common disease conditions.
Rendering voice instructions which leads for a better usability and reliability of the
application.
Providing the locations of the nearest hospitals and their contact information.

3 Methodology
For the development and the implementation of the Paediaroid application System
Development Life Cycle (SDLC) is being currently adopted as the procedure. SDLC is a
systematic approach for application development or system development. SDLC is the
process of building the system that result in a high quality, cost-effective, within the proposed
time frame and efficient application that is cheap to maintain, easy to enhance and that can
work effectively

[9]

. SDLC is divided into several phases and each phase is comprised of

multiple steps, and they are as follows:


Initiation
System Concept Development
Planning
Analysis
Design
Development
Integration and Test
Implementation
Operation and Maintenance
A methodology is a formalized approach of implementing SDLC. It refers to the framework
that is used to structure, plan, and control the process of developing an information system. A
wide variety of such frameworks have evolved over the years, each with its own recognized
strengths and weaknesses. Each of the available methodologies is best suited to specific kinds
of projects, based on various technical, organizational, project and team considerations [10].
Prototype Methodology [11], [12] will be adapted for development of the Paediaroid application
as the procedure in delivering the product as an outcome. The prototyping methodology
performs the analysis, design, and implementation phases concurrently, and all three phases
are performed repeatedly in a cycle until the system is completed. The ultimate goal of
prototyping based development is to eliminate limitations of waterfall development
methodology. Thus prototype is developed based on the currently known requirements.

Figure 3 : System Development Life Cycle

3.1 Initiation & System Concept Development


The initiation phase is the first step in the SDLC where an organization or the clients initiates
the need of a requirement. In this phase project team will identify the requirement for the
Paediaroid application, why it should be built and develop a concept for the system. Both
initiation and System Concept Development goes together in a manner where the project is to
be commenced. The System Concept Development defines the boundary of the concept
including systems boundary document, cost benefit analysis, risk management plan and
feasibility study.

3.2 Planning
During the planning phase project management plans and the required other planning
documents are developed. This phase provides the basis for acquiring the resources needed to
provide the best solution for the requirements of the project.
Identifying project value As a team in this stage, the project need was identified. The
major value in developing the application was clearly identified. The basic functionalities
that are expected from the application were also clearly defined. Where the major are:

User Login

Locating nearby hospitals

Supporting emergency situations

Providing better predictions

10

Feasibility analysis This analysis helped to identify the risks associated with the project
and determines whether to proceed with the project. Technical feasibility was carried out
to identify the limitations associated with the available technology to develop the system
and to use the system. Financial feasibility was performed in order to identify the costs
and benefits associated with Paediaroid. Organizational feasibility was done in order to
identify how well the system will be ultimately accepted by its users.
Work plan A dynamic schedule of all tasks that need to be accomplished over the life of
the project is prepared. Therefore the overall objectives for the system were listed and all
the tasks that need to be accomplished to achieve these objectives were identified. Once
tasks were identified the estimated time needed to complete these tasks were calculated.
Staff plan Each member was assigned to work and develop at least one function of the
system. Apart from that, based on the skills they possess tasks were allocated to them.
Control and direct Until the end of the research, controlling and direction of the project
will be handled by the leader as well as the project supervisor. This will be carried out by
tracking tasks, refining estimates, motivating other members and make sure everything is
happening according to the schedule. A frequently updating repository log is maintained
to direct the members with respective tasks and share information among the group. A
project plan in the form of Gantt chart has been prepared and that will be used as a
measure of control and direction.

11

3.3 Analysis
The analysis phase provides analytical solutions for the questions of who will use the system,
what the system will do, and where and when, how it will be used.
Problem analysis In this stage the current systems regarding the pediatric healthcare
were analyzed and identified, how they operate, their strengths and weaknesses; and the
research team proposed the new concept for the development of the Paediaroid
application
Information gathering A crucial step to be followed in this stage is collection of
information.

Primary data gathering This process was done by gathering information from
others, by doing questioners and referring other related researches. The result and
questioners is produced below (Refer Appendix).

Secondary data gathering In this step, developers identified researches that were
done regarding Pediatric healthcare and other components by retreating existing
research papers and books. All the developers were involved in this step and using
this, the developers got a good idea about how to implement the system.

Process modeling Here object oriented modeling will be used. Set of graphic notation
techniques is used to create visual models of object oriented software intensive systems
which is known as the Unified Modeling Language. It would act as a communication tool
and UML will be effective for the future development purposes and understandings.
Shown below are the UML Diagrams of the system (Refer Appendix).
Data modeling In this stage it is expected to model the database scheme, the data model
will be compromised with the data types, attributes, relationship between data. For this
system will have to use advanced techniques as its expected to transfer navigation
information. In this special techniques are used to retrieve fast and securely from the data
stores. In data modeling will use a set of symbols and text to precisely explain a subset of
real information and thereby lead to a more flexible and stable application environment.
To represent the data model, Entity Relationship Diagram (ERD) will be developed
during this stage.

12

3.4 Design and Development


The primary objective of the design phase is to create a design that satisfies the agreed
application requirements. In the design phase the SDLC process continues to move from the
what" questions of the analysis phase to the "how" questions.
Physical design Here the logical diagrams that show the analysis phase requirements are
converted to physical diagrams. The goal of the design phase is to create a blue print for a
system that makes sense to implement. The input, output, storage, processing, recovery
and backup requirements are identified. The skills of the team members will be used to
come up with their own system looks and functions to suite the requirements.
Architecture design This resembles an important step of this stage, which is the plan for
the hardware, software and communications infrastructure for the new system, security
and global support. This system will be client-server architecture, therefore would build
the processing for the system into the server. This will be accessed by system admin
through client side devices to update the database. A network model then needs to be
developed to show how the computers, mobile phones, remote devices will be located and
connected to each other. A detail hardware and software requirements need is identified
which is given below. A security plan needs to be designed to address how to keep the
system and its data secure. Therefore the threats will be identified, the risk of each threat
will be assessed and then create controls to maintain security.
Interface design This process will define how the system will interact with external
entities such as users, administrators. The team will be more concerned on providing a
much attractive user interface for the users of the system. The reliable appearance of the
interfaces will be highly concerned. The colors of interfaces will be attractive and
sensible to use. The users satisfaction through simple pleasing attractive interfaces is
expected.
Database and file design In this stage, the Entity Relationship diagram which was
developed, was reanalyzed and was normalized in order to provide better database
functionalities to improve the efficiency of the communication between the database and
the application. The finalized tables which were created in the system were produced
along with the primary keys and relevant validations and constraints. The database will be
linked with the application developed. Queries which need to be run in the system will be
designed according to the functional requirements of the application.

13

Program design In this stage, the team will produce pieces of code and fit together to
form a program. The top-down modular approach will be adopted and structure chart can
be used as a technique to show all components of code that must be included in a program
at a high level. Each component will be fairly divided and developed within the team.
The following software and hardware requirements were utilized during the major stages of
the SDLC.
3.4.1 Software Resources
Can be categorized as
1. Software required in designing & implementing the system
2. Software required for the documentations
Software required in designing & implementing the system
Microsoft Visual Studio 2012
Microsoft SQL Server 2012
Microsoft .NET Framework 3.5 or higher
Eclipse
Android SDK
Software needed in the documentation
Microsoft Office Professional Plus 2013
Microsoft Project Professional 2013
Microsoft Visio Professional 2013
IBM Rational Software Architect Standard Edition 7.5
Word Web 7.1

14

3.4.2 Hardware Resources


Recommended Requirements for the development process of the system.

2GHz or faster multi core CPU

1GB or greater RAM

100GB hard disk space

A local server is used for the system testing purposes and in the implementation an
IIS Server will be used.
Android application simulator or a mobile phone

Android OS, v2.3.4 (Gingerbread) or Higher.

512 or greater RAM

Approach - The Object Oriented (OO) concepts will be used as an approach throughout
SDLC. The team will be modeling the system using Unified Modeling Language (UML)
which will help stakeholders to interact with system functionalities easily. The object
oriented approach has the following advantages.

Simplicity: Software objects model real world objects, so the complexity is


reduced and the program structure is very clear.

Modularity: Each object forms a separate entity whose internal workings are
decoupled from other parts of the system.

Modifiability: It is easy to make minor changes in the data representation or the


procedures in an OO program. Changes inside a class do not affect any other part
of a program, since the only public interface that the external world has to a class
is through the use of methods.

Extensibility: adding new features or responding to changing operating


environments can be solved by introducing a few new objects and modifying
some existing ones.

Maintainability: objects can be maintained separately, making locating and fixing


problems easier.

Re-usability: objects can be reused in different programs.

15

3.5 Integration and Test


Since costs of bugs will immense in testing phase, testing is one of the most critical steps in
prior to the implementation phase, which will effectively serves the errors of the program.
Identifying errors and fixing those bugs is a critical milestone in the development of a
software application. The system should be tested according to several stages. The following
are testing performed by the team to test the system. After development testing will be done
systematically and the results will be documented.
A test plan will be developed which will define a series of tests that will be conducted. Unit
tests will be carried out to ensure that the module or program performs its function as defined
in the specification. Integration tests will be carried out to assess whether a set of modules or
programs that must work together so without error. System test will be performed to ensure
that all modules and programs work together without error. Acceptance test will be
performed in order to make sure the system is complete, meets the need that is to increase
efficiency. All test cases and results should be properly documented for future references.

3.6 Implementation
Implementation is the final stage of SDLC. Here what the project team does is the
transformation of the design output into programs that are executable. A good
implementation reflects the design decisions.
Construction The hardware and software components required to solve the research
problem will be built. Planned software components for the mobile application and data
transfer services are to be implemented using the accurate protocols. Programming
languages such as Java and C# have been used for coding. Microsoft SQL Server 2012 is
currently being used for the development of database component. The modules that are
related, are grouped together so that each programmer is working on related program
modules and are assigned to programmers to implement. After implementing all modules,
they all are integrated to build the final System.
Installation As expected the server side applications will be installed, and the database
will be hosted on Microsoft IIS Server. Mobile applications will be loaded to the required
mobile platforms. More over the product is expected to be developed only up to a
prototype version. With the developments of project success the team might implement
up to the best level of implementation.

16

3.7 Operation and Maintenance


Continuous maintenance is expected to be made, since the system needs to be up to date and
going according to the rapidly changing user environments and the advancing development of
the technology used in developing new systems. Updates will be provided with the addition
of new disease conditions, better predictive results as well as much better user experience.

17

4 Results and Discussion


4.1 Evidence
4.1.1 Interfaces
Welcome Page
Once the user logs in to the application, the following interface is displayed. The user is
allowed to view/ edit the details via View Profile button and it is navigated to the Profile
page. The user can select the symptoms via Select Symptoms button and then user is
allowed to check on the symptoms. And also if the user needs to view the history of the
patient, user can view it via View History button. When the user is needed to logout from
the account, can be done via Logout button and it will navigate to the login page. And also
user can exit from the application via Exit button which will close the application.

Figure 4 : Welcome Page interface

18

User register
Once the user clicks on the register button, the following page is displayed. The user is
allowed to enter the name of the user, select the gender, and enter the designation, email,
contact number, username and the password. And also it is required to confirm the password
as well. The Application validates each and every field of the User registration. Once the
details are filled user needs to click on the Continue button in order to continue the
registration.

Figure 5 : User Register interface

19

Patient register
Once the user completed the User registration and continue, the following interface is
displayed which is needed to fill the patient details. The user is required to fill the name of
the patient, age, weight, height, select the gender and then enter the details of the patient,
special cases. The application validates each and field of the Patient registration. Once the
details are filled, User needs to click on the Continue button in order to continue the
registration.

Figure 6 : Patient Register Interface

20

4.1.2 Coding
SMS Code
public void Emergency_Interface(View view)
{
setContentView(R.layout.activity_emergency);
SmsManager smsManager = SmsManager.getDefault();
smsManager.sendTextMessage("0717167432", null, "It is an emergency Situation", null, null);
smsManager.sendTextMessage("0776988801", null, " It is an emergency Situation ", null, null);
Intent sendIntent = new Intent(Intent.ACTION_VIEW);
sendIntent.putExtra("sms_body", "default content");
sendIntent.setType("vnd.android-dir/mms-sms");
startActivity(sendIntent);
}

Voice Output
public void listenToPrecautions(View view)
{
setContentView(R.layout.activity_first_aid);
final TextView precaution;
// TextToSpeech test;
precaution = (TextView) findViewById(R.id.precaution);
test = new TextToSpeech(getApplicationContext(), new TextToSpeech.OnInitListener() {
@Override
public void onInit(int status) {
if (status != TextToSpeech.ERROR)
{
test.setLanguage(Locale.UK);
}
String toSpeak = (String) precaution.getText();
//Toast.makeText(getApplicationContext(),toSpeak,Toast.LENGTH_SHORT).show();
test.speak(toSpeak,TextToSpeech.QUEUE_FLUSH,null);
}
});
}

21

4.1.3 Test Cases and Test Results


Test Specification: Login Validation
Table 2 : Login Validation test case 01

Test Case : LV_ 01

User enters the Valid Username & the Valid Password


Navigate to the Correct Application.
Click on the Login.

Test Steps

Enter the Valid Username.


Enter the Valid Password.
Click Login.
Username

Inputs

Password

Expected Output

The application navigates to the Welcome Interface.

Test Result

Passed

Table 3 : Login Validation test case 02

Test Case : LV_ 02

User enters the Valid Username But an Invalid Password


Navigate to the Correct Application.
Click on the Login.

Test Steps

Enter the Valid Username.


Enter the Invalid Password.
Click Login.

Inputs

Username
Password

Expected Output

The application prompts an error Invalid Password

Test Result

Passed

22

Table 4 : Login Validation test case 03

Test Case : LV_ 03

User enters an Invalid Username But Valid Password


Navigate to the Correct Application.
Click on the Login.

Test Steps

Enter the Invalid Username.


Enter the Valid Password.
Click Login.
Username

Inputs
Password
Expected Output

The application prompts an error Invalid Username

Test Result

Passed

Table 5 : Login Validation test case 04

Test Case : LV_ 04

User does not enter either the Username or the Password.


Navigate to the Correct Application.
Click on the Login.

Test Steps

Does not enter the Username.


Does not enter the Password.
Click Login.

Inputs

No Inputs

Expected Output

The application prompts an error Enter Username

Test Result

Passed

23

Table 6 : Login Validation test case 05

Test Case : LV_ 05

User enters Username but does not enter the Password.


Navigate to the Correct Application.
Click on the Login.

Test Steps

Enter the Username.


Does not enter the Password.
Click Login.
Username

Inputs
Password
Expected Output

The application prompts an error Invalid Password

Test Result

Passed

Table 7 : Login Validation test case 06

Test Case : LV_ 06

User does not enter the username but enter the Password.
Navigate to the Correct Application.
Click on the Login.

Test Steps

Does not enter the Username.


Enter the Password.
Click Login.
Username

Inputs

Password

Expected Output

The application prompts an error Enter Username

Test Result

Passed

24

4.2 Discussion
When considering the current development of android applications regarding disease
diagnosing, the trends must be steered towards much extensive curves and drifts. When
considering the overview of the project; the application has been developed focusing mainly
upon the toddlers, which is operated by their guardians. The Paediaroid team mainly focused
on the latest technology advancement which in return will be a helping hand for the guardians
of toddlers to avoid these major troubles.
The research team first sorted out different systems regarding the pediatric health care and
proposed the main idea of developing the Paediaroid application. In order to increase the
reliability and the accuracy level of the application, the Paediaroid application utilizes a welldefined dataset with better accuracy levels; which were obtained from reliable data sources.
The dataset is arranged in such a way, the data structures are defined. The data mining
function is performed using an algorithm which is of high accuracy, which provides better
predicting results. Since the algorithm is tested using a better dataset, the accuracy level of
the predictions are in a much higher level; so that it increases the reliability and the accuracy
level of the application.
The Paediaroid application is a prototype system done in object oriented approach. Since the
research team has performed the unit testing and error handling well, the system is running
without any major issues but the proper testing with test cases are yet to be done. During the
development of the application the team faced several problems and issues in technical point
of view as well as in the view of implementing the application. They are as follows,
Issues in gathering accurate and reliable data sources.
Conflicts in choosing better disease conditions.
Providing reliable and accurate predictions to the users.
To overcome the above mentioned issues, the research team followed the following
techniques.
Gathered data from reliable sources.
Acquired advices from experienced pediatric doctors.
Created a dataset with better results.
Utilization of a better algorithm for prediction of results.

25

5 Conclusion
5.1 Importance of Outcome
The Paediaroid Project, Users (Guardian of the child) can easily identify the illnesses and
Control decease before going to bad condition. Users can use this software without having
wide knowledge about deceases and pre hospital care especially on diagnosing medical
conditions of infants, by replacing the diagnosis part of a doctor. It provides the easy way to
get decisions when patient is in bad situation. From this project the people who are using
android devices, recently can get an advantage. It helps to decrease child mortality rate by
giving instructions to guardian till patient admit to hospital, current location of the patient
will be provide to doctor and if it is emergency nearest hospital location also provide to
guardian. Finally System will give future prediction about disease to guardian.

5.2 Limitations
The Paediaroid android application provides decisions utilizing the medical conditions and
symptoms the user enters through the application. So In critical situation application will
guide the user for meet the doctor, since in critical events the decisions which are provided by
the application would decide the future events of the toddler. And also, this application
provides the precautions that should be taken by a guardian prior to
This project provides nearest hospital location and send message to guardian and family
doctor using the internet connectivity of the mobile device. Therefore the internet
connectivity must be available during the operations of the application.

5.3 Recommendations
There are several reasons for recommending the Paediaroid project.
Toddlers health care application is increase parents knowledge about toddler`s heath
care.
The connection between parent and family doctor can increase.
Child mortality rate can be decreased.
The parents can predict the future health of the child, which is supported by the
application.
The parents might not have much knowledge on diseases and the precautions that
should be given in case in an emergency by this application.

26

5.4 Future Work


In the future works, the team has suggested to develop the application on to a more advanced
level; by expanding the range of diseases that are predicted through the application. And also
the application can be developed in order to provide graphical images in following the
instructions which are provided by the application; so that the users can obtain a better idea in
following the required instructions and the precautions. Furthermore, the application would
be extended to provide predictions for children over 1-5 range of age, with more advanced
features and user functionalities.

27

6 References
[1]. CyberMedia Research (CMR) Sri Lanka Quarterly Mobile Handsets Market Review, Sri
Lanka:

Mobile

Handsets

Market

Review

Q3

2014

[Online],

Available:

https://infogr.am/sri-lanka-mobile-handset-market-review---q3-2014

and

http://digit.lk/sri-lanka-mobile-handsets-market-review-q1-2014/
[2]. ONeill, S. and Brady, R. R. W. (2012), Colorectal smartphone apps: opportunities and
risks. Csssolorectal Disease, 14: e530e534. doi: 10.1111/j.1463-1318.2012.03088.x
[3]. Kharrazi, Hadi, et al. "Mobile personal health records: an evaluation of features and
functionality." International journal of medical informatics 81.9 (2012): 579-593.
[4]. Hii, Pei-Cheng, and Wan-Young Chung. "A comprehensive ubiquitous healthcare
solution on an Android mobile device." Sensors 11.7 (2011): 6799-6815.
[5]. Rosser, Benjamin A., and Christopher Eccleston. "Smartphone applications for pain
management." Journal of telemedicine and telecare 17.6 (2011): 308-312.
[6]. Aanensen, David M., et al. "EpiCollect: linking smartphones to web applications for
epidemiology, ecology and community data collection." PloS one 4.9 (2009): e6968.
[7]. Moodley, Amaran, Julie E. Mangino, and Debra A. Goff. "Review of infectious diseases
applications for iPhone/iPad and Android: from pocket to patient." Clinical infectious
diseases 57.8 (2013): 1145-1154.
[8]. Breslauer, David N., et al. "Mobile phone based clinical microscopy for global health
applications." PloS one 4.7 (2009): e6320.
[9]. System

Development

Life

Cycle.

[Online].Available:

http://www.capacitywebsolutions.com/system_development_life_cycle.html
[10].

System Analysis and Design. Sri Lanka Institute of Information Techonology, 2014.

[11].

Prototype Methodology Information management, David Bowmans Information

Management

Checklist

[Online],

Available:http://www.information-management-

architect.com/prototyping-methodology.html
[12].

Jones, Toni Stokes, and Rita C. Richey. "Rapid prototyping methodology in action: A

developmental study." Educational Technology Research and Development 48.2 (2000):


63-80.

28

7 Appendices
7.1 Appendices A
7.1.1 Use Case Diagram

Figure 7 : Use Case Diagram

29

7.1.2 Class Diagram

Figure 8 : Class diagram

30

7.1.3 Entity Relationship Diagram (ER)

Figure 9 : Entity Relationship Diagram

31

7.2 Appendices B
7.2.1 Interfaces
Guardian register
Once the user completed the Patient registration and continue, the following interface is
displayed which is needed to fill the guardian details. The use is required to fill the name of
the guardian and the contact number. The application validates each and every field of the
Guardian registration. Once the details are filled, user needs to click on the Continue button
in order to continue the registration.

Figure 10 : Guardian register interface

32

Doctor register
Once the user completed the Guardian registration and continue, the following interface is
displayed which is needed to fill the family doctor details. The use is required to fill the name
of the doctor, contact number, address and the specialty. The application validates each and
every field of the Doctor registration. Once the details are filled, user needs to click on the
Continue button in order to continue the registration.

Figure 11 : Doctor Register interface

33

Doctor work place register


Once the user completed the Doctor registration and continue, the following interface is
displayed which is needed to fill the Doctors work place details. The use is required to fill
the place of work, contact number, working hours and address. The application validates each
and every field of the Doctor work place registration. Once the details are filled, user needs to
click on the Register button in order to confirm the registration.

Figure 12 : Doctor Work Place Register interface

34

Symptoms
Once the user clicks on the View Symptoms, the following page is displayed. The user can
check on the symptoms of the toddler and click on Predict. The application will validate the
symptoms, whether it is checked or not.

Figure 13 : Symptoms interface

35

Prediction
Once the user select the symptoms and click on Predict button the following page is
displayed. That is, it displays the disease condition of the toddler. The user can view for the
Precautions via Precautions button. And also if its an emergency condition, user can click
on Emergency button and it will send an SMS to the guardian and the family doctor
automatically mentioning about the emergency condition.

Figure 14 : Prediction interface

36

Precautions
Once the user clicks on the Precautions button in the Prediction page, the system will
displays the following interface. The first aid that should be given for the toddler is displayed
in the page and the user can listen to the precautions via Listen button. And also if it is
needed user can pause and stop the voice output via Pause and Stop buttons respectively.

Figure 15 : Precautions interface

37

Emergency
Once the user clicks on the Emergency button in the Prediction page, the system will
displays the following interface. Here if the user is required to view the current location,
he/she can check on it via View Current Location button and the system will detect your
location. And also if the user needs to check on the nearest hospitals click View nearest
hospitals button.

Figure 16 : Emergency interface

38

7.2.2 Test Cases and Test Results


Test Specification: User Register Validation
Table 8 : User Register Validation test case 01

Test Case : UR_ 01

User fill all the mandatory fields.


Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Select the Gender.
Enter the Designation.

Test Steps

Enter the Email.


Enter the Contact Number.
Enter the Username.
Enter the Password.
Enter the Confirm Password.
Click Continue.
Name
Gender
Designation
Email

Inputs
Contact Number
Username
Password
Confirm Password
Expected Output

The application will navigate to the Patient Register


Interface.

Test Result

Passed

39

Table 9 : User Register Validation test case 02

Test Case : UR_ 02

User does not fill all the mandatory fields.


Navigate to the Correct Application.
Click on the Register.
Does not enter the Name.
Does not select the Gender.
Does not enter the Designation.

Test Steps

Does not enter the Email.


Does not enter the Contact Number.
Does not enter the Username.
Does not enter the Password.
Does not enter the Confirm Password.
Click Continue.

Inputs

No Inputs

Expected Output

The application will prompt an error Fill Name.

Test Result

Passed

40

Table 10 : User Register Validation test case 03

Test Case : UR_ 03

User fill all the mandatory fields except the Name.

Test Steps

Navigate to the Correct Application.


Click on the Register.
Does not enter the Name.
Select the Gender.
Enter the Designation.
Enter the Email.
Enter the Contact Number.
Enter the Username.
Enter the Password.
Enter the Confirm Password.
Click Continue.

Inputs

Gender
Designation
Email
Contact Number
Username
Password
Confirm Password

Expected Output

The application will prompt an error Fill Name.

Test Result

Passed

41

Table 11 : User Register Validation test case 04

Test Case : UR_ 04

User fill all the mandatory fields except the Gender.


Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Does not select the Gender.
Enter the Designation.

Test Steps

Enter the Email.


Enter the Contact Number.
Enter the Username.
Enter the Password.
Enter the Confirm Password.
Click Continue.
Name
Designation
Email

Inputs

Contact Number
Username
Password
Confirm Password

Expected Output

The application will prompt an error Select Gender.

Test Result

Passed

42

Table 12 : User Register Validation test case 05

Test Case : UR_ 05

User fill all the mandatory fields except the Designation.


Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Select the Gender.
Does not enter the Designation.

Test Steps

Enter the Email.


Enter the Contact Number.
Enter the Username.
Enter the Password.
Enter the Confirm Password.
Click Continue.
Name
Gender
Email

Inputs

Contact Number
Username
Password
Confirm Password

Expected Output

The application will prompt an error Fill Designation.

Test Result

Passed

43

Table 13 : User Register Validation test case 06

Test Case : UR_ 06

User fill all the mandatory fields except the Email.


Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Select the Gender.
Enter the Designation.

Test Steps

Does not enter the Email.


Enter the Contact Number.
Enter the Username.
Enter the Password.
Enter the Confirm Password.
Click Continue.
Name
Gender
Designation

Inputs

Contact Number
Username
Password
Confirm Password

Expected Output

The application will prompt an error Fill Email.

Test Result

Passed

44

Table 14 : User Register Validation test case 07

Test Case : UR_ 07

User fill all the mandatory fields except the Contact


Number.
Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Select the Gender.
Enter the Designation.

Test Steps

Enter the Email.


Does not enter the Contact Number.
Enter the Username.
Enter the Password.
Enter the Confirm Password.
Click Continue.
Name
Gender
Designation

Inputs

Email
Username
Password
Confirm Password

Expected Output

The application will prompt an error Fill Contact


Number.

Test Result

Passed

45

Table 15 : User Register Validation test case 08

Test Case : UR_ 08

User fill all the mandatory fields except the Username.


Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Select the Gender.
Enter the Designation.

Test Steps

Enter the Email.


Enter the Contact Number.
Does not enter the Username.
Enter the Password.
Enter the Confirm Password.
Click Continue.
Name
Gender
Designation

Inputs

Email
Contact Number
Password
Confirm Password

Expected Output

The application will prompt an error Fill Username.

Test Result

Passed

46

Table 16 : User Register Validation test case 09

Test Case : UR_ 09

User fill all the mandatory fields except the Password.


Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Select the Gender.
Enter the Designation.

Test Steps

Enter the Email.


Enter the Contact Number.
Enter the Username.
Does not enter the Password.
Enter the Confirm Password.
Click Continue.
Name
Gender
Designation

Inputs

Email
Contact Number
Username
Confirm Password

Expected Output

The application will prompt an error Fill Password.

Test Result

Passed

47

Table 17 : User Register Validation test case 10

Test Case : UR_ 10

User fill all the mandatory fields except the Confirm


Password.
Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Select the Gender.
Enter the Designation.

Test Steps

Enter the Email.


Enter the Contact Number.
Enter the Username.
Enter the Password.
Does not enter the Confirm Password.
Click Continue.
Name
Gender
Designation

Inputs

Email
Contact Number
Username
Password

Expected Output

The application will prompt an error Passwords does not


match.

Test Result

Passed

48

Table 18 : User Register Validation test case 11

Test Case : UR_ 11

User fill the Email in the incorrect format


Navigate to the Correct Application.
Click on the Register.
Enter the Name.
Select the Gender.
Enter the Designation.

Test Steps

Enter the Email.


Enter the Contact Number.
Enter the Username.
Enter the Password.
Enter the Confirm Password.
Click Continue.
Name
Gender
Designation

Inputs

Email : abdf@.com
Contact Number
Username
Password

Expected Output

The application will prompt an error Fill Email.

Test Result

Passed

49

Test Specification: Patient Register Validation


Table 19 : Patient Register Validation test case 01

Test Case : PR_ 01

User fill the all the Mandatory fields.


Navigate to the Correct Page.
Enter the Name.
Enter the Age.
Enter the Weight.

Test Steps

Enter the Height.


Enter the Gender.
Enter the Details.
Enter the Special Cases.
Click Continue.
Name
Age
Weight

Inputs

Height
Gender
Details
Special Cases

Expected Output

The system will navigates to the Guardian Register Page.

Test Result

Passed

50

Table 20 : Patient Register Validation test case 02

Test Case : PR_ 02

User does not fill the all the Mandatory fields.


Navigate to the Correct Page.
Does not enter the Name.
Does not enter the Age.
Does not enter the Weight.

Test Steps

Does not enter the Height.


Does not enter the Gender.
Does not enter the Details.
Does not enter the Special Cases.
Click Continue.

Inputs

No inputs

Expected Output

The application will prompt an error Fill Patients Name.

Test Result

Passed

51

Table 21 : Patient Register Validation test case 03

Test Case : PR_ 03

User does not fill the all the Patients Name.


Navigate to the Correct Page.
Does not enter the Name.
Enter the Age.
Enter the Weight.

Test Steps

Enter the Height.


Enter the Gender.
Enter the Details.
Enter the Special Cases.
Click Continue.
Age
Weight
Height

Inputs
Gender
Details
Special Cases
Expected Output

The application will prompt an error Fill Patient Name.

Test Result

Passed

52

Table 22 : Patient Register Validation test case 04

Test Case : PR_ 04

User does not fill the all the Patients Age.

Test Steps

Navigate to the Correct Page.


Enter the Name.
Does not enter the Age.
Enter the Weight.
Enter the Height.
Enter the Gender.
Enter the Details.
Enter the Special Cases.
Click Continue.

Inputs

No inputs

Expected Output

The application will prompt an error Fill Age.

Test Result

Passed

53

Table 23 : Patient Register Validation test case 05

Test Case : PR_ 05

User does not fill the all the Patients Weight.


Navigate to the Correct Page.
Enter the Name.
Enter the Age.
Does not enter the Weight.

Test Steps

Enter the Height.


Enter the Gender.
Enter the Details.
Enter the Special Cases.
Click Continue.
Name
Age
Height

Inputs
Gender
Details
Special Cases
Expected Output

The application will prompt an error Fill Weight.

Test Result

Passed

54

Table 24 : Patient Register Validation test case 06

Test Case : PR_ 06

User does not fill the all the Patients Height.


Navigate to the Correct Page.
Enter the Name.
Enter the Age.
Enter the Weight.

Test Steps

Enter the Height.


Does not enter the Gender.
Enter the Details.
Enter the Special Cases.
Click Continue.
Name
Age
Weight

Inputs
Gender
Details
Special Cases
Expected Output

The application will prompt an error Fill Height.

Test Result

Passed

55

Table 25 : Patient Register Validation test case 07

Test Case : PR_ 07

User does not fill the all the Patients Gender.


Navigate to the Correct Page.
Enter the Name.
Enter the Age.
Enter the Weight.

Test Steps

Enter the Height.


Does not enter the Gender.
Enter the Details.
Enter the Special Cases.
Click Continue.
Name
Age
Weight

Inputs
Height
Details
Special Cases
Expected Output

The application will prompt an error Select Gender.

Test Result

Passed

56

Table 26 : Patient Register Validation test case 08

Test Case : PR_ 08

User does not fill the all the Patients Details.


Navigate to the Correct Page.
Enter the Name.
Enter the Age.
Enter the Weight.

Test Steps

Enter the Height.


Enter the Gender.
Does not enter the Details.
Enter the Special Cases.
Click Continue.
Name
Age
Weight

Inputs
Height
Gender
Special Cases
Expected Output

The application will prompt an error Fill Details.

Test Result

Passed

57

Table 27 : Patient Register Validation test case 09

Test Case : PR_ 09

User does not fill the all the Patients Special Cases.
Navigate to the Correct Page.
Enter the Name.
Enter the Age.
Enter the Weight.

Test Steps

Enter the Height.


Enter the Gender.
Enter the Details.
Does not enter the Special Cases.
Click Continue.
Name
Age
Weight

Inputs
Height
Gender
Details
Expected Output

The application will prompt an error Fill Special Cases.

Test Result

Passed

58

Test Specification: Guardian Register Validation


Table 28 : Guardian Register Validation test case 01

Test Case : GR_ 01

User fills all the mandatory fields


Navigate to the Correct Page.
Enter the Name.

Test Steps

Enter the Contact Number.


Click Continue.
Name

Inputs
Contact Number
Expected Output

The Application will navigate to the Family Doctor


Register Page.

Test Result

Passed

Table 29 : Guardian Register Validation test case 02

Test Case : GR_ 02

User does not fills all the mandatory fields


Navigate to the Correct Page.

Test Steps

Does not enter the Name.


Does not enter the Contact Number.
Click Continue.

Inputs

No inputs

Expected Output

The application will prompt an error Fill Name.

Test Result

Passed
Table 30 : Guardian Register Validation test case 03

Test Case : GR_ 03

User does not fills the Name of the Guardian.


Navigate to the Correct Page.

Test Steps

Does not enter the Name.


Enter the Contact Number.
Click Continue.
Inputs

Contact Number

Expected Output

The application will prompt an error Fill Name.

Test Result

Passed

59

Table 31 : Guardian Register Validation test case 04

Test Case : GR_ 04

User does not fill the Contact Number of the Guardian.


Navigate to the Correct Page.
Enter the Name.

Test Steps
Does not enter the Contact Number.
Click Continue.
Inputs

Name

Expected Output

The application will prompt an error Fill Contact


Number.

Test Result

Passed

Test Specification: Family Doctor Register Validation


Table 32 : Family Doctor Register Validation test case 01

Test Case : FDR_ 01

User fills all the Mandatory Fields.


Navigate to the Correct Page.
Enter the Name.

Test Steps

Enter the Contact Number.


Enter the Address.
Enter the Specialty.
Click Continue.
Name
Contact Number
Inputs
Address
Specialty
Expected Output

The Application will navigate to the Family Doctor Work


Place Register Page.

Test Result

Passed

60

Table 33 : Family Doctor Register Validation test case 02

Test Case : FDR_ 02

User does not fills all the Mandatory Fields.


Navigate to the Correct Page.
Does not enter the Name.
Does not enter the Contact Number.

Test Steps

Does not enter the Address.


Does not enter the Specialty.
Click Continue.

Inputs

No inputs

Expected Output

The application will prompt an error Fill Name.

Test Result

Passed

Table 34 : Family Doctor Register Validation test case 03

Test Case : FDR_ 03

User does not fill the Name of the Doctor.


Navigate to the Correct Page.
Does not enter the Name.

Test Steps

Enter the Contact Number.


Enter the Address.
Enter the Specialty.
Click Continue.
Contact Number

Inputs

Address
Specialty

Expected Output

The application will prompt an error Fill Name.

Test Result

Passed

61

Table 35 : Family Doctor Register Validation test case 04

Test Case : FDR_ 04

User does not fill the Contact Number of the Doctor.


Navigate to the Correct Page.
Enter the Name.
Enter the Contact Number.

Test Steps

Enter the Address.


Enter the Specialty.
Click Continue.
Name

Inputs

Address
Specialty

Expected Output

The application will prompt an error Fill Contact


Number.

Test Result

Passed

Table 36 : Family Doctor Register Validation test case 05

Test Case : FDR_ 05

User does not fill the Address of the Doctor.


Navigate to the Correct Page.
Enter the Name.
Enter the Contact Number.

Test Steps

Does not enter the Address.


Enter the Specialty.
Click Continue.
Name

Inputs

Contact Number
Specialty

Expected Output

The application will prompt an error Fill Address.

Test Result

Passed

62

Table 37 : Family Doctor Register Validation test case 06

Test Case : FDR_ 06

User does not fill the Specialty of the Doctor.


Navigate to the Correct Page.
Enter the Name.
Enter the Contact Number.

Test Steps

Enter the Address.


Does not enter the Specialty.
Click Continue.
Contact Number

Inputs

Address
Specialty

Expected Output

The application will prompt an error Fill Specialty.

Test Result

Passed

63

Test Specification: Family Doctor Work Place Register Validation


Table 38 : Family Doctor Work Place Register Validation test case 01

Test Case : FDWPR_ 01

User fill all the mandatory fields.


Navigate to the Correct Page.
Enter the Place of Work.
Enter the Contact Number.

Test Steps
Enter the Working Hours.
Enter the Address.
Click Register.
Place of Work
Contact Number
Inputs

Working Hours
Address

Expected Output

The application will navigate to the Login Page.

Test Result

Passed

Table 39 : Family Doctor Work Place Register Validation test case 02

Test Case : FDWPR_ 02

User does not fill all the mandatory fields.


Navigate to the Correct Page.
Does not enter the Place of Work.
Does not enter the Contact Number.

Test Steps
Does not enter the Working Hours.
Does not enter the Address.
Click Register.
Inputs

No Inputs

Expected Output

The application will prompt an error Fill Place of Work.

Test Result

Passed

64

Table 40 : Family Doctor Work Place Register Validation test case 03

Test Case : FDWPR_ 03

User does not fill the Place of work.


Navigate to the Correct Page.
Does not enter the Place of Work.
Enter the Contact Number.

Test Steps

Enter the Working Hours.


Enter the Address.
Click Register.
Contact Number

Inputs

Working Hours
Address

Expected Output

The application will prompt an error Fill Place of Work.

Test Result

Passed

Table 41 : Family Doctor Work Place Register Validation test case 04

Test Case : FDWPR_ 04

User does not fill the Contact Number.


Navigate to the Correct Page.
Enter the Place of Work.

Test Steps

Does not enter the Contact Number.


Enter the Working Hours.
Enter the Address.
Click Register.
Place of Work
Inputs

Working Hours
Address

Expected Output

The application will prompt an error Fill Contact


Number.

Test Result

Passed

65

Table 42 : Family Doctor Work Place Register Validation test case 05

Test Case : FDWPR_ 05

User does not fill the Working Hours.


Navigate to the Correct Page.
Enter the Place of Work.
Enter the Contact Number.

Test Steps

Does not enter the Working Hours.


Enter the Address.
Click Register.
Place of Work

Inputs

Contact Number
Address

Expected Output

The application will prompt an error Fill Working


Hours.

Test Result

Passed

Table 43 : Family Doctor Work Place Register Validation test case 06

Test Case : FDWPR_ 06

User does not fill the Address.


Navigate to the Correct Page.
Enter the Place of Work.
Enter the Contact Number.

Test Steps

Enter the Working Hours.


Does not enter the Address.
Click Register.
Place of Work

Inputs

Contact Number
Working Hours

Expected Output

The application will prompt an error Fill Address.

Test Result

Passed

66

Test Specification: User checks for the Disease Condition


Table 44 : User checks for the Disease Condition test case 01

Test Case : DC_ 01

User selects one or more of the Symptoms


Login as the user.
Click Select Symptoms.

Test Steps
Check on the Symptoms.
Click Predict.
Inputs

No inputs

Expected Output

The Application will navigate to the Disease Prediction


page and the predicted disease condition is displayed on
the page.

Test Result

Table 45 : User checks for the Disease Condition test case 02

Test Case : DC_ 02

User does not select any of the symptoms.


Login as the user.
Click Select Symptoms.

Test Steps
Does not check on the Symptoms.
Click Predict.
Inputs

No inputs

Expected Output

The Application will prompt an error Select the


Symptoms to Predict the Disease.

Test Result

67

Test Specification: User checks for the Precaution


Table 46 : User checks for the Precaution test case 01

Test Case : P_ 01

User listen to the precautions


Login as the user.
Click Select Symptoms.
Does not check on the Symptoms.

Test Steps

Click Predict.
Click Precautions.
Click Listen.

Inputs

No inputs

Expected Output

The application will read the precautions for the user.

Test Result

Passed

Table 47 : User checks for the Precaution test case 02

Test Case : P_ 02

User Pause listening to the Precautions


Login as the user.
Click Select Symptoms.

Test Steps

Does not check on the Symptoms.


Click Predict.
Click Precautions.
Click Pause.
Inputs

No inputs

Expected Output

The application will pause the voice output.

Test Result

Passed

68

Table 48 : User checks for the Precaution test case 03

Test Case : P_ 03

User Stop listening to the Precautions


Login as the user.
Click Select Symptoms.
Does not check on the Symptoms.

Test Steps

Click Predict.
Click Precautions.
Click Stop.

Inputs

No inputs

Expected Output

The application will stop the voice output.

Test Result

Passed

Test Specification: User checks on the Emergency


Table 49 : User checks on the Emergency test case 01

Test Case : E_ 01

User view the Current Location


Login as the user.
Click Select Symptoms.

Test Steps

Does not check on the Symptoms.


Click Predict.
Click Emergency.
Click View Current Location.
Inputs

No inputs

Expected Output

The application checks on the current location.

Test Result

Passed

69

Table 50 : User checks on the Emergency test case 02

Test Case : E_ 02

User view the Nearest Hospitals


Login as the user.
Click Select Symptoms.
Does not check on the Symptoms.

Test Steps

Click Predict.
Click Emergency.
Click View Nearest Hospitals.

Inputs

No inputs

Expected Output

The application checks on the nearest hospitals.

Test Result

Table 51 : User checks on the Emergency test case 03

Test Case : E_ 03

User inform the Guardian & the Family Doctor about the
emergency via SMS.
Login as the user.
Click Select Symptoms.

Test Steps

Does not check on the Symptoms.


Click Predict.
Click Emergency.

Inputs

No inputs

Expected Output

The application will send a sms to the guardian and the


doctor automatically.

Test Result

Passed

70

7.3 Appendices C
7.3.1 Definitions, Acronyms, and Abbreviations
Table 52 : Definitions, Acronyms, and Abbreviations

Modules

A logically self-contained and discrete part of a larger computer program.

Server

A server is a running instance of an application (software) capable of


accepting requests from the client and giving responses accordingly. Servers
can run on any computer including dedicated computers.

Database

A structured set of data held in a System and to retrieve data

Android

Linux based operating system for mobile devices such as smartphones and
tablet computers. It is developed by the Open Handset Alliance led by
Google

User

A user is a person who uses a computer or software system to get an output


from the system according to given commands

RAM

RAM is an acronym for random access memory, a type of computer


memory that can be accessed randomly; that is, and any byte of memory can
be accessed without touching the preceding bytes. RAM is the most
common type of memory found in computers and other devices, such as
printers.

Use Case

A broad level diagram of the project showing a basic overview

DB

Database, which can store the data

SQL

Structured Query Language

OS

(Operating System) An Operating System is the software that tells a


computer/device how to operate. It controls hardware, executes programs,
manages tasks and resources, and provides the user with an interface to the
computer.

Client

Intended users of the software or a client is a piece of computer hardware or


software that accesses a service made available by a server.

Interface

Something use to communicate across different medium

71

7.3.2 Questionnaire
The following questionnaire is based on the research conducted by the Paediaroid team
currently studying Bachelor of Science in Information Technology in final year at Sri Lanka
Institute of Information Technology. These data is to be used for the statistical analysis
purposes. The questionnaire is based on two sections. The first section is regarding the
smartphones, and the next follows the details regarding toddlers.
Please be kind enough to provide your honest opinion on the following questions.
(Put a cross over the correct choice

Section 01 Regarding your smartphone.


1. Do you use smart phones?
Yes

No

2. What kind of a smartphone are you using?


a. Samsung
b. Apple
c. HTC
d. Nokia Lumia
e. Nokia Symbian
f. Sony
g. Any other
3. Do you use toddlers healthcare applications?
Yes

No

I got many

4. Do you need an application which can identify the disease condition and which gives
the correct precautions for the disease condition in an emergency situation and also do
future predictions on your kids health?
Yes

No

I already have

5. Do you have the basic knowledge in operating an application in your smartphone?


Yes

No

Average

72

6. How much do you utilize location based service applications in your smartphone?
Often

Average

Less often

Not at all

7. How much do you trust in following guidelines given by an application in different


kinds of health matters which occurs in day to day life events?
Very well

Average

Much lesser

I have no idea

8. Would you prefer listening to the instructions rather reading them?


Yes

No

Section 02 Regarding your toddlers.


9. Do you have Kids?
Yes

No

Expecting

10. Age Between?


a. 1 5
b. 5+
11. If youre having kids;
No. of kids

Age

Gender

1
2
3
4

12. Have you ever faced any emergency situation on a disease condition of your kid?
Yes

No

13. If yes, were you able predict the disease condition at that time?
Yes

No

Average

73

14. Do you have an idea on the precautions for the particular disease condition?
Yes

No

Average

15. Have you given the correct precautions for the Kid in the emergency situation?
Yes

No

Got help from a Doctor

16. What are your level of knowledge up on the common disease conditions that causes
for toddlers?
Yes

No

Average

17. How efficient are you in contacting the required medical places in your areas in the
cause of a severe disease conditional situation of your child?
Very well

Average

Much lesser

I have no idea

18. Whats the degree of knowledge you have in predicting future events of your childs
healthcare?
Very well

Average

Much lesser

I have no idea

19. State your Ideas


___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________
___________________________________________________________________________

Thank you for your kind response.


Regards: Paediaroid Developing Team.

74

75

Anda mungkin juga menyukai