Emergency App
Mid Review Report
Project ID: 10
Submitted to
Sri Lanka Institute of 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
Project ID
: 10
Student ID
Student Name
IT 13 0917 12
L V Jayasinghe
IT 13 2331 36
IT 13 2454 98
L M C Jayasinghe
IT 13 2380 18
C S Dissanayake
Signature
Signature
Date
Signature
Date
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
1.2
1.3
1.4
1.5
1.6
1.7
2.1.1
2.1.2
2.1.3
2.1.4
2.1.5
2.1.6
2.1.7
Mobile Phone Based Clinical Microscopy for Global Health Applications. ...... 8
2.2
2.3
Methodology ................................................................................................................. 9
3.1
3.2
Planning ................................................................................................................ 10
3.3
Analysis ................................................................................................................ 12
IV
3.4
3.4.1
Software Resources........................................................................................ 14
3.4.2
3.5
3.6
Implementation ..................................................................................................... 16
3.7
Evidence ............................................................................................................... 18
4.1.1
Interfaces ....................................................................................................... 18
4.1.2
Coding ........................................................................................................... 21
4.1.3
4.2
5
Discussion............................................................................................................. 25
Conclusion .................................................................................................................. 26
5.1
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
7.1.2
Class Diagram................................................................................................ 30
7.1.3
7.2
Appendices B ........................................................................................................ 32
7.2.1
Interfaces ....................................................................................................... 32
7.2.2
7.3
Appendices C ........................................................................................................ 71
7.3.1
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
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
E-tel
Micromax
Brand
Operating System
Nokia
Windows / Symbian
22 %
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.
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.
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]
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]
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]
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]
demonstrating its potential for clinical use; substantially resulted in a platform for highresolution clinical light microscopy.
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]
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
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
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
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
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.
Modularity: Each object forms a separate entity whose internal workings are
decoupled from other parts of the system.
15
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
17
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.
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.
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
Test Steps
Inputs
Password
Expected Output
Test Result
Passed
Test Steps
Inputs
Username
Password
Expected Output
Test Result
Passed
22
Test Steps
Inputs
Password
Expected Output
Test Result
Passed
Test Steps
Inputs
No Inputs
Expected Output
Test Result
Passed
23
Test Steps
Inputs
Password
Expected Output
Test Result
Passed
User does not enter the username but enter the Password.
Navigate to the Correct Application.
Click on the Login.
Test Steps
Inputs
Password
Expected Output
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
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].
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
28
7 Appendices
7.1 Appendices A
7.1.1 Use Case Diagram
29
30
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.
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.
33
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.
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.
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.
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.
38
Test Steps
Inputs
Contact Number
Username
Password
Confirm Password
Expected Output
Test Result
Passed
39
Test Steps
Inputs
No Inputs
Expected Output
Test Result
Passed
40
Test Steps
Inputs
Gender
Designation
Email
Contact Number
Username
Password
Confirm Password
Expected Output
Test Result
Passed
41
Test Steps
Inputs
Contact Number
Username
Password
Confirm Password
Expected Output
Test Result
Passed
42
Test Steps
Inputs
Contact Number
Username
Password
Confirm Password
Expected Output
Test Result
Passed
43
Test Steps
Inputs
Contact Number
Username
Password
Confirm Password
Expected Output
Test Result
Passed
44
Test Steps
Inputs
Email
Username
Password
Confirm Password
Expected Output
Test Result
Passed
45
Test Steps
Inputs
Email
Contact Number
Password
Confirm Password
Expected Output
Test Result
Passed
46
Test Steps
Inputs
Email
Contact Number
Username
Confirm Password
Expected Output
Test Result
Passed
47
Test Steps
Inputs
Email
Contact Number
Username
Password
Expected Output
Test Result
Passed
48
Test Steps
Inputs
Email : abdf@.com
Contact Number
Username
Password
Expected Output
Test Result
Passed
49
Test Steps
Inputs
Height
Gender
Details
Special Cases
Expected Output
Test Result
Passed
50
Test Steps
Inputs
No inputs
Expected Output
Test Result
Passed
51
Test Steps
Inputs
Gender
Details
Special Cases
Expected Output
Test Result
Passed
52
Test Steps
Inputs
No inputs
Expected Output
Test Result
Passed
53
Test Steps
Inputs
Gender
Details
Special Cases
Expected Output
Test Result
Passed
54
Test Steps
Inputs
Gender
Details
Special Cases
Expected Output
Test Result
Passed
55
Test Steps
Inputs
Height
Details
Special Cases
Expected Output
Test Result
Passed
56
Test Steps
Inputs
Height
Gender
Special Cases
Expected Output
Test Result
Passed
57
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
Inputs
Height
Gender
Details
Expected Output
Test Result
Passed
58
Test Steps
Inputs
Contact Number
Expected Output
Test Result
Passed
Test Steps
Inputs
No inputs
Expected Output
Test Result
Passed
Table 30 : Guardian Register Validation test case 03
Test Steps
Contact Number
Expected Output
Test Result
Passed
59
Test Steps
Does not enter the Contact Number.
Click Continue.
Inputs
Name
Expected Output
Test Result
Passed
Test Steps
Test Result
Passed
60
Test Steps
Inputs
No inputs
Expected Output
Test Result
Passed
Test Steps
Inputs
Address
Specialty
Expected Output
Test Result
Passed
61
Test Steps
Inputs
Address
Specialty
Expected Output
Test Result
Passed
Test Steps
Inputs
Contact Number
Specialty
Expected Output
Test Result
Passed
62
Test Steps
Inputs
Address
Specialty
Expected Output
Test Result
Passed
63
Test Steps
Enter the Working Hours.
Enter the Address.
Click Register.
Place of Work
Contact Number
Inputs
Working Hours
Address
Expected Output
Test Result
Passed
Test Steps
Does not enter the Working Hours.
Does not enter the Address.
Click Register.
Inputs
No Inputs
Expected Output
Test Result
Passed
64
Test Steps
Inputs
Working Hours
Address
Expected Output
Test Result
Passed
Test Steps
Working Hours
Address
Expected Output
Test Result
Passed
65
Test Steps
Inputs
Contact Number
Address
Expected Output
Test Result
Passed
Test Steps
Inputs
Contact Number
Working Hours
Expected Output
Test Result
Passed
66
Test Steps
Check on the Symptoms.
Click Predict.
Inputs
No inputs
Expected Output
Test Result
Test Steps
Does not check on the Symptoms.
Click Predict.
Inputs
No inputs
Expected Output
Test Result
67
Test Case : P_ 01
Test Steps
Click Predict.
Click Precautions.
Click Listen.
Inputs
No inputs
Expected Output
Test Result
Passed
Test Case : P_ 02
Test Steps
No inputs
Expected Output
Test Result
Passed
68
Test Case : P_ 03
Test Steps
Click Predict.
Click Precautions.
Click Stop.
Inputs
No inputs
Expected Output
Test Result
Passed
Test Case : E_ 01
Test Steps
No inputs
Expected Output
Test Result
Passed
69
Test Case : E_ 02
Test Steps
Click Predict.
Click Emergency.
Click View Nearest Hospitals.
Inputs
No inputs
Expected Output
Test Result
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
Inputs
No inputs
Expected Output
Test Result
Passed
70
7.3 Appendices C
7.3.1 Definitions, Acronyms, and Abbreviations
Table 52 : Definitions, Acronyms, and Abbreviations
Modules
Server
Database
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
RAM
Use Case
DB
SQL
OS
Client
Interface
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
No
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
No
Average
72
6. How much do you utilize location based service applications in your smartphone?
Often
Average
Less often
Not at all
Average
Much lesser
I have no idea
No
No
Expecting
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
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
74
75