Paediaroid: Toddlers Healthcare and

Emergency app
Software Requirement Specification

Submitted to
Sri Lanka Institute of Information Technology

In partial fulfillment of the requirements for the

Degree of Bachelor of Science in Information Technology

May, 2015

Table of Contents
1

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

Purpose ................................................................................................................... 1

1.2

Scope ...................................................................................................................... 1

1.3

Definitions, Acronyms, and Abbreviations .............................................................. 2

Overall Descriptions ...................................................................................................... 3

2.1

Overview ................................................................................................................ 3

2.2

Product perspective ................................................................................................. 6

2.3

User perspective requirements................................................................................. 7

2.3.1

System interfaces ............................................................................................. 7

2.3.2

User interfaces ................................................................................................. 7

2.3.3

Hardware interfaces ......................................................................................... 7

2.3.4

Software interfaces........................................................................................... 8

2.3.5

Communication interfaces ................................................................................ 8

2.3.6

Memory constraints ......................................................................................... 8

2.3.7

Operations ....................................................................................................... 8

2.3.8

Deployment requirements ................................................................................ 9

2.4

Product functions .................................................................................................... 9

2.4.1

Use Case diagram .......................................................................................... 13

2.4.2

Use Case scenarios ......................................................................................... 14

2.5

User characteristics ............................................................................................... 19

2.6

Constraints ............................................................................................................ 19

2.7

Assumptions and dependencies ............................................................................. 20

2.8

Distribution of requirements.................................................................................. 20

Specific Requirements ................................................................................................. 21

3.1

External interface requirements ............................................................................. 21

3.1.1

Detailed user interfaces .................................................................................. 21

3.1.2

Hardware interface integrations ...................................................................... 28

3.1.3

Software interface integrations ....................................................................... 29

3.1.4

Communication interface integrations ............................................................ 29

3.2

Classes/Objects ..................................................................................................... 30

3.3

Performance requirements ..................................................................................... 31

3.4

Design constraints ................................................................................................. 31

3.5

Software system attributes..................................................................................... 31

3.5.1

Reliability ...................................................................................................... 31

3.5.2

Availability .................................................................................................... 31

3.5.3

Security ......................................................................................................... 32

3.5.4

Maintainability............................................................................................... 32

Supporting Information ............................................................................................... 33

4.1

References ............................................................................................................ 33

4.2

Appendices ........................................................................................................... 34

4.2.1

Entity Relationship Diagram of the system..................................................... 34

4.2.2

Detailed User Interfaces - Extended ............................................................... 35

4.2.3

Activity Diagrams of the Use Case Scenarios ................................................. 41

4.2.4

Questionnaire ................................................................................................. 44

II

List of Figures
Figure 1 : Sri Lankan Mobile Handsets Market Share Q3-2014 ............................................. 4
Figure 2 : High Level Architecture of the system .................................................................. 5
Figure 3 : Use Case Diagram ............................................................................................... 13
Figure 4 : Home Screen Interface ........................................................................................ 21
Figure 5 : Login Interface .................................................................................................... 22
Figure 6 : Register User Details Interface ......................................................................... 23
Figure 7 : Register Patient Details Interface ...................................................................... 24
Figure 8 : Selecting Symptoms Interface ............................................................................. 25
Figure 9 : Disease Predicting Interface ................................................................................ 26
Figure 10 : First Aid Interface ............................................................................................. 27
Figure 11 : Class Diagram ................................................................................................... 30
Figure 12 : Entity Relationship Diagram of the system ........................................................ 34
Figure 13 : Register Guardian Details Interface ................................................................ 35
Figure 14 : Register Family Doctor Details Interface ........................................................ 36
Figure 15 : Register Family Doctor (Place of work) Details Interface ............................... 37
Figure 16 : Welcome Page Interface .................................................................................... 38
Figure 17 : Emergency Condition Interface ......................................................................... 39
Figure 18 : View History Interface ...................................................................................... 40
Figure 19 : View History Activity ....................................................................................... 41
Figure 20 : View Precautions Activity ................................................................................. 42
Figure 21 : Emergency Condition Activity .......................................................................... 43

III

List of Tables
Table 1 : Definitions, Acronyms, and Abbreviations ............................................................. 2
Table 2 : Statistics of Sri Lankan Mobile Handsets Market Share Q3-2014 ........................... 4
Table 3 : Minimum Hardware Requirements ......................................................................... 7
Table 4 : Login Function ..................................................................................................... 10
Table 5 : Register Function ................................................................................................. 10
Table 6 : Enter the Symptoms Function ............................................................................... 10
Table 7 : Inform the Guardian Function............................................................................... 11
Table 8 : Check on the Current Location ............................................................................. 11
Table 9 : Check on the Nearest Hospitals Function .............................................................. 11
Table 10 : Listen to the Precautions Function ...................................................................... 11
Table 11 : Edit Details Function .......................................................................................... 12
Table 12 : Login Use Case Scenario .................................................................................... 14
Table 13 : Register Use Case Scenario ................................................................................ 14
Table 14 : Enter the Symptoms Use Case Scenario .............................................................. 15
Table 15 : Inform the Guardian Use Case Scenario.............................................................. 15
Table 16 : Check on the Current Location Use Case Scenario ............................................. 16
Table 17 : Listen to the Precautions Use Case Scenario ....................................................... 16
Table 18 : Edit Details Use Case Scenario ........................................................................... 17
Table 19 : View History Use Case Scenario ........................................................................ 17
Table 20 : Home Screen Interface functionalities................................................................. 21
Table 21 : Login Interface functionalities ............................................................................ 22
Table 22 : Register User Details interface functionalities .................................................. 23
Table 23 : Register Patient Details Interface functionalities .............................................. 24
Table 24 : Selecting Symptoms Interface functionalities ...................................................... 25
Table 25 : Disease Predicting Interface functionalities......................................................... 26
Table 26 : First Aid Interface fuctionalities ......................................................................... 27
Table 27 : Register Guardian Details Interface functionalities........................................... 35
Table 28 : Register Family Doctor Details Interface functionalities .................................. 36
Table 29 : Register Family Doctor (Place of work) Details Interface functionalities ......... 37
Table 30 : Welcome Page Interface functionalities .............................................................. 38
Table 31 : Emergency Condition Interface functionalities.................................................... 39
Table 32 : View History Interface functionalities ................................................................ 40

IV

1
1.1

Introduction
Purpose

The purpose the Software Requirement Specification document is to define and describe
detailed information about the proposed system which is to be designed in order to provide the
efficient Android application which is focused on predicting symptoms for the disease
conditions of toddlers, and one of the main goal of this document is provide a detailed overview
of the proposed software product, its parameters and goals. This document describes the
project's target audience and its user interface, hardware and software requirements. It defines
how the end user, team and audience see the product and its functionality. Nonetheless, it helps
any designer and developer to assist in software delivery lifecycle (SDLC) processes.
In this document it describes the functional and the non-functional requirements of the system.
It has several parties which have the legal inheritance. The document is beneficial to the android
powered smart phone users. Another beneficiary of this document is SLIIT where they will be
the third party of monitoring the progress of the project. Our Supervisor Mr. Ivantha Guruge,
Lecturer in-charge Ms. Gayana Fernando and Group Members are going to get a thorough
knowledge of the system by referring this document.
1.2

Scope

This is an Android application for toddlers. When user is in an emergency situation application
will send a text message to the guardian about toddlers situation. Android application will be
providing a well identified and a wide range of disease diagnosing expertise in predicting the
symptoms of common infant diseases and acquire a good guidance by providing accurate
instructions for taking the necessary precautions. Paediaroid android application will
establishing a communication interface with the guardians and the family doctor for better
safety and providing locations of the nearby hospitals through a location based service. This
will be supporting any emergency situational conditions Application will provide voice
instructions rather reading the instructions precautions that should be taken, through the phone.
This document will be discussed all these kind of things with details in below chapters.

1.3

Definitions, Acronyms, and Abbreviations

Table 1 : Definitions, Acronyms, and Abbreviations

Modules

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

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

Server

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

Linux based operating system for mobile devices such as smartphones

Android

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 is an acronym for random access memory, a type of computer
memory that can be accessed randomly; that is, and any byte of memory

RAM

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

SRS

Software Requirement Specification

DB

Database, which can store the data

SQL

Structured Query Language

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

OS

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
Interface

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.
Something use to communicate across different medium
A software requirements specification (SRS) is a description of a software

SRS

system to be developed, laying out functional and non-functional

requirements, and may include a set of use cases that describe interactions
the users will have with the software.

2 Overall Descriptions
2.1

Overview

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 replacing
the diagnosis part of a doctor. 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 is 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 [1].
(According to the statistics of Sri Lanka: Mobile Handsets Market Review)
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 2 : 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

2.2

Product perspective

Paediaroid application is a research oriented project, where data mining concepts and
algorithms will be utilized in order for the predicting purposes as well as identifying disease
conditions of toddlers. The main research arena covers up the disease prediction based on the
pediatric field, where the symptoms of kids and babies will be used in predicting the
precautions that a guardian should follow 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; in which the Paediaroid application will serve the assistance during such a situation.
The following table differentiates the contrasting factors between Paediaroid and other related
similar systems.
Although several endeavors have been spent upon the development of applications on the
patients, especially on diagnosing medical conditions of infants, providing instructions,
precautions and predicting the future, our research team will provide the unique solution full
filling the research gap which in return provide solutions for the following elements.
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
Provision of information with much higher accuracy and increasing the usage of the
application by the users with better trust

2.3

User perspective requirements

2.3.1 System interfaces

The proposed system will utilize a location based service provider, i.e. Google Maps, Nokia
Maps or Bing Maps in order to get the location of the device in which the application is
operated. The voice outputs which are expected to be used in listening the intended precautions
would be generated using a text to speech service application. Services on Google APIs or any
other Web Speech API can be used to provide the services. If in case the services would be
much heavier for the application to interact, a library would be used in developing the service
application.
2.3.2 User interfaces
This application will be provide separate for each facility that included in Paediaroid. Details
and sample interfaces are included under 3.1.1 Section. All the user interacting interfaces are
developed using Android Studio selecting an eye catching design with more interacting colors
and font types. The interfaces will be designed in such a way that theyll automatically adjust
to the screen size of the application running device, but restricting some older versions of
Android (i.e. Honey Comb Android 3.0). Despite of these restrictions, all the other features
of the designing will be implanted as mentioned in the previous sections.
2.3.3 Hardware interfaces
The minimum hardware requirements are as follows.
Table 3 : Minimum Hardware Requirements

During development

During implementation

PC with 2GHz processor or above

Hosting Server Outsourcing server

2 GB RAM or above

PC with 1.5GHz processor or above

Hard disk space of 20GB or above

2 GB RAM or above
HDD 10GB or above

A compatible server (i.e.: IIS Server) for the database to be implemented. Android Smart Phone
with the following specifications is to be used for the testing purposes of the application.
Android OS, v 4.0 (Jellybean) or higher with 1GB RAM.

2.3.4 Software interfaces

This Android application is developed to be used by a single user. The application will
communicate through a Wi-Fi or a data connection of the mobile device. The following
software applications will be used in developing the system.
Android Studio
Adobe Photoshop Creative Suite 6
Microsoft SQL Server 2015
Microsoft Visual Studio 2012
2.3.5 Communication interfaces
This system mainly runs through an internet connection. User access web site through modem.
And also there can be accessible mobile devices through mobile network based connections
and wireless connections such as Wi-Fi. TCP/IP will be used as the communication protocol
for the connections.
2.3.6 Memory constraints
During the implementation system is expected to use minimum of 1GB RAM to run and a
cache memory or a temporary memory of 10-50MB.And also throughout the development
procedure the system requires minimum of 2GB RAM and minimum of 20GB of hard disk
space.
The mobile application is expected to use up to 1GB RAM of the mobile device and a space of
minimum 20MB.
2.3.7 Operations
Android smart phone user will be provide with the following functionalities.
Login
Register
Enter the Symptoms
Inform the guardian
Check on the current location
Listen to the precautions
Edit details
View History
Please refer section 2.4 for detailed description of components.

2.3.8 Deployment requirements

The system is composed of the user application & database. The mobile application will be
made available to be installed on devices used by android users. The database is planned to be
initially deployed on a server using a service application to communicate with the mobile
device.
2.4

Product functions

The following product functionalities will be available for the user through the application.
Login
User can login to the system after enable data connection/Wi-Fi.
Register
If the user is not a registered user he/she should register to the system. There the user
him/herself should get registered and then he/she should register the Patient, Guardian
and the family doctor.
Enter the Symptoms
The user will be allowed to enter the symptoms on the particular interface.
Inform the Guardian
In case in an emergency, the user is allowed to inform the guardian via Emergency
option.
Check on the current location
The user is allowed to check on the current location via GPS service.
Listen to the precautions
The user is allowed to listen to the precautions once the system identifies the particular
disease condition.
Edit Details
The user is allowed to edit the details of the User, Patient, Guardian and the Family
doctor.

 View History
The user is allowed to view history of the patient.
Detailed descriptions of the product functions are as follows
Login
Table 4 : Login Function

Input

Username
Password

Process
Read the values
Connect to the Database and
retrieve data
Compare and validate
If valid display the welcome
menu
If invalid display an error

Output

Welcome Menu or Error

Register
Table 5 : Register Function

Input
User Details
Patient Details
Guardian Details
Family Doctor details and
his/her working place

Process
Read the values
Connect to the Database and
store the details.

Output

Welcome Menu

Enter the Symptoms

Table 6 : Enter the Symptoms Function

Input
Symptoms

Process
Output
Read the Values
Predicted Disease Condition
Connect to the Database and
retrieve data
Identify
the
disease
condition and display to the
user.

10

 Inform the Guardian

Table 7 : Inform the Guardian Function

Input
User Details
Patient Details

Process
Output
Read the Details
A text message
Connect to the Database and
read the Guardians Contact
Number.
Send a message to the
Guardian.

Check on the Current Location

Table 8 : Check on the Current Location

Input
User Details
Patient Details

Process
Output
Check on the current location Display the current location
via GPS location identifier.

Check on the nearest hospitals

Table 9 : Check on the Nearest Hospitals Function

Input
User Details
Patient Details

Process
Output
Check on the current location Display the nearest hospitals
via GPS location identifier.
Then the hospitals are
identified which are nearest
to the location.

Listen to the Precautions

Table 10 : Listen to the Precautions Function

Input
Precautions in plain text

Process
Translate text to voice

11

Output
Voice
record
of
instructions

the

 Edit Details
Table 11 : Edit Details Function

Input
User Details
Patient Details
Guardian Details
Family Doctor Details

Process
Output
The application will store the Profile with the edited details
edited details

View History
Input
User Details
Patient Details

Process
Output
Connect to the database and Display the history
retrieve the past records of
the patient.
Display it to the user

12

2.4.1 Use Case diagram

Figure 3 : Use Case Diagram

13

2.4.2 Use Case scenarios

Login
Table 12 : Login Use Case Scenario

Use Case Name

Login

Actor

User

Goal

To login to the system successfully

Pre-condition

The Data connection should be Up.

1. Click on the Paediaroid Icon
2. Click on the Login Button

Typical Course of Events

3. Insert the Username and Password.
4. Click Login
Steps 2 3
Alternatives

If user forgets the Username/Password, click

on the Forget Username/Password option.

Register
Table 13 : Register Use Case Scenario

Use Case Name

Register

Actor

User

Goal

To register to the system successfully

Pre-condition

The Data connection should be Up

1. Click on the Paediaroid Icon
2. Click on the Register button
3. Fill the required details to register
the User
4. Fill the required details to register
the patient

Typical Course of Events

5. Fill the required details to register

the Guardian
6. Fill the required details to register
the family doctor
7. Click Register

14

Enter the Symptoms

Table 14 : Enter the Symptoms Use Case Scenario

Use Case Name

Enter the Symptoms

Actor

User

Goal

To identify the disease condition

Pre-condition

The Data connection should be Up and the

user should be login to the system.
1. Tick on the symptoms mentioned in
the display.

Typical Course of Events

2. Click Done
Steps 1
Alternatives

Other option is given to type any other

symptoms which is not given in the list.

Inform the Guardian

Table 15 : Inform the Guardian Use Case Scenario

Use Case Name

Inform the Guardian

Actor

User

Goal

To inform the guardian about the emergency

situation

Pre-condition

The Data connection should be Up and the

user should be login to the system.
1. Once the disease condition is
identified, click on the Emergency
button.

Typical Course of Events

15

Check on the Current Location

Table 16 : Check on the Current Location Use Case Scenario

Use Case Name

Check on the Current Location

Actor

User

Goal

To check on the current location of the user

Pre-condition

The Data connection should be Up and the

user should login to the system.
1. Click on the Emergency button in
the screen.

Typical Course of Events

2. Then click on the View Current

Location button.

Listen to the precautions

Table 17 : Listen to the Precautions Use Case Scenario

Use Case Name

Listen to the Precautions

Actor

User

Goal

To listen to the precautions of the identified

disease condition.

Pre-condition

The Data connection should be Up and the

user login to the system.
1. Click on the Precautions button.

Typical Course of Events

2. The system displays the first aid.

3. Click on the Listen button.
Steps 2 3

Alternatives

If the disease condition is a server/critical

condition, the user is warned to meet the
doctor immediately as a message.

16

Edit Details
Table 18 : Edit Details Use Case Scenario

Use Case Name

Edit Details

Actor

User

Goal

To edit the details of the user, patient,

guardian and the family doctor.

Pre-condition

The Data connection should be Up and the

user should be login to the system.
1. Click on the My Profile button in
the welcome interface.

Typical Course of Events

2. Your details are viewed.

3. Click on the Edit Details Button.

View History
Table 19 : View History Use Case Scenario

Use Case Name

View History

Actor

User

Goal

To view the history of the patient

Pre-condition

The Data connection should be Up and the

user should login to the system.
1. Click on the View History button
in the welcome interface.

Typical Course of Events

2. The history is displayed.

17

View nearest Hospital

Use Case Name

View nearest Hospital

Actor

User

Goal

To check on the Nearest Hospital

Pre-condition

The Data connection should be Up and the

user should login to the system.
1. Click on the Emergency button in
the screen.

Typical Course of Events

Alternatives

2. Then click on the View Nearest

Hospital button.
-

18

2.5

User characteristics

There is one main user of this Paediaroid Application. That User,

Should have basic knowledge to user android application.
Should be able to work with android mobile phone.
Should be able to understand English language.
The mainly focused end user of the proposed system would be
2.6

Constraints

The application is developed using java and C# programming languages. The main user
interface is developed using java, where Android Studio is used as the developing tool. The
back end, or the server side database transactions are processed using a service application
which is developed using C# language. C# will be utilized and the database will be developed
using Microsoft SQL Server 2012/2014. The data mining procedure will be followed enhancing
a specific mining algorithm and a better dataset. The results will be analyzed and the decisions
will be gathered with better results. The application will communicate through the server using
the service application which is expected to be developed using Windows Communication
Foundation services. The requesting services can be enhanced with efficient service references.
Concurrency is a critical task in this project because for any purpose data cannot be loose or
overwritten and real time transaction.
The ability to maintain real-time operations over realistic extended periods of time is dependent
on the mean time to failure of the hardware and software components of the communications
systems.

19

2.7

Assumptions and dependencies

Assumptions

Developing team has assumed people who using web site has a fair enough knowledge about
the web based and mobile applications.
Microsoft SQL Server 2014 is used as the server for the database during the development.
Dependencies
The system depends on the availability and correct functionality of the following services:
Data/Wi-Fi Connection
Paediaroid Software
The implementation of the android application depend on the performance of the device the
application is currently running.
2.8

Distribution of requirements

The requirements described in sections 1 and 2 of this document are referred to as primary
specifications; those in section 3 are referred to as functional specifications. The two levels of
requirements are intended to be consistent. Inconsistencies are to be logged as defects. In the
event that a requirement is stated within both primary and functional specifications, the
application will be built from functional specification since it is more detailed.
'Essential requirements' (referred to in section 3) are to be implemented for the first version of
the system. 'Desirable requirements' are to be implemented in this release if possible, but are
not committed to by the developers.
All the functionalities stated in the Software Requirement Specification would be implemented
using the above mentioned tools and software platforms and the implementation would be
carried out as specified. All functional and non-functional requirements have been distributed
among the members of the research group weighing the same pressure up on each member.

20

3 Specific Requirements
3.1

External interface requirements

3.1.1 Detailed user interfaces

Home Screen interface

Figure 4 : Home Screen Interface

Table 20 : Home Screen Interface functionalities

Number
1
2

Function
Login Button
Register Button

Description
To login to the account
To register to the application

21

Access Level
User
User

Login Interface

4
5

Figure 5 : Login Interface

Table 21 : Login Interface functionalities

Number
1
2
3
4

Function
Text Field
Text Field
Login Button
Forgot Button

Back Button

Description
To enter the Username
To enter the Password
To login to the application
In case if the username/
password is forgotten, To
receive an email with the
recovery Username/Password
To go back to the Home

22

Access Level
User
User
User
User

User

Register User Details interface

1
2
3
4
5
6
8
7
9
1

Figure 6 : Register User Details Interface

Table 22 : Register User Details interface functionalities

Number
1
2
3

Function
Text Field
Radio buttons
Text Field

4
5

Text Field
Text Field

6
7
8
9
10

Text Field
Text Field
Text Field
Back Button
Continue Button

Description
To enter the Name of the User
To select the gender of the user
To enter the designation of the
user
To enter the email of the user
To enter the contact number of
the user
To enter the Username
To enter the Password
To confirm the password
To go back to the home
To continue with the
registration

23

Access Level
User
User
User
User
User
User
User
User
User
User

Register Patient Details interface

1
2
3
4
5
6
8

10

Figure 7 : Register Patient Details Interface

Table 23 : Register Patient Details Interface functionalities

Number
1
2
3
4
5
6
7
8
9
10

Function
Text Field
Text Field
Text Field
Text Field
Radio buttons
Text Field
Text Field
Text Field
Back Button
Continue Button

Description
To enter the Name of the Patient
To enter the age of the Patient
To enter the weight of the Patient
To enter the height of the Patient
To select the gender of the Patient
To enter details of the Patient
To enter special cases of Patient
To enter the current location
To go back to the home
To continue with the registration

24

Access Level
User
User
User
User
User
User
User
User
User
User

Selecting Symptoms interface

Figure 8 : Selecting Symptoms Interface

Table 24 : Selecting Symptoms Interface functionalities

Number
1

Function
Check Boxes

Predict the Disease

Button
Back Button

Description
Select the symptoms of the
Patient
To predict the disease
condition of the Patient
To go back to the Welcome
Page

25

Access Level
User
User
User

Disease Predicting interface

Figure 9 : Disease Predicting Interface

Table 25 : Disease Predicting Interface functionalities

Number
1

Function
Label

2
3

Precaution Button
Emergency Button

Back

Description
Display the Predicted Disease
Condition
Directs for the First Aid
A message will be sent to the
Guardian and the Family
Doctor and also directs to the
Location checker
To go back to the Symptoms

26

Access Level
User
User
User

User

First Aid interface

1
2

4
3

5
6

Figure 10 : First Aid Interface

Table 26 : First Aid Interface fuctionalities

Number
1

Function
Label

2
3
4
5
6

Listen Button
Pause Button
Stop Button
Exit Button
Back

Description
Display the First Aid for the
Predicted Disease
To Listen to the first aid
To Pause the Voice Output
To stop the Voice Output
To exit from the Application
To go back to the Previous
Interface

27

Access Level
User
User
User
User
User
User

3.1.2 Hardware interface integrations

Basically the web based system will interact with the following hardware interfaces.
Server and database
The database includes all the records required for different requirements and functionalities.
The entities which have been specified through the Entity-relationship diagram will be the
required tables for the database and the specified attributes or the records will be saved in the
database using different tables and relationships among them. The server is responsible for
maintaining concurrent access of users and the real time transactions, which in return provide
the users a reliable source for their interactions. The database will be utilized using a data
mining algorithm in order to predict the future events, in deciding the precautions required for
the different symptoms provided by the user.
User interfaces
User interfaces, essentially the Android application will be the graphical user interface for the
users to interact with the system. The developing team will ensure the compatibility of the data
presentation and the application presentation that results the ease of the usability for the clients.
The system will comprises of the above mentioned hardware interfaces to provide the
requirements explicitly defined by the developing team.

28

3.1.3 Software interface integrations

Can be categorized as
1. Software needed in designing & implementing the system
2. Software needed in the documentation
Software needed in designing & implementing the system

Microsoft SQL Server 2012

Microsoft Visual Studio 2012

Microsoft .NET Framework 3.5 or higher

Android Studio

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

3.1.4 Communication interface integrations

Internet or the WWW (World Wide Web) will be used as the main source of Communication
or the media of data communication. For the connection purposes devices such as modems,
routes and wireless technologies can be used by the clients or the users of the web system. The
developed system will be implemented in a real time server (i.e.: IIS server) and will be
available for the users through a service application.

29

3.2

Classes/Objects

Figure 11 : Class Diagram

30

3.3

Performance requirements

Mainly the performance of the system depends on the efficiency of the server as well as the
efficiency of the mobile device which the system is implemented. Since the system is
developed to operate in an Android mobile operating system, the running time varies from one
device to another; due to the hardware specifications of the running device. In order for the
application to run on a client device, the following performance requirements are required.
Processor 1 GHz or higher performing processor
Memory 1 GB minimum
Space 20 MB minimum of memory space
3.4

Design constraints

A primary goal of the system is to be a low cost solution. This is a constraint on the technologies
used. Also, the system is planned to be designed and developed using the following
technologies, which will impose constraints on the design.
Android Platform
GPS Technology
3.5

Software system attributes

3.5.1 Reliability
The system should not have any reliability issues. The system will be thoroughly tested and
any issues will be resolved. Since the prototype methodology is followed in developing the
system, if in case a major problem peeks in; the whole system can be reinitiated.
3.5.2 Availability
The system will be implemented as a web service based system, so as long as the server is
running without any failure, the web system will be available 24x7. The key to maintaining
availability will be by ensuring a connection to the database server is available. Failure to
connect to the database will make the data unavailable.

31

3.5.3 Security
This system is intended to communicate over the internet, therefore security is of a major
concern. The users will be provided with a username and a password, if they are required to
have privileged options. The username and password will be verified using the database
whenever a login is attempted. And also the system will use secure layer protocols to
communicate in order to ensure better safety of the users.
3.5.4 Maintainability
The software design is being done with modularity in mind. Therefore maintainability can be
done efficiently. A commercial database is used for maintaining the database and the
application server can update easily because it only has one central server application. The
software will be composed of various modules decreasing the complexity of expansion and
increasing the performance and the ease of maintenance.

32

4 Supporting Information
4.1

References

[1]. Prototype Methodology Information management, David Bowmans Information

Management

Checklist

[Online],

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

architect.com/prototyping-methodology.html
[2]. 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.
[3]. K. Schwalbe, Information Technology Project Management, 3rd ed. Boston: Course
Technology, 2004.
[4]. [2] A. Dennis, B. H. Wixom, D. Tegarden, Systems Analysis and Design with UML
Version 2.0, Second Edition. Leyh Publishing: John Wiley & Sons, 2005.
[5]. [3] H. K. Edwards and V. Sridhar, "Analysis of software requirements engineering
exercises in a global virtual team setup",Journal of Global Information Management, vol.
13, no. 2, p. 21+, April-June 2005. [Online]. Available: Academic OneFile,
http://find.galegroup.com.
[6]. [4] Allan Denis, Barbara Haley Wixom, System Analysis and Design, John Wiley
&Sons.Inc, 2000.
[7]. [5] RamezElmasri, ShamkantB.Navathe, Fundamental of DataBaseSystems,Addison
Systems, 2002.

33

4.2

Appendices

4.2.1 Entity Relationship Diagram of the system

Entity Relationship Diagram of the system
Figure 12 : Entity Relationship Diagram of the system

34

4.2.2 Detailed User Interfaces - Extended

Register Guardian Details interface

Figure 13 : Register Guardian Details Interface

Table 27 : Register Guardian Details Interface functionalities

Number

Function

Description

Access Level

Text Field

To enter the Name of the

Guardian

User

Text Field

To enter the Contact Number

of the Guardian

User

Continue Button

To continue to the Registration

User

Back Button

To go back to the Patient

Details

User

35

Register Family Doctor Details interface

1
2
3
4

Figure 14 : Register Family Doctor Details Interface

Table 28 : Register Family Doctor Details Interface functionalities

Number

Function

Description

Access Level

Text Field

To enter the Name of the

Family Doctor

User

Text Field

To enter the Contact Number

of the Family Doctor

User

Text Field

To enter the address of the

Family Doctor

User

Text Field

To enter the specialty od the

Family Doctor

User

Continue Button

To continue to the Registration

User

Back Button

To go back to the Guardian

Details

User

36

Register Family Doctor (Place of work) Details interface

1
2

3
4

Figure 15 : Register Family Doctor (Place of work) Details Interface

Table 29 : Register Family Doctor (Place of work) Details Interface functionalities

Number

Function

Description

Access Level

Text Field

To enter the work place of the

Family Doctor

User

Text Field

To enter the Contact Number

of the Working Place

User

Text Field

To enter the working hours of

the family doctor

User

Text Field

To enter the Address of the

working place

User

Register Button

To complete to the Registration User

Back Button

To go back to the Family

Doctor Details

37

User

Welcome Page interface

1
2
3
4

Figure 16 : Welcome Page Interface

Table 30 : Welcome Page Interface functionalities

Number

Function

Description

Access Level

My Profile Button

To view the Users Profile

User

Enter Symptoms
Button

To go the Symptoms interface

User

View History Button

To view the history of the

Patient

User

Logout Button

To Logout from the Account

User

Exit Button

To Exit from the Application

User

38

Emergency Condition interface

1
2

3
4

Figure 17 : Emergency Condition Interface

Table 31 : Emergency Condition Interface functionalities

Number

Function

Description

Access Level

View Current
Location Button

To view the current location of

the Patient in an emergency

User

Label

Displays the current Location

of the Patient

User

View Nearest Hospital

Button

To view the nearest hospitals

in case in an emergency

User

Label

Displays the nearest hospital

User

Back Button

To go back to the previous

interface

User

39

View History interface

Figure 18 : View History Interface

Table 32 : View History Interface functionalities

Number

Function

Description

Access Level

Text Area

Displays the history of the

Patient

User

Clear History Button

To clear the history of the

Patient

User

Back Button

To go back to the Welcome

Interface

User

40

4.2.3 Activity Diagrams of the Use Case Scenarios

View History

Figure 19 : View History Activity

41

View Precautions

Figure 20 : View Precautions Activity

42

Emergency Condition

Figure 21 : Emergency Condition Activity

43

4.2.4 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
44

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

45

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

46

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.
47