A MOBILE BASED SYSTEM FOR SEARCHING AND

LOCATING NEARBY PLACES AND SERVICES IN UGANDA

CASE STUDY: KABALAGALA-KANSANGA

BY

KINTU MUSOKE

BIT/43134/151/DU

&

A RESEARCH REPORT SUBMITTED

TO SCHOOL OF COMPUTING AND INFORMATION TECHNOLOGY IN

PARTIAL FULLFILLMENT FOR THE REQUIREMENT OF THE
AWARD OF A BACHELORS DEGREES IN COMPUTER SCIENCE,
INFORMATION TECHNOLOGY OF KAMPALA INTERNATIONAL
UNIVERSITY

MARCH 2018
DECLARATION
We hereby declare that this project report on a mobile based system for searching
and locating nearby services is entirely our original work and has not been
Published and/or submitted for any other degree award to this or any other
university before.

Name:…………………………………….Sign:………………Date:……………

Department of Information Technology

School of Computing and Information Technology

Kampala International University

i
APPROVAL
The project report titled “mobile based system for searching and locating nearby
services and places in Uganda (Kabalagala-Kansanga),” has been submitted for
examination with my approval.

Signature…………………………………Date…………………….

PROJECT SUPERVISOR

MR BEMERA LIVINGSTTONE

Department of Computer Science

School of Computing and Information Technology

Kampala International University

ii
DEDICATION
We dedicate this report to our beloved Parents and friends for their continuous
support and encouragements that always allowed us to achieve our wishes without
forgetting all those who have been praying for us from day one up to now.
May God grant Heaven to our beloved parents!

iii
ACKNOWLEDGEMENT
We first thank the ALMIGHTY GOD for the protection, love, care, provision and
the far we have gone. It has been God throughout not by our power.

We would like to take this great honor to say big thanks to our thesis Supervisor
MR.KAMUGISHA GEOFREY, May God richly bless you. We are so much
thankful to our project advisor MR. GRACE KAMULEGEYA, Research
coordinator MR.ZIRIMENYA, DEAN SCIT and the entire SCIT staff for their
encouragement, advice, guidance and support during project work.

We take this great honor in thanking our lovely parents, family members, relatives
and friends for their continuous support and help. Our class members, fellow
comrades, KIU community, kabalagala-kansanga business men and women thank
you so much for your cooperation any contribution you gave us. Us alone we
wouldn’t have reached to the conclusion and closure of the project.

May God richly bless you

iv
List of acronyms
MBS Mobile based system

SCIT School of Computing and Information Technology

PHP Hypertext preprocessor
API Application Programming Interface
GPS Graphical Positioning System
APPS Applications
Wi-Fi Wireless fidelity
HTC High Tech Computer
Ios Input output system
OS Operating System
LBS Location Based System
ATM Automated Teller Machine
JDK Java Development Kit
Xampp Cross platform(X) Apache MySQL PHP Perl
SAD System Application Development
DFD Data Flow Diagram
ERD Entity Relationship Diagram
RAD Rapid Application Development
IDE Integrated Development Environment
GHz Giga Hertz
CPU Central Processing Unit
KIU Kampala International University

v
List of figures

Figure 1.1 the conceptual model showing the architectural design of the system ....5
Fig 2.1 Waterfall Model. ......................................... Error! Bookmark not defined.
Figure 3.1 that follows shows the system’s development methodology. ................18
Figures 4.1: data flow diagram symbols ..................................................................28
Figure 4.2 showing the flow chart diagram of MBS ...............................................29
Figure 5.1 Snapshot of the System mobile app Sign up interface ..........................35
Figure 5.2 Snap shot showing what happens when a user signs up with a username
and a password less than 7
Figure 5.5 Snapshot of a user signing up /creating an account ..............................37
Figure 5.6 Snapshot showing account successfully created and login page ...........38
Figure 5.7 Snapshot of a user logging in .................................................................39
Figure 5.8 Snapshot of a user successfully logged in ..............................................40
Figure 5.9 Snapshot showing a user login with incorrect password or wrong
account .....................................................................................................................45
Figure 5.10 Snapshot of a google map displaying selected service (phamarcies). .43
Figure 5.11 Snapshot showing the possible route and direction to the selected
service. .....................................................................................................................44
Figure 5.12 Snapshot of A home page for the web app...........................................46
Figure 5.13 Snapshot of about us page ....................................................................47
Figure 5.14 A snapshot of services page .................................................................47
Figure 5.15 Snapshot of portfolio page ...................................................................48
Figure 5.16 Snapshot of contact us .........................................................................48
Figure 5.17 Snapshot of admin login panel .............................................................49
Figure 5.18 Snapshot of the admin dashboard .........................................................50
Figure 5.19 Snapshot of viewing the facilities / services ........................................51
Figure 5.21 Snapshot of adding a service/a facility Error! Bookmark not defined.

vi
Figure 5.22 Snapshot of Deleting a service/ facility................................................52
Figure 5.23 snapshot for updating a service / a facility ...........................................53

vii
List of tables

Table 3.1 showing the different strata and number in the strata......................16
Table 3.2 showing sample size...............................................................................17
Table 4.1 Showing Hardware Requirements. .....................................................25
Table 4.2 Showing Software Requirements.........................................................25
Table 4.3 Data dictionary showing description of entities. ................................30
Table 4.4 Data dictionary showing description of processes .............................31
Table 4.5 Data dictionary showing description of data stores ...........................31
Table 4.6 Entities and their attributes ................................................................32
Table 7.1 Facility ....................................................................................................66
Table 7.2 Services ...................................................................................................66
Table 7.3 Users .......................................................................................................66

viii
ABSTRACT
Mobile applications are one of the best ways to keep consumers engaged with a
brand as they are on the move. With the increase in demand for smartphones and
efficiency of wireless networks, the demand for mobile applications has increased
incredibly. Android is one of the most popular open source platforms that offer the
developers’ full access to the framework API’s so as to build innovative
applications.

The main aim of this project was to develop a mobile based system to help users to
search and locate nearby places and services depending on their current location
like hostels, universities, Banks, hospitals, hotels and pharmacies in a Uganda
(kabalagala-kansanga) according to their tastes and point of interest.

Mobile Based System was developed to provide the users a rich user experience by
having all the information in one place, easy-to-access and interactive. The user
will be able to view the description, the location address and the detailed
information about the selected place. Uganda especially in kabalagala-kansanga is
still using the traditional information system for searching and locating services
nearby, “The Manual Information System”. This system takes long time to find a
service, thereby leading to delayed work and time wastage.

When services are needed, especially by new people in the environment, it takes
long time to get a single service to help them. At times people get lost and tracing
back their current location becomes a problem since the system is not automated
and they are not familiar with the place. This has created a lot of loop holes in the
system because there is no clear guide or information of the system for the places
and services available in the kabalagala-kansanga. It necessitated automating the
system to make it more efficient and effective.

There was close study of the existing manual system that was in use, it was
compared to the developed mobile based system for searching and locating nearby
services in Uganda (kabalagala-kansanga). Codes were written using Android
Studio, Java JDK, MYSQL with PHP, Xampp server, JSON all integrated with
Google maps and GPS that produced fully functioning of the system.

ix
 Table of content

DECLARATION...................................................................................................... i
APPROVAL ............................................................................................................ ii
DEDICATION ........................................................................................................ iii
ACKNOWLEDGEMENT ..................................................................................... iv
List of acronyms .......................................................................................................v
List of figures .......................................................................................................... vi
List of tables .......................................................................................................... viii
ABSTRACT ............................................................................................................ ix
Table of content ........................................................................................................x
CHAPTER ONE ......................................................................................................1
INTRODUCTION....................................................................................................1
1.1 Back ground of the project ...................................................................................2
1.2 Problem Statement ...............................................................................................3
1.3 Objectives of the project ......................................................................................3
1.3.1 General Objective .............................................................................................3
1.3.2 Specific objective ..............................................................................................3
1.4 Scope of the study ................................................................................................4
1.4.1 Geographical scope ...........................................................................................4
1.4.2 Time scope ........................................................................................................4
1.4.3 Content scope ....................................................................................................4
1.5 Significance of the study ......................................................................................4
1.6 Conceptual framework .........................................................................................5
1.7 Limitations to the study .......................................................................................6

CHAPTER TWO .....................................................................................................7

x
LITERATURE REVIEW .......................................................................................7
2.1 Introduction ..........................................................................................................7
2.2 The following are reviews of relevant article and journals that have been made.
....................................................................................................................................7
2.2.1 Android and Mobile Application ......................................................................7
2.2.2 Mobile application ............................................................................................8
2.2.2.1 Advantages of android mobile apps...............................................................8
2.2.2.2 Disadvantages of Android.............................................................................9
2.2.3 Google maps and API .......................................................................................9
2.2.3.1 Google Maps API ........................................................................................10
2.3 Existing mobile based location system (Related studies) ..................................10
2.3.1 Location Based services to improve public transportation .............................10
2.3.2 Sharing the Square: Collaborative Leisure in the City Streets. ......................11
2.4 The implemented System ...................................................................................12
2.4.1 Value of the implemented system ...................................................................12
2.4.2 Objectives of implemented system are ...........................................................12
2.5 Development model process of MBS ................................................................12

CHAPTER THREE ...............................................................................................15

METHODOLOGY.................................................................................................15
3.0 Introduction ......................................................................................................15
3.1 Research design..................................................................................................15
3.2 Target Population of study .................................................................................15
3.2.1 Sampling .........................................................................................................15
3.2.2 Sampling Techniques ......................................................................................16
3.2.3 Sample size .....................................................................................................16
3.3 Development methodology ................................................................................17

xi
3.4 Requirements identification ...............................................................................18
3.4.1 System study and investigation.......................................................................18
3.4.1.1 Data Collection Methods .............................................................................18
3.5 System Design....................................................................................................20
3.6 System Implementation .....................................................................................20
3.7 System testing and validation ............................................................................21

CHAPTER FOUR ..................................................................................................22

SYSTEM ANALYSIS AND SYSTEM DESIGN ................................................22
4.0 Introduction ........................................................................................................22
4.1 Weakness and Strength of the Current Systems used to search and locate
nearby places and services within kabalagala-kansanga. ........................................22
4.1.1 Weakness ........................................................................................................22
4.1.2 Strength ...........................................................................................................22
4.2 System analysis and Study .................................................................................23
4.3 Requirements Specification ...............................................................................23
4.3.1 Functional Requirements ................................................................................24
4.3.2 Non-Functional Requirements ........................................................................24
4.3.4 User Requirement ...........................................................................................24
4.3.5 System Requirement .......................................................................................24
4.3.5.1 Hardware Requirement ................................................................................24
4.3.5.1 Software Requirements ................................................................................25
4.3.6 Environmental Requirements..........................................................................26
4.4 Structured Requirements Analysis.....................................................................26
4.4.1 Data Flow Diagram .........................................................................................26
4.4.2 Context Diagram .............................................................................................28
4.3 System Design....................................................................................................33

xii
CHAPTER FIVE....................................................................................................34
SYSTEM IMPLEMENTATION RESULTS ......................................................34
5.0 Introduction ........................................................................................................34
5.1 Snapshots of the output of User Interface Design of MBS ...............................34
5.1.1 User interface (login/sign up) .........................................................................34
5.1.2 Signing up with a wrong username and a password .......................................35
5.1.3 Correct username and password signup..........................................................37
5.1.4 Login Form .....................................................................................................38
5.2 MBS web app /server for the user and admin dashboard ..................................46

CHAPTER SIX ......................................................................................................54

DISCUSSION, CONCLUSION AND RECOMMENDATIONS ......................54
6.1 Discussion ..........................................................................................................54
6.2 Conclusion .........................................................................................................55
6.3 Recommendations ..............................................................................................56
6.3.1 Areas for Further Study ..................................................................................56
REFERENCES.........................................................................................................58
APPENDICES .........................................................................................................59
Appendix A: Questionnaire .....................................................................................59
Appendix B: Interview .............................................................................................61
Appendix C: Sample codes ......................................................................................62
Appendix D: Screenshot of database tables .............................................................66

xiii
 CHAPTER ONE

INTRODUCTION
The ubiquity of wireless networking and the trend towards component
miniaturization have led to the evolution of cell phones from mere telephony
devices to powerful mobile computing platforms that provide the basis for a host of
other applications. With the rise of mobile phone applications, so-called apps,
people today are more looking for information on the go. This is one area of
mobile phone technology enhancement that allows developers and programmers to
offer users just what they seek under their preferred area of interest. Google’s
Android is one of the latest and unique innovations, which instantly has taken over
the mobile market.

The project focused on mobile based system (mobile app) development for
Google’s Android OS, a hugely popular open-source platform based on the Linux-
kernel and Java development environment. A growing number of cell phone
manufacturers and vendors such as Samsung, HTC, Techno, Huawei, Itel have
adopted Android as the platform of choice for their products. It is an open source
mobile platform which allows developers from around the world to develop
applications for Android supported mobile devices. Android supports to develop a
location based services application utilizing Global Positioning System (GPS) and
Android’s Network Location Provider to acquire the user location. Although GPS
is most accurate, it only works outdoors; it quickly consumes battery power, and
doesn't return the location as quickly as users want. Android's Network Location
Provider (NLP) determines user location using cell tower and Wi-Fi signals,
providing location information in a way that works indoors and outdoors, responds
faster, and uses less battery power. To obtain the user location in the application,
both GPS and the Network Location Provider can be used or just one.

Ten billion apps have been downloaded in the past three years. There are 17,000
location-based travel apps on the market, and 160 million app compatible devices
are owned worldwide – iPhones, Androids, BlackBerrys and tablet devices such as
the iPad and Motorola Xoom.

1
1.1 Back ground of the project
The big picture of this research was to invent a mobile based system for searching
and locating nearby places and services within kabalagala-kansanga. It comes from
a real issue that happens to new people that have just visited or come to stay in
kabalagala-kansanga. Many of these people come from other countries and Uganda
itself. Kabalagala is a fast-growing neighborhood within in Kampala, Uganda's
capital, and largest city, the neighborhood is famous for its many restaurants, bars
nightclubs and many more services and It is a major entertainment center, with
many of the establishments open 24 hours, 7 days a week.

The neighborhood has become a vibrant business hub, with new commercial
banks, supermarkets, fuel stations and a university campus and it is a favorite
hangout for foreigners visiting or resident in Uganda who like hanging out and
having leisure. From this issue, as they are still new to this location, they do not
specifically know the specific location where to get the services of their own taste.
It is really hard to find the nearest service especially when the new in the place is.
New people tend to get lost because of the fact that they are not familiar with the
area. In fact, searching the nearest service takes a lot of times.

It is really awful as not to get the desired service simply because they cannot find
it. In order to prevent this problem or difficulty which is to navigate to the nearest
services, the researcher took an initiative to invent a mobile based system for
searching and locating nearby places that can works as navigation tool for new
people. Basically, the application will works as a helping tool that can display map
and the list of nearest services to the current location of user while in kabalaga-
kansanga.

The name Kabalagala is derived from the Luganda name of a pancake made from
sweet bananas, cassava flour and is spiced with local peppers. Street vendors of
this food delicacy would yell "Kabalagala" to motorists waiting to turn at the
junction. The name stuck. Prior to that, the neighborhood was known as "Kisugu".
That name is now reserved for the more affluent residential area further north and
east of Kabalagala.

2
Kabalagala is bordered by Kibuli to the northwest, Namuwongo to the northeast,
Muyenga to the east and southeast, Kansanga to the south, Lukuli to the southwest
and Nsambya to the west. Kabalagala is located about 6 kilometres (3.7 mi)
southeast of Kampala's central business district. The coordinates of the
neighborhood are:0° 17' 53.00"N, 32° 36' 2.00"E (Latitude:0.298056;
Longitude:32.600556).

1.2 Problem Statement

There is no mobile based system (mobile app) to search and locate services and
places like hotels, ATM, Banks in Uganda kabalagala-kansanga in particular
mostly for people who are new in the place and are not used with the place
kabalagala-kansanga. Currently, people use manual system by asking and reading
posters to get services to locate the desired place. This has resulted in time
wastage, cost in terms of transport and airtime, increased conning especially from
boda boda riders, a lot of confusion and misguidance. It’s against this background
that a Mobile Based System for searching and locating nearby services and places
in kabalagala-kansanga was developed and implemented to ease the process.

1.3 Objectives of the project

1.3.1 General Objective

The general objective of this project was to develop a mobile based system (mobile
app) that was used to search and locate nearby places and services depending on
the user’s current location in real time.

1.3.2 Specific objective

1. To study, analyze, identify and investigate the requirements for building a
mobile based system for searching and locating nearby places in Uganda.
2. To design a prototype mobile based system for searching and locating
nearby places in Uganda in regards to our case study.
3. To test and validate the system developed during the course of study.
4. To implement the system developed.

3
1.4 Scope of the study

1.4.1 Geographical scope

Covered Kabalagala-Kansanga in Uganda.

1.4.2 Time scope

The research project took a period of 4 months.

1.4.3 Content scope

The study was limited to the development of a mobile based System for searching
and locating nearby places and services in kabalagala-kansanga, limited to
provision of list view of features using a graphical user interface, map view using
Google maps, search button, authentication of the users to the system, able to
access available services anywhere any time as long as its within kabalagala-
kansanga with the help of internet. The study was therefore to help the researcher
in achieving the study goal and management on improving their system. The
methods that were used for capturing information were limited to observation,
interviewing, questionnaires and the softwares that were used for development
were Android studio, Java JDK, Xampp server, PHP, MySQL all integrated with
Google maps.

1.5 Significance of the study

The significance of the study was to make a mobile based system for searching and
locating nearby places based on the user current location beneficial in the
following.

To the users, the system was able help them locate/search nearby services of their
tastes and preferences depending on their current location.

Developers were able to gain avast degree of knowledge and experience

concerning the development of mobile based system (mobile app) .

4
The community got a portable map for direction, and location finder for its towns
within the case study.

To the government, the system helps the new delegates /foreign government
officials to locate their intended destinations /towns and will reduce on cases like
people being conned.

Helps them locate hostels close by, banks for banking and withdrawing money and
most important universities, hostels.

1.6 Conceptual framework

The concept of the system was based on a kind of mobile based system for
searching and locating nearby places and services. It was used by users to view
nearby places, locate and map places depending on the users’ current location.

The following is the architectural design of how the MBS is operating.

Figure 1.1 the conceptual model showing the architectural design of the
system

In implementing the above mechanism, the following functionalities were designed

and implemented using Android studio, Java JDK, Google maps (mapping),
Wampp/Xampp server, PHP and MYSQL Server, Java, JSON, Bootstrap.

MBS consists of the following;

5
A database that keeps the information about different places (MYSQL database)
back end server.

A mobile app that is used to search and locate nearby places and services by the
users. An interactive user interface on the mobile app.

A web server (admin control panel) that is used to filter and pass the users request
to the back and server and bring the response back. On this PHP as a server-side
scripting language will be used.

1.7 Limitations to the study

There was always a lot of uncertainties with data correctness, Expensive in terms
of transportation, Language barrier, Constant loss of Battery charge of the
information gathering tools (smart phone, camera), Unpredictable weather
changes, Busy respondents (people to give you information)

6
 CHAPTER TWO

LITERATURE REVIEW
This chapter deals with the analysis of existing relevant literature of MBS for
searching and locating nearby services, their benefits and limitations; it further
stretches the development of mobile based android apps.

2.1 Introduction

Literature review chapter involves the identification, location and analysis of

documents, books, journals and reports containing information related to mobile
based system, android mobile app solutions brought by different authors. The
purpose of this chapter was to determine what was already done by others and gain
familiarity with the research topic and thus to avoid duplication of previous work.
In this study the literature review explained about the relevance of theories and
principals to the research study and an empirical review concerning the mobile app
solutions.

2.2 The following are reviews of relevant article and journals that have
been made.

2.2.1 Android and Mobile Application

7
Android is a software platform developed by combination of Google and The Open
Handset Alliance that consist approximately 30 organization (IndustryLeaders,
n.d.). This Android is an open-source software that contain operating system,
middleware and key mobile applications that can shape mobile application into
new areas (Meier, 2012). Several companies such as Google, HTC, Motorola and
etc joined together to shape a new product ‘Android’. The combination of this
‘Android’ is an open-source software platform built on Linux kernel version
(Hartman, Greg, &Kroah, n.d.). In addition, Android also has a set of applications
that consists of email clients, calendar, maps browser and more. All of these
applications are written in Java language or C++ language. The Android have been
selected or to be the most selected choice from the developer. There are two main
reasons why this occurs;The first reason is Android provide access to technical
advantages. As been told, android was created by using Java language, which is
powerful and can be adopted language in the global development community. The
second advantage is business advantages. All of the Android application can be
sold on Android market Google’s open source.

2.2.2 Mobile application

Mobile applications (also known as mobile apps) are software programs developed
for mobile devices such as smartphones and tablets. They turn mobile devices into
miniature powerhouses of function and fun. Some devices come preloaded with
some mobile apps courtesy of their manufacturers or the mobile service providers
with which they're associated (for example, Verizon, AT&T, T-Mobile, etc.), but
many more apps are available through device-specific app stores.

2.2.2.1 Advantages of android mobile apps

To the User Android Apps are easy to access and free to download, user friendly
interface, Android phones are cheaper, Offers Ample Widget, ROM can be
increased.

To the Business Owners Target audience is high, Adoptable features, and

Development cost is low.

8
To the App Developers Features can be modified easily, Code Reuse, API
implementation is easy, Testing is easy.

2.2.2.2 Disadvantages of Android

Little Memory for Storage, Force Close on Large App/Games, requires Data
Connection, Battery Problem, Box of Malware Google play store.

2.2.3 Google maps and API

Google Maps is a web mapping service developed by Google. It offers satellite

imagery, street maps, 360° panoramic views of streets (Street View), real-time
traffic conditions (Google Traffic), and route planning for traveling by foot, car,
bicycle (in beta), or public transportation. Google Maps began as a C++ desktop
program designed by Lars and Jens Eilstrup Rasmussen at Where 2
Technologies. In October 2004, the company was acquired by Google, which
converted it into a web application.

After additional acquisitions of a geospatial data visualization company and a real-

time traffic analyzer, Google Maps was launched in February 2005. Google Map
Maker allowed users to collaboratively expand and update the service's mapping
worldwide but was discontinued from March, 2017. However, crowd sourced
contributions to Google Maps were not discontinued as the company announced
those features will be transferred to Google Local Guides program.

On May 25, 2007, Google released Google Street View, a new feature of Google
Maps which provides 360° panoramic street-level views of various locations. On
the date of release, the feature only included five cities in the US. It has since
expanded to thousands of locations around the world. In July 2009, Google began
mapping college campuses and surrounding paths and trails. Street View garnered
much controversy after its release because of privacy concerns about the
uncensored nature of the panoramic photographs. A side effect of this is that
many unrelated objects, such as traffic signs, road information, and street
advertising, have often been blurred.

9
In March 2011, indoor maps were added to Google Maps for Android, giving users
the ability to navigate themselves within buildings such as airports, museums,
shopping malls, big-box stores, universities, transit stations, and other public
spaces (including underground facilities).

2.2.3.1 Google Maps API

After the success of reverse-engineered mashups such as chicagocrime.org and

housingmaps.com, Google launched the Google Maps API in June 2005 to allow
developers to integrate Google Maps into their websites. By using the Google
Maps API, it is possible to embed Google Maps site into an external website, on to
which site specific data can be overlaid. Although initially only a JavaScript API,
the Maps API was expanded to include an API for Adobe Flash applications (but
this has been deprecated), a service for retrieving static map images, and web
services for performing geocoding, generating driving directions, and obtaining
elevation profiles.

2.3 Existing mobile based location system (Related studies)

2.3.1 Location Based services to improve public transportation

The next research is focusing on mobile app that provides info about the state
public transport (buses) for the selected route (Srinivasan, 2011). The researcher
takes benefit from Location Based System (LBS) to optimize city bus services. The
main objective of this research is to help the user by providing information
regarding the public transport. To achieve that, the researcher developed a mobile
application. This mobile application is also using GPS based system that can
determine the current location of the user. After the current location have been
identified, a map interface will display important information such as potential bus
stop. Moreover, the list of directions also will be appeared to be access to the user.
The researcher has decided to run this mobile application on Android system
mobile phone compared to other system such as iOS and Blackberry. The choosing
of Android platform compared to others is because the Android is more marketable
and free access to developer also to the user. To develop this mobile application,
the researcher also used Android SDK, Eclipse and Google Maps. The

10
disadvantage of this mobile application is that it is based on only transportation and
cannot serve other services.

2.3.2 Sharing the Square: Collaborative Leisure in the City Streets.

The next related study is from this paper. This paper is about the collaborative
filtering algorithm uses historical data of previous user to recommend places
(Brown et al., 2005). In this paper, the suggestion place is still focus on tourism
area. The developers have been developing this mobile application that allows the
users to collaborate to each other through sharing experiences. They can share
pictures and voice among each other in term of interested place.

All of these experiences to the user are as leisure that takes benefits from access
mobile user collaboration. If the mobile application have a lot of user, the leisure
will Increase as they can share even more with user. In this research, there are 4
important criteria to make this mobile application a success. The first one is user’s
location are tracked with GPS and will be display on the map. Next, the user can
capture the pictures from the interested places then shared it with others. Third,
from all of experiences from the user, the systems will analyses and make a
suggestion of interested places that will be displayed on the map. Lastly, to
enhance more collaborative leisure among user, the developer allows voiceover-IP
to support chat among user. The system developed is George Square system that
works for outdoors as long as connection is available. Although it is a good system
that provides access to the user as guideline and navigator tool, a disadvantage has
been found on this mobile application. The main weakness is as it is a collaborative
system; the user only can only be shared with others that have installed the
application in their mobile phone. If the user did not install it, the shared place or
event cannot be seen. Even the pictures and voice talk will not be recorded into the
George System. It also does not give a clear description of the places and services
available within the selected place.

11
2.4 The implemented System

MBS displays the nearest places and services like hotels, hostels, ATM machines,
Banks, Hospitals, and more places and services using mobile app in a map and list
view on the basis of the user’s current location. The user selects the place
depending on his/her preference and need at that particular time. The user locates
any nearby place at his/her current location as long as he/she is connected on
internet and using an android smart phone.

2.4.1 Value of the implemented system

The implementation of the new system improved the efficiency to the stakeholders
by ensuring availability of places and services all equipped in one place. The
system also helps the new people search and locate places and services in Uganda
(kabalagala-kansanga), locate where they can have their emergencies in case they
need, where to go next and give them directions without wasting time.

2.4.2 Objectives of implemented system are

To combine Wireless technology and Android OS to automate place locator and

mapping process, To utilize wireless communication and smart phone technology
in implementing the automated system, To make more user interface friendly and
customized system for the users, To enable real-time feedback between the users,
System that provided attractive interfaces with easy navigation throughout the
system, System that would improve on the efficiency of information storage and
retrieval.

2.5 Development model process of MBS

We mainly used the waterfall model for development of mobile based system, and
this model ran through the following phases; requirements definition, system and
software design, implementation and unit testing, integration and system testing,
operation and maintenance. An overview of the process is shown in Figure below.

12
Requirements Identification: In this phase, the needs of the users are identified and
documented on a high abstraction level. Thereafter, the requirements are refined so
that they can be used as input to the design and implementation phase. The number
of requirements selected depends on the available resources for the project.

System Design, Implementation and Unit testing: In the design phase the
architecture of the system is created and documented. Thereafter, the actual
development of the system takes place, during the system development, android
studio, java JDK, MySQL and PHP, Xampp server, Google maps are used. The
developers also conduct basic unit testing before handing the developed code over
to the test phase.

Integration and System Testing: In this phase the system integration is tested
regarding quality and functional aspects. In order to make a decision whether the
system can be deployed; measures of performance for example throughput are
collected in the test laboratory. As the company provides complete solutions
including hardware and software the tests have to be conducted on a variety of
hardware and software configurations as those differ between customers.

13
Operation and Maintenance: After the product has been released to the user it has
to be maintained. That is, if users discover problems in the app they report them to
the developers and get support in solving them. If the problems are due to faults in
the app, packages for updating the system are delivered to the users.

14
 CHAPTER THREE

METHODOLOGY

3.0 Introduction
This chapter presents the description of methods chosen to achieve the objectives
of the implemented system. It describes the techniques of data collection that we
employed in the research study of the implemented system. It focused on detailed
description of the data collection techniques that were employed in coming up with
the implemented system. The chapter also looks at the relevant tools and research
approaches that we took in requirements collection and analyzing, planning, design
and implementation of the system.

3.1 Research design

The study employed qualitative approach and descriptive methods to describe the
characteristics of the research variables. It was qualitative in that opinions of the
people were sought and the researcher contextualized them according to his/her
understanding. A case study was used at kabalagala-kansanga. The deep
understanding of kabalagala-kansanga would assimilate other places/towns country
wide. The existing system was studied to establish its weak and strong points. The
information that was acquired from this study gave the basis for the design of the
system.

3.2 Target Population of study

The target population for this study was businessmen, boda boda riders,
custodians, taxi drivers, residents and other beneficiaries would include bankers,
waiters /waitresses, receptionists, students and street people in kabalagala-
kansanga.

3.2.1 Sampling
A sample is an element of the population considered for actual inclusion in the
study, or it is a subset of measurements drawn from a population we are interested
in. therefore sampling can be defined as selecting or choosing a small portion of
15
the total set of objects, events, persons, which together comprise the subjects of the
study.

3.2.2 Sampling Techniques

Stratified sampling together with purposive sampling methods was used as the
major sampling techniques, grouping population into different strata. The
population sample is divided into distinct, independent strata that can enable the
researchers to draw inferences about specific subgroups like businessmen, boda
boda cyclists, taxi drivers, students, residents.
Strata Total number of people in the strata
Boda boda 200

Students 200
Residents 100

Businessmen 300
Tax drivers 100
Street vendors 200
Hotels/Banks/Hostels managers 200
Others 200
Total 1500

Table 3.1 showing the different strata and number in the strata.

3.2.3 Sample size

This research project based on places and services like hostels, banks, universities,
hospitals therefore from each included service the researcher took a stratum of
population and used it to get some information about the existing system and the

16
implemented one using research tools. The researcher took 10% of every strata and
used it to get responses. (Sample size of the strata = 10%* strata number).
Strata Total number of Sample size=10%of strata
people in the strata
Boda boda 200 (10/100)*200=20

Students 200 (10/100)*200=20

Residents 100 (10/100)*200=20

Businessmen 300 (10/100)*200=30

Tax drivers 100 (10/100)*200=10
Street vendors 200 (10/100)*200=20
Hotel/hostel managers 200 (10/100)*200=20
Others 200 (10/100)*200=20
Total sample size 150

Table 3.2 showing sample size

3.3 Development methodology

The following were the steps that were deployed to fully understand the current
system that was being used. These include; requirement identification; design;
implementation, testing and validation. However, the development process will be
iterative, though it will be depicted as comparing of phases.

17
Figure 3.1 that follows shows the system’s development methodology.

3.4 Requirements identification

To identify the requirements of the system, various approaches were used as
explained below.

3.4.1 System study and investigation

There was a thorough study of the existing systems in the Uganda particularly
kabalagala-kansanga in order to understand the loop holes before developing the
mobile-based system for searching and locating places and services. This was
achieved by use of Data Collection Methods like questionnaires, interviews and
observations.

3.4.1.1 Data Collection Methods

We used the following methods during data collection: Observation, Interviewing
and Questionnaires as our research methods.
Observation
The researcher moved around different places in kabalagala-kansanga seeing how
people in a new place locate and find nearby places depending on their current.

Advantages of observation

18
It was direct method for collecting data or information it helped the researcher in
studying data critically, Data collected was very accurate and very reliable.
Problem of depending on respondents decreased, this helped the researcher in
understanding the verbal response more efficiently.

Disadvantage

It was so costly, time consuming, tiresome and made the researcher to be more idle
in the field.

Interviews
Oral interviews were conducted between the researcher and the local people,
foreigners, students and others.

Advantages of interviews

Interviews gave the researcher the opportunity to motivate the interviewee to

respond freely and openly to questions, also allowed the researcher to probe for
more feedback from interviewee, Interviews permitted researcher to adopt or
reward questions for each individual and quick responses from the respondent.

Disadvantages of interviews

Interviewing was time consuming since the interviewees gave information

according to their own understanding, Difficult to organize data according to their
views, Costly, success of interviews was highly dependent on the systems human
relation skills and interviewing may be impractical due to the location of
interviewees.

Questionnaires
In this approach, printed questionnaires were given to some of the stakeholders to
fill in the blank spaces. This helped the researcher to know the operation of the
existing system. Questionnaires allow the analysts to collect data from large
number of people while maintaining uniform response, when dealing with large
audience, no other fact finding technique can tabulate the same facts as efficiently.
Advantages of questionnaires
19
Questionnaires were answered quickly, people completed and return questionnaires
at their convenience, questionnaires produce relatively inexpensive means of
gathering data from a large number of individuals, questionnaires allow individuals
to maintain anonymity and responses can be tabulated and analysed quickly.
Disadvantages of questionnaires
The number of respondents was low, there was no guarantee that an individual
would answer some or all questions, questionnaires tend to be inflexible. It was
also not possible for the analyst to observe and analyse the respondent’s body
language and there was no immediate opportunity clarify vague or incomplete
answer to any question.

3.5 System Design

The analysis of the requirements acquired in the requirements identification phase
led to the development of the mobile based system for searching and locating
nearby places and services. The Database system was developed using Xampp,
MYSQL and the programming frame work of the system was done using Android
studio, Java JDK, JSON, PHP, Bootstrap integrated with Google maps. There was
removal of redundancies by normalization of the data in order to get the right
material to be entered into the tables to be used for the system. There was
conceptual database design by having the Entity Relational Diagram and the Entity
Relations. There was also the Logical design where entities, attributes, data lengths
were made to remove the redundancies in the system and duplicates. This led to
physical database design where MySQL with PHP script was used to design the
system that enabled database connection to the android app. The system design
objectives includes: Usability, performance, reliability, software architecture and
package.

3.6 System Implementation

During system implementation, The android app was able to run on smart android
OS phones of version 2.3 and above and the web app was able to run on windows
and it was best suited for Pentium 4 computers or higher processors with a speed of
at least 500MHZ considerable amount of Ram and 80GB hard disc space was
required for proper functionality of the system. RAM of 512 MB and above was

20
recommended and a computer monitor with a high resolution and a standard
keyboard and mouse connected to the system.

3.7 System testing and validation

Software testing is a fundamental component of software quality assurance and
represents a review of specification design and coding. Unit and module testing
was used during the process. During unit testing, individual functions were tested
to prove their functionality. This helped to reduce errors during module testing
where units were combined as one to form a module. A successful testing resulted
into a complete system that was tested as a whole to check for its capabilities and
also techniques like black box testing were also employed so as to achieve the
system’s final objective. The validation process involved checking the
implemented system whether it confirms inputs to the specifications. Several
validation tests such as data and security were carried out to ensure that the system
can validate data input from the users, reject any data which is supplied in wrong
format and prevent unauthorized users from accessing the system resources.

21
 CHAPTER FOUR

SYSTEM ANALYSIS AND SYSTEM DESIGN

4.0 Introduction

In this section, weakness and strength of the current system, analysis and detailed
design issues, design requirements and system functionalities are all discussed
within this chapter. It addresses the conditions that were necessary for the effective
functioning of the system and also the tools that were used in the development and
design of the new system.

4.1 Weakness and Strength of the Current Systems used to search and
locate nearby places and services within kabalagala-kansanga.

4.1.1 Weakness
The following were the limitations of the current systems used to search ad locate
nearby places and services in Uganda (kabalagala-kansanga);

Requires one to be connected to the internet in order to use the system, Requires
one to be having a smart phone running android O.S, Supports only android O.S
phones versions 2.3 or higher.

4.1.2 Strength
However the following were the advantages of the current systems used to search
and locate nearby services in kabalagala-kansanga;

Provide higher level of compliance and faster service with lower cost and higher
efficiency, Furthermore it also facilitates, regulates and simplifies the processes of
finding places by visitors who are coming to visit the place for the first time, more
user interfaces friendly and customized, Enable real-time feedback about the
services to the users, Free to download.

22
4.2 System analysis and Study

The researcher studied the existing system to identify its strength and weaknesses.
The information that was acquired from this study by employing a number of
techniques and tools such as observation and interview guides gave the basis for
the design of the new system. An interview guide with open ended questions was
prepared and administered to the respondents so as to enable them give their views
freely. This technique was chosen because it helped the researcher to get full range
and depth of information. Observation was also used to gather accurate
information about how the system actually operates, particularly about processes.
Although the method was time consuming, it gave more detailed and context
related information. The researcher realized that the existing system is manual
whereby a person first have to ask or takes time looking around to get service in
kabalagala-kansanga. This system is associated with risks like loss conning that
results into loosing money, phone and other gadgets by users. This has created a
need for a system that will allow stake holders access services immediately
anywhere within the country particularly kabalagala-kansanga, provide security by
authentication and also reduce redundancy and time wastage.

4.3 Requirements Specification

The requirement analysis stage of a software engineering is the practice of

obtaining, collecting and analyzing information that is used to identify the users’
requirement of the new system. The term elicitation is used in research to raise the
fact that good requirement cannot just be collected from users as would be
indicated by the name requirement engineering. Requirement elicitation is not
trivial because you can never be sure that you will get all requirements from users
by asking them what the system would do and it includes the process like
interview, observation, workshop, brain storming and questionnaires. Identifying
the required functionality of the system is very important as a system with the
incomplete functionality may lead to it being rejected. A description of the aim of
the project is given here along with the details of the functional and non-functional
requirements for the system.

23
4.3.1 Functional Requirements
The system was required to perform automation of the process of services’ details,
locations and give quick retrieval of required information basing on the users
current location, interest and taste. It ought to overcome the anomalies of the
manual system.

4.3.2 Non-Functional Requirements

The new system ensures that: A security system prevented unauthorized users from
accessing the system. This was achieved by using usernames and passwords. A
user accessible catalog provided description of the data in the mobile app that is
retrieved from the database. System allowed access to the database by using JSON
to retrieve data via the mobile app. An integrity system maintained the consistent
users accessing the database.

4.3.4 User Requirement

During data collection, we investigated and found out how current directors
(people helping to direct others) respond to the people in search of their places of
interest and also tried out which problems are faced and how best can they be
settled. The users recommended that the proposed system should be; User friendly,
able to respond without errors, operate without fail while on the move, provide
quick response and should be reliable.

4.3.5 System Requirement

These requirements are required by the system to be able to perform its expected
functionalities efficiently and effectively. The following are required to run the
system:

4.3.5.1 Hardware Requirement

Hardware Minimum System requirement
Processor 2.4 GHZ processor speed
Memory 4GB RAM ( Recommended)
Disk space 80 GB (including 20 GB for database

24
 Management system)
Display 800 x 600 colors (1024 x 768 High color- 16 bit
Recommended)
Smart phone android O.S Version 2.3 and above
Backup hard disk 80 GB

Table 4.1 Showing Hardware Requirements.

The table above shows hardware components of the machine that allows the
system to function as required.

4.3.5.1 Software Requirements

Software Minimum System requirement
Operating System Windows
Android studio bundle Version latest 3.0.1
Java JDK 7 and above
Google maps
Xampp server Latest version
MySQL
Php
Sublime text Version 3.5

Table 4.2 Showing Software Requirements.

The table above shows software requirements recommended to enable the system
to run as required.

25
4.3.6 Environmental Requirements
i. Smart phones that are connected to the internet.
ii. A Server as a backup for the system.

4.4 Structured Requirements Analysis

This section describes the flow of data or information between entities and the
processes involved during searching and locating places using MBS. Context
diagrams and use case diagram, DFDs were used to achieve this. There are mainly
four components of a data flow diagram and are represented by the symbols as
discussed below.

4.4.1 Data Flow Diagram

A data flow diagram (DFD) or a bubble chart is a graphical tool for structured
analysis. It was De Marco (1978) and Gane and Sarson (1979) who introduced
DFD.DFD models a system by using external entities from which data flows to a
process, which transforms the data and creates, output-data-flows which go to
other process or external entities or files. Data in files may also flow to processes
as arrows. There are various symbols used in the DFD. Bubbles represent the
processes. Named arrows indicate the data flow. External entities are represented
by rectangles and are outside the system such as vendors or customers with whom
the system interacts. They either supply or consume data. Entities supplying data
are named as sources and those that consume data are called sinks. Data are stored
in a data store by a process in the system. Each component in a DFD is labeled
with a descriptive name. Process names are further identified with a number. Data
Flow Diagrams are made up of a number of symbols, which represents system
components. Data flow modeling method uses four kinds of symbols, which are
used to represent four kinds of system components. These are;

Process

Process shows the work of the system. Each process has one or more data inputs
and produce one or more data outputs. Processes are represented by rounded
rectangles or ovals in Data Flow Diagram. Each process has a unique name and
number. This name and number appears inside the rectangle that represents the
process in a Data Flow Diagram.

26
The process symbol represents the activity that transforms the data

Data flow

Data flows show the passage of data in the system and are represented by lines
joining system components. An arrow indicates the direction of flow and the line is
labeled by name of the data flow.

The data flow symbol represents movement of data.

External entity

External entities are outside the system but they either supply input data into the
system or use other systems output. They are entities on which the designer has
control. They may be an organizations customer or other bodies with which the
system interacts. External entities that supply data into the system are sometimes
called source. External entities that use the system data are sometimes called sinks.
These are represented by rectangles in the Data flow Diagram.

The external entity symbol represents sources of data to the system or the
destination of data from the system.

27
Data store

A data store is a repository of data. Processes can enter data, into a store or retrieve
the data from the data store. Each data has a unique name.

Figures 4.1: data flow diagram symbols

4.4.2 Context Diagram

MBS is a three tier archecture; it consist of mobile app (for users), web app (admin
control panel) which also acts as a webserver and backend server that is MYSQL
database.

The Context Diagram of the Developed System

Figure 4.1 Show contextual diagram of MBS

28
Figure 4.2 showing the DFD level 0 diagram of MBS

29
Figure 4.3 showing use case diagram of MBS

Data Dictionary of the Level 0 data Flow Diagram

Entity Description
Admin Responsible for CRUDE (Create, read, update, delete, edit

Table 4.3 Data dictionary showing description of entities.

Process Description

30
System The process through which system users and administrators are
authentication authenticated.
Add a service, The process through which services need in the system are
update, delete and added, updated, edited and deletion of un necessary services.
Edit

Table 4.4 Data dictionary showing description of processes

Data respiratory Description

Services Shows services that are stored in the MBS database
Users Holds username, password and the user type of the user
(whether normal user or administrator).
Facility Shows the information about all the details of a particular
service, the location, the type that are available in kabalagala-
kansanga

Table 4.5 Data dictionary showing description of data stores

Database Design
This section describes the process of creating a design for the database that
supports the operation of the developed application. There are basically three
phases that make up this process; the conceptual, logical and physical database
designs.

The conceptual involves the creation of a theoretical data model of the part of the
system that we are interested in. under this model, the relevant entities, tables,
relationships, key attributes and entity relationship diagrams are clearly organized
from the data collected.

Logical database design is the process of constructing a data model of information

used in the system based on the specific data model but independent of a particular

31
database management system. In this phase, normalization procedures and
definition of integrity rules are properly applied.

Tables and their relationships are clearly constructed as per the conceptual design.
Physical database design is the process of producing the description of the
implementation of the database on a secondary storage media. It describes
relations, file organization and indexes used to achieve efficient access to data and
associated security measures and integrity constraints.

In this case, actual programming of the database is done, taking into account the
features and the limitations of the DBMS being used and clients. Within this
particular project, the relational data model was used. Data and relationships are
represented as tables, each of which has a number of unique names also known as
attributes, represented as tables, each of which has a number of unique names also
known as attributes.

Identification of Entities and Their Attributes

Entity Description Attributes

Users Users (stakeholders) Username, password, email, phone,

user_type, status.
Services Services provided Service_id, service name,
facility_id
Facility Detailed information of services Facility_id, Facility_name, address,
address_description, facility_type,
status.

Table 4.6 Entities and their attributes

Relationships between Entities

One form of relationship was identified that is, one to one. A one to one
relationship represents a single Association between a sole entity occurrence and a
single entity occurrence as shown below.

32
Entity Relational Diagram
An entity relational diagram (ERD) is used to visualize the system and represent
the user’s requirements. This is used to represent entities and how they relate to
one another. Figure below is an ER diagram that shows the relationships between
the entities, their occurrence (multiplities) and attributes.

Figure 4.1 showing entity relationship diagram

4.3 System Design

After interpretation of the data, tables were drawn and process of data determined
to guide the researcher of the implementation stage of the project. The tools, which
were employed during this methodology stage, were mainly tables and ERDs were
used to analyze the tables.

33
 CHAPTER FIVE

SYSTEM IMPLEMENTATION RESULTS

5.0 Introduction
This chapter highlights the findings and results of the project and the snap shots for
each of the activities are shown along with the discussion of each activity
describing its working. Each snap shop describes each every single step of the
MBS.

5.1 Snapshots of the output of User Interface Design of MBS

User interface (UI) design is a human-computer interaction, operating logic and
interface aesthetics for software design. It enables application to become operation,
friendly and freely. Here will discuss about UI in MBS.

5.1.1 User interface (login/sign up)

This is the first page of the system mobile app that is displayed when the app is
loaded for use. When the user in puts correct username and password, the page
redirects to listview which contains all the necessary information. When the user in
puts wrong username or password, the system loads incorrect username or
password. If the user is not registered it will first ask him or her to create an
account.

34
Figure 5.1 Snapshot of the System mobile app Sign up interface

5.1.2 Signing up with a wrong username and a password

When a user creates an account with a user name that has characters less than
seven and a password with less than seven it gives out an error. The username and
the password must be greater or equal to seven characters.

35
Figure 5.2 Snap shot showing what happens when a user signs up with a
username and a password with below 7 characters.

36
5.1.3 Correct username and password signup
When the user in puts correct username and password in the form, successful
created an account message will be displayed and it will redirect the user to the
login page .

Figure 5.3 Snapshot of a user signing up /creating an account

37
Figure 5.4 Snapshot showing account successfully created and login page

5.1.4 Login Form

When the user input the username and password and confirms the password, he or
she will be directed to login page and a message “Account Successfully Created”
will be displayed. When the user in puts correct username and password in the
login form, he or she will be redirected to a listview which contains all the
information about different categories of places and services and an option of a
google map icon.

38
Figure 5.5 Snapshot of a user logging in
A “successful logged in” message will be displayed on the listview of categories of
services and a map icon on each category

39
Figure 5.6 Snapshot of a user successfully logged in
The user will base on this listview to select his option. For example if the user is
interested in pharmacies and clicks on pharmacy fragment it will redirect him to
the list of all pharmacies available within kabalagala-kansanga.

40
 Figure 5.7 showing the listview of pharmacies in kabalagala-kansanga

The user then can select his preferred pharmacy by clicking on it. It will redirect
him to the details of the selected pharmacy. For example if the user selected
Mustard Pharmacy it will redirect her to the details

41
 Figure 5.8 showing details of selected pharmacy

The user can either base on this information or can check the distance from his or
her current location to the selected pharmacy using “view map” button. When it is
clicked it will take the user to the Google maps and will display all the nearby
pharmacies including the selected one.

42
Figure 5.9 Snapshot of a Google map displaying selected service (phamarcies).

The red button on the map stands for selected categories and the blue dot show the
users’ current location. The white lines are for roads and all possible routes.

When user clicks on one of the pharmacies “mustard” it will show the distance,
how many kilometres from his current location. If he or she wants the direction, it
will calculate the shortest route and it will be displayed against time one can take
to reach the desired destination. The user only has to click on the direct button

43
Figure 5.10 Snapshot showing the possible route and direction to the selected
service.

44
The following message will be display When a user login with incorrect password
or has no account and tries to login “Sorry! SignUp First. OR password incorrect”

Figure 5.11 Snapshot showing a user login with incorrect password or wrong
account

45
5.2 MBS web app /server for the user and admin dashboard
This displays about the services, contacts of the developers and consist of the
admin login section/panel. The admin panel/dashboard can only be accessed by the
admin for adding information about the services and places, managing users and
the services.
Home page displays all the pages within the web app including login for the admin
to the dashboard.

Figure 5.12 Snapshot of A home page for the web app

If a user is interested in knowing about the developers he show she can click on
about us page.

46
Figure 5.13 Snapshot of about us page
The user can still check the categories of services available in MBS

Figure 5.14 A snapshot of services page

47
Figure 5.15 Snapshot of portfolio page

Figure 5.16 Snapshot of contact us

48
Admin dashboard/login panel
This is where the admin manages the entire MBS system. He/ she adds, deletes,
edits and update services to or within the database. The admin also manages users
from the admin dashboard.

Figure 5.17 Snapshot of admin login panel

When the admin successfully logins it redirects him or her to the admin dashboard
where he or she is able to carry out administrative operations. Services/ facilities
are displayed and a form for adding is also shown. If the admin is interested in
adding new services to the system he can use the form below

49
Figure 5.18 admin dashboard showing a form for adding services

If the admin wants to view the facilities or services available, he will right click on
services then view services. It will display all the services available within the
database.

50
Figure 5.19 Snapshot of viewing the services / facilities
If the admin want to delete a service or facility, he will go to view services clicks
on close button of the service he wants to delete. It will ask him “are you sure you
want to close forexample kiu ?” if he clicks yes kiu will be removed from the
database

51
Figure 5.20 Snapshot of Deleting a service/ facility
The admin can still update services or facilities within the table. He will click on
the service he wants to update, click on edit button it will redirect her to the
information in the form form and he can edit the interested information.

52
Figure 5.21 snapshot for updating a service / a facility

When the admin logs out it redirects him or her to the web app home page.
In order for the mobile app to have or retrieve information there should be
assistance of web app because that’s where the admin adds information and
manages the database from where the user retrieves the information. That is why it
is called MBS, integrated mobile app, web app and the back end server database
(MYSQL).

53
 CHAPTER SIX

DISCUSSION, CONCLUSION AND RECOMMENDATIONS

This chapter examines how the objectives of the study were achieved using the
system that was Developed. The outcomes and contribution of the study to
evaluation of changes of the way places and services are located and found in
kabalagala-kansanga are handled are discussed and conclusions are given below
and also the recommendations.

6.1 Discussion
The designed system can capture, store, retrieve, show and display information
about the places and services in kabalagala-kansanga easily. Now that the system
can capture, store and retrieve information about services and places such as
hospitals at once then only updates would be required.

Instead of people moving around asking for services, places, facilities and
directions MBS acts as their respiratory and guide, has all services kept in one
place where they are retrieved easily, embedded with Google maps where users
check the location and direction depending on their current location and all the
possible routes. It was developed to help a layman who is new within the area and
has no clue about the place. It has been noted that being misled, conmen so called
“kifesi” cases have reduced to some extent unlike in the past where offenders
relaxed. This was partly due to lack of information about services and places in
kabalagala-kasanga.
A user-centered approach to software development was completely adhered to.
Furthermore, software engineering principles were strictly followed making the
software highly user friendly yet minimizing any undesirable trade-offs.
Robustness, usability, interoperability, efficiency and platform neutrality are the
major plus for the tool.

A three-tier architecture was used and the system is into three sections; mobile app
for users to access information and details about places and services available in

54
kabalagala-kansanga, web app where we find the admin dashboard for managing
the system and users and the database back end server which is MYSQL.

The web app consists of secure login, where the admin gets the System Operations
that have links to the database and mobile app that provides necessary information
about the services and services in kabalagala-kansanga, edit forms, delete, update,
add the necessary information all necessary for updating the information. The
logout menu exits the system. The login page is fully functional and only permits
the system admin to access the administrator dashboard where administrative tasks
are performed; it requires entering a valid username and password.

The mobile app is where the user accesses the information from by logging in with
username and a password. The user has to first create an account in order to access
the services. The database stores all the information and the registered users.

The system was developed using Android studio, Java JDK for programming,
Xampp Server as a localhost, MySQL as back end server, PHP as server side
scripting language, JSON for retrieving data from the database, Sublime text as the
text editor all integrated with Google maps for easy location and directions. A
majority of the system functionality was provided using android studio together
with Java JDK integrated with Google maps , Xampp, JSON, MYSQL and PHP
since information is retrieved from the database and displayed on mobile app using
internet.

6.2 Conclusion
This study was set out to develop a MBS for searching and locating nearby places
and services using a user-centered approach to software development. The scope
set at inception was restricted to developing a system for searching and locating
nearby places and services. The study led to design and implementation of a
prototype for a MBS for searching and locating nearby places and services. The
system was tested and validated for functionality. The system was implemented
using a3-tier architecture, with a backend database (specifically MYSQL
database), a middle tier of Apache server and PHP, and a front end mobile app
(client). This report has also discussed each of the underlying techniques used to
design and implement the application and the steps undertaken to achieve this.
The system developed can now provide means for the new people in kabalagala-
55
kansanga to easily search and locate places and services nearby depending on their
current location. The system has removed delays which were experienced through
the old system because cross checking while asking through the streets of
kabalagala-kansanga has been time consuming. Businessmen, companies, clients
has benefited from the new system because there businesses are brought on line
and can easily be viewed

6.3 Recommendations
The findings of the study recommended adoption and usage of the developed
system (mobile based system for searching and locating nearby places and
services) so as to improve on the security of users gadgets like phones, money,
misdirection and also easy retrieve of information, reduce on time of identification
of particular service or place information. The following recommendations are to
be ensured to enhance areal time, maintainable and robust system in place. We do
recommend that users should atleast acquire android smart phones version 2.3 and
above to be able to use the system and the location on their phone should always
be turned on and should have some internet connection, , The researchers also do
recommend that all new people ,and others within Uganda should try to find the
application and install it on their gadgets and go fully digital in searching, locating
and finding places in Uganda in relation to our case study, also do recommend that
the users of the system should take time to learn how to use Google maps with
much ease if they aren’t familiar with it because it a great feature or tool embedded
in the system, The researchers also highly recommend that if their some
uncertainties of areas of concern say need to make change within the app
functionalities, feel free and communicate with developers through the web app
plat using email or phone number provided there

6.3.1 Areas for Further Study

It’s recommended that the following modules, be added to the developed system
(MBS) so as to perform more tasks:
Should also add a chat activity such that users can connect straight to the service/
place owners and can order incase of anything or get help.

56
The backup module should also be incorporated so as to ensure that the
information that is kept is safe and to ensure that there is ready backup information
in case the original information gets corrupted or lost.
The developed system component can have the capability to be used in different
languages. Further work is recommended so that it can have the capability of being
usable different languages since different people are going to be using it.
Look into how the system can help other users who are not using android OS
phone like ios phones.

57
REFERENCES

1. J. DongjiuGeng, YueSuo, Yu Chen, Jun Wen, Yongqing Lu, Remote Access

and Control System Based on Android MobilePhone. Journal of Computer
Applications, 2011,vol.2 pp. 560-562
2. M. Fengsheng Yang, Android Application Development Revelation, China
Machine Press, 2010,1
3. J. Li Lin, ChangweiZou, Research on Cloud Computing Based on Android
Platform, Software Guide, 2010, vol.11pp.137-139
4. M. Zhengguo Hu, Jian Wu, Zhenggong Deng, Programming Methodology,
National Defence Industry Press, 2008,6
5. M. Junmin Ye, Software Engineering, Tsinghua University Press, 2006,6
6. Gartner Indentifies the top 10 consumer mobile applications for2012,
Stamford, Conn., Gartner Inc., November 18, 2009.
7. "Google Company: Our history in depth". google.co.uk. Google. Archived
from the original on April 6, 2016. Retrieved June 13, 2016, view on 12
April 2018.
8. "What is the Google Maps API?". Archived from the original on April 12,
2018.
9. Perez, Sarah. "Google to shut down Map Maker, its crowd sourced map
editing tool | TechCrunch". Archived from the original on August 11, 2017.
Retrieved June 23, 2017 viewed 12 April 2018.
10. "Blurry or Outdated Imagery". Archived from the original on October 24,
2013.

58
APPENDICES

Appendix A: Questionnaire
1. Please respond to the questions and kindly grade accordingly.
Gender: Female Male

2. Age bracket : 15-25 26-35 36-45 46-60 >60

3. Category
Student
Tourist
Resident
Others

4. How do you locate and search nearby places and services?

………………………………………………………………………………………
……………………………………………………………………………………...
5. What is the best way to locate a nearby place / a service?
...................................................................................................................................
..................................................................................................................................
6. And, how good and fast is it (above mentioned method)?
........................................................................................................................
.......................................................................................................................
7. What are the common challenges you face while trying to search and
locate a nearby place and services?
........................................................................................................................
.......................................................................................................................

59
8. Do you have a smart phone? How often do you use internet to search?
........................................................................................................................
.......................................................................................................................
9. Have you ever used android operating system?
Yes No
10. If yes, how is/was it?
………………………………………………………………………………
11. And what are the challenges of using android operating system on a
phone?
………………………………………………………………………………
12. Would you want some changes in the current system of searching and
locating nearby places depending on your taste?
Yes No
13. If yes how would you want it to be?
........................................................................................................................
.......................................................................................................................
14. Which type of system would you prefer?
Mobile App Web App Both
15. How would you rate the services provided by existing system for locating
a nearby place depending on your current location?
Poor Good Excellent
16. What if a new system is to be developed, would you be in for it?
…………………………………………………………………………
17. What would you recommend the researchers to do?
…………………………………………………………………………
18. Your conclusion
…………………………………………………………………………
Thank you

60
Appendix B: Interview

1. What type of a phone do you use?

2. Do you use mobile apps?
3. Name 3 of your favorite mobile apps
4. What do you use them for?
5. What features do you use most?
6. Have you ever used Google maps using any mobile app?
7. Have you participated in the creation of any app that is available in the
iTunes or Android stores?
8. Tell us about some of the disadvantages of both Android and iOS.
9. What are the main differences between desktop/web apps vs. mobile apps?
10.How do you handle security issues?
11.What’s the importance of location based services mobile application
development?
12.Do you have any experience migrating an app from one platform to another?

61
Appendix C: Sample codes
i) A sample login code
<?php

include '../DbConfig.php';

// if (isset($_POST['uname']) && isset($_POST['upass'])) {

if($_SERVER['REQUEST_METHOD']=='POST'){

$userName = $_POST['uname'];

$passWord = $_POST['upass'];

//$userName = "Admin";

//$passWord = "admin123";

$query = "select * from users where(username = '$userName' and password =

'$passWord' and status = 1)";

$result = mysqli_query($con, $query);

if (mysqli_num_rows($result) > 0) {

echo "success";

exit;

} else {

echo "Failed";

exit;

} else {

echo "Require Parameters!";

62
 exit;

?>

ii) A sample code for signup

<?php

include '../DbConfig.php';

if($_SERVER['REQUEST_METHOD']=='POST'){

$userName = $_POST['uname'];

$passWord = $_POST['upass'];

$userType = $_POST['utype'];

$query = "insert into users(username, password, email, phone, user_type,status)

values('$userName','$passWord', 'client@lapisha.com', '+256','$userType', 1)";

$run_query = mysqli_query($con, $query);

if ($run_query) {

echo "success";

exit;

} else {

echo "Failed".mysqli_error($con);

exit;

} else {

63
 echo "Require Parameters!";

exit;

?>

iii) Sample code for database connection

<?php

$con = mysqli_connect("localhost","root","","locationapp_db") or die("Connection

was not established");

?>

iv) Android main activity sample code

64
v) Sample code for http parse.java android

65
Appendix D: Screenshot of database tables

Table 7.1 Facility

Table 7.2 Services

Table 7.3 Users

66