Docu Need To Be Revised

ASIAN INSTITUTE OF COMPUTER STUDIES
410 D and I Bldg, Edsa Corner, Caloocan City

Metro Manila, Philippines
Date:_________
APPROVAL FOR BINDING
This is to certify that we have examined the manuscript which entitled:
TOMB LOCATOR USING GLOBAL POSITIONING SYSTEM (GPS) VIA

ANDROID APPLICATION and found that all the comments and
recommendations of the Oral Examination Panel had been reflected.
This certification is issued to allow the proponents to submit the

manuscript for final binding.
The Oral Examination Panel:
Name Signature
1. Mr. Manuel C. Delos Santos, MSCS Committee Chairman ________
2. Mr. Jesus Victor G. Lacerna, ECE, MIS Technical Adviser ________
3. Ms. Nena F. Famocol, MBA, PhD Committee Member ________
4. Mr. Ronald S. Tinio, MSE, MCP Committee Member ________
Recommending Approval:
__________________________
Ms. Cecilia P. Abaricia, DT
Thesis Adviser
________________________________
Mr. Manuel Luis C. Delos Santos, MSCS
Dean, Computer Science Department
COMPUTER SCIENCE DEPARTMENT

1
Dedication
The group dedicates this thesis to the loving parents for helping
through the darkest midst of the subject giving financial and moral support. To
professor Ms. Cecilia P. Abaricia, adviser of thesis subject for not letting
down, encourages to finish and surpassed it. To all person who helped to
finish this study. To God be all the Glory and thanks giving.

2
Acknowledgement
The proponents would like to take the opportunity to thanks the
persons that helps in the making or finishing the thesis and documentation.
Deserving a special mention Ms. Cecilia P. Abaricia, thesis adviser who
helps and guides every time to make a step finish these.
And to Mrs. Milagros O. Laygo instructor and head faculty of the
school, who help and gave encouragement, uplifted, advises when the group
feels upset, and looks hopeless.
To the classmates, friends, family, and every single person that was
there in ups and down, thrived to become better and told that the group could
show the best potential and got to make it.
Lastly, the group would like to thank Almighty God for giving strength,
courage, faith, believe that whatever happens by trusting and believing in God
would finish and made this study. Again thanks to everyone from the bottom
and deepest heartfelt thanks.

3
Abstract
Introductory statement
Problem encountered by the people -- the proponents decided to develop this
application.....
Objectives of the study
This study focuses on mapping and navigating the location of the Tomb
at Sangandaan Cemetery, the proponents conduct this study in order to
create an application that provides navigation, regarding the birth and death
date of the tomb and blockings for each specific tomb. The proponents used
Google Map to provide the navigation, also the map where the cemetery was
located, each tomb has specific marker to provide a path towards the tomb,
along with the list of the tomb, there was the name of the deceased person
and the blockings of the tomb. Tomb Locator via Android Application was
software that let the user store the location of the deceased, the user can
insert image of the grave, and the specific location for the desired tomb.
Significance of the study
Design and Methodology

4
Results and Discussion (Evaluation of the system)
Conclusion
The proponents recommend the implementation of the proposed
system for effective and quick way of gathering data or information at locating
the easiest or quickest way to go to tomb, also for the future reference for
other proponents, the proponents would prefer this application for lessen the
hassle of remembering a place far from the user.

5
Chapter I
Introduction
In regular days finding the tomb was hard, visiting the cemetery was a
tradition every year to pay a visit to the loved ones. Cemeteries have vast
area of burial spot, visitors had to experience the situations like asking the
information to locate the tomb of loved ones, but people still experience
difficulties to find the tomb. Peak season comes on first week of November, so
many people visit the loved ones, compare in regular days less people come
in to cemetery. Emergency teams scattered around the cemetery, to secure
the safeness of people.
The proponents proposed a system regarding Tomb Locator using
Global Positioning System (GPS) via Android Application, to help navigate the
tomb using the application through Smartphones or Android Phones. This can
help people or user if visiting the cemetery. People can forget the location and
landmark of the tomb. This document shows or explains how the application
works for users. The location of this application located at Sangandaan

6
Cemetery, one of the most cemeteries that has a large amount of people
buried and has a huge area.
Tomb Locator was developed to easy navigate the tomb. The users of
this application can already have information of the tomb, so the users have a
tendency not to ask information to stranger.
Project Context
This application helps the people locate, the exact mark of the tomb,
using this application can make easy for user to ask questions or guidance of
the personnel to locate the tomb of the dead family member. Sangandaan
Cemetery has a large area, so this application provides the direction of the
tomb.
To use this application, the user needs to connect in internet and
access the Global Positioning System (GPS) in the smartphone. It has a
search function that includes the first and last name of the deceased, also it
includes the date of birth and the year of death, take picture of the tomb and
locate the coordinates of the tomb then saving it. After inputting the required
information, the details of the dead person can show the information and also
the way to navigate the tomb.

7
This application uses Google map and has a feature of voice
notification to notify if the user arrived at the destination, and Google Maps
provide a satellite view. The proponents have inputted two (2) markers for
locating the tomb. First, the red marker where the tomb was located and
second, the blue marker would navigate the direction going towards to the red
marker where the tomb was located.
Purpose and Description
Statement of the Problem
The main problem in locating the tomb at the cemetery was to ask
people where the specific tomb was located, some people cannot provide
tomb location easily, and the visitor of the cemetery manually search the
location of the tomb that led visitors to be tired before finding the exact
location of the tomb.
General Problem
The ways to improve the management of the Sangandaan Cemetery in
terms of mapping and location of the tombs.

8
Specific Problem
1. What were the ways of locating the tomb easily?

2. How can navigation help the user to locate the tomb easily?
3. How the blocking of the tomb can help the people visit at the
cemetery?
Specifically, the proponents sought to answer the following queries:
1. What were the demographic profile of the respondents in terms of:

1.1 age
1.2 gender
1.3 designation
1.4 Highest Educational Attainment
2. What were the problems encountered in using the manual process?
3. How the proponents develop the Tomb Locator using GPS via Android
Application?
4. How the respondents assess the system in terms of :
4.1 Compatibility
4.2 Functionality
4.3 Portability
4.4 Maintainability
4.5 Reliability
4.6 Security
4.7 Usability
5. What was the result of the software evaluation?

9
General Objectives
The study aims to improve the management of the Sangandaan
Cemetery in terms of mapping the location of the tombs and providing
information of the deceased using this application for Sangandaan Cemetery.
Specific Objectives
1. To develop the proposed system using Android Studio and SQLite
for database management.

2. To integrate Global Positioning System (GPS) and Android
Application for easy navigating the tomb.

3. To test and evaluate the efficiency of the proposed system based
on ISO/IEC 25010 with the following criteria:

3.1 Compatibility
3.2 Functionality
3.3 Maintainability
3.4 Portability
3.5 Reliability
3.6 Security
3.7 Usability
Scope and Limitation
Scope
The scope of the application Tomb Locator, navigates the path through
the tomb. This application can search and show the details of the dead
person, navigate the way to the area of the tomb, has a marker shown at the
map to indicate the location. The features of the application it use a Global
Positioning System (GPS) of an smart phone, with required use of an internet

10
or data mobile connection to use the GPS, an android application that can be
accessed using smart phone and can be installed as an Android Application
Package (APK), this application can run smoothly if the user has a fast
internet connection.
The application uses Google Maps and has a feature of voice
notification to notify if the user arrived at the destination, and Google Maps
provide a satellite view, to see the street inside the cemetery and a hassle-
free navigating.
Limitation
The limitation of this application, can only locate area of the deceased,
pictures of the tomb or area not included because the application only
provides aerial view of the map. Navigating the tomb may not exactly accurate
because the Global Positioning System (GPS) rely on the signal of the
smartphone.
Significance of the study
The current standard operating procedure in mapping the tomb was
time consuming for finding the tomb. Normally, family or visitors asks the
administrator or the personnel in the cemetery where the tomb of deceased.
Family. The study provides the family future reference for own
purposes, or providing a better interpretation and systems software compare
to the existing developed software.

11
Administrator. The study provides the administrator or staff of the
cemetery to have a deeper understanding to the said mapping of the tomb. By
this study, this comes up with easier access on the tomb.

Proponents. The study gave the idea to the proponents to develop a
system that may help the said company Sangandaan Cemetery to have a
better way of data records of patients.

Future Researchers. The study can provide help for the future
researcher as a guide in the study.

Future Developers. The study provides the future developers to
have a guide in the study that may be conducted in the future.

12
Chapter II
Review of Related Literature
Conceptual Literature
Conceptual literature pertains to printed materials such as books,
professional journals, magazines, encyclopedias, newspapers and other
publications written by authorities giving opinions, experience, theories and
ideas. Conceptual literature also composed of discussions of facts and
principles that have relevance to the present study.
Foreign Literature
Foreign literature was the thesis topic other than own native literature.
This can be the literature of another literature, comparative literature or any
theme, topic, genre of a foreign literature. This can be written in ones own
native language.
ANC Explorer / Arlington National Cemetery Application
Arlington National Cemetery, a United States military cemetery in
Arlington County, Virginia, across the Potomac River from Washington, D.C.,
in whose 624 acres (253 ha) the dead of the nation's conflicts have been
buried, beginning with the American Civil War, as well as re-interred dead

13
from earlier wars. The United States Department of the Army, a component of
the United States Department of Defense, controls the cemetery.
Arlington National Cemetery's app, ANC Explorer, enables families,
visitors and the public to locate gravesites, events or other points of interest
throughout the cemetery; view front-and-back headstone photos and points of
interest; and receive directions to these locations. The latest version also
includes self-guided tours, easy access to general information, and provides

[1]
the ability to save searched burial records to a mobile device.
The Arlington Application National Cemeterys app was a similar app to
the Tom Locator via Global Positioning System (GPS) via Android Application,
the ANC application also used Global Positioning System (GPS) to determine
the location of the tomb, also the blocking included in the map, when the map
was clicked and zoomed, the blocking can appear and the information of the
tomb and the navigation would started.
Cambridge American Cemetery (C.A.C)
American armed forces used Great Britain as a base of operations
during the war, further solidifying the friendship and alliance between the two
nations. Many buried at the cemetery died during the Battle of the Atlantic
the Allied effort to secure routes and shipping lanes, and during the Strategic
Bombing Campaignthe Allied effort to destroy German infrastructure and
hinder military operations. Allied forces changed the course of world history.

14
The Cambridge American Cemetery and Memorial site in England,
30.5 acres in total, was donated by the University of Cambridge. It lies on a
slope with the west and south sides framed by woodland [2]
The Cambridge American Cemetery has a similar feature to Tomb
Locator Application; it displays the information of the tomb and the picture of
the tomb. But Cambridge American Cemetery Application do not provide
navigation and maps, unlike Tomb Locator for Sangandaan Cemetery, the
proponents provided maps to lessen the hustle for navigation.
GIS-based Muslim Cemetery Information System
The GIS-based Muslim Cemetery Information was essential in fulfilling
the user's requirement particularly in giving grave direction and death
information. The Islam-21 allowed the user to perform database query for
grave or death searching, provided user with map direction of the detailed
spatial death information.
The application that was study explains that the current manual
registration system applied by the MajlisBandaraya Shah Alam (MBSA),
Jabatan Agama Islam Selangor (JAIS), and local cemetery visitor in searching
death information and grave cemetery location are still operated manually.
[3]
This paper demonstrated the potential of GIS, GPS.
This application provides an Information System for the Cemetery, a
Geographical Information System for a cemetery, it reveals the real-time
observation and activities to the cemetery.

15
Memorial Park Cemetery Digitally Mapped to Help Relatives Locate
Grave Sites
Memorial Park Cemetery, Moline is digitally mapping the 7,600 burials
at Memorial Park Cemetery to make it easier for people to locate a grave site.
Intern Jeremy Sundberg, an Augustana College student, has been working
with Todd Green.
Moline's Geographic Information System administrator, on the
summer-long project, which, when complete later this year, can allow anyone
to type in a name and locate where the person is buried in the cemetery at
5001 34th Ave. [4]
The application explains that a digitally mapping for 7,600 buried at
Memorial Park Cemetery makes it easier for family or people to locate the
grave site. , The GIS can allow people to search, then see a map marking the
location of the grave and landmarks visible to help guide them, such as
adjacent trees or a nearby building.
Digitally Mapping Graveyards Geographical Information System
Digitally Mapping Geographical Information System (GIS) Over the
past few weeks I have been working on mapping a cemetery in a Geographic
Information System (GIS) as both part of a class and part of my own research.
We received a number of question and comments on Twitter from
readers asking how this was done and what exactly I was doing. What I want
to share today is a little background on doing spatial analyses of cemeteries,
and some projects that have already been completed using GIS. [5]

16
The above topic or study explains how GIS was used for digitally
mapping tomb, gravesites and how it can be used for the family, visitors and
others. It also gives information about the deceased, give collected
information on preservation in order to determine which areas of the cemetery
were in most need of conservation or renewal.
A Cemetery Information System and Customer Service Center for
Wilmington, Massachusetts
Wildwood Cemetery, in Wilmington, Massachusetts, has been in
operation for over 100 years. The cemetery has been storing its owner and
burial information in a Microsoft Access database since 2000, but the spatial
data was recorded exclusively on paper maps.
Searching for records, or performing updates or analysis was difficult
and time consuming. Assisting customers often required the customer to wait
for available staff and then for staff to search the records. The town needed a
system that would allow personnel to access, update, maintain, and analyze
[6]
the data in an efficient and timely manner.
This explains that the study helps and allows the users to pan and
zoom the cemetery map, and visualize, locate, query, and analyze the
cemetery data. The custom interface and tools lets the user input data and
perform queries or analyses on that input. Cemetery customers have access
to this system and can perform genealogy research, look for lots to purchase,
or view important documents, without the assistance of cemetery personnel.
The advantages of this system are that it permits the town to use its existing

17
software and data, and to perform much of the setup and maintenance in-
house. This was more efficient and economical than purchasing an outside
system. This system also has the ability to be expanded in the future as
additional data is acquired and needs are assessed.
Mapping cemeteries by UAV in Czech Republic
Mapping Cemeteries by UAV. A Czech Republic-based company uses
unmanned aerial vehicles to map the cemeteries in the country to maintain an
up-to-date database of all the graves.Traditionally, military have been using
Unmanned Aerial Vehicles (UAVs) for intelligence gathering. But now, UAVs
are being used in mapping and surveying for various other purposes. A Czech
Republic-based UAS company UPVISION in cooperation with Brno City Hall
(the second largest city Czech Republic), explored the possibilities of using a
UAV to map the cemeteries in the country. After mapping the cemeteries the
data, was integrated into a GIS system. This up-to-date database proved
extremely beneficial to the administrators in managing public cemeteries and
hundreds of associated permits.
A Czech Republic-based company uses unmanned aerial vehicles to
map the cemeteries in the country to maintain an up-to-date database of all
the graves. [7]
This study explains that company uses unmanned aerial vehicles to
map cemeteries to maintain an up-to-date database of all graves. Each
cemetery was mapped in a single flight by the UAV. For mapping smaller

18
cemeteries, Hexacopter with flight plan, image resolution 1 cm/pixel, overlaps
80/60 was used. The mapping was done in just 10 minutes.
Historical and Identification Mapping of a Cemetery
Australia's cemeteries contain a vast resource of cultural and historical
information, the importance of which was currently undervalued by most
sections of society. The resources that are present within a cemetery were
assets to be valued by the community, as they provide a direct link to
Australia's past.
This project has researched the application of geographic information
system technology to the management of data such as that contained within
the Beenleigh Cemetery. [8]
This project shows or explains what has researched the application of
geographic information system technology to the management of data such
as that contained within the Beenleigh Cemetery. This project has found that
the application of this technology to this data type was possible, and in fact
could be easily attached to the current system employed by the local authority
to manage data contained within in the cemetery.
Local Literature

19
Local literature refers to a thesis topic by own literature. This may be
the literature of another literature in here, comparative literature or any theme,
topic, genre of own literature. This cannot be written in other native language.
Locate dearly departed at the Manila North Cemetery with this website
This year, Filipinos with relatives buried in the Manila North Cemetery
may no longer have to worry about locating the tombs of dearly departed.
That is, if they have an Internet connection. Management of Metro Manila's
biggest cemetery had set up a website to help people locate the deceased
loved ones' tombs. Visitors to the website can see a map of the cemetery, and
a list of records of the deceased buried there. They can type in loved ones'
names in the search box.
The Manila North Cemetery may no longer have to worry about
locating the tombs of dearly departed. That is, if they have an Internet
connection. Management of Metro Manila's biggest cemetery had set up a
website to help people locate the deceased loved ones' tombs. Visitors to the
website can see a map of the cemetery, and a list of records of the deceased
buried there. They can type in the loved ones' names in the search box. [9]
Manila North Cemetery is the biggest in Metro Manila, with an area of
54 hectares. Filipinos with relatives buried in the Manila North Cemetery may

20
no longer have to worry about locating the tombs of the dearly departed. That
is, if they have an Internet connection.
Residential Burial Re-use in Coastal Ilocos Sur, Philippines
Residential Burial Re-Use Information System. A pervasive practice
that we see in house societies is residential burial as a means by which house
societies are able to supplant themselves into a landscape. Residential burials
are dug directly underneath stilt houses. It is argued in this paper that the very
same practice is seen in Sapilang site (CE 1200 to CE 1600, CE 1800- CE
1900), Ilocos Sur, Philippines. Residential burial re-use is a historically
established practice among the Tingguians and the ancestors (i.e. Cole 1922;
Gironire 1854).
Archaeological markers of this practice also appear in Sapilang site
(i.e. Lara 2011; E. Lim 2012; Lim and Basilia 2012) and other parts of Ilocos
[10]
like Galimuyod (Ingel 2015) and Nagsingcaoan (Canilao 2011).
The use of correlation statistical analysis to see the nature of the
relationship of the three archaeological materials with one another as well as
with site stratigraphic levels was tackled and discussed in this researched
paper.

21
Research Literature
This pertains to local and foreign studies to inquiries or investigate that
has already similarities to the current investigation. Citation from literature
was taken usually unpublished materials thesis, desertion and manuscript.
Foreign Studies
Laser Scanning and Infra-Red Thermographic Prospecting for
Diagnostic Mapping and Restoration Projects: The
Case the Painted Tombs at Cyrene (Libya)
The team of Chieti University is involved in a GIS project of the
monumental rupestrian necropolis of the Greco-Roman site of Cyrene (Libya).
In order to explain the methodologies and the technologies in use for this
project, the Painted tombs of the northern and southern necropolis are
presented in this paper, as examples of the technical protocols and of the
multidisciplinary approach converging into a multilayer GIS project.
To explain the methodologies and the technologies in use for this
project, the Painted tombs of the northern and southern necropolis are
presented in this paper, as examples of the technical protocols and of the

[11]
multidisciplinary approach converging into a multilayer GIS project.
This application provides the infrared and laser scanning diagnostic
mapping for cemetery, it provides a Geographical Information System (GIS).

22
Using Geographic Information System (GIS) In Spatial Analysis of
Mortuary.
This thesis focuses on the use of geographic information systems
(GIS) to examine mortuary practices in the Romano-Byzantine period Kellis 2
cemetery located in the Dakhleh Oasis, Egypt. The first research objective
examines the relationship between age, sex and grave substructures of 701
burials in Kellis 2 cemetery.
The aim of this research objective was to determine if the presence
and style of grave substructures were influenced by sex or age. Although not
statistically significant, GIS analysis revealed that most of the graves in the
Kellis 2 cemetery have no associated substructures, but of those that did have
associated substructures, adult male burials were more likely to have a

[12]
substructure than adult females or juveniles.
The aim of this research objective was to determine if the presence
and style of grave substructures were influenced by sex or age. Although not
statistically significant, GIS analysis revealed that most of the graves in the
Kellis 2 cemetery have no associated substructures, but of those that did have
associated substructures, adult male burials were more likely to have a
substructure than adult females or juveniles. Moreover, males and females

23
aged from 22 to 50 years were more likely to have an associated substructure
than younger and older individuals.
Geoelectrical mapping of contamination in the cemeteries: the case
study in Piracicaba, So Paulo/Brazil
This paper presents the results of electrical resistivity methods in the
area delineation that was potentially contaminated by liquefaction products,
which are also called putrefactive liquids in Vila Rezende municipal
cemetery, Piracicaba, So Paulo, Brazil. The results indicate a depth of
water table between 3.1 and 5.1 m, with two groundwater direction flows,
one to the SW and another to the SE. Due to the contamination plumes,
which have the same groundwater direction flow, as well the conductive
anomalies observed in the geoelectric sections, the contamination
suspicions in the area were confirmed. The probable plume to the SE
extends beyond the limits of the cemetery. The location of the conductive
anomalies and the probable contamination plumes showed that the
contamination is linked with the depth of the water table and the burial time.
Mapping using the geostatistical method of ordinary kriging applied to the
work drew structural characteristics of the regional phenomenon and spatial

[13]
behavior of the electrical resistivity data.
The paper presents the results of electrical resistivity methods in the
area delineation that was potentially contaminated by liquefaction products,

24
which are also called putrefactive liquids in Vila Rezende municipal
cemetery, Piracicaba, So Paulo, Brazil. The results indicate a depth of
water table between 3.1 and 5.1 m, with two groundwater direction flows,
one to the SW and another to the SE.
Local Studies
Synthesis of the Study
1st Paragraph - common characteristics of existing system and proposed
system
The proponents made some research regarding to the field of mapping
and navigating that can be helpful for the developing of the application, hence
providing information that benefits the study and importance of navigation and
mapping, the researchers conduct a study to understand the importance of
Global Positioning System, to the locations that can be forgotten easily, with
the result of the research and observation, researchers planned to use a
Google Maps provided by Google to create an interactive mapping and
navigation for the users.
2nd Paragraph - differences of characteristics of existing system and proposed
system
3rd Paragraph - unique characteristics of the proposed system

25
The proposed navigating and mapping application titled Tomb Locator
using Global Positioning System (GPS) via Android Application, through the
use of Global Positioning System and mobile internet like Wi-Fi, was to
develop an application that let the user decide and pick the desired location
the user wants, the proponents planned to develop a proposed system that let
the user interact to the using Google Maps and Global Positioning System.
Chapter III
Technical Background
This chapter views on the general methods and design used by the
proponents in conducting the research. Discussed here were the research
design, research locale and data gathering tools and instruments that the
proponents considered towards the analysis, development and evaluation of
the proposed study.
Hardware Requirements
A Hardware Requirements Specification (HRS) shows a
comprehensive description of hardware tools used for the intended purpose
and environment for the software under development. An HRS minimizes the
time and effort required by developers to achieve desired goals and also
minimizes the development cost. A good HRS defines how an application
interacts with system hardware, other programs and human users in a wide
variety of real-world situations

26
Table 3.1
Hardware Requirements
Quantity Component Description Specifications

1 piece Smart phone A smartphone or RAM: at least
smart phone is a 1GB
mobile phone
with an advanced Processor: Quad-
mobile operating Core1.5Ghz
system which CortexA53 &
combines Quad-core
features of a 2.1GHCortex-A57
personal
computer Network: 3G/4G
operating system LTE
with other
features useful WiFi: Ready
for mobile or
handheld use.
Software Requirements
A Software Requirements Specification (SRS) shows a
comprehensive description of the intended purpose and environment for

27
software under development. The SRS fully describes what the software does
and how it expected to perform.
An SRS minimizes the time and effort required by developers to
achieve desired goals and also minimizes the development cost. A good SRS
defines how an application interacts with system hardware, other programs
and human users in a wide variety of real-world situations
Table 3.2
Software Requirements
Quantity Component Description Specifications

1 piece Android The software that Android 4.4 Kit
supports a Kat
computer's basic
functions, such
as scheduling
tasks, executing
applications, and
controlling
peripherals.
1 piece Internet The Internet is

the global system Wi-Fi / Data
of interconnected Connection
computer
networks that use
the Internet
protocol suite
(TCP/IP) to link
devices
worldwide.
1 piece

28
Global The Global

Positioning Positioning
System (GPS) System (GPS) is
a space-based
navigation
system that
provides location
and time
information in all
weather
conditions,
anywhere on or
near the Earth
where there is an
unobstructed line
of sight to four or
more GPS
satellites.
Chapter IV
Research Design and Methodology
This chapter views on the general methods and design used by the
proponents in conducting the research. Discussed here were the research
design, research locale and data gathering tools and instruments that the
proponents considered towards the analysis, development and evaluation of
the proposed study.
Research Design
The proponents applied in the study, the descriptive method of
research. Descriptive method of research was a fact-finding study with
adequate and accurate interpretation of the findings. It simply describes with
emphasis what actually exists such as current conditions, practices,

29
situations, or any phenomena. It describes the status of the system. In the
method, the proponents were able to gather all the necessary findings and
present it through narrative.
The software design includes the Requirement gathering and analysis,
Software Design Specification, Design and Development of Software,
Implementation, Verification, Evaluating the Performances, and Maintenance
and Support.
Project Design

30
Figure 4.1 Project Design
Figure 4.1 illustrates the user launches the application. It shows that
the user can search people, and add a tomb. The application used a Wi-Fi
and a GPS. The function of the Wi-Fi was to access the Maps for navigation,
and the use of GPS was to locate the coordinates when adding the Tomb.
Then locating where the user and the tomb was mapped and launched. The
application shows that the user can add tomb and add image of the tomb.
Respondents of the Study

31
The respondent near from Sangandaan Cemetery where known daily
happenings and need a proper time management for quality performance of
securing and guiding the visitors to the tomb.
Sampling Technique
The capacity of the Sangandaan Cemetery to provide direction and
managing the records of the cemetery must be carefully understanding before
making a decision. Tomb records, blockings and rentals were all very crucial
in order to maintain the overall management of Sangandaan Cemetery.
Data Gathering Procedure
A letter requesting assistance and recommendation was given to the
company by asking permission to let the Sangandaan Cemetery in the course
of study in developing narrative statements were used through the survey
questionnaire.
The proponents created a question regarding the biography of the
Sangandaan Cemetery, including the opening and closing time, days open,
and blockings of the tomb.

32
Interview
A method of data gathering in which a person involved to the whole
process of the business where questions were asked by interviewer to obtain
information from the interviewee.
The data needed for this study were gathered through personal
interview, survey which uses a questionnaire and key informant interviews.
The proponents have a personal touch or direct knowledge of software
development.
Validation and Distribution of the Instruments Used
The validation and distribution of the questionnaire were based on the
respondents that involved within the system. Question in the survey forms
were based in the daily routines of the company process and the
respondents. In this case, the classification of the proponents determined. In
order to classify the respondents, the proponents determined the positions
and level of each respondent that which involve within the process of the
system, so that the distribution of survey form be accurate to the level of
knowledge of the user that involves to the process of the system.

33
Data Encoding and Formulation of the Solution
The given data which provided from gathering data forms used in the
formulation of different statistical tools and scales techniques to give a well-
presented graphical presentation and analysis in this study. The given data
calculated through the formulation techniques such as mean and other
statistical techniques.
Evaluation of Data and Result
The proponents evaluate all the data received from the respondents
and use the different statistical method. The analysis statistical formula shows
up the results and interpreted by the graphical presentation of the data.
Statistical Tools and Instruments
Statistical Tools
The statistical tools used this to help the proponents too easily tabulate
and analyze the data gathered during the survey process. It was based on
how data interpreted using the statistics. These tools can also help the
proponents to draw a valid conclusion and to continue the development of the
proposed system.

34
Frequency
A record on how often a value of a variable in a certain question
occurs. This was the number of times that the event occurs in a study. The
formula of getting the frequency shown below,
F = f/N
where,
F = the relative frequency of each class interval
f = sum of the frequency of class interval
N = the sample size
Percentage
The statistical method used to determine the percentage of the
respondents that was conducted given by this percentage formula,
P = f/N x 100
where,
P = percentage
f = frequency of each rating scale
N = number of respondents

35
Mean
The average of a population set. This found by multiplying the
population means to appropriate frequency and add the entire product then
divide the sum of all the frequency by the number of all frequencies. The
formula was:
X= fx/ N
where,
X = mean
f = number of frequency
X = rate given by the respondents
N = No. of all frequencies
Likert Scale
A scale commonly used in a survey to measure the respondents
responses through questionnaire with a set of statements or questions about
the main topic, and also to measure the positive and negative response of the
respondents to the topic.
Table of Likert Scale

36
Chi- square of Test Goodness of fit

The Chi- Square Test of Goodness of Fit (X 2) was used in determining
the number of objects or responses, which fell in different categories for a
single qualitative variable and in knowing if the sample under observation and
analysis was drawn from a population with some specified distribution or not.
Further, this was the sum of the squared differences of the observed
and expected frequencies divided by the expected frequency. The formula
employed in the said test statistic therefore was,
X2 = (O-E) 2
E
with df = c- 1 and an = 0.05
where,
X2= computed Chi-square value
O= observed frequency
E= expected frequency
df= degrees of freedom

37
c= total number of columns
= level of significance
Conceptual Framework
A conceptual framework was used in research to outline possible
courses of action or to present a preferred approach to an idea or thought. It
was a type of intermediate theory that attempts to connect to all aspects of
inquiry such as problem definition, rationale, and review of related literature,
methodology, data collection and analysis. Conceptual framework can act like
a map that gives coherence to empirical inquiry as far as the research
problem was concerned.
Manual Process

38
Conceptual Framework of Proposed System
IPO (appendices)
Figure 4.2 Conceptual Framework of
Proposed System

39
Figure 4.2 Proposed System, in this figure the Inputs are Add Tomb
and Search Tomb, Process are Input Data, Coordinates, and Image,
Launching Google Maps, the Output are Save and Navigate, navigate and
reach destination, as you can see in this figure, Figure 4.2 show the specific
details of function of the application.
Flow Chart
Figure 4.3 Flow Chart

40
Figure 4.3 displays the launching the application and searching the tomb,
after searching, launch the Google Maps and prompted to turn on the Wi-Fi
and GPS. If yes, show the coordinates and proceed to navigate into the tomb.
Adding a tomb, Input the Name, Date of Birth, Date of Death, to locate the
coordinates, turn on the Wi-Fi and GPS to collect coordinates and proceed to
add image of the tomb then save.
Figure 4.4 Data Flow Diagram

41
In this figure, the user can search about the name of the deceased
person and then it can show information of the tomb. Then when locating it by
using google maps it can request the location and give you coordinates or
marker on the map on where the user was and your real time location.
After it theres navigation which can show you the way on how to
reach the destination and a voice command can notify you during and after
arriving to it. Lastly, there was a add deceased where you can input the name
of the deceased and information.

42
Figure 4.5 Context Flow Diagram
In this figure above, the circle shaped is the system, there are two(2)
entities included at the diagram. First is the Developer
and second is the User, the role of the developer is to
send updates to the application, while the role of the
user is to add a tomb, navigate and locate using the
application. The functionality of the process or the
system is to handle reliability to the user and developer by providing its uses.

43
Figure 4.6 Network Diagram
In the figure above, it shows how the network diagram flows between
the user, GPS, internet and GSM provider. The user turns on the GPS to
access the Google Maps, Google Maps is viewable only if the user has an
Internet, so the user turns on the internet, Tomb Locator can also be used by
a 3G Data Cellular Connection so there is a GSM Provider included at the
network diagram. GSM Provider provides cellular connection if the user has a
sufficient load in the users sim card.

44
Storyboard Android Application
WELCOME SCREEN
This screen can show when the
app is launch by the user.
SEARCH SCREEN
When the search button is tapped or
clicked, you can input the name of the
person you want or the date of birth of
date of death, if you dont know the name
of the deceased.

45
HOME SCREEN
HOME SCREEN is the default window,
where the user can see the list of people that
are inputted on the application.
Search button can be tap to search the

list of the deceased.
RESULT SCREEN
After searching, the result screen can show.

Revealing the image and the information of
the deceased. A Note is included for
references, like which Block the Tomb is
located, or messages engraved at the
Tomb.

46
Adding a Grave/Family Member
If you have a member of the family that is buried at Sangandaan

Cemetery, you can add the tomb of your family member that was gone.
All fields of information are required to add a family member.
Name:
Birth Date: DD/MM/YY
Death Date: DD/MM/YY
Location In your smartphone, turn ON the GPS first to set the
location inside the cemetery. Then click the EDIT button to
start.
Photo: Input the Photo of your family member, or the Tomb
picture.
Then click save button at the upper right side.

47
A B C
When at the RESULT SCEREN, there is a Red Grave Button, tap it

then the window B can appear, the marker can show. Tap the marker and you
can see the label of the marker. Tap the navigation button and the
direction can show, as reaching the marker. The application can provide a
navigation and minutes of arrival at destination.

48
System Development Standard
Figure 4.8
The fundamental objective of the ISO/IEC 9126 standard is to address
some of the well-known human biases that can adversely affect the delivery
and perception of a software development project. These biases include
changing priorities after the start of a project or not having any clear
definitions of "success". By clarifying, then agreeing on the project priorities
and subsequently converting abstract priorities (compliance) to measurable
values ISO/IEC 9126 tries to develop a common understanding of the
project's objectives and goals.

49
The ISO 9126-1 software quality model identifies 6 main quality
characteristics, namely:
Functionality
Reliability
Usability
Efficiency
Maintainability
Portability
Functionality
Functionality was the essential purpose of any product or service. For
certain items this is relatively easy to define, for example a ship's anchor has
the function of holding a ship at a given location. The more functions a
product has, e.g. an ATM machine, then the more complicated it becomes to
define its functionality. For software a list of functions can be specified, i.e. a
sales order processing systems should be able to record customer
information so that it can be used to reference a sales order.
Reliability
Once a software system is functioning, as specified, and delivered the
reliability characteristic defines the capability of the system to maintain its
service provision under defined conditions for defined periods of time.
Usability

50
Usability only exists with regard to functionality and refers to the ease
of use for a given function. For example, a function of an ATM machine is to
dispense cash as requested. Placing common amounts on the screen for
selection, i.e. $20.00, $40.00, $100.00 etc., does not impact the function of
the ATM but addresses the Usability of the function. The ability to learn how to
use a system (learnability) is also a major sub characteristic of usability.
Efficiency
This characteristic is concerned with the system resources used when
providing the required functionality. The amount of disk space, memory,
network etc. provides a good indication of this characteristic. As with a
number of these characteristics, there are overlaps. For example, the usability
of a system is influenced by the system's Performance, in that if a system
takes 3 hours to respond the system would not be easy to use although the
essential issue is a performance or efficiency characteristic.
Maintainability
The ability to identify and fix a fault within a software component is what the
maintainability characteristic addresses. In other software quality models this
characteristic is referenced as supportability. Maintainability is impacted by
code readability or complexity as well as modularization. Anything that helps
with identifying the cause of a fault and then fixing the fault is the concern of
maintainability. Also the ability to verify (or test) a system, i.e. testability, is one
of the sub characteristics of maintainability.

51
Portability
This characteristic refers to how well the software can adopt to changes in its
environment or with its requirements. The sub characteristics of this
characteristic include adaptability. Object oriented design and implementation
practices can contribute to the extent to which this characteristic is present in
a given system.
ISO 9126 Observations
Using the ISO 9126 (or any other quality model) for derivation of
system requirements brings clarity of definition of purpose and operating
capability.
For example, a rules engine approach to compliance would enable greater
adaptability, should the compliance rules change. The functionality for
compliance could be implemented in other ways but these other
implementation methods may not produce as strong an adaptability
characteristic as a rule, or some other component based, architecture.
IPO Chart (add to IPO)

52
Input Process Output
Smartphone, Input Data, Save and navigate

Pocket Wi-Fi Coordinates and navigate and reach
Global Images destination
Positioning
System
Figure 4.8 IPO Chart of Project
In the figure above the input, process, output of the proponent project show
that how the project process conducted.

53
Figure 4.9 Mobile Application Development Life Cycle
The figure above focuses on the development of Mobile Application
Life Cycle; it covers the phases of building a Mobile Application or an Android
Application.

54
The Discovery Phase
Before getting to design the app to rule over them all, mobile
application developers have to do a lot of research and brainstorming. Take
your time and think of unique ideas. Compile the ideas and settle on those
that seem promising and feasible. Come up with the concept of the app and
finalize it. Once the developers settle on the final concept, it is then that the
main development project work starts.
Requirements of the app are then taken into account with all its intended
functions getting documented. As with every development process, there are
limitations. Not all app functionality can make it to the final product.
At the end of the discovery phase the Who, Why, What, When and Where
should be scrutinized and sent as part of the problem statement before
finalizing the app project.
The Design Phase
The type of application you want to develop. You ve gathered all the
nuts and bolts to proceed. Now its time for the software development to start.
Assemble your dream team which knows the requirements of the project in
and out. Come up with a work flow chart and design for the project to
demarcate certain responsibilities.

55
The Development and Testing Phase
Following the success of the design phase, its time for the software
development team to initiate work on the project. This process is iterative and
cyclical. Development goes side by side with testing so that any errors or
bugs in the program are caught at the earliest and rectified right away. This is
true for mobile application development. It is time to also do regular reviews to
check the progress of the project goes smoothly and according to time.
Once the application is completed, it has to undergo further testing so that all
application components are found to work in unison and harmony.
The Deployment Phase
Your app is ready to be unleashed to the world after rigorous a
development and testing period. This is the point for the advertising and
marketing team to step in and help popularize the app to stratospheric
heights. A good marketing campaign is integral to a successful app launch.
Angry Birds couldnt be the juggernaut it is if it was not marketed properly. So
make sure never to underestimate the power of marketing.
Maintenance and Updates Phase

56
After your app is in the hands of users, provide necessary maintenance
and updates. Failure to do so can make the app retention rate drop by the
dozen. This phase is also known as post development phase.
Chapter V
Results and Discussion
This chapter presents the data gathered through the research
instrument. These data are analyzed and statistically treated in order to derive
interpretations and inferences. The data are presented in accordance with the
statement of the specific problem.
1. Demographic Profile of the Respondents
1.1 Gender
Table 5.1
Demographic Profile of the Respondents in terms of Gender
Gender Frequency Percentage Rank

(f) (%)
Male 10 50%
Female 10 50%
Total No. of Respondents (N) 20 100%

57
As shown in the table, out of 20 respondents, the frequency of male is
10 which was equivalent to 50%, while the female frequency was 10, which
was equivalent to 50%.
1.2 Civil Status
Table 5.2
Demographic Profile of the Respondents in terms of Civil Status
Civil Status Frequency Percentage Rank

(f) (%)
Single 8 40% 1st
Married 8 40% 1st
Seperated 0 0%
Widowed 4 20% 2nd
As depicted from the table, out of 20 respondents, the frequency of
Single was 8 which was equivalent to 40% and was in rank 1, the frequency
of married was 8 which was equivalent to 40% and was also in rank 1, while
the frequency of widowed is 4 which was equivalent to 20% and was in rank
2nd.

58
1.3 Age Bracket
Table 5.3
Demographic Profile of the Respondents in terms of Age Bracket
Age Bracket Frequency Percentage Rank

(f) (%)
18 25 8 40% 1st
26 33 2 10% 4th
34 41 5 25% 2nd
42-49 1 5% 5th
50 above 4 20% 3rd
As gleaned from the table, out of 20 respondents, age 18-25 frequency
was 8 and was equivalent to 40% and was at 1st rank, age 26-33 frequency
was 2 which was equivalent to 10% and rank 4th, age 34-41 frequency was 5
which was equivalent to 25% and rank 2nd, age 42-49 frequency was only 1
and the equivalent was 5% that get the rank 5th which is the least, age 50
above frequency was 4 which was equivalent to 20% and ranking 3rd.

59
1.4 Highest Educational Attainment
Table 5.4
Demographic Profile of the Respondents in terms of Highest
Educational Attainment
Age Bracket Frequency Percentage Rank

(f) (%)
High School 7 35% 2nd
College 10 50% 1st
Vocational 2 10% 3rd
Masteral 0 0%
Doctorate 1 5% 4th
The conclusion from the above table, the High School frequency is 7
which was equivalent to 35% and gets the rank 2nd, the College frequency is
10 which was equivalent to 50% and rank 1st, the vocational frequency was 2
which was equivalent to 10% and ranks 3rd, lastly the Doctorate frequency
was 1 and equivalent to 5% and get the last rank which is 4th.

60
2. Testing and Evaluation of the System
2.1 In terms of Compatibility
Table 5.5
Software Evaluation for the Proposed System in terms of Compatibility
Compatibility Freque Percenta Rank Mean Chi-

ncy ge Square
(f) (%)
Excellent 10 50% 1st
Very Good 4 20% 3rd
Good 6 30% 2nd

4.2
Satisfactory
Poor
Total No. of 20 100%

Respondents (N)
As observed in the table, out of 20 respondents, 50% of the
respondents rated Excellent which is in rank 1, 30% of the respondents
rated Good which is in rank 2, while 20% rated Very Good which is in rank
3. The computed mean was 4.2 and the verbal interpretation in the systems
functionality classified as Very Good.

61
2.2 In terms of Functionality
Table 5.6
Software Evaluation for the Proposed System in terms of Functionality
Functionality Freque Percenta Rank Mean Chi-

ncy ge Square
(f) (%)
Very Good 5 20% 2nd
Good 4 20% 3rd

4.3
Satisfactory
Poor

Respondents (N)
As observed in the table, out of 20 respondents, 55% of the
rated Very Good which is in rank 2, while 20% rated Very Good which is in
rank 3. The computed mean was 4.3 and the verbal interpretation in the
systems functionality classified as Very Good.

62
2.3 In terms of Maintainability
Table 5.7
Software Evaluation for the Proposed System in terms of Maintainability
Maintainability Freque Percenta Rank Mean Chi-

ncy ge Square
(f) (%)
Very Good 3 15% 3rd
Good 5 25% 2nd

4.3
Satisfactory
Poor

Respondents (N)
As stated in the table, out of 20 respondents, 60% of the respondents
rated Excellent which is in rank 1, 25% of the respondents rated Good
which is in rank 2, while 15% rated Very Good which is in rank 3. The
computed mean was 4.3 and the verbal interpretation in the systems

63
2.4 In terms of Portability
Table 5.8
Software Evaluation for the Proposed System in terms of Portability
Portability Freque Percenta Rank Mean Chi-

ncy ge Square
(f) (%)
Excellent 9 45% 1st
Very Good 7 35% 2nd
Good 4 20% 3rd

4.2
Satisfactory
Fair

Respondents (N)
As described in the table, out of 20 respondents, 45% of the
rated Very Good which is in rank 2, while 20% rated Good which is in rank

64
2.5 In terms of Reliability
Table 5.9
Software Evaluation for the Proposed System in terms of Reliability
Reliability Frequency Percentage Rank Mean Chi-

(f) (%) Square
Excellent 9 45% 1st
Very Good 8 40% 2nd
Good 3 15% 3rd

4.3
Satisfactory
Fair

Respondents (N)
As depicted in the table, out of 20 respondents, 45% of the
rated Very Good which is in rank 2, while 15% rated Good which is in rank

65
2.6 In terms of Security
Table 5.10
Software Evaluation for the Proposed System in terms of Security
Security Freque Percenta Rank Mean Chi-

ncy ge Square
(f) (%)
Very Good 5 25% 2nd
Good
4.7
Satisfactory
Poor

Respondents (N)
As seen in the table above, the respondents rated the evaluation in
terms of security 100% for the Excellent which is in rank 1. The computed
mean was 5 and the verbal interpretation in the systems functionality
classified as Excellent. The computed mean was 4.7 and the verbal
interpretation in the systems functionality classified as Very Good.

66
3. Summary of the Respondents Evaluation Criteria
Table 5.11
Summary Rate of Proposed System in terms of Criteria
Criteria Mean Verbal Rank

Interpretation
Compatibility 4.2 Very Good 3rd
Functionality 4.3 Very Good 2nd
Maintainability 4.3 Very Good 2nd
Portability 4.2 Very Good 3rd
Reliability 4.3 Very Good 2nd
Security 4.7 Very Good 1st
Average Mean 4.3 Very Good
As seen in the table above, the computed mean on the compatibility
was 4.2 which was equivalent to Very good and rank 3 rd, the functionality
mean was 4.3 which was equivalent to 4.3 and rank 2 nd, the maintainability
mean was 4.3, resulting to very good verbal interpretation and ranking 2 nd,
portability was 4.2 and rank 3rd, reliability was 4.3 and verbal interpretation
was very good and ranking 2nd, the 1st ranking is the Security which was
equivalent to very good and the Average Mean was 4.3 and equivalent to very
good.

67
System Results Analysis
Chapter VI
Summary, Conclusion and Recommendation
This chapter presents the summary or the research work undertaken,
the conclusions drawn and the recommendations made as an outgrowth of
the study. This study was to help the user locate easily the tomb of the
beloved ones using this application Tomb Locator using Global Positioning
System (GPS) via Android Application.
Summary of Findings
The main purpose of our study was to locate the tomb easily especially
see details of the deceased like full name, date of birth, date of death, and
also picture of the tomb. Then after clicking it, user can see the navigation and
direction were to go easily and quickly to the tomb. After that a voice
notification can notify you that you have arrived.
We surveyed 20 different people about our application they gave
grades, comments, suggestions and we told them that we studied our
application for about months. As part of our study we group mates researched
a cemetery where can we have an application that can help people from the
problems and made solution for it. We interviewed people, administrator or
managements of cemetery, gave them some letters requesting that we
students can made a legitimate study research for this topic. User or
respondents used the application to locate the tomb.

68
1. How do the user evaluate the application in terms of:
1.1 Compatibility
The respondents average weighted mean was 4.2 and the verbal
interpretation in the systems functionality classified. The computed mean was
4.7 and the verbal interpretation in the systems functionality classified as
Very Good.d as Very Good.
1.2 Functionality
1.3 Maintainability
1.4 Portability
1.5 Reliability

69
1.6 Security
Conclusion
This section contains conclusions based on the findings from the study.
Conclusions were organized by research question and supported by
quantitative data.
Based on the findings the following conclusions were drawn:
The survey results in combination with the results from respondent
interviews indicate that families or friends are currently using the mobile
devices to perform a variety of locating, navigating, the tomb on how to get
there. Some used to remember blockades, but were also using devices as
tools to locate it. Results from the survey indicate that family believes that
locating tomb should be able to use mobile devices in the cemetery and that
kind of use would be beneficial for the user. Most people also reported that
they believed that they would be able to incorporate mobile mapping.
Although people believed that mobile devices could impact mapping,
navigating and security of information or details about the deceased and
tombs, management of cemetery indicated that they only thought that the use
of mobile devices could have an impact outside the cemetery with regard to

70
participation of mapping and viewing it real time via aerial view, with respect to
these questions. A family in Binukawan Bagac Bataan was surveyed and
responses were significantly higher than faculty responses, even when both
responses were positive.
In terms of Functionality, majority of the respondents perceived that the
proposed system provides sufficient guidelines on how to use the application.
In terms of Usability, majority of the respondents perceived that the proposed
system operates in the convenience of the user. In terms of Maintainability,
majority of the respondents convinced that the proposed system was capable
in updating and monitoring technical stumble. In terms of Reliability, majority
of the respondents were satisfied with the system by providing the right
tutorial for the user. In terms of Efficiency, majority of the respondents
perceived that the proposed system is capable of delivering a quality tutorial
to the user. (compatibility, security)
The proposed system has satisfied all the criteria set forth. Therefore,
the proposal was found to be functional, maintainable, reliable, usable and
efficient with an overall mean of 4.3 for the proposed system concludes a
verbal interpretation of Very Good.
All queries answered , based on the Problem and Objectives

71
Recommendation
Based on the results of the conclusions gathered, the proponents
would like to recommend the following.
1. Proponents recommend the implementation of the proposed system
for effective and quick way of gathering data or information at locating
the easiest or quickest way to go to tomb.
2. The proponents recommend the proposed system as future
references of future proponents.
3. Proponents recommend the proposed system can be used for safety
monitoring of information and security.
4. Proponents suggest that the proposed system can have a basis for
providing an enhancement to the data or information gathered during
the study.

72
Bibliography
[1] U.S. Army Arlington National Cemetery Arlington, VA 22211 877-907-

8585 2010
[2] Cambridge American Cemetery Coton CB23 7PHCambridgeUnited

Kingdom tel +44 (0)1954 210 350 2011
[3] 3600 Hennepin Ave. S. Minneapolis, MN 55408 | (612) 822-2171 | A

Nonprofit Association Governed by a Board of Trustees. 2010
[1] Kerem Ok, Vedat Coskun, Busra Ozdenizci (2011), Theory to Practice,
John Wiley & Son Ltd.: Atrium, Southern Gate, chicsussex, P019
8SQ, United Kingdom. (PATTERN FOR BIBLIOGRAPHY)
[9] SPHM2S: Smart Patient m-Healthcare Monitoring System with NFC

http://www.ijcat.com/archives/volume4/issue12/ijcatr04121015.pdf
September 28, 2016 Accessed time:10:04 pm
(ACCESED DATE. AND TIME)
[4] April 2013with49 Reads DOI: 10.1109/BEIAC.2013.656014 Conference:
Business Engineering and Industrial Applications Colloquium (BEIAC), 2013
IEEE
[5] Dawn Neuses, dneuses@qconline.com Jul 16, 2014
[6] March 21, 2013 by Kathryn Meyers Emery in Cemeteries, Digital
Archaeology, Methods.

73
[7] Carlson, S. E. (2006). A Cemetery Information System and Customer
Service Center for Wilmington, Massachusetts (Master's thesis, University of
Redlands)
[8] Jakub Karas - March 10, 2014
[9] Millen, Benjamin Wilkes, University of Southern Queensland.

Faculty of Engineering and Surveying, 2010
[10] Joel Locsin/VC, GMA News, October 28, 2014 6:59pm
[11] Michael Armand P. CanilaoJanuary 02, 2014

74
User Manual

75
Screen 1
This picture can show once you click or open the
application about Tomb Locator.
Screen 2
This screen was all about the details of deceased
people who were buried in Sangandaan Cemetery.
Tap the search button so you can search the name
of deceased

76
Screen 3
Now in this screen, the example search is
office, so the office result can appear.
Screen 4
Now the search has

appeared, click the Office of
the Cemetery it can show
an image, and the Note.

77
In the next screen, we can show you the result of an actual person and
its location, also how to navigate.
Screen 5
This screen, you can see the deceased

person named Felomena C. Callanta,
Here is the date of birth and date of death.
As you can see here, the Blocking information

is included at the Note.

78
This button with a cross shaped is the Navigation button, as you tap it, it can
proceed to the next screen, which is the Google Maps.
In this application, the navigation we used is the Google Maps.
Screen 6
This screen provides the marker of the

specific person.
The pin marker, includes the

coordinates (lat,lng)

79
Screen 7
This icon is the (GPS) Global

Positioning System, it shows where
you are in the Map. As you move, it
also moves depending on your
coordinates.
As you see the navigation

path is the blue colored dots, when
navigation is pressed, it can show you
the way how to get to the Pin.
This is the navigation button.

80
Adding a Tomb
Image: Add image

of the tomb
Name: input the name of the deceased.
Birth date: DD/MM/YY
Death Date: DD/MM/YY
Note: Insert the information of the

blockings and cause of death.
Tap Edit:
The user can tap the Edit and get the

coordinates of the user; this can be the
location of the specific tomb being added.

81
Appendix A
Approval Letter

82
Appendix B
Evaluation Tools

83
Tomb Locator using Global Positioning System (GPS) via

Android Application
Name (Optional): Date:
Instruction: this questionnaire consists of two parts. Please read carefully
And the direction called for
Part 1. Personal/Professional Qualifications (Please mark the box Provide

with an x
1. Age 2. GGender
18-25 Male
23-33 Female
34-41
42-49
50 above

84
3. DDesignation 4. HHighest Educational
Attainment
Police
Teacher Elementary
Student
Staff High School
Others
College
Masteral
Part II Software design evaluation to determine the environment of of the
system in terms of criteria under ISO/EC25010, please rate the following
Based on the result as truthfully and objectively as possible and place an
X in the Box that represent your opinion
Legend (for A-D): 5 is the Highest and 1 was the lowest

Verbal interpretation Rating
CRITERIA 1 2 3 4 5
Excellent 5
Compatibility (This term refers to availability
Very good 4
of the System Locate records easily)
Good 3
- How would you rate the accessibility of?
Satisfactory 2
proposed system Fair

in searching and retrieving 1
the information?
Functionality (The user-friendliness of the system s
graphical user interface (GUI)).
- Is the system design suitable for all?
Maintainability (This term refers to the availability of

85
the proposed system to provide sustainability)
- How would you rate the maintainability of the
proposed system in the updating/modifying?
stored data?
Security (This term refers to the availability of the
proposed system to provide protection for the user)
- How would you rate the security of the proposed
system in the accessing data?
Portability (This term refers to the availability of the
proposed system to provide sustainability)
- How would you rate the portability of the
proposed system?
Comments/Suggestions:
Your participation is highly appreciated. Thank You!

86

87
Appendix C
Screenshots

88
Appendix D
Market Analysis
TOMB LOCATOR USING GLOBAL POSITIONING SYSTEM (GPS)

89
VIA ANDROID APPLICATION
Hardware Requirement
Quantity Brand/ Item Unit Price Total Cost Price

(pcs)
1 Samsung Galaxy Php 5,999 Php 5,999

J2 Prime
1
Globe 4G Mobile 1,300 1,300

Wi-Fi
TOTAL Php 7,299
Software Requirement
Quantity Brand/ Item Unit Price Total Cost Price

(pcs)
1 Android 4.3 Free Free

TOTAL Free
Factor to Consider:
1. Android Operating System a free firmware when buying a

Smartphone device.
Maintenance Cost:
Maintenance Cost = Total Amount * 0.20
= 35,565 * 0.20

90
Maintenance Cost= Php7, 113.00
Development Cost:
Profit = Total Amount * 0.50 - Maintenance cost
= 35, 565 * 0.50 - Maintenance cost
Profit = Php10, 669.50 - Php 7,113.00
Development Cost = 35,565 + 10, 669.50
Development Cost = Php46, 234.50

91
Appendix E
Environmental Analysis

92
Environmental Analysis
The things to consider that benefits each of these technologies can
provide independently. With the use of this technology, this lessens the hustle
of locating the exact location of the tomb. With the use of smartphone, the
user can install the application and start to use it in the desired cemetery, a
pocket Wi-Fi is required to locate the location of the tomb, it provides an
internet connection access and Global Positioning System access to locate
and navigate to the tomb.
Components Toxic Non-toxic
Samsung Galaxy J2 X
Prime
Globe 4G Pocket Wi-Fi X
Appendix F
93
Legal Implications
Legal Implications
The implications of extended and intensive use of near field
communications (NFC) were far reaching for new business applications, for
the delivery of public services such as transport, and for public policy. This
technology trans-formative for a large number of applications and has
stimulated innumerable innovative forms, but so far there has been insufficient
insight expressed in discussions about its impact and risks.
[REPUBLIC ACT NO. 10173]

94
AN ACT PROTECTING INDIVIDUAL PERSONAL INFORMATION IN

INFORMATION AND COMMUNICATIONS SYSTEMS IN THE
GOVERNMENT AND THE PRIVATE SECTOR, CREATING FOR THIS
PURPOSE A NATIONAL PRIVACY COMMISSION, AND FOR OTHER
PURPOSES
Be it enacted, by the Senate and House of Representatives of the Philippines

in Congress assembled:
CHAPTER I
GENERAL PROVISIONS
SECTION 1. Short Title. This Act shall be known as the Data Privacy Act of
2012.
Law on implementing the system based on Tomb Locator
SEC. 2. Declaration of Policy. It is the policy of the State to protect the
fundamental human right of privacy, of communication while ensuring free
flow of information to promote innovation and growth. The State recognizes
the vital role of information and communications technology in nation-building
and its inherent obligation to ensure that personal information in information
and communications systems in the government and in the private sector are
secured and protected.
SEC. 3. Definition of Terms. Whenever used in this Act, the following terms
shall have the respective meanings hereafter set forth:
(a) Commission shall refer to the National Privacy Commission created by
virtue of this Act.

95
(b) Consent of the data subject refers to any freely given, specific, informed
indication of whereby the data subject agrees to the collection and processing
of personal information about and/or relating to him or her. Consent shall be
evidenced by written, electronic or recorded means. It may also be given on
behalf of the data subject by an agent specifically authorized by the data
subject to do so.
(c) Data subject refers to an individual whose personal information is
processed.
(d) Direct marketing refers to communication by whatever means of any
advertising or marketing material which is directed to particular individuals.
(e) Filing system refers to any act of information relating to natural or juridical
persons to the extent that, although the information is not processed by
equipment operating automatically in response to instructions given for that
purpose, the set is structured, either by reference to individuals or by
reference to criteria relating to individuals, in such a way that specific
information relating to a particular person is readily accessible.
(f) Information and Communications System refers to a system for generating,
sending, receiving, storing or otherwise processing electronic data messages
or electronic documents and includes the computer system or other similar
device by or which data is recorded, transmitted or stored and any procedure

96
related to the recording, transmission or storage of electronic data, electronic
message, or electronic document.
(g) Personal information refers to any information whether recorded in a
material form or not, from which the identity of an individual is apparent or can
be reasonably and directly ascertained by the entity holding the information,
or when put together with other information would directly and certainly
identify an individual.
(h) Personal information controller refers to a person or organization who
controls the collection, holding, processing or use of personal information,
including a person or organization who instructs another person or
organization to collect, hold, process, use, transfer or disclose personal
information on his or her behalf. The term excludes:
(1) A person or organization who performs such functions as instructed by
another person or organization; and
(2) An individual who collects, holds, processes or uses personal information
in connection with the individuals personal, family or household affairs.
(i) Personal information processor refers to any natural or juridical person
qualified to act as such under this Act to whom a personal information
controller may outsource the processing of personal data pertaining to a data
subject.

97
(j) Processing refers to any operation or any set of operations performed upon
personal information including, but not limited to, the collection, recording,
organization, storage, updating or modification, retrieval, consultation, use,
consolidation, blocking, erasure or destruction of data.
(k) Privileged information refers to any and all forms of data which under the
Rules of Court and other pertinent laws constitute privileged communication.
(l) Sensitive personal information refers to personal information:
(1) About an individuals race, ethnic origin, marital status, age, color, and
religious, philosophical or political affiliations;
(2) About an individuals health, education, genetic or sexual life of a person,
or to any proceeding for any offense committed or alleged to have been
committed by such person, the disposal of such proceedings, or the sentence
of any court in such proceedings;
(3) Issued by government agencies peculiar to an individual which includes,
but not limited to, social security numbers, previous or cm-rent health records,
licenses or its denials, suspension or revocation, and tax returns; and
(4) Specifically established by an executive order or an act of Congress to be
kept classified.
SEC. 4. Scope. This Act applies to the processing of all types of personal
information and to any natural and juridical person involved in personal

98
information processing including those personal information controllers and
processors who, although not found or established in the Philippines, use
equipment that are located in the Philippines, or those who maintain an office,
branch or agency in the Philippines subject to the immediately succeeding
paragraph: Provided, That the requirements of Section 5 are complied with.
This Act does not apply to the following:
(a) Information about any individual who is or was an officer or employee of a
government institution that relates to the position or functions of the individual,
including:
(1) The fact that the individual is or was an officer or employee of the
government institution;
(2) The title, business address and office telephone number of the individual;
(3) The classification, salary range and responsibilities of the position held by
the individual; and
(4) The name of the individual on a document prepared by the individual in the
course of employment with the government;
(b) Information about an individual who is or was performing service under
contract for a government institution that relates to the services performed,
including the terms of the contract, and the name of the individual given in the
course of the performance of those services;

99
(c) Information relating to any discretionary benefit of a financial nature such
as the granting of a license or permit given by the government to an
individual, including the name of the individual and the exact nature of the
benefit;
(d) Personal information processed for journalistic, artistic, literary or research
purposes;
(e) Information necessary in order to carry out the functions of public authority
which includes the processing of personal data for the performance by the
independent, central monetary authority and law enforcement and regulatory
agencies of the constitutionally and statutorily mandated functions. Nothing in
this Act shall be construed as to have amended or repealed Republic Act
No. 1405, otherwise known as the Secrecy of Bank Deposits Act; Republic Act
No. 6426, otherwise known as the Foreign Currency Deposit Act; and
Republic Act No. 9510, otherwise known as the Credit Information System Act
(CISA);
(f) Information necessary for banks and other financial institutions under the
jurisdiction of the independent, central monetary authority or Bangko Central
ng Pilipinas to comply with Republic Act No. 9510, and Republic Act No. 9160,
as amended, otherwise known as the Anti-Money Laundering Act and other
applicable laws; and

100
(g) Personal information originally collected from residents of foreign
jurisdictions in accordance with the laws of those foreign jurisdictions,
including any applicable data privacy laws, which is being processed in the
Philippines.
SEC. 5. Protection Afforded to Journalists and The Sources. Nothing in this
Act shall be construed as to have amended or repealed the provisions of
Republic Act No. 53, which affords the publishers, editors or duly accredited
reporters of any newspaper, magazine or periodical of general circulation
protection from being compelled to reveal the source of any news report or
information appearing in said publication which was related in any confidence
to such publisher, editor, or reporter.
SEC. 6. Extraterritorial Application. This Act applies to an act done or
practice engaged in and outside of the Philippines by an entity if:
(a) The act, practice or processing relates to personal information about a
Philippine citizen or a resident;
(b) The entity has a link with the Philippines, and the entity is processing
personal information in the Philippines or even if the processing is outside the
Philippines as long as it is about Philippine citizens or residents such as, but
not limited to, the following:
(1) A contract is entered in the Philippines;

101
(2) A juridical entity unincorporated in the Philippines but has central
management and control in the country; and
(3) An entity that has a branch, agency, office or subsidiary in the Philippines
and the parent or affiliate of the Philippine entity has access to personal
information; and
(c) The entity has other links in the Philippines such as, but not limited to:
(1) The entity carries on business in the Philippines; and
(2) The personal information was collected or held by an entity in the
Philippines.
CHAPTER II
THE NATIONAL PRIVACY COMMISSION
SEC. 7. Functions of the National Privacy Commission. To administer and
implement the provisions of this Act, and to monitor and ensure compliance of
the country with international standards set for data protection, there is hereby
created an independent body to be known as the National Privacy
Commission, winch shall have the following functions:

102
(a) Ensure compliance of personal information controllers with the provisions
of this Act;
(b) Receive complaints, institute investigations, facilitate or enable settlement
of complaints through the use of alternative dispute resolution processes,
adjudicate, award indemnity on matters affecting any personal information,
prepare reports on disposition of complaints and resolution of any
investigation it initiates, and, in cases it deems appropriate, publicize any such
report: Provided, That in resolving any complaint or investigation (except
where amicable settlement is reached by the parties), the Commission shall
act as a collegial body. For this purpose, the Commission may be given
access to personal information that is subject of any complaint and to collect
the information necessary to perform its functions under this Act;
(c) Issue cease and desist orders, impose a temporary or permanent ban on
the processing of personal information, upon finding that the processing be
detrimental to national security and public interest;
(d) Compel or petition any entity, government agency or instrumentality to
abide by its orders or take action on a matter affecting data privacy;
(e) Monitor the compliance of other government agencies or instrumentalities
on the security and technical measures and recommend the necessary action
in order to meet minimum standards for protection of personal information
pursuant to this Act;

103
(f) Coordinate with other government agencies and the private sector on
efforts to formulate and implement plans and policies to strengthen the
protection of personal information in the country;
(g) Publish on a regular basis a guide to all laws relating to data protection;
(h) Publish a compilation of agency system of records and notices, including
index and other finding aids;
(i) Recommend to the Department of Justice (DOJ) the prosecution and
imposition of penalties specified in Sections 25 to 29 of this Act;
(j) Review, approve, reject or require modification of privacy codes voluntarily
adhered to by personal information controllers: Provided, That the privacy
codes shall adhere to the underlying data privacy principles embodied in this
Act: Provided, further, that such privacy codes may include private dispute
resolution mechanisms for complaints against any participating personal
information controller. For this purpose, the Commission shall consult with
relevant regulatory agencies in the formulation and administration of privacy
codes applying the standards set out in this Act, with respect to the persons,
entities, business activities and business sectors that said regulatory bodies
are authorized to principally regulate pursuant to the law: Provided,
finally. That the Commission may review such privacy codes and require
changes thereto for purposes of complying with this Act;

104
(k) Provide assistance on matters relating to privacy or data protection at the
request of a national or local agency, a private entity or any person;
(l) Comment on the implication on data privacy of proposed national or local
statutes, regulations or procedures, issue advisory opinions and interpret the
provisions of this Act and other data privacy laws;
(m) Propose legislation, amendments or modifications to Philippine laws on
privacy or data protection as may be necessary;
(n) Ensure proper and effective coordination with data privacy regulators in
other countries and private accountability agents, participate in international
and regional initiatives for data privacy protection;
(o) Negotiate and contract with other data privacy authorities of other
countries for cross-border application and implementation of respective
privacy laws;
(p) Assist Philippine companies doing business abroad to respond to foreign
privacy or data protection laws and regulations; and
(q) Generally perform such acts as may be necessary to facilitate cross-
border enforcement of data privacy protection.
SEC. 8. Confidentiality. The Commission shall ensure at all times the
confidentiality of any personal information that comes to its knowledge and
possession.

105
SEC. 9. Organizational Structure of the Commission. The Commission shall
be attached to the Department of Information and Communications
Technology (DICT) and shall be headed by a Privacy Commissioner, who
shall also act as Chairman of the Commission. The Privacy Commissioner
shall be assisted by two (2) Deputy Privacy Commissioners, one to be
responsible for Data Processing Systems and one to be responsible for
Policies and Planning. The Privacy Commissioner and the two (2) Deputy
Privacy Commissioners shall be appointed by the President of the Philippines
for a term of three (3) years, and may be reappointed for another term of three
(3) years. Vacancies in the Commission shall be filled in the same manner in
which the original appointment was made.
The Privacy Commissioner must be at least thirty-five (35) years of age and of
good moral character, unquestionable integrity and known probity, and a
recognized expert in the field of information technology and data privacy. The
Privacy Commissioner shall enjoy the benefits, privileges and emoluments
equivalent to the rank of Secretary.
The Deputy Privacy Commissioners must be recognized experts in the field of
information and communications technology and data privacy. This shall enjoy
the benefits, privileges and emoluments equivalent to the rank of
Undersecretary.
The Privacy Commissioner, the Deputy Commissioners, or any person acting
on the behalf or under the direction, shall not be civilly liable for acts done in

106
good faith in the performance of the duties. However, he or she shall be liable
for canful or negligent acts done by him or her which are contrary to law,
morals, public policy and good customs even if he or she acted under orders
or instructions of superiors: Provided, that in case a lawsuit is filed against
such official on the subject of the performance of his or her duties, where such
performance is lawful, he or she shall be reimbursed by the Commission for
reasonable costs of litigation.
SEC. 10. The Secretariat. The Commission is hereby authorized to
establish a Secretariat. Majority of the members of the Secretariat must have
served for at least five (5) years in any agency of the government that is
involved in the processing of personal information including, but not limited to,
the following offices: Social Security System (SSS), Government Service
Insurance System (GSIS), Land Transportation Office (LTO), Bureau of
Internal Revenue (BIR), Philippine Health Insurance Corporation (Phil Health),
Commission on Elections (COMELEC), Department of Foreign Affairs (DFA),
Department of Justice (DOJ), and Philippine Postal Corporation (Philpost).
CHAPTER III
PROCESSING OF PERSONAL INFORMATION
SEC. 11. General Data Privacy Principles. The processing of personal
information shall be allowed, subject to compliance with the requirements of
this Act and other laws allowing disclosure of information to the public and

107
adherence to the principles of transparency, legitimate purpose and
proportionality.
Personal information must, be:
(a) Collected for specified and legitimate purposes determined and declared
before, or as soon as reasonably practicable after collection, and later
processed in a way compatible with such declared, specified and legitimate
purposes only;
(b) Processed fairly and lawfully;
(c) Accurate, relevant and, where necessary for purposes for which it is to be
used the processing of personal information, kept up to date; inaccurate or
incomplete data must be rectified, supplemented, destroyed or the further
processing restricted;
(d) Adequate and not excessive in relation to the purposes for which collected
and processed;
(e) Retained only for as long as necessary for the fulfillment of the purposes
for which the data was obtained or for the establishment, exercise or defense
of legal claims, or for legitimate business purposes, or as provided by law;
and
(f) Kept in a form which permits identification of data subjects for no longer
than is necessary for the purposes for which the data were collected and

108
processed: Provided, that personal information collected for other purposes
may lie processed for historical, statistical or scientific purposes, and in cases
laid down in law may be stored for longer periods: Provided, further, that
adequate safeguards are guaranteed by said laws authorizing the processing.
The personal information controller must ensure implementation of personal
information processing principles set out herein.
SEC. 12. Criteria for Lawful Processing of Personal Information. The
processing of personal information shall be permitted only if not otherwise
prohibited by law, and when at least one of the following conditions exists:
(a) The data subject has given his or her consent;
(b) The processing of personal information is necessary and is related to the
fulfillment of a contract with the data subject or in order to take steps at the
request of the data subject prior to entering into a contract;
(c) The processing is necessary for compliance with a legal obligation to
which the personal information controller is subject;
(d) The processing is necessary to protect vitally important interests of the
data subject, including life and health;
(e) The processing is necessary in order to respond to national emergency, to
comply with the requirements of public order and safety, or to fulfill functions

109
of public authority which necessarily includes the processing of personal data
for the fulfillment of its mandate; or
(f) The processing is necessary for the purposes of the legitimate interests
pursued by the personal information controller or by a third party or parties to
whom the data is disclosed, except where such interests are overridden by
fundamental rights and freedoms of the data subject which require protection
under the Philippine Constitution.
SEC. 13. Sensitive Personal Information and Privileged Information. The
processing of sensitive personal information and privileged information shall
be prohibited, except in the following cases:
(a) The data subject has given his or her consent, specific to the purpose prior
to the processing, or in the case of privileged information, all parties to the
exchange have given the consent prior to processing;
(b) The processing of the same is provided for by existing laws and
regulations: Provided, that such regulatory enactments guarantee the
protection of the sensitive personal information and the privileged
information: Provided, further, That the consent of the data subjects are not
required by law or regulation permitting the processing of the sensitive
personal information or the privileged information;

110
(c) The processing is necessary to protect the life and health of the data
subject or another person, and the data subject is not legally or physically
able to express his or her consent prior to the processing;
(d) The processing is necessary to achieve the lawful and noncommercial
objectives of public organizations and the associations: Provided, that such
processing is only confined and related to the bona fide members of these
organizations or the associations: Provided, further, That the sensitive
personal information are not transferred to third parties: Provided, finally, that
consent of the data subject was obtained prior to processing;
(e) The processing is necessary for purposes of medical treatment, is carried
out by a medical practitioner or a medical treatment institution, and an
adequate level of protection of personal information is ensured; or
(f) The processing concerns such personal information as is necessary for the
protection of lawful rights and interests of natural or legal persons in court
proceedings, or the establishment, exercise or defense of legal claims, or
when provided to government or public authority.
SEC. 14. Subcontract of Personal Information. A personal information
controller may subcontract the processing of personal
information: Provided, That the personal information controller shall be
responsible for ensuring that proper safeguards are in place to ensure the
confidentiality of the personal information processed, prevent its use for
unauthorized purposes, and generally, comply with the requirements of this

111
Act and other laws for processing of personal information. The personal
information processor shall comply with all the requirements of this Act and
other applicable laws.
SEC. 15. Extension of Privileged Communication. Personal information
controllers may invoke the principle of privileged communication over
privileged information that lawfully control or process. Subject to existing laws
and regulations, any evidence gathered on privileged information is
inadmissible.

112
Appendix G
Relevant Source Code
Source Code
AndroidManifest.xml
<uses-feature

113
android:name="android.hardware.location"
android:required="true" />
<uses-feature
android:name="android.hardware.location.gps"
android:required="true" />
<uses-permission
android:name="android.permission.ACCESS_COARSE_LOCATION" />
<uses-permission
android:name="android.permission.ACCESS_FINE_LOCATION" />
<uses-permission android:name="android.permission.ACCESS_WIFI_STATE" />
<uses-permission android:name="android.permission.ACCESS_NETWORK_STATE"
/>
<uses-permission android:name="android.permission.INTERNET" />
<uses-permission
android:name="android.permission.WRITE_EXTERNAL_STORAGE" />
<application
android:allowBackup="true"
android:icon="@mipmap/ic_launcher"

114
android:label="Tomb Locator"
android:supportsRtl="true"
android:theme="@style/AppTheme">
<activity
android:name=".MainActivity"
android:configChanges="orientation|keyboardHidden|screenSize"
android:launchMode="singleTask">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.DEFAULT" />
</intent-filter>
</activity>
<activity
android:name=".AddGraveActivity"
android:launchMode="singleTask"
android:parentActivityName=".MainActivity" />
<activity

115
android:name=".MapSelectActivity"
android:parentActivityName=".AddGraveActivity" />
<activity
android:name=".DetailsActivity"
android:configChanges="orientation|keyboardHidden|screenSize" />
<activity
android:name=".PreferencesMainActivity"
android:parentActivityName=".MainActivity" />
<activity android:name=".Splashscreen">
<intent-filter>
<action android:name="android.intent.action.MAIN" />
<category android:name="android.intent.category.LAUNCHER" />
</intent-filter>
</activity>

116
<activity
android:name=".Main2Activity"
android:label="@string/title_activity_main2"
android:theme="@style/AppTheme.NoActionBar"></activity>
</application>
AddGraveActivity.class
import android.app.Activity;
import android.content.DialogInterface;
import android.content.Intent;
import android.graphics.Bitmap;
import android.graphics.drawable.BitmapDrawable;
import android.net.Uri;
import android.os.Bundle;
import android.support.v7.app.AlertDialog;
import android.support.v7.app.AppCompatActivity;
import android.view.Menu;
import android.view.MenuItem;

117
import android.view.View;
import android.widget.Button;
import android.widget.EditText;
import android.widget.ImageView;
import android.widget.TextView;
import com.squareup.picasso.Picasso;
public class AddGraveActivity extends AppCompatActivity {
private final int MAP_REQUEST_ID = 73;
private final int IMAGE_REQUEST_ID = 92;
private double latitude = 0;
private double longitude = 0;
private TextView textViewLatitude;
private TextView textViewLongitude;
private EditText editTextName;

118
private EditText editTextBirth;
private EditText editTextDeath;
private EditText editTextNote;
private ImageView imageViewPhoto;
@Override
protected void onCreate(Bundle savedInstanceState) {
super.onCreate(savedInstanceState);
setContentView(R.layout.activity_add_grave);
getSupportActionBar().setDisplayHomeAsUpEnabled(true);
textViewLatitude = (TextView) findViewById(R.id.textViewLatitude);
textViewLongitude = (TextView) findViewById(R.id.textViewLongitude);
editTextName = (EditText) findViewById(R.id.editTextName);
editTextBirth = (EditText) findViewById(R.id.editTextBirth);
editTextDeath = (EditText) findViewById(R.id.editTextDeath);
editTextNote = (EditText) findViewById(R.id.editTextNote);
imageViewPhoto = (ImageView) findViewById(R.id.imageViewPhoto);

119
setButton();
updateUI();
@Override
public boolean onCreateOptionsMenu(Menu menu) {
getMenuInflater().inflate(R.menu.menu_add_grave,menu);
return super.onCreateOptionsMenu(menu);
@Override
public boolean onOptionsItemSelected(MenuItem item) {
if (item.getItemId() == R.id.menu_item_save_and_add) {
if
(checkEnteredData(editTextName.getText().toString(),editTextBirth.getText().toString(
), editTextDeath.getText().toString())) {
DatabaseHelper db = new DatabaseHelper(this);
Bitmap bitmap = ((BitmapDrawable)
imageViewPhoto.getDrawable()).getBitmap();

120
db.insertGrave(editTextName.getText().toString(),
editTextBirth.getText().toString(), editTextDeath.getText().toString(), latitude,
longitude, bitmap, editTextNote.getText().toString());
setResult(Activity.RESULT_OK);
finish();
return super.onOptionsItemSelected(item);
private boolean checkEnteredData(String name, String data1, String data2) {
if (name.isEmpty() || data1.isEmpty() || data2.isEmpty()) {
showWrongDataDialog(getString(R.string.error_empty_text_boxes));
return false;
if (!data1.matches("[0-9]{2}[.][0-9]{2}[.][0-9]{2}")) {
showWrongDataDialog(getString(R.string.error_birth_bad_format));

121
return false;
if (!data2.matches("[0-9]{2}[.][0-9]{2}[.][0-9]{2}")) {
showWrongDataDialog(getString(R.string.error_death_bad_format));
return false;
return true;
private void showWrongDataDialog(String message) {
AlertDialog.Builder builder = new AlertDialog.Builder(this);
builder.setTitle(getString(R.string.saving_error));
builder.setMessage(message);
builder.setPositiveButton(getString(R.string.ok_capital), new
DialogInterface.OnClickListener() {
public void onClick(DialogInterface dialog, int id) {

122
});
AlertDialog dialog = builder.create();
dialog.show();
private void setButton() {
Button buttonEditLocation = (Button) findViewById(R.id.buttonEditLocation);
buttonEditLocation.setOnClickListener(new View.OnClickListener() {
@Override
public void onClick(View view) {
Intent intent = new Intent(getBaseContext(), MapSelectActivity.class);
startActivityForResult(intent,MAP_REQUEST_ID);
});
Button buttonEditImage = (Button) findViewById(R.id.buttonEditPhoto);
buttonEditImage.setOnClickListener(new View.OnClickListener() {
@Override

123
selectImage();
});
private void updateUI() {
textViewLatitude.setText(getString(R.string.latitude) + "" + latitude);
textViewLongitude.setText(getString(R.string.longitude) + "" + longitude);
private void selectImage() {
Intent intent = new Intent();
intent.setType("image/*");
intent.setAction(Intent.ACTION_GET_CONTENT);
startActivityForResult(Intent.createChooser(intent,
getString(R.string.select_img)), IMAGE_REQUEST_ID);

124
@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
if (resultCode == Activity.RESULT_OK) {
if (requestCode == MAP_REQUEST_ID) {
latitude = data.getDoubleExtra(Tags.MAP_LATITUDE, 0);
longitude = data.getDoubleExtra(Tags.MAP_LONGITUDE, 0);
} else if (requestCode == IMAGE_REQUEST_ID) {
if (data != null) {
Uri imageUri = data.getData();
Picasso.with(this).load(imageUri).fit().centerInside().into(imageViewPhoto);
updateUI();
super.onActivityResult(requestCode, resultCode, data);

125
CameraFragment.class
import android.support.v4.app.Fragment;
import android.view.LayoutInflater;
import android.view.ViewGroup;
/**
* A simple {@link Fragment} subclass.
*/
public class CameraFragment extends Fragment {
public CameraFragment() {
// Required empty public constructor

126
@Override
public View onCreateView(LayoutInflater inflater, ViewGroup container,
Bundle savedInstanceState) {
// Inflate the layout for this fragment
return inflater.inflate(R.layout.fragment_camera, container, false);
Databasehelper.class
import android.content.ContentValues;
import android.content.Context;
import android.database.Cursor;
import android.database.sqlite.SQLiteDatabase;
import android.database.sqlite.SQLiteOpenHelper;

127
import android.graphics.BitmapFactory;
import java.io.ByteArrayOutputStream;
import java.util.ArrayList;
import java.util.List;
import java.util.Random;
public class DatabaseHelper extends SQLiteOpenHelper {
private static final int DATABASE_CURRENT_VERSION = 2;
private static final String DATABASE_NAME = "UserDatabase.db";
private final String TABLE_GRAVES = "graves";
private final String GRAVES_ID = "id";
private final String GRAVES_NAME = "name";
private final String GRAVES_BIRTH = "birth";
private final String GRAVES_DEATH = "death";
private final String GRAVES_LATITUDE = "lati";
private final String GRAVES_LONGITUDE = "long";

128
private final String GRAVES_PHOTO = "photo";
private final String GRAVES_NOTE = "note";
private Random random;
public DatabaseHelper(Context context) {
super(context, DATABASE_NAME, null, DATABASE_CURRENT_VERSION);
random = new Random();
@Override
public void onCreate(SQLiteDatabase db) {
db.execSQL("CREATE TABLE " + TABLE_GRAVES + " (" + GRAVES_ID + "
INTEGER PRIMARY KEY AUTOINCREMENT, "
+ GRAVES_NAME + " TEXT, " + GRAVES_BIRTH + " TEXT, " +
GRAVES_DEATH + " TEXT, "
+ GRAVES_LATITUDE + " TEXT, " + GRAVES_LONGITUDE + " TEXT, "
+ GRAVES_PHOTO + " BLOB, " + GRAVES_NOTE + " TEXT)");

129
@Override
public void onUpgrade(SQLiteDatabase db, int oldVer, int newVer) {
while (oldVer < newVer) {
if (oldVer == 1) {
db.execSQL("ALTER TABLE " + TABLE_GRAVES + " ADD COLUMN " +
GRAVES_NOTE + " TEXT");
oldVer++;
private byte[] bitmapToBytes(Bitmap bitmap) {
ByteArrayOutputStream stream = new ByteArrayOutputStream();
bitmap.compress(Bitmap.CompressFormat.PNG, 0, stream);
return stream.toByteArray();
private Bitmap bytesToBitmap(byte[] image) {

130
return BitmapFactory.decodeByteArray(image, 0, image.length);
public void insertGrave(String name, String birth, String death, double latitude,
double longitude, Bitmap photo, String note) {
SQLiteDatabase db = this.getWritableDatabase();
ContentValues contentValues = new ContentValues();
contentValues.put(GRAVES_NAME,name);
contentValues.put(GRAVES_BIRTH,birth);
contentValues.put(GRAVES_DEATH,death);
contentValues.put(GRAVES_LATITUDE,String.valueOf(latitude));
contentValues.put(GRAVES_LONGITUDE,String.valueOf(longitude));
contentValues.put(GRAVES_PHOTO,bitmapToBytes(photo));
contentValues.put(GRAVES_NOTE, note);
db.insert(TABLE_GRAVES, null, contentValues);

131
private Cursor getGravesCursor() {
Cursor res = db.rawQuery("select * from " + TABLE_GRAVES, null);
return res;
public List<Grave> getAllGraves() {
Cursor cursor = getGravesCursor();
if (cursor.getCount() == 0)
return new ArrayList<>();
List<Grave> graves = new ArrayList<>();
while (cursor.moveToNext()) {
String note;
if (cursor.getString(7) == null)
note = "";
else
note = cursor.getString(7);

132
graves.add(new Grave(cursor.getInt(0),
random.nextInt(9),cursor.getString(1),cursor.getString(2),cursor.getString(3),note));
return graves;
private Cursor getGravesCursorById(int id) {
Cursor res = db.rawQuery("select * from " + TABLE_GRAVES + " WHERE " +
GRAVES_ID + " = " + id, null);
return res;
public Bundle getOneGrave(int id) {
Bundle bundle = new Bundle();
Cursor res = getGravesCursorById(id);
res.moveToNext();

133
Bitmap bitmap = bytesToBitmap(res.getBlob(6));
bundle.putParcelable(Tags.PHOTO, bitmap);
bundle.putDouble(Tags.MAP_LATITUDE,res.getDouble(4));
bundle.putDouble(Tags.MAP_LONGITUDE,res.getDouble(5));
bundle.putString(Tags.NOTE,res.getString(7));
return bundle;
public void removeGraveById(int id) {
db.delete(TABLE_GRAVES, GRAVES_ID + "=" + String.valueOf(id),null);
db.close();
DetailsActivity.class

134
import android.net.Uri;
import android.support.design.widget.FloatingActionButton;
import android.support.v4.app.ActivityCompat;
public class DetailsActivity extends AppCompatActivity {
private TextView textViewName;
private TextView textViewDate;
private TextView textViewNote;
private ImageView imageViewPhoto;
private FloatingActionButton floatingActionButtonMap;

135
private double latitude;
private double longitude;
@Override
setContentView(R.layout.activity_details);
textViewName = (TextView) findViewById(R.id.textViewName);
textViewDate = (TextView) findViewById(R.id.textViewDates);
textViewNote = (TextView) findViewById(R.id.textViewNoteContent);
imageViewPhoto = (ImageView) findViewById(R.id.imageViewPhoto);
setData();
floatingButton();
@Override

136
if (item.getItemId() == android.R.id.home)
ActivityCompat.finishAfterTransition(this);
private void floatingButton() {
floatingActionButtonMap = (FloatingActionButton)
findViewById(R.id.floatingActionButtonAddToMap);
floatingActionButtonMap.setOnClickListener(new View.OnClickListener() {
@Override
String uri = "http://maps.google.com/maps?q=loc:" + latitude + "," +
longitude + " (" + getIntent().getExtras().getString(Tags.NAME) + ")";;
Intent intent = new Intent(Intent.ACTION_VIEW, Uri.parse(uri));
startActivity(intent);
});

137
private void setData() {
DatabaseHelper db = new DatabaseHelper(this);
Bundle bundle = db.getOneGrave(getIntent().getExtras().getInt(Tags.ID));
textViewName.setText(getIntent().getExtras().getString(Tags.NAME));
textViewDate.setText(getIntent().getExtras().getString(Tags.DATE));
textViewNote.setText(bundle.getString(Tags.NOTE));
latitude = bundle.getDouble(Tags.MAP_LATITUDE);
longitude = bundle.getDouble(Tags.MAP_LONGITUDE);
Bitmap bitmap = bundle.getParcelable(Tags.PHOTO);
imageViewPhoto.setImageBitmap(bitmap);
Devicelocation.class
import android.Manifest;

138
import android.app.ProgressDialog;
import android.content.DialogInterface;
import android.content.pm.PackageManager;
import android.location.Location;
import android.location.LocationListener;
import android.location.LocationManager;
import android.support.v7.app.AlertDialog;
import org.osmdroid.api.IMapController;
import org.osmdroid.util.GeoPoint;
import org.osmdroid.views.MapView;
import org.osmdroid.views.overlay.Marker;
public class DeviceLocation implements LocationListener {
private LocationManager locationManager;
private Marker locationMarker;

139
private boolean locationSaved;
private ProgressDialog loadingDialog;
private IMapController mapController;
private MapView mapView;
private Context context;
private Activity activity;
public DeviceLocation(IMapController mapController, MapView mapView, Context
context, Activity activity) {
this.mapController = mapController;
this.mapView = mapView;
this.context = context;
this.activity = activity;
locationSaved = false;
public void getLocation() {

140
locationManager = (LocationManager)
context.getSystemService(Context.LOCATION_SERVICE);
if (ActivityCompat.checkSelfPermission(activity,
Manifest.permission.ACCESS_FINE_LOCATION) !=
PackageManager.PERMISSION_GRANTED
&&ActivityCompat.checkSelfPermission(activity,
Manifest.permission.ACCESS_COARSE_LOCATION) !=
PackageManager.PERMISSION_GRANTED) {
ActivityCompat.requestPermissions(activity, new String[]
{Manifest.permission.ACCESS_COARSE_LOCATION}, 1);
{Manifest.permission.ACCESS_FINE_LOCATION}, 1);
boolean requestedLocation = false;
if (locationManager.isProviderEnabled(LocationManager.GPS_PROVIDER)) {
requestedLocation = true;
locationManager.requestLocationUpdates(LocationManager.GPS_PROVIDER, 0, 0,
this);

141
if
(locationManager.isProviderEnabled(LocationManager.NETWORK_PROVIDER)) {
requestedLocation = true;
locationManager.requestLocationUpdates(LocationManager.NETWORK_PROVIDER
, 0, 0, this);
if (!requestedLocation) {
showDialogLocationProviderError();
} else {
showLoading();
private void showDialogLocationProviderError() {
AlertDialog.Builder builder = new AlertDialog.Builder(activity);
builder.setTitle(context.getString(R.string.no_location_services_title));
builder.setMessage(context.getString(R.string.no_location_services));

142
builder.setPositiveButton(context.getString(R.string.ok_capital), new
DialogInterface.OnClickListener() {
public void onClick(DialogInterface dialog, int id) {
});
AlertDialog dialog = builder.create();
dialog.show();
public void drawMarker(GeoPoint geoPoint) {
if (locationMarker == null)
locationMarker = new Marker(mapView);
locationMarker.setPosition(geoPoint);
locationMarker.setAnchor(Marker.ANCHOR_CENTER,
Marker.ANCHOR_BOTTOM);
mapView.getOverlays().add(locationMarker);

143
locationMarker.setTitle(context.getString(R.string.set_location));
mapView.invalidate();
private void showLoading() {
if (loadingDialog == null)
loadingDialog = ProgressDialog.show(activity, "",
context.getString(R.string.wait_loading), true);
private void hideLoading() {
loadingDialog.cancel();
public GeoPoint getMarkerPosition() {
if (locationMarker == null) {
return null;
} else {

144
return locationMarker.getPosition();
public void removeUpdates() {
if (ActivityCompat.checkSelfPermission(activity,
Manifest.permission.ACCESS_FINE_LOCATION) !=
PackageManager.PERMISSION_GRANTED
&&ActivityCompat.checkSelfPermission(activity,
PackageManager.PERMISSION_GRANTED) {
{Manifest.permission.ACCESS_FINE_LOCATION}, 1);
locationManager.removeUpdates(this);
@Override
public void onLocationChanged(Location location) {

145
GeoPoint myPointPosition = new GeoPoint(location);
if (!locationSaved) {
drawMarker(myPointPosition);
mapController.setCenter(myPointPosition);
hideLoading();
locationSaved = true;
} else {
mapController.animateTo(myPointPosition);
removeUpdates();
@Override
public void onStatusChanged(String s, int i, Bundle bundle) {
@Override
public void onProviderEnabled(String s) {

146
@Override
public void onProviderDisabled(String s) {
GalleryFragment.class
/**
* A simple {@link Fragment} subclass.
* Use the {@link GalleryFragment#newInstance} factory method to
* create an instance of this fragment.

147
*/
public class GalleryFragment extends Fragment {
// TODO: Rename parameter arguments, choose names that match
// the fragment initialization parameters, e.g. ARG_ITEM_NUMBER
private static final String ARG_PARAM1 = "param1";
private static final String ARG_PARAM2 = "param2";
// TODO: Rename and change types of parameters
private String mParam1;
private String mParam2;
public GalleryFragment() {
/**
* Use this factory method to create a new instance of
* this fragment using the provided parameters.

148
* @param param1 Parameter 1.
* @param param2 Parameter 2.
* @return A new instance of fragment GalleryFragment.
*/
// TODO: Rename and change types and number of parameters
public static GalleryFragment newInstance(String param1, String param2) {
GalleryFragment fragment = new GalleryFragment();
Bundle args = new Bundle();
args.putString(ARG_PARAM1, param1);
args.putString(ARG_PARAM2, param2);
fragment.setArguments(args);
return fragment;
@Override
public void onCreate(Bundle savedInstanceState) {
if (getArguments() != null) {

149
mParam1 = getArguments().getString(ARG_PARAM1);
mParam2 = getArguments().getString(ARG_PARAM2);
@Override
return inflater.inflate(R.layout.fragment_gallery, container, false);
GettingHereFragment.class

150
public class GettinghereFragment extends Fragment {
public GettinghereFragment() {
@Override
return inflater.inflate(R.layout.fragment_gettinghere, container, false);
Grave.class
public class Grave {
private int id;
private int color;

151
private String name;
private String birthDate;
private String deathDate;
private String note;
public Grave(int id, int color, String name, String birthDate, String deathDate,
String note) {
this.id = id;
this.color = color;
this.name = name;
this.birthDate = birthDate;
this.deathDate = deathDate;
this.note = note;
public int getId() {
return id;

152
public int getColor() {
return color;
public String getName() {
return name;
public String getBirthDate() {
return birthDate;
public String getDeathDate() {
return deathDate;
public String getNote() {
return note;

153
GravesAdapter.class
import android.graphics.drawable.Drawable;
import android.support.v4.app.ActivityOptionsCompat;
import android.support.v4.util.Pair;
import android.support.v7.widget.RecyclerView;
import android.transition.Fade;
import android.widget.Filter;
import android.widget.Filterable;

154
import java.util.ArrayList;
import java.util.List;
public class GravesAdapter extends
RecyclerView.Adapter<GravesAdapter.MyViewHolder> implements Filterable {
private LayoutInflater inflater;
private Activity activity;
private List<Grave> gravesList;
private List<Grave> originalGravesList;
public GravesAdapter(Context context, Activity activity, List<Grave> gravesList) {
inflater = LayoutInflater.from(context);
this.activity = activity;
this.gravesList = gravesList;
@Override
public MyViewHolder onCreateViewHolder(ViewGroup parent, int viewType) {

155
View view = inflater.inflate(R.layout.row_grave_item,parent,false);
MyViewHolder holder = new MyViewHolder(view);
return holder;
@Override
public void onBindViewHolder(MyViewHolder holder, int position) {
holder.textViewName.setText(gravesList.get(position).getName());
holder.textViewDates.setText(gravesList.get(position).getBirthDate() + " - " +
gravesList.get(position).getDeathDate());
holder.textViewInitials.setText(parseInitials(gravesList.get(position).getName()));
holder.imageViewCircle.setImageDrawable(getCircleColor(position));
holder.idValue = gravesList.get(position).getId();
public String parseInitials(String nameToParse) {
if (nameToParse.matches("[a-zA-Z]+") == true &&
nameToParse.length() >= 2) {
return nameToParse.substring(0, 2).toUpperCase();

156
} else if (nameToParse.matches("[a-zA-Z]+ [a-zA-
Z]+")) {
String returnedValue = "";
returnedValue += nameToParse.toUpperCase().charAt(0);
int i = 1;
while (nameToParse.charAt(i) != ' ')
i++;
returnedValue += nameToParse.toUpperCase().charAt(i+1);
return returnedValue;
} else {
return "??";
public void refreshData(List<Grave> gravesList) {
this.gravesList = gravesList;

157
notifyDataSetChanged();
public Grave removeItem(int position) {
Grave removedGraved = gravesList.get(position);
gravesList.remove(position);
notifyItemRemoved(position);
originalGravesList = null;
return removedGraved;
public void restoreItem(int positon, Grave grave) {
gravesList.add(positon, grave);
notifyItemInserted(positon);
originalGravesList = null;
public int getGraveId(int position) {
return gravesList.get(position).getId();

158
public Drawable getCircleColor(int position) {
switch (gravesList.get(position).getColor()) {
case 0:
return inflater.getContext().getDrawable(R.drawable.circle_100);
case 1:
case 2:
case 3:
case 4:
case 5:
case 6:
case 7:

159
case 8:
default:
return null;
@Override
public int getItemCount() {
return gravesList.size();
@Override
public Filter getFilter() {
return new Filter() {
@Override
protected FilterResults performFiltering(CharSequence charSequence) {
final FilterResults oReturn = new FilterResults();

160
final List<Grave> results = new ArrayList<>();
if (originalGravesList == null)
originalGravesList = gravesList;
if (charSequence != null){
String searchedValue = charSequence.toString().toLowerCase();
if(originalGravesList !=null & originalGravesList.size()>0 ){
for ( final Grave g : originalGravesList) {
if (g.getName().toLowerCase().contains(searchedValue) ||
g.getBirthDate().toLowerCase().contains(searchedValue) ||
g.getDeathDate().toLowerCase().contains(searchedValue) ||
g.getNote().toLowerCase().contains(searchedValue)) {
results.add(g);
oReturn.values = results;

161
return oReturn;
@Override
protected void publishResults(CharSequence charSequence, FilterResults
filterResults) {
gravesList = (ArrayList<Grave>)filterResults.values;
notifyDataSetChanged();
};
class MyViewHolder extends RecyclerView.ViewHolder implements
View.OnClickListener {
TextView textViewName;
TextView textViewDates;

162
TextView textViewInitials;
ImageView imageViewCircle;
int idValue;
public MyViewHolder(View itemView) {
super(itemView);
itemView.setOnClickListener(this);
textViewName = (TextView) itemView.findViewById(R.id.textViewName);
textViewDates = (TextView) itemView.findViewById(R.id.textViewDates);
textViewInitials = (TextView) itemView.findViewById(R.id.textViewInitials);
imageViewCircle = (ImageView)
itemView.findViewById(R.id.imageViewMulticolorCircle);
@Override
Intent intent = new Intent(inflater.getContext() ,DetailsActivity.class);

163
activity.getWindow().setEnterTransition(new Fade(Fade.IN));
intent.putExtra(Tags.ID, idValue);
intent.putExtra(Tags.NAME, textViewName.getText().toString());
intent.putExtra(Tags.DATE, textViewDates.getText().toString());
ActivityOptionsCompat options =
ActivityOptionsCompat.makeSceneTransitionAnimation(
activity,
new Pair<View,
String>(view.findViewById(R.id.textViewName),inflater.getContext().getString(R.string
.transition_name)),
new Pair<View,
String>(activity.findViewById(R.id.floatingActionButtonAdd),inflater.getContext().getSt
ring(R.string.transition_floating_button)),
new Pair<View,
String>(view.findViewById(R.id.textViewDates),inflater.getContext().getString(R.string
.transition_date))
);
ActivityCompat.startActivity(inflater.getContext(),intent,options.toBundle());

164
Main2Activity.class
import android.support.design.widget.Snackbar;
import android.support.v4.app.FragmentManager;
import android.support.design.widget.NavigationView;
import android.support.v4.view.GravityCompat;
import android.support.v4.widget.DrawerLayout;
import android.support.v7.app.ActionBarDrawerToggle;
import android.support.v7.widget.Toolbar;
import android.widget.Toast;

165
public class Main2Activity extends AppCompatActivity
implements NavigationView.OnNavigationItemSelectedListener {
@Override
setContentView(R.layout.activity_main2);
Toolbar toolbar = (Toolbar) findViewById(R.id.toolbar);
setSupportActionBar(toolbar);
getSupportActionBar().setTitle("Sangandaan Cemetery");
toolbar.setSubtitle("aics.edu.ph");
toolbar.setLogo(android.R.drawable.ic_menu_info_details);
FloatingActionButton fab = (FloatingActionButton) findViewById(R.id.fab);
fab.setOnClickListener(new View.OnClickListener() {
@Override

166
Snackbar.make(view, "Replace with your own action",
Snackbar.LENGTH_LONG)
.setAction("Action", null).show();
});
DrawerLayout drawer = (DrawerLayout) findViewById(R.id.drawer_layout);
ActionBarDrawerToggle toggle = new ActionBarDrawerToggle(
this, drawer, toolbar, R.string.navigation_drawer_open,
R.string.navigation_drawer_close);
drawer.setDrawerListener(toggle);
toggle.syncState();
NavigationView navigationView = (NavigationView)
findViewById(R.id.nav_view);
navigationView.setNavigationItemSelectedListener(this);
@Override
public void onBackPressed() {

167
if (drawer.isDrawerOpen(GravityCompat.START)) {
drawer.closeDrawer(GravityCompat.START);
} else {
super.onBackPressed();
@Override
// Inflate the menu; this adds items to the action bar if it is present.
getMenuInflater().inflate(R.menu.main2, menu);
return true;
@Override
// Handle action bar item clicks here. The action bar can
// automatically handle clicks on the Home/Up button, so long

168
// as you specify a parent activity in AndroidManifest.xml.
int id = item.getItemId();
//noinspection SimplifiableIfStatement
if (id == R.id.action_settings) {
return true;
@SuppressWarnings("StatementWithEmptyBody")
@Override
public boolean onNavigationItemSelected(MenuItem item) {
// Handle navigation view item clicks here.
int id = item.getItemId();
if (id == R.id.nav_camera) {
Toast.makeText(this, "Cemetery", Toast.LENGTH_SHORT).show();

169
GalleryFragment galleryFragment = new GalleryFragment();
FragmentManager manager = getSupportFragmentManager();
manager.beginTransaction().replace(R.id.relativelayout_for_fragment,
galleryFragment,
galleryFragment.getTag()
).commit();
} else if (id == R.id.nav_gallery) {
Toast.makeText(this, "Developers", Toast.LENGTH_SHORT).show();
CameraFragment cameraFragment = new CameraFragment();
cameraFragment,
cameraFragment.getTag()
).commit();
} else if (id == R.id.nav_gettinghere){
Toast.makeText(this, "Getting Here", Toast.LENGTH_SHORT).show();
GettinghereFragment gettinghereFragment = new GettinghereFragment();

170
gettinghereFragment,
gettinghereFragment.getTag()
).commit();
} else if (id == R.id.nav_share) {
} else if (id == R.id.nav_send) {
drawer.closeDrawer(GravityCompat.START);
return true;
MainActivity.class

171
import android.content.SharedPreferences;
import android.preference.PreferenceManager;
import android.support.design.widget.Snackbar;
import android.support.v7.widget.DividerItemDecoration;
import android.support.v7.widget.LinearLayoutManager;
import android.support.v7.widget.RecyclerView;
import android.support.v7.widget.SearchView;
import android.support.v7.widget.helper.ItemTouchHelper;
import android.widget.Toast;
public class MainActivity extends AppCompatActivity {

172
private final int ADD_REQUEST_ID = 92;
private FloatingActionButton floatingActionButtonAdd;
private RecyclerView recyclerView;
private GravesAdapter gravesAdapter;
private DatabaseHelper db;
private boolean isReadyToExit = false;
private SharedPreferences preferencesMain;
@Override
setContentView(R.layout.activity_main);
db = new DatabaseHelper(this);
preferencesMain = PreferenceManager.getDefaultSharedPreferences(this);
setFloatingActionButton();
setRecyclerView();

173
PermissionChecker.checkForPermissions(this);
@Override
getMenuInflater().inflate(R.menu.menu_main,menu);
SearchView searchView = (SearchView)
menu.findItem(R.id.menu_searcher).getActionView();
searchView.setMaxWidth(Integer.MAX_VALUE);
searchView.setOnQueryTextListener(new SearchView.OnQueryTextListener() {
@Override
public boolean onQueryTextSubmit(String query) {
return false;
@Override
public boolean onQueryTextChange(String newText) {
if (newText.isEmpty()) {

174
gravesAdapter.getFilter().filter("");
} else {
gravesAdapter.getFilter().filter(newText);
return false;
});
@Override
if (item.getItemId() == R.id.menu_settings) {
startActivity(new Intent(this, PreferencesMainActivity.class));
else if (item.getItemId() == R.id.menu_close_app) {
finishAffinity();

175
@Override
public void onBackPressed() {
if (isReadyToExit) {
finishAffinity();
} else {
Toast.makeText(this, getString(R.string.press_back_button_to_exit),
Toast.LENGTH_LONG).show();
isReadyToExit = true;
private void setFloatingActionButton() {
floatingActionButtonAdd = (FloatingActionButton)
findViewById(R.id.floatingActionButtonAdd);

176
floatingActionButtonAdd.setOnClickListener(new View.OnClickListener() {
@Override
Intent intent = new Intent(getBaseContext(), AddGraveActivity.class);
startActivityForResult(intent,ADD_REQUEST_ID);
});
private void setRecyclerView() {
recyclerView = (RecyclerView) findViewById(R.id.recyclerView);
gravesAdapter = new GravesAdapter(this,this,db.getAllGraves());
recyclerView.setAdapter(gravesAdapter);
recyclerView.setLayoutManager(new LinearLayoutManager(this));
LinearLayoutManager linearLayoutManager = new LinearLayoutManager(this);

177
DividerItemDecoration dividerItemDecoration = new
DividerItemDecoration(recyclerView.getContext(),
linearLayoutManager.getOrientation());
recyclerView.addItemDecoration(dividerItemDecoration);
ItemTouchHelper itemTouchHelper = new
ItemTouchHelper(createItemTouchCallback());
itemTouchHelper.attachToRecyclerView(recyclerView);
private ItemTouchHelper.Callback createItemTouchCallback() {
ItemTouchHelper.SimpleCallback simpleCallback = new
ItemTouchHelper.SimpleCallback(0,
ItemTouchHelper.LEFT | ItemTouchHelper.RIGHT) {
@Override
public boolean onMove(RecyclerView recyclerView,
RecyclerView.ViewHolder viewHolder, RecyclerView.ViewHolder target) {
return false;

178
@Override
public void onSwiped(RecyclerView.ViewHolder viewHolder, int direction) {
final int positonRemovedItem = viewHolder.getAdapterPosition();
final int idItemToRemove =
gravesAdapter.getGraveId(positonRemovedItem);
final Grave removedGrave =
gravesAdapter.removeItem(positonRemovedItem);
if (preferencesMain.getBoolean("pref_snackbar",true)) {
Snackbar snackbar = Snackbar
.make(recyclerView, getString(R.string.item_removed),
Snackbar.LENGTH_LONG)
.setAction(getString(R.string.undo_upper), new
View.OnClickListener() {
@Override
gravesAdapter.restoreItem(positonRemovedItem,
removedGrave);

179
});
snackbar.addCallback(new Snackbar.Callback() {
@Override
public void onDismissed(Snackbar snackbar, int event) {
if (event == Snackbar.Callback.DISMISS_EVENT_TIMEOUT)
db.removeGraveById(idItemToRemove);
});
snackbar.show();
} else {
db.removeGraveById(idItemToRemove);
};
return simpleCallback;

180
@Override
protected void onActivityResult(int requestCode, int resultCode, Intent data) {
if (requestCode == ADD_REQUEST_ID) {
if (preferencesMain.getBoolean("pref_snackbar",true) && resultCode ==
Activity.RESULT_OK)
Snackbar.make(recyclerView, getString(R.string.item_added),
Snackbar.LENGTH_LONG).show();
gravesAdapter.refreshData(db.getAllGraves());
super.onActivityResult(requestCode, resultCode, data);
public void onButtonClick(View view)
if(view.getId() == R.id.Bdisplay)

181
Intent i = new Intent(MainActivity.this, Main2Activity.class);
startActivity(i);
MapSelectActivity.class
import android.content.SharedPreferences;
import android.preference.PreferenceManager;
import org.osmdroid.api.IMapController;
import org.osmdroid.events.MapEventsReceiver;
import org.osmdroid.tileprovider.constants.OpenStreetMapTileProviderConstants;

182
import org.osmdroid.tileprovider.tilesource.TileSourceFactory;
import org.osmdroid.util.GeoPoint;
import org.osmdroid.views.MapView;
import org.osmdroid.views.overlay.MapEventsOverlay;
import org.osmdroid.views.overlay.infowindow.InfoWindow;
public class MapSelectActivity extends AppCompatActivity implements
MapEventsReceiver {
private MapView map;
private IMapController mapController;
private MapEventsOverlay mapEventsOverlay;
private DeviceLocation deviceLocation;
private SharedPreferences preferencesMain;
@Override
setContentView(R.layout.activity_map_select);

183
preferencesMain = PreferenceManager.getDefaultSharedPreferences(this);
PermissionChecker.checkForPermissions(this);
enableMaps();
setOverlay();
deviceLocation = new DeviceLocation(mapController,map,this,this);
deviceLocation.getLocation();
@Override
protected void onDestroy() {
super.onDestroy();
deviceLocation.removeUpdates();
@Override

184
getMenuInflater().inflate(R.menu.menu_map_select,menu);
@Override
if (item.getItemId() == R.id.menu_item_set_location) {
Intent resultData = new Intent();
GeoPoint geoReturnPoint = deviceLocation.getMarkerPosition();
if (geoReturnPoint == null) {
resultData.putExtra("Lat", 0);
resultData.putExtra("Lon", 0);
} else {
resultData.putExtra(Tags.MAP_LATITUDE, geoReturnPoint.getLatitude());
resultData.putExtra(Tags.MAP_LONGITUDE,
geoReturnPoint.getLongitude());

185
setResult(Activity.RESULT_OK, resultData);
finish();
private void setOverlay() {
mapEventsOverlay = new MapEventsOverlay(this, this);
map.getOverlays().add(0, mapEventsOverlay);
private void enableMaps() {
OpenStreetMapTileProviderConstants.setUserAgentValue(BuildConfig.APPLICATIO
N_ID);
map = (MapView) findViewById(R.id.map);
setMapSource();

186
map.setBuiltInZoomControls(true);
map.setMultiTouchControls(true);
mapController = map.getController();
mapController.setZoom(20);
private void setMapSource() {
switch (Integer.valueOf(preferencesMain.getString("pref_map_provider","3"))) {
case 0:
map.setTileSource(TileSourceFactory.CYCLEMAP);
break;
case 1:
map.setTileSource(TileSourceFactory.BASE_OVERLAY_NL);
break;
case 2:
map.setTileSource(TileSourceFactory.HIKEBIKEMAP);
break;
case 3:

187
map.setTileSource(TileSourceFactory.MAPNIK);
break;
case 4:
map.setTileSource(TileSourceFactory.USGS_SAT);
break;
default:
map.setTileSource(TileSourceFactory.MAPNIK);
break;
@Override
public boolean singleTapConfirmedHelper(GeoPoint geoPoint) {
InfoWindow.closeAllInfoWindowsOn(map);
deviceLocation.drawMarker(geoPoint);
return false;

188
@Override
public boolean longPressHelper(GeoPoint geoPoint) {
return false;
PermissionChecker.class
import android.Manifest;
import android.content.pm.PackageManager;
import android.support.v4.content.ContextCompat;
public class PermissionChecker {
public static void checkForPermissions(Activity activity) {
if (ContextCompat.checkSelfPermission(activity,
Manifest.permission.WRITE_EXTERNAL_STORAGE) !=
PackageManager.PERMISSION_GRANTED)

189
{Manifest.permission.WRITE_EXTERNAL_STORAGE}, 1);
if (ContextCompat.checkSelfPermission(activity,
PackageManager.PERMISSION_GRANTED)
PreferencesMainActivity.class
import android.app.FragmentManager;
import android.app.FragmentTransaction;
import android.preference.PreferenceFragment;
public class PreferencesMainActivity extends AppCompatActivity {
@Override

190
setContentView(R.layout.activity_preferences_main);
FragmentManager mFragmentManager = getFragmentManager();
FragmentTransaction mFragmentTransaction =
mFragmentManager.beginTransaction();
PreferenceFragment mPrefsFragment = new PreferencesMainFragment();
mFragmentTransaction.replace(android.R.id.content, mPrefsFragment);
mFragmentTransaction.commit();
PreferencesMainFragment.class
import android.preference.PreferenceFragment;
public class PreferencesMainFragment extends PreferenceFragment {
@Override

191
addPreferencesFromResource(R.xml.preferences_main);
SplashScreen.class
import android.graphics.PixelFormat;
import android.view.Window;
import android.view.animation.Animation;
import android.view.animation.AnimationUtils;
import android.widget.LinearLayout;
public class Splashscreen extends Activity {
public void onAttachedToWindow() {

192
super.onAttachedToWindow();
Window window = getWindow();
window.setFormat(PixelFormat.RGBA_8888);
/** Called when the activity is first created. */
Thread splashTread;
@Override
setContentView(R.layout.activity_splashscreen);
StartAnimations();
private void StartAnimations() {
Animation anim = AnimationUtils.loadAnimation(this, R.anim.alpha);
anim.reset();
LinearLayout l=(LinearLayout) findViewById(R.id.lin_lay);
l.clearAnimation();
l.startAnimation(anim);

193
anim = AnimationUtils.loadAnimation(this, R.anim.translate);
anim.reset();
ImageView iv = (ImageView) findViewById(R.id.splash);
iv.clearAnimation();
iv.startAnimation(anim);
splashTread = new Thread() {
@Override
public void run() {
try {
int waited = 0;
// Splash screen pause time
while (waited < 4500) {
sleep(100);
waited += 100;
Intent intent = new Intent(Splashscreen.this,
MainActivity.class);
intent.setFlags(Intent.FLAG_ACTIVITY_NO_ANIMATION);

194
startActivity(intent);
Splashscreen.this.finish();
} catch (InterruptedException e) {
// do nothing
} finally {
Splashscreen.this.finish();
};
splashTread.start();
Tags.class
public class Tags {
static String MAP_LATITUDE = "_map_latitude";
static String MAP_LONGITUDE = "_map_longitude";

195
static String ID = "_id";
static String NAME = "_name";
static String DATE = "_date";
static String PHOTO = "_photo";
static String NOTE = "_note";
Alpha.xml
<?xml version="1.0" encoding="utf-8"?>
<alpha
xmlns:android="http://schemas.android.com/apk/res/android"
android:fromAlpha="0.0"
android:toAlpha="1.0"
android:duration="3000" />
Translate.xml
<set
xmlns:android="http://schemas.android.com/apk/res/android">
<translate

196
android:fromXDelta="0%"
android:toXDelta="0%"
android:fromYDelta="200%"
android:toYDelta="0%"
android:duration="2000"
android:zAdjustment="top" />
</set>
Activity_add_grave.xml
<ScrollView xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto"
xmlns:tools="http://schemas.android.com/tools"
android:id="@+id/activity_add_grave"
android:layout_width="match_parent"
android:layout_height="match_parent"
android:descendantFocusability="beforeDescendants"
android:focusableInTouchMode="true"

197
android:background="@drawable/background"
tools:context="com.jakubbilinski.cemeterygravelocator.AddGraveActivity">
<LinearLayout
android:layout_height="wrap_content"
android:orientation="vertical"
android:layout_margin="@dimen/activity_vertical_margin">
<android.support.design.widget.TextInputLayout
android:layout_height="match_parent">
<EditText
android:hint="@string/name"
android:id="@+id/editTextName"
android:maxLines="1" />

198
</android.support.design.widget.TextInputLayout>
<EditText
android:hint="@string/birth_date"
android:inputType="date"
android:id="@+id/editTextBirth"

199
<EditText
android:hint="@string/death_date"
android:inputType="date"
android:id="@+id/editTextDeath"
<EditText
android:hint="@string/note"
android:id="@+id/editTextNote"
android:inputType="textMultiLine"/>

200
<Space
android:layout_height="10dp" />
<TextView
android:text="@string/location"
android:id="@+id/textViewLocation"
android:textSize="20sp" />
<TextView
android:text="@string/latitude"
android:id="@+id/textViewLatitude" />

201
<TextView
android:text="@string/longitude"
android:id="@+id/textViewLongitude" />
<Button
android:text="@string/edit"
android:id="@+id/buttonEditLocation"
style="@style/Widget.AppCompat.Button.Borderless" />
<TextView
android:text="@string/photo"
android:id="@+id/textViewPhoto"
android:textSize="20sp" />

202
<ImageView
app:srcCompat="@drawable/replace"
android:id="@+id/imageViewPhoto"
android:scaleType="centerInside"
android:layout_height="200dp"
android:contentDescription="@string/photo_of_grave" />
<Button
android:text="@string/edit"
android:id="@+id/buttonEditPhoto"
style="@style/Widget.AppCompat.Button.Borderless" />
<Space

203
</LinearLayout>
</ScrollView>
Activity_details.xml
<android.support.constraint.ConstraintLayout
android:id="@+id/activity_details"
tools:context="com.jakubbilinski.cemeterygravelocator.DetailsActivity">
<ImageView
android:layout_width="wrap_content"
app:srcCompat="@drawable/replace"
android:id="@+id/imageViewPhoto"

204
android:scaleType="centerCrop"
app:layout_constraintTop_toTopOf="parent"
app:layout_constraintLeft_toLeftOf="parent"
app:layout_constraintRight_toRightOf="parent"
android:elevation="2dp"
android:contentDescription="@string/photo_of_grave" />
<View
android:layout_width="0dp"
android:background="@color/colorPrimaryDark"
app:layout_constraintTop_toBottomOf="@+id/imageViewPhoto"
android:id="@+id/ViewColoredDark"
<View
android:background="@android:color/white"

205
android:id="@+id/ViewColoredWhite"
app:layout_constraintHorizontal_bias="1.0"
app:layout_constraintTop_toBottomOf="@+id/ViewColoredDark"
app:layout_constraintBottom_toBottomOf="parent"
android:elevation="2dp" />
<TextView
android:text="TextView"
android:id="@+id/textViewName"
android:layout_marginStart="16dp"
app:layout_constraintTop_toBottomOf="@+id/imageViewPhoto"
android:layout_marginTop="16dp"
android:textSize="36sp"

206
android:transitionName="@string/transition_name"
android:textColor="@android:color/white"
tools:ignore="HardcodedText" />
<TextView
android:id="@+id/textViewDates"
app:layout_constraintTop_toBottomOf="@+id/textViewName"
android:transitionName="@string/transition_date"
android:textColor="@android:color/white"
<android.support.design.widget.FloatingActionButton

207
android:clickable="true"
app:fabSize="normal"
app:srcCompat="@drawable/ic_add_location"
android:id="@+id/floatingActionButtonAddToMap"
android:layout_marginEnd="16dp"
app:layout_constraintTop_toTopOf="@+id/imageViewPhoto"
android:transitionName="@string/transition_floating_button"
android:layout_marginTop="175dp" />
<TextView
android:id="@+id/textViewNoteContent"

208
android:layout_marginBottom="16dp"
app:layout_constraintTop_toBottomOf="@+id/textViewNote"
android:elevation="2dp"
app:layout_constraintVertical_bias="0.0" />
<TextView
android:text="@string/note_colon"
android:id="@+id/textViewNote"
app:layout_constraintTop_toBottomOf="@+id/ViewColoredDark"
android:elevation="2dp"/>

209
</android.support.constraint.ConstraintLayout>
Activity_main.xml
android:id="@+id/activity_main"
tools:context="com.jakubbilinski.cemeterygravelocator.MainActivity">
<android.support.v7.widget.RecyclerView

210
app:layout_constraintVertical_bias="0.0"
android:id="@+id/recyclerView" />
android:clickable="true"
app:srcCompat="@drawable/ic_add"
android:id="@+id/floatingActionButtonAdd"
app:layout_constraintBottom_toBottomOf="@+id/recyclerView"
app:layout_constraintRight_toRightOf="@+id/recyclerView"
android:transitionName="@string/transition_floating_button"
app:fabSize="normal" />

211
<Button
android:id="@+id/Bdisplay"
android:layout_marginRight="72dp"
android:background="@mipmap/ic_launcher"
android:onClick="onButtonClick"
android:text=""
app:layout_constraintBottom_toBottomOf="@+id/recyclerView"
app:layout_constraintRight_toRightOf="@+id/recyclerView"
tools:layout_editor_absoluteX="247dp"
tools:layout_editor_absoluteY="424dp" />
Activity_main2.xml

212
<android.support.v4.widget.DrawerLayout
android:id="@+id/drawer_layout"
android:fitsSystemWindows="true"
tools:openDrawer="start">
android:background="@drawable/background1"
<include
layout="@layout/app_bar_main2"
android:layout_height="match_parent" />
<android.support.design.widget.NavigationView
android:id="@+id/nav_view"

213
android:layout_gravity="start"
android:fitsSystemWindows="true"
app:headerLayout="@layout/nav_header_main2"
app:menu="@menu/activity_main2_drawer" />
</android.support.v4.widget.DrawerLayout>
Activity_map_select.xml
<LinearLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:id="@+id/activity_map_select"
tools:context="com.jakubbilinski.cemeterygravelocator.MapSelectActivity">
<org.osmdroid.views.MapView android:id="@+id/map"
android:layout_height="match_parent" />
</LinearLayout>

214
Activity_preferences_main.xml
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:id="@+id/activity_preferences_main"
android:paddingBottom="@dimen/activity_vertical_margin"
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
tools:context="com.jakubbilinski.cemeterygravelocator.PreferencesMainActivity">
</RelativeLayout>
Activity_splashscreen.xml
android:layout_width="fill_parent"
android:layout_height="fill_parent"

215
android:background="#ffffff"
android:layout_gravity="center"
android:id="@+id/lin_lay"
android:gravity="center"
android:orientation="vertical">
<ImageView
android:id="@+id/splash"
android:background="@drawable/splash_img" />
</LinearLayout>
App_bar_main2.xml
<android.support.design.widget.CoordinatorLayout

216
tools:context="com.jakubbilinski.cemeterygravelocator.Main2Activity">
<android.support.design.widget.AppBarLayout
android:theme="@style/AppTheme.AppBarOverlay">
<android.support.v7.widget.Toolbar
android:id="@+id/toolbar"
android:layout_height="?attr/actionBarSize"
android:background="?attr/colorPrimary"
app:popupTheme="@style/AppTheme.PopupOverlay" />
</android.support.design.widget.AppBarLayout>

217
<include layout="@layout/content_main2" />
android:id="@+id/fab"
android:layout_gravity="bottom|end"
android:layout_margin="@dimen/fab_margin"
android:visibility="invisible"
app:srcCompat="@android:drawable/ic_dialog_email" />
</android.support.design.widget.CoordinatorLayout>
Content_main2.xml
<RelativeLayout xmlns:android="http://schemas.android.com/apk/res/android"
android:id="@+id/relativelayout_for_fragment"

218
app:layout_behavior="@string/appbar_scrolling_view_behavior"
tools:context="com.jakubbilinski.cemeterygravelocator.Main2Activity"
tools:showIn="@layout/app_bar_main2">
</RelativeLayout>
Fragment_camera.xml
tools:context="com.jakubbilinski.cemeterygravelocator.CameraFragment">


219
<TextView
android:id="@+id/textView11"
android:text="About the Developers"
android:textAppearance="@style/TextAppearance.AppCompat.Button"
android:textStyle="bold|italic"
tools:layout_editor_absoluteY="0dp" />
<TextView
android:fontFamily="sans-serif-condensed"
android:text="This application was created by the students of Asian Institute of
Computer Studies. This application was created to fulfill the requirements for the
degree of Bachelor of Computer Science (BSCS)"

220
app:layout_constraintTop_toBottomOf="@+id/textView11"
tools:layout_editor_absoluteX="0dp" />
<TextView
android:text="ACKNOWLEDGEMENT"
tools:layout_editor_absoluteX="0dp" />
<TextView
android:layout_marginLeft="8dp"

221
android:text="The proponents want to give thanks to all the person that have
become a big part of this study."
app:layout_constraintHorizontal_bias="0.517" />
<TextView
android:text="First we would like to thank our God for giving us the strength to
finish this study."

222
<TextView
android:text="To our families for the moral and financial support in order to finish
this study."

223
<TextView
android:text="To Mr. Tomas Benjamin P. Berbano III for giving us time to finish
this study and approved our study."
app:layout_constraintRight_toRightOf="parent" />
<TextView

224
android:text="To Mrs. Cecila P, Abarich. Our thesis professor who support us
until the end of the school year."
app:layout_constraintTop_toBottomOf="@+id/textView22" />
<TextView
android:text="And lastly to all the respondents for the full cooperation that made
them a big part of this study."

225
<TextView
android:text="Lorenzo O. Hernandez IV"
<TextView

226
android:text="John Kevin G. Roque"
<TextView
android:layout_marginTop="-1dp"
android:text="Dustin Junnell B. Camacho"

227
<TextView
android:text="Jhaycee N. Benitez"
<ImageView
android:id="@+id/imageView6"
app:srcCompat="@drawable/aics"

228
android:layout_marginBottom="33dp" />
<TextView
android:text="Asian Institute of Computer Studies"
app:layout_constraintLeft_toRightOf="@+id/imageView6"
<TextView

229
android:text="Bachelor of Computer Scienc (BSCS)"
app:layout_constraintLeft_toRightOf="@+id/imageView6"
Fragment_Gallery.xml

230
tools:context="com.jakubbilinski.cemeterygravelocator.GalleryFragment">
<ImageView
android:id="@+id/imageView2"
android:scaleType="centerCrop"
app:srcCompat="@drawable/sangandaan"
tools:layout_editor_absoluteY="-4dp" />
<TextView

231
android:text="SANGANDAAN CEMETERY CALOOCAN"
app:layout_constraintTop_toBottomOf="@+id/imageView2" />
<TextView
android:text="Address"
android:textStyle="bold"

232
<TextView
android:text="Marcelo H. Del Pilar St, Sangandaan, Caloocan, Metro Manila"
<TextView

233
android:text="Open Hours:"
<TextView
android:text="Monday - Sunday 8AM TO 5PM"

234
<TextView
android:text="Owner:"
<TextView

235
android:text="Caloocan City Government"
Fragment_gettinghere.xml
tools:context="com.jakubbilinski.cemeterygravelocator.GettinghereFragment">

236
<TextView
android:text="HOW TO NAVIGATE:"
tools:text="HOW TO NAVIGATE:" />
<TextView

237
android:text="Using of 3G Data Connection, may not be accurate because of
the signal and speed of connection."
<TextView
android:text="Using of 4G LTE Data Connection, you can get fast accuracy of
navigation. 4G LTE and Pocket Wi-FI are the same because both devices uses LTE
SimCard."

238
<TextView
android:text="Since Google Maps didn't capture road inside the Sangandaan
Cemetery, you may want to switch to Satellite View when using the Navigation."

239
<TextView
android:text="The Red Marker should indicate the Pin where the Tomb is
located, if the GPS is on, a color blue circle icon is your location. Walk until you reach
the Red Pin Marker and look the name of the Tomb."
<TextView

240
android:text="If you have any question and want to make this application better,
kindly contact us on facebook. "
<ImageView
android:id="@+id/imageView"
app:srcCompat="@android:drawable/stat_sys_phone_call"

241
app:layout_constraintVertical_bias="0.157"
<TextView
android:text="facebook.com/enzooooKAI"
app:layout_constraintLeft_toRightOf="@+id/imageView"

242
<TextView
android:text="facebook.com/kevin.roque.19"
<TextView

243
android:text="facebook.com/24dustincamacho"
Nav_header_main2.xml
android:layout_height="@dimen/nav_header_height"
android:background="@drawable/splash_img"
android:gravity="bottom"

244
android:paddingBottom="@dimen/activity_vertical_margin"
android:paddingLeft="@dimen/activity_horizontal_margin"
android:paddingRight="@dimen/activity_horizontal_margin"
android:paddingTop="@dimen/activity_vertical_margin"
android:theme="@style/ThemeOverlay.AppCompat.Dark">
<TextView
android:paddingTop="@dimen/nav_header_vertical_spacing"
android:text="SANGANDAAN CEMETERY CALOOCAN"
android:textAppearance="@style/TextAppearance.AppCompat.Body1"
android:textColor="@android:color/holo_orange_dark" />
<TextView
android:id="@+id/textView"
android:text="Androidprogrammers@EnDustVin"

245
android:textColor="@color/colorPrimaryLight" />
</LinearLayout>
Row_Grave_Item.xml
android:orientation="horizontal" android:layout_width="match_parent"
android:layout_height="55dp">
<RelativeLayout
<ImageView

246
app:srcCompat="@drawable/circle_500"
android:layout_centerVertical="true"
android:layout_centerHorizontal="true"
android:id="@+id/imageViewMulticolorCircle"
android:contentDescription="@string/circle_initials" />
<TextView
android:text="TV"
android:layout_centerVertical="true"
android:layout_centerHorizontal="true"
android:id="@+id/textViewInitials"
android:textAlignment="center"
android:textColor="@android:color/background_light"

247
</RelativeLayout>
<LinearLayout
<TextView
android:id="@+id/textViewName"
android:transitionName="@string/transition_name"
<TextView

248
android:id="@+id/textViewDates"
android:textStyle="normal|italic"
android:transitionName="@string/transition_date"
</LinearLayout>
Activity_main_2_drawer.xml
<menu xmlns:android="http://schemas.android.com/apk/res/android">
<group android:checkableBehavior="single">
<item
android:id="@+id/nav_camera"
android:icon="@drawable/ic_menu_cross"
android:title="About the Cemetery" />
<item

249
android:id="@+id/nav_gallery"
android:icon="@drawable/ic_menu_group"
android:title="About the Developers" />
<item
android:id="@+id/nav_gettinghere"
android:icon="@drawable/ic_menu_bus"
android:title="How to Use" />
</group>
<item android:title="Communicate">
<menu>
<item
android:id="@+id/nav_share"
android:icon="@drawable/ic_menu_share"
android:title="Share" />
<item
android:id="@+id/nav_send"
android:icon="@drawable/ic_menu_send"

250
android:title="Send" />
</menu>
</item>
</menu>
Main2.xml
<menu xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto">
<item
android:id="@+id/action_settings"
android:orderInCategory="100"
android:title="@string/action_settings"
app:showAsAction="never" />
</menu>
Menu_add_grave.xml
<menu xmlns:app="http://schemas.android.com/apk/res-auto"

251
<item android:id="@+id/menu_item_save_and_add"
android:title="@string/save"
app:showAsAction="always"
android:icon="@drawable/ic_save_white_24dp"/>
</menu>
Menu_main.xml
<menu xmlns:android="http://schemas.android.com/apk/res/android"
xmlns:app="http://schemas.android.com/apk/res-auto">
<item android:id="@+id/menu_searcher"
android:title="@string/search"
android:icon="@drawable/ic_search_white_24dp"
app:actionViewClass="android.support.v7.widget.SearchView"
app:showAsAction="always" />
<item android:id="@+id/menu_settings"
android:title="@string/settings"

252
android:icon="@drawable/ic_settings_white_24dp"
app:showAsAction="ifRoom" />
<item android:id="@+id/menu_import_export"
android:title="@string/import_export"
<item android:id="@+id/menu_close_app"
android:title="@string/close_app"
</menu>
Menu_map_select.xml
<menu xmlns:app="http://schemas.android.com/apk/res-auto"
<item android:id="@+id/menu_item_set_location"
android:title="@string/set"

253
app:showAsAction="always"
android:icon="@drawable/ic_done_white_24dp" />
</menu>
Dependencies(build.gradle)module;app
apply plugin: 'com.android.application'
repositories {
maven { url "https://jitpack.io" }
android {
compileSdkVersion 25
buildToolsVersion "25.0.0"
defaultConfig {
applicationId "com.jakubbilinski.cemeterygravelocator"
minSdkVersion 21
targetSdkVersion 25
versionCode 1020170125
versionName "1.0.2017.01.25"
testInstrumentationRunner "android.support.test.runner.AndroidJUnitRunner"

254
buildTypes {
release {
minifyEnabled false
proguardFiles getDefaultProguardFile('proguard-android.txt'), 'proguard-
rules.pro'
dependencies {
compile fileTree(dir: 'libs', include: ['*.jar'])
androidTestCompile('com.android.support.test.espresso:espresso-core:2.2.2', {
exclude group: 'com.android.support', module: 'support-annotations'
})
compile 'com.android.support:appcompat-v7:25.1.0'
compile 'com.android.support.constraint:constraint-layout:1.0.0-beta4'
compile 'com.android.support:recyclerview-v7:25.1.0'
compile 'com.android.support:design:25.1.0'

255
compile 'com.github.MKergall:osmbonuspack:6.0'
compile 'com.squareup.picasso:picasso:2.5.2'
compile 'com.android.support:support-v4:25.3.0'
testCompile 'junit:junit:4.12'
Appendix H
Gantt chart
256

257
NOVEMBER
OCTOBER
AUGUST
SEPT.
JUNE
MAR.
DEC.
JULY
APR.
FEB.
JAN.
TASK
WEEK 1-4
Constructing a
Proposed Title
Gathering
Information about
the
Proposed Study
Analyzing the
Proposed System
Documentation of
the Proposed
Study
Designing the
Proposed System
Experimentation
Deployment and
Software
Implementation of
the Proposed
System

258
Appendix I
Progress Report

259
Progress Report
Introduction
Progress of the proposed system: Tomb Locator using Global
Positioning System (GPS) via Android Application the assignment
development and accomplishment schedules of the tasks reflected on the
Gantt chart were promptly described towards the system developments
progress evaluation.
TASK 1.
Searching for Subject Company
INCLUSIVE DATES: 10-03-16 to 10-08-16
DESCRIPTION:
For 5 days the proponents search for a prospective company and
decided to conduct study in Sangandaan Cemetery in Sangandaan, Caloocan
City. The challenge is how the study be conducted in order that the proposed
system results be successful. In the Sangandaan Cemetery, the proponents
noticed that mapping system was needed in order to organize all the details
and ways of getting to the tomb.

260
TASK 2:
Conducting the Initial Interview
DESCRIPTION:
In this period, the proponents have conducted an initial interview with
the key informant of the research project, Mr. Federico Maghinang, Cemetery
Administrative Officer.
TASK 3:
Analyzing the Existing Problem
INCLUSIE DATES: 10-28-16 to 11-11-16
DESCRIPTION:
This was existing problem in every cemetery in which the proper record
management must maintained. In this way, the proponents have come up with
the idea of using Global Positioning System (GPS) in the way to mapped and
locate the tomb to be used in order to provide navigation with ease to the
Sangandaan Cemetery.

261
TASK 4:
Documenting the Study
DESCRIPTION:
This was conducted in more than (7) seven months; the proponents
were on track in documenting this study. The documentation of this study was
able to provide the necessary requirements and information which were
needed in order to ease the work of personnel in tracking and mapping of
tombs in the cemetery.
TASK 5:
Developing the System
DESCRIPTION:
This was intended for more than seven (7) months, the proponents
engineered the proposed system. The ideas and concepts formed from the
analysis of the problem were applied to use in system development and thus
the following stages of system development were worked out with the

262
requirements stage: Deployment and Software, Prototyping and
Implementation of the Proposed System.
TASK 6:
Testing and Evaluating the System
DESCRIPTION:
In the facilitation of the proposed system the data of the patients were
input in the tomb locator to ease the work of the personnel. After the
implementation stage, the surveys were facilitated in the personnel and
random family that had been the subject of the study. Twenty (20)
respondents were being used in the pursuit of this study.
TASK 7:
Analyzing the Survey Results
DESCRIPTION:
The data gathered from the conducted survey were analyzed by the
proponents for the studys statistical treatment. Each respondents rating was

263
carefully tabulated in order to derive a credible and unbiased findings or
result. The Likert Scale method was towards the rating scheme of the
respondents.
TASK 8:
Operating the Proposed System
DESCRIPTION:
The final task in the entire study was to operate the system and this
fully-developed system was presented to the faculty of AICSs Computer
Science Department for further recommendations. This has been suggested
for further revisions to accomplish the entire the study.

264
Appendix J
Computation for
Statistical Treatment
265
Compatibility in the Proposed System
I. Computation of Frequency
Formula: F = F/N
where,
F= the relative frequency of each class interval
F = sum of the frequency of class interval
N = the sample size
Solution:
Excellent:

266
f = (2)/1
f=2
Very Good:
f= (8)/1
f=8
Good:
f = (11)/1
f = 11
Satisfactory:
f = (3)/1
f= 3
Fair:
f= (1)/1
f= 1
Excellent Very Good Good Satisfactory Fair Total
2 8 11 3 1 25

267
II. Computation of Percentage
Formula: P = f/ N x 100
where,
P = percentage
F = frequency of each rating scale
Solution:
Excellent:
P = (2/25) * 100
P = 8%
Very Good:
P = (8/25) * 100
P = 32%
Good:
P = (11/25) * 100

268
P = 44%
Satisfactory:
P = (3/25) * 100
P = 12%
Fair:
P = (1/25) * 100
P = 4%
8% 32% 44% 12% 4% 100%
III. Computation of Mean
X
x
Formula: n
where:
X = mean of the ungrouped data
x = sum of the observed frequencies
n= number of frequency in the sample
Solution:

269
X ( 2 8 11 3 1) / 7 3.57
Categ Items Mean

ory
Actual Observation Per Respondents
No.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 1 19 20 21 2 23 24 25
8 2
Comp 1 4 2 3 3 3 3 3 3 3 4 3 3 2 3 4 4 3 4 4 3 3 3 3 4 1
atibilit
y
IV. Computation of Chi - Square
(O E ) 2

2
Formula:
x E , with df = c-1
where,
X 2 = computed Chi - Square value
O = observed frequency
E = expected frequency
df = degrees of freedom
C = total number of columns
Ho : There was no significant difference in the evaluations respondents
in terms of the overall compatibility feature of the proposed system improving
health center service using Mobile Tap Card.

270
H1: There was a significant difference in the respondents in terms of the
overall compatibility feature of the proposed system improving health center
service using Mobile Tap Card.
Level of Significance = 0.05
Rejection Region: Reject Hoif X Computed X Table

2 2
Computation:
X2 = [(2-4)2/4] + [(8-4)2/4]+[(11-4)2/4]+[(3-4)2/4]+[(1-4)2/4] = 1.00 + 4.00 + 12.3 +
0.3 + 2.25 = 19.85
O E O-E (O-E)2 (O-E)2E
2 4 -2 4 1
8 4 4 16 4
11 4 7 49 12.3
3 4 -1 1 0.3
1 4 -3 9 2.25
X2 Computed 19.85
Statistical Decision Reject Ho since the computed value of Chi- Square
(19.85) was greater than the critical or table value (9.48) at 0.05 level of
significance with 4 degrees of freedom.
X2 Computed > X2 Table

271
Interpretation /Conclusion: In this case, the proponents concluded that
there was a significant difference in the evaluations of the respondents in
terms of the overall compatibility feature of the proposed Mobile tap card. The
ability of the system to provide medical record of the patient using NFC card
was evident.
Functionality in the Proposed System
Formula: F = F/N
where,
N = the sample size
Solution:
Excellent:
f = (0)/1
f=0
Very Good:

272
f= (10)/1
= 10
Good:
f = (8)/1
f=8
Satisfactory:
f = (7)/1
f=7
Fair:
f= (0)/1
f=0
0 10 8 7 0 25
where,
P = percentage

273
Solution:
Excellent:
P = (0/25) * 100
P = 0%
Very Good:
P = (10/25) * 100
P = 40%
Good:
P = (8/25) * 100
P = 32%
Satisfactory:
P = (7/25) * 100
P = 28%
Fair:
P = (0/25) * 100
P = 0%

274
0% 40% 32% 28% 0% 100%
Formula:
X
x
n
where:
n= number of all frequencies
Solution:
X (0 10 8 7 0) / 7 4.00
Categ Items
ory
Actual Observation Per Respondents Mean
No.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Functi 1 2 2 4 4 4 4 4 3 4 2 2 4 3 2 3 3 3 4 3 2 2 3 4 4 3
onalit
4.00
y

275
Formula:
(O E ) 2

2
x E , with df = c-1
where,
Ho:There was no significant difference in the evaluations respondents in
terms of the overall functionality feature of the proposed system improving
H1:There was a significant difference in the respondents in terms of the
overall functionality feature of the proposed system improving health center

276
Rejection Region: Reject Hoif X2 Computed
Computation:
X2 = [(0-4)2/4] + [(10-4)2/4] + [(8-4)2/4] + [(7-4)2/4] + [(0-4)2/4] = 4.00 + 9.00 +
4.00 + 2.25 + 4.00 = 23.25
0 4 -4 16 4
10 4 6 36 9
8 4 4 16 4
7 4 3 9 2.25
0 4 -4 16 4
X2 Computed 23.25
(23.25) was greater than the critical or table value (9.48) at 0.05 level of
X2 Computed > X2 Table
terms of the overall functionality feature of the proposed Mobile tap card. The

277
was evident.
Maintainability in the Proposed System
Formula: F = F/N
where,
N = the sample size
Solution:
Excellent:
f = (7)/1
=7
Very Good:
f= (12)/1
= 12

278
Good:
f = (4)/1
=4
Satisfactory:
f = (2)/1
=2
Fair:
f= (0)/1
=0
7 12 4 2 0 25
where,
P = percentage

279
Solution:
Excellent:
P = (7/25) * 100
= 28%
Very Good:
P = (12/25) * 100
= 48%
Good:
P = (4/25) * 100
= 16%
Satisfactory:
P = (2/25) * 100
= 8%
Fair:
P = (0/25) * 100
= 0%

280
28% 48% 16% 8% 0% 100%
Formula:
X
x
n
where:
Solution:
X (7 12 4 2 0) / 7 3.60
Categ Items Mean

ory
No.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Maint 1 3 5 4 2 4 4 3 4 3 4 3 2 3 2 4 4 4 4 3 2 3 3 4 3 4
anabil
4.00
ity

281
Formula:
(O E ) 2

2
x E , with df = c-1
where,
Ho There was no significant difference in the evaluations respondents in
terms of the overall maintainability feature of the proposed system improving
H1 There was a significant difference in the respondents in terms of the
overall maintainability feature of the proposed system improving health center
Rejection Region: Reject Hoif X2 Computed X2 Table
Computation:

282
X2 = [(7-4)2/4] + [(12-4)2/4] + [(4-4)2/4] + [(2-4)2/4] + [(0-4)2/4] = 4.00 + 16.00 +
0.00 + 1.00 + 4.00 = 25.00
7 4 -4 16 4
12 4 8 64 16
4 4 0 0 0
2 4 -2 4 1
0 4 -4 16 4
X2 Computed 25.00
(25.00) was greater than the critical or tabular value (9.48) at 0.05 level of
X2 Computed > X2 Tabular
terms of the overall maintainability feature of the proposed Mobile tap card.
The ability of the system to provide medical record of the patient using NFC
card was evident.

283
Portability in the Proposed System
Formula: F = F/N
where,
N = the sample size
Solution:
Excellent:
f = (3)/1
=3
Very Good:
f= (8)/1
=8
Good:
f = (11)/1
= 11

284
Satisfactory:
f = (3)/1
=3
Fair:
f= (0)/1
=0
3 8 11 3 0 25
where,
P = percentage
Solution:
Excellent:
P = (3/25) * 100

285
= 12%
Very Good:
P = (8/25) * 100
= 32%
Good:
P = (11/25) * 100
= 44%
Satisfactory:
P = (3/25) * 100
= 12%
Fair:
P = (0/25) * 100
= 0%
12% 32% 44% 12% 0% 100%

286
Formula:
X
x
n
where:
Solution:
X (7 12 4 2 0) / 7 4.00
Categ Items
ory
No.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Porta 1 4 5 3 3 4 4 3 3 4 4 4 3 3 2 3 3 3 4 4 4 2 3 3 3 3
bility
4.00
Formula:

287
(O E ) 2

2
x E , with df = c-1
where,
terms of the overall portability feature of the proposed system improving
overall portability feature of the proposed system improving health center
Rejection Region: Reject Hoif X2 Computed x2 table
Computation:

288
X2 = [(3-4)2/4]+ [(8-4)2/4]+[(11-4)2/4]+[(3-4)2/4]+[(0-4)2/4] = 0.25 + 4.00 + 12.25
+ 1.00 + 4.00 = 21.50
3 4 -1 1 0.25
8 4 4 16 4
11 4 7 49 12.25
3 4 -1 1 1
0 4 -4 16 4
X2 Computed 21.50
(21.50) was greater than the critical or tabular value(9.48) at 0.05 level of
terms of the overall portability feature of the proposed Mobile tap card. The
was evident.
Reliability in the Proposed System

289
Formula: F = F/N
where,
N = the sample size
Solution:
Excellent:
f = (1)/1
=1
Very Good:
f= (9)/1
=9
Good:
f = (11)/1
= 11

290
Satisfactory:
f = (4)/1 = 4
Fair: f= (0)/1
=0
1 9 11 4 0 25
where,
P = percentage
Solution:
Excellent:
P = (1/25) * 100
= 4%

291
Very Good:
P = (9/25) * 100
= 36%
Good:
P = (11/25) * 100
= 44%
Satisfactory:
P = (4/25) * 100
= 16%
Fair:
P = (0/25) * 100
= 0%
4% 36% 44% 16% 0% 100%
X
x
Formula: n

292
where:
Solution:
X (7 12 4 2 0) / 7 3.57
Categ Items Mean

ory
No.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Reliab 1 2 4 4 3 3 3 4 4 3 2 1 3 3 2 3 3 4 3 3 3 4 3 4 4 4
ility
4.00
Formula:
(O E ) 2

2
x E , with df = c-1
where,

293
terms of the overall reliability feature of the proposed system improving health
center service using Mobile Tap Card.
overall reliability feature of the proposed system improving health center
Rejection Region: Reject Hoif X2 Computed 49
Computation:
X2 = [(1-4)2/4]+ [(9-4)2/4]+[(11-4)2/4]+[(4-4)2/4]+[(0-4)2/4] = 0.25 + 6.25 + 12.25
+ 1.00 + 4.00 = 23.75

294
1 4 -3 1 0.25
9 4 5 25 6.25
11 4 7 49 12.25
3 4 -1 1 1
0 4 -4 16 4
X2 Computed 23.75
terms of the overall reliability feature of the proposed Mobile tap card. The
was evident.
Security in the Proposed System
Formula: F = F/N
where,

295
N = the sample size
Solution:
Excellent:
f = (6)/1
=6
Very Good:
f= (13)/1
= 13
Good:
f = (4)/1
=4
Satisfactory:
f = (2)/1
=2
Fair:
f= (0)/1

296
=0
6 13 4 2 0 25
where,
P = percentage
Solution:
Excellent:
P = (6/65) * 100
= 24%
Very Good:
P = (13/25) * 100
= 52%
Good:

297
P = (4/25) * 100
= 16%
Satisfactory:
P = (2/25) * 100
= 8%
Fair:
P = (0/25) * 100
= 0%
24% 52% 16% 2% 0% 100%
Formula:
X
x
n
where:

298
Solution:
X (6 13 4 2 0) / 7 4.00
Categ Items
ory
No.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Securi 1 3 4 4 2 3 4 3 4 3 2 2 3 2 3 4 4 4 3 4 3 2 4 3 4
ty
4.00
Formula:
(O E ) 2

2
x E , with df = c-1
where,

299
terms of the overall security feature of the proposed system improving health
overall security feature of the proposed system improving health center
Computation:
X2 = [(6-4)2/4]+ [(13-4)2/4]+[(4-4)2/4]+[(2-4)2/4]+[(0-4)2/4] = 1.00 + 20.25 + 0.00
+ 1.00 + 4.00 = 25.00
6 4 2 4 1
13 4 9 81 20.25
4 4 0 0 0
2 4 -2 4 1
0 4 -4 16 4
X2 Computed 26.25

300
terms of the overall security feature of the proposed Mobile tap card. The
was evident.
Usability in the Proposed System
Formula: F = F/N
where,
N = the sample size
Solution:

301
Excellent:
f = (7)/1
=7
Very Good:
f= (13)/1
= 13
Good:
f = (4)/1
=4
Satisfactory:
f = (1)/1
=1
Fair:
f= (0)/1
=0
7 13 4 1 0 25

302
where,
P = percentage
Solution:
Excellent:
P = (7/25) * 100
= 28%
Very Good:
P = (13/25) * 100
= 52%
Good:
P = (4/25) * 100
= 16%
Satisfactory:

303
P = (1/25) * 100
= 4%
Fair:
P = (0/25) * 100
= 0%
28% 52% 16% 4% 0% 100%
Formula:
X
x
n
where:

304
Solution:
X (7 13 4 1 0) / 7 3.57
Categ Items Mean

ory
No.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25
Usabil 1 2 2 3 3 3 4 3 4 3 2 2 2 2 3 3 3 3 3 3 3 3 3 3 4 3
ity
4.00
Formula:
(O E ) 2

2
x E , with df = c-1
where,

305
terms of the overall usability feature of the proposed system improving health
overall usability feature of the proposed system improving health center
Computation:
X2 = [(7-4)2/4]+ [(13-4)2/4]+[(4-4)2/4]+[(1-4)2/4]+[(0-4)2/4] = 0.25 + 12.25 + 0.00
+ 2.25 + 4.00 = 25.00
7 4 3 9 2.25
13 4 7 49 12.25
4 4 0 0 0
1 4 -3 9 2.25
0 4 -4 16 4
X2 Computed 20.75

306
terms of the overall portability feature of the proposed Mobile tap card. The
was evident.

307
Appendix K
Grammarians Certificate
April 24, 2017
G R A M M A R I A N S C E R T I F I C A T E
This is to certify that the undersigned, a/an English Teacherat
Kaunlaran High School has reviewed and went through all the pages of the
Thesis entitled TOMB LOCATOR USING GLOBAL POSITIONING SYSTEM

308
(GPS) VIA ANDROID APPLICATION as against the set of structural rules
that govern the composition of sentences, phrases, and words in the English
language.
SIGNED:
MRS. MILAGROS O. LAYGO
Grammarian
Resume Mam Laygo after the Grammarian

309
Appendix M
Curriculum Vitae

310

Docu Need To Be Revised

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

Docu Need To Be Revised

Загружено:

Авторское право:

Доступные форматы

ASIAN INSTITUTE OF COMPUTER STUDIES

410 D and I Bldg, Edsa Corner, Caloocan City

APPROVAL FOR BINDING

This is to certify that we have examined the manuscript which entitled:

TOMB LOCATOR USING GLOBAL POSITIONING SYSTEM (GPS) VIA

This certification is issued to allow the proponents to submit the

The Oral Examination Panel:

1. Mr. Manuel C. Delos Santos, MSCS Committee Chairman ________

2. Mr. Jesus Victor G. Lacerna, ECE, MIS Technical Adviser ________

3. Ms. Nena F. Famocol, MBA, PhD Committee Member ________

4. Mr. Ronald S. Tinio, MSE, MCP Committee Member ________

COMPUTER SCIENCE DEPARTMENT

COMPUTER SCIENCE DEPARTMENT

The proponents would like to take the opportunity to thanks the

Deserving a special mention Ms. Cecilia P. Abaricia, thesis adviser who

helps and guides every time to make a step finish these.

And to Mrs. Milagros O. Laygo instructor and head faculty of the

feels upset, and looks hopeless.

show the best potential and got to make it.

and deepest heartfelt thanks.

COMPUTER SCIENCE DEPARTMENT

Problem encountered by the people -- the proponents decided to develop this

Objectives of the study

at Sangandaan Cemetery, the proponents conduct this study in order to

Significance of the study

Design and Methodology

COMPUTER SCIENCE DEPARTMENT

Results and Discussion (Evaluation of the system)

The proponents recommend the implementation of the proposed

hassle of remembering a place far from the user.

COMPUTER SCIENCE DEPARTMENT

in to cemetery. Emergency teams scattered around the cemetery, to secure

the safeness of people.

The proponents proposed a system regarding Tomb Locator using

works for users. The location of this application located at Sangandaan

COMPUTER SCIENCE DEPARTMENT

buried and has a huge area.

tendency not to ask information to stranger.

To use this application, the user needs to connect in internet and

access the Global Positioning System (GPS) in the smartphone. It has a

the way to navigate the tomb.

COMPUTER SCIENCE DEPARTMENT

This application uses Google map and has a feature of voice

marker where the tomb was located.

Purpose and Description

Statement of the Problem

location of the tomb.

The ways to improve the management of the Sangandaan Cemetery in

terms of mapping and location of the tombs.

COMPUTER SCIENCE DEPARTMENT

1. What were the ways of locating the tomb easily?

Specifically, the proponents sought to answer the following queries:

1. What were the demographic profile of the respondents in terms of:

2. What were the problems encountered in using the manual process?

4. How the respondents assess the system in terms of :

5. What was the result of the software evaluation?

COMPUTER SCIENCE DEPARTMENT

The study aims to improve the management of the Sangandaan

Cemetery in terms of mapping the location of the tombs and providing

information of the deceased using this application for Sangandaan Cemetery.

1. To develop the proposed system using Android Studio and SQLite

for database management.

Application for easy navigating the tomb.