CHAPTER ONE

INTRODUCTION

1.0 OVERVIEW

The Android-based Fire Incident Reporting System is an innovative mobile

application designed to enhance the speed, accuracy, and efficiency of

reporting fire incidents. This system leverages the ubiquity of Android

smartphones to provide users with an accessible and easy-to-use platform

for immediately reporting fire-related emergencies. By integrating modern

smartphone capabilities, such as GPS for precise location tracking the

system ensures that emergency responders receive comprehensive and

accurate information as soon as an incident occurs. The core functionality

of the system includes a simple interface where users can quickly report

fire incidents by filling out details about the type and severity of the fire.

The application automatically tags the exact location of the incident, which

is crucial for guiding emergency services to the scene without delay. This

real-time data transmission significantly reduces response times and

improves the coordination between various emergency response teams,

such as fire departments, police, and medical services. The Android-based

Fire Incident Reporting System also plays a crucial role in facilitating

communication between the public and emergency services. Once a fire

1
incident is reported, the system immediately notifies the nearest fire

department, along with all the relevant details such as location, severity,

and potential hazards. This real-time data transmission not only speeds up

the response process but also enhances coordination among various

emergency services, including fire departments, police, and medical teams.

This integrated approach ensures that all necessary resources are mobilized

quickly and efficiently, minimizing the impact of the fire.

1.1 HISTORICAL BACKGROUND

The evolution of fire incident reporting has been shaped by technological

advancements and the growing need for efficient emergency response

systems. Historically, fire reporting relied heavily on manual methods, such

as telephone calls to emergency services or in-person notifications at local

fire stations. These traditional methods were often slow, prone to errors,

and lacked the capability to provide real-time information, which is crucial

for timely and effective responses to fire incidents. In the early 20th

century, fire alarm boxes were installed in many urban areas, allowing

people to pull a lever to alert the fire department of an emergency. These

alarm boxes were connected to central fire stations via telegraph wires,

signaling the need for a response. Although an improvement over previous

methods, this system still had limitations, including a lack of detailed

information about the nature and location of the fire. As cities grew and fire

2
departments became more sophisticated, the demand for better

communication and faster response times increased.

The advent of mobile communication in the late 20th century brought

significant changes to emergency reporting. With the widespread adoption

of mobile phones, individuals could report fire incidents more quickly and

from almost any location. This development marked a significant step

forward, but challenges remained, particularly in terms of providing

accurate location data and detailed information about the fire. Emergency

responders often had to rely on incomplete or unclear reports, which could

delay their arrival and hinder their ability to assess the situation properly.

The rise of smartphones in the 2000s introduced new possibilities for

emergency management. These devices combined communication

capabilities with advanced features such as GPS, cameras, and internet

connectivity, opening the door for more sophisticated fire incident reporting

systems. Early attempts to harness smartphone technology for emergency

reporting were largely experimental, focusing on basic text-based reporting

or GPS location sharing. However, these early applications laid the

groundwork for more integrated and comprehensive systems. As Android

became one of the most widely used mobile operating systems globally,

developers began to explore its potential for creating specialized

applications for various purposes, including emergency management. The

3
first generation of Android-based fire incident reporting systems emerged

in the early 2010s, offering a more streamlined and efficient way to report

fires. These early applications allowed users to report incidents with greater

accuracy by utilizing the smartphone’s GPS and camera features, providing

emergency services with more detailed and actionable information.

Over time, these systems evolved to include real-time data transmission,

user-friendly interfaces, and integration with emergency services. The

growing recognition of the importance of data in emergency management

also led to the development of systems that could store and analyze fire

incident data, helping authorities to identify trends and improve response

strategies. These advancements have made Android-based fire incident

reporting systems a critical tool in modern emergency management,

significantly enhancing the ability of fire departments to respond quickly

and effectively to incidents.

1.2 STATEMENT OF THE PROBLEM

In time, fire incidents pose a significant threat to lives, property, and

economic stability. Urban areas, in particular, are highly vulnerable due to

dense populations, inadequate infrastructure, and often poorly regulated

construction practices. Despite the frequency and severity of these

incidents, the current methods of reporting and responding to fires are

plagued by inefficiencies that hinder timely intervention and effective

4
management. The lack of a centralized, efficient system for fire incident

reporting is a major challenge that exacerbates the impact of fire-related

emergencies. Traditional fire reporting methods, which primarily rely on

phone calls to emergency services or in-person alerts, are often slow and

unreliable. These methods are prone to delays, miscommunication, and

inaccuracies, especially in high-stress situations where clarity and speed are

crucial. Additionally, many communities lack access to reliable

communication channels or are not aware of the appropriate emergency

numbers to call, further delaying response times. This delay in reporting

often results in fires escalating beyond control, leading to more extensive

damage, loss of life, and higher costs for recovery. Another critical issue is

the lack of precise location data in emergency reports. Urban areas,

particularly in informal settlements, often have poorly defined addresses or

none at all, making it difficult for emergency responders to locate the scene

of a fire quickly. Without accurate geolocation, fire departments can

struggle to navigate congested urban areas, leading to further delays in their

arrival. This challenge is compounded by traffic congestion, inadequate

road networks, and the limited availability of fire-fighting resources, all of

which contribute to slower response times and increased risks.

Fire incidents are a recurring challenge that result in significant loss of life,

property, and economic resources. Despite the presence of fire services

5
across the country, the current methods of reporting and managing fire

incidents are often slow, inefficient, and plagued by numerous challenges.

These issues are particularly acute in densely populated urban areas, where

the risk of fire is higher and the consequences of delayed responses are

more severe. One of the primary problems is the reliance on traditional

methods of fire reporting, such as phone calls to emergency services. This

approach is often hindered by poor communication infrastructure, leading

to delays in reaching emergency responders. Additionally, many reports

lack precise location information, making it difficult for fire services to

quickly locate and address the fire. The absence of real-time data further

complicates the ability of fire departments to assess the severity of

incidents and allocate resources effectively.

1.3 OBJECTIVE OF THE STUDY

The study aims to explore and evaluate the implementation of an Android-

based Fire Incident Reporting System, with the goal of improving fire

incident

reporting and emergency response across the country. Below are some

objectives:

i. To Design and Develop an Android-Based Fire Incident Reporting

Application.

6
 ii. To Enhance Public Awareness and Engagement in Fire Safety and

Reporting.

iii. To Improve the Efficiency of Fire Emergency Responses.

iv. To Integrate and Test the System within the Existing Emergency

Response.

1.4 SIGNIFICANCE OF THE STUDY

The implementation of an Android-based Fire Incident Reporting System in

Nigeria holds immense significance in enhancing the nation's emergency

response capabilities. By leveraging widely accessible mobile technology,

the system enables real-time reporting and accurate location tracking of fire

incidents, thereby significantly reducing response times and mitigating the

devastating effects of fires on lives and property. This modernization of

reporting mechanisms addresses existing communication gaps and equips

emergency services with timely and precise information necessary for

effective intervention. Furthermore, the study promotes increased public

participation and awareness in fire safety measures. Empowering citizens

with a user-friendly platform to report fires encourages community

engagement and responsibility, fostering a collaborative approach to

disaster management. The aggregated data collected through the system can

also be utilized to identify patterns and high-risk areas, informing proactive

7
prevention strategies and resource allocation for both local and national

authorities.

i. Enhancement of Fire Emergency Response.

ii. Reduction in Fire-Related Losses.

iii. Improved Emergency Response

iv. Technological Advancement.

1.5 SCOPE AND LIMITATION

The scope of this study encompasses the development, implementation, and

evaluation of an Android-based Fire Incident Reporting System specifically

tailored. The study focuses on creating a mobile application that allows

users to report fire incidents in real-time, providing emergency services

with precise location data and detailed information about the incident. The

system is designed to be user-friendly and accessible to a wide range of

users, including those in urban and rural areas.

The study also includes an analysis of the current fire incident reporting,

identifying the gaps and challenges that the new system aims to address.

Additionally, the research explores the integration of the reporting system

with existing emergency response frameworks, assessing its impact on

response times, resource allocation, and overall fire management efficiency.

The system's potential for data collection and analysis is also within the

8
study’s scope, particularly in terms of how it can be used to inform fire

prevention strategies and improve future emergency responses.

Despite its comprehensive scope, the study is subject to several limitations.

One of the primary limitations is the reliance on smartphone access and

digital literacy among the population. This digital divide could limit the

system's reach and effectiveness in certain regions. A major limitation of

the system is its reliance on GPS and location services, which may not

always provide pinpoint accuracy, especially in densely populated urban

areas or remote locations with poor signal reception. This can result in

delays or errors in identifying the exact location of fire incidents,

potentially affecting response times.

1.6. DEFINITION OF TERMS

Android-Based Fire Incident Reporting System: A mobile application

designed for Android smartphones that allows users to report fire incidents

in real-time, providing emergency services with detailed information and

accurate location data to facilitate quick and effective responses.

Emergency Response: The coordinated actions taken by emergency

services, such as fire departments, police, and medical teams, to address

and manage an incident or disaster, including fire outbreaks, to minimize

harm to life, property, and the environment.

9
App: An android app is a software application running on the android

platform.

GPS (Global Positioning System): A satellite-based navigation system that

provides location and time information anywhere on Earth, used in the

Android-based system to accurately pinpoint the location of a reported fire

incident.

User-Friendly Interface: A design feature of the mobile application that

makes it easy for users, regardless of their technical expertise, to navigate

and use the system to report fire incidents quickly and efficiently.

Fire Incident: Any event involving an uncontrolled fire that poses a threat

to life, property, or the environment, requiring intervention by emergency

services.

Digital Literacy: The ability to effectively use digital devices, such as

smartphones and computers, and to understand and operate software

applications. Digital literacy is crucial for users of the Android-based Fire

Incident Reporting System to report fires accurately.

Emergency Services: Public organizations such as fire departments,

police, and medical services that are responsible for responding to

emergencies, including fire outbreaks, to protect public safety and welfare.

10
Urban Areas: refer to regions characterized by higher population density,

infrastructure, and development, often including cities and towns.

Rural Areas are less densely populated regions with more open space,

agricultural land, and limited infrastructure, where access to emergency

services may be more challenging.

1.7 PROJECT ORGANIZATION

This project is organized in six (6) chapters as follows; each chapter is

centered on a particular subject matter as also has sub heading which is

used most time to buttress a point. Chapter one (1) focused on introduction,

overview, historical background, Statement of the problem, objective of the

study, significance of the study, scope and limitations, Definition s of terms

project organization. Chapter two (2) contains the literate review, over

view, feasibility study. Chapter Three (3) system analysis, overview of the

chapter, analysis of the existing system, exiting system characterization,

existing system flow chats, existing system dataflow diagrams, feasibility

analysis, new system requirements hardware requirements, software

requirement. Chapter four (4) system design overview of design, software

design etc. chapter five (5) testing and implementation, project summary,

changeover plane etc. chapter six (6) summery, conclusion,

recommendation of the project, Reference, and Appendix.

11
 CHAPTER TWO

LITERATURE REVIEW

2.0 OVERVIEW

Recent advancements in mobile technology have transformed emergency

response systems, particularly in fire incident reporting. The Android-based

Fire Incident Reporting System leverages the widespread use of

smartphones to provide real-time data transmission, location services, and

multimedia support, which significantly improves the speed and accuracy

of fire emergency responses. The Android-Based Fire Incident Reporting

System is designed to modernize and streamline the process of reporting

fire emergencies by leveraging mobile technology. Traditionally, fire

reporting has relied heavily on phone calls and manual logging, both of

which can be time-consuming and prone to delays or errors, especially in

high-stress situations. This proposed system addresses these issues by

enabling real-time fire reporting through an accessible mobile app that is

available on Android devices, which have a large user base worldwide.

Through this mobile app, users can report fire incidents instantly with

details that are crucial for emergency, fire severity, and any immediate

dangers present at the scene. By minimizing these communication gaps, the

system ensures that emergency responders have accurate data from the

onset, reducing the likelihood of delays due. The global adoption of

12
Android devices, makes it an ideal platform for developing emergency

reporting systems that are accessible to a broad audience. These systems

are designed to leverage the capabilities of mobile devices—such as real-

time data transmission, GPS, and multimedia sharing. The use of mobile

technology, particularly in the Android ecosystem, has proven to be highly

effective due to the wide adoption of Android smartphones globally. Chien,

Hsu, and Liu (2019) noted that Android’s open-source nature allows

developers to create customized applications that cater to specific regional

needs. The system has been designed with scalability in mind, meaning it

can be adapted for use across various regions or even internationally. While

it relies on Android technology, which is accessible to many, the system

could be expanded to include other platforms or integrate with existing

local emergency services frameworks, making it flexible and versatile for

diverse community needs. This scalability also means that as mobile

technology evolves, the system can continue to integrate new features or

adapt to advancements. This flexibility is crucial in the development of fire

incident reporting systems, as they can be tailored to local emergency

response protocols and integrated with existing frameworks. Android's

dominance in global smartphone markets further amplifies the potential

reach and impact of these systems, especially in developing regions where

access to technology may be limited but growing. Recent studies

13
underscore the benefits of mobile-based emergency systems. Smith and Liu

(2020) highlighted that mobile applications can significantly reduce the

time it takes for emergency services to receive critical information about an

incident. This is especially important in fire emergencies where delays in

reporting can lead to extensive damage and loss of life. The real-time

communication feature of such systems enables users to provide precise

location data and additional details, such as the severity of the fire, which

can greatly assist emergency services in making informed decisions. The

Android-based system’s integration with existing emergency response

infrastructures makes it adaptable and versatile. Fire departments and

emergency response centers can access the real-time data through a

dedicated web interface or dashboard, allowing them to continuously

monitor incoming reports and adjust response strategies as needed. This

adaptability is vital for scalable deployment, meaning the system can be

tailored to different regions, from densely populated urban centers to rural

communities with limited emergency support. the Android Fire Incident

Reporting System represents a significant advancement in emergency

management, combining modern technology with intuitive user design to

improve public safety. By empowering citizens to report incidents quickly

and accurately, the system fosters a collaborative approach to emergency

response, which ultimately benefits both individuals and communities.

14
2.1 CURRENT PRACTICES AND INNOVATIONS

Mobile technology has revolutionized the way we respond to emergencies.

Mobile applications designed for emergency reporting have emerged as

communicate with first responders. These apps leverage the power of

smartphones to provide critical information, such as incident details and

GPS-based locations, thereby enhancing response times and saving lives.

Android-based fire incident reporting systems are gaining increasing

attention in recent years due to the rapid proliferation of mobile technology

and the need for more efficient emergency response mechanisms. These

systems utilize Android smartphones' capabilities to provide a platform

where users can report fire emergencies in real-time, supplying emergency

services with critical data such as the incident's location, severity, and

potential hazards. Nguyen et al. (2022) developed a mobile-based fire

reporting system that integrates GPS for location accuracy and cloud

computing for data management. Their research highlights the system’s

effectiveness in urban areas, where accurate location tracking and

immediate data transmission are critical. According to the authors, the use

of cloud computing ensures real-time updates and storage, allowing

emergency responders to make informed decisions based on comprehensive

data that is easily accessible and continually updated (Nguyen et al., 2022).

The system is designed to improve the overall response time, resource

15
allocation, and coordination between emergency teams, a critical factor in

managing fire incidents effectively (Chen, Wang, & Li, 2022). Mobile-

based reporting systems are transforming how emergency situations are

handled globally, as noted by Smith and Liu (2020), who emphasize that

these systems have drastically reduced the communication lag traditionally

associated with fire emergencies. In their study, they found that mobile

applications, especially those integrated with GPS and real-time data

transmission, can cut the response time by up to 30%, a significant

improvement compared to traditional methods like phone calls or manual

reporting. Another key aspect of these systems is their ability to integrate

multimedia data such as images and videos. According to Chen, Wang, and

Li (2022), this multimedia capability allows first responders to gain a

clearer understanding of the situation before arriving at the scene, further

enhancing their preparedness. Such features help bridge the gap between

reporting and actual on-ground scenarios, offering a more comprehensive

approach to emergency management. The flexibility of Android’s open-

source platform allows developers to tailor fire incident reporting systems

to local needs, making it a scalable solution for different regions. For

instance, Johnson and Patel (2021) explored the adaptability of Android-

based systems in regions with varying levels of technological

infrastructure, noting that the platform’s customizability makes it ideal for

16
diverse geographical areas. This adaptability is essential as different

regions require different levels of integration with local emergency

services, making the system flexible enough to accommodate varying

needs.

2.1.1 ADVANTAGE OF PROPOSED SYSTEM

The proposed Android-based Fire Incident Reporting System offers several

advantages that can significantly improve the speed, accuracy, and

effectiveness of fire emergency response. These benefits are particularly

important in today’s increasingly interconnected world, where rapid

communication is essential for minimizing damage and saving lives.

• Incident Reporting: One of the key advantages of the system is its

ability to enable real-time reporting of fire incidents. Traditional methods,

such as phone calls to emergency services, often involve time delays due to

the need for manual data entry and communication.

• Improved Resource Allocation: By providing detailed information

about the type and severity of the fire, the system allows emergency

services to better allocate their resources. Fire departments can prioritize

incidents based on urgency, ensuring that the right equipment and personnel

are dispatched to the right location.

17
• Enhanced Public Safety and Awareness: The system empowers the

public to play a more active role in fire prevention and safety. With the

application’s user-friendly interface, citizens can easily report fire hazards

or potential fire risks before they escalate into emergencies.

• The application will send GPS coordinate to location: the application

will help user with a GPS to track an locate the current and exact location

2.1.2 HOW THE SYSTEM WORKS

The Android-based Fire Incident Reporting System allows users to report

fire emergencies in real-time through a mobile app. After registering, users

can submit a report by providing details such as the fire’s location

(automatically captured via GPS). This information is immediately

transmitted to the nearest fire department, enabling emergency services to

respond quickly with precise data on the incident. Emergency teams can

view the report and plan the fastest route to the scene, reducing response

times and improving resource allocation.

2.2 FEASIBILITY STUDY

A system is feasible, if the goal and requirement can be satisfied within the

limited available resources and technology. In this study I searched for

diffident solution strategies to be devised for the system and each of the

18
solution strategies toughly analyzed before arriving at the final module for

the system. Some consideration in the feasibility analysis of the system are:

2.2.1 TECHNICAL FEASIBILITY

The technical feasibility of the system is high due to the widespread

availability and adoption of Android smartphones. Android, as an open-

source platform, offers flexibility for developers to build applications with

GPS integration, multimedia features, and real-time data transmission

(Android Open Source Project, n.d.). Most Android devices are equipped

with the necessary hardware and software, including internet connectivity

and GPS, to support real-time incident reporting (Mohanty et al., 2020).

Additionally, the integration of multimedia inputs (photos, videos) into fire

reports is feasible, as modern Android devices can easily handle these

features.

2.2.2 ECONOMIC FEASIBILITY

Developing and maintaining the system is economically feasible as the

development of Android applications is cost-effective compared to

proprietary platforms (Statista Research Department, 2023). The primary

costs will include app development, server infrastructure, user support, and

regular maintenance. The potential benefits, such as reduced response times

and improved fire management, can offset these costs by saving lives and

reducing property damage (Haddow & Bullock, 2022). Since the proposed

19
system's expected benefits equal or exceed the expected costs, the proposed

system is therefore feasible. The proposed system will be available and

affordable for all users. It has to do with establishing the cost-effectiveness

of the proposed system.

2.2.3 OPERATIONAL FEASIBILITY

To use the developed application, the user needs an Android OS-based

smartphone with version 4.0 or higher and internet support on the phone

(Android Developers, n.d.). With these components, it is preferable to use

the new system compared to the old system because it prevents time waste.

The proposed system is feasible in the sense that it will be time (operation)

considerate. Its operation will benefit the organization, and there is a high

possibility of using the system effectively by the user after being developed

and implemented (Kwan & Lee, 2022).

20
 CHAPTER THREE

SYSTEM ANALYSIS

3.0 OVERVIEW

This chapter looks at the operational status of the current system to see

whether or not a computerized system could be designed to ease the

difficulties encountered during the system’s operation. The chapter

comprises of system analysis, System flowchart and data flow diagram that

shows how the user can log in and access it services, feasibility study and

new system hardware and software requirements.

3.1 ANALYSIS OF EXISTING SYSTEM

The existing system in various fire reporting system includes either manual

work. The present system is an undeveloped form and the manual process

of the overall system is too clumsy and complicated. This analysis involved

detailed study of the current system leading to specification of a new

system. Analysis is a detailed study of various operations performed by a

system and their relationship within and outside the system. System

analysis also includes sub-devising of complex process involving the entire

system, identification of data store and manual process

21
3.1.1 EXISTING SYSTEM CHARACTERIZATION

Traditional fire reporting systems, often reliant on manual processes, which

include the following.

• Bystander Intervention

• Telephone

• Mass media

• Town crier

Bystander Intervention: involves individuals physically reporting a fire or

taking immediate action to alert others. This can include shouting to warn

nearby people, running to the nearest fire station, or using a public phone to

call emergency services. Bystanders might also assist in guiding people to

safety or helping contain small fires if safe to do so.

Telephone: is a type key tool for reporting fires by directly connecting

individuals to emergency services, fire departments, or local authorities.

When a fire is spotted, a bystander manually dials the emergency hotline or

a designated number to report the incident, providing details like the

location and severity of the fire. This method relies entirely on the caller’s

22
ability to convey accurate information and on the responders to act quickly

based on the report.

Mass media: mass media plays a critical role in fire reporting by

disseminating information through traditional channels like radio,

television, online newspapers, and public announcements. Fire incidents

can be reported to media outlets, which then broadcast alerts, safety

instructions, and updates to the public.

Town crier: Town crier plays a vital role in spreading fire alerts and safety

information within a community. The town crier, often equipped with a bell

or drum, moves through neighborhoods announcing fire incidents,

evacuation instructions, and safety measures loudly. This traditional

method ensures that critical information reaches people quickly, especially

in areas without modern communication systems, helping to coordinate

responses and reduce harm during emergencies.

23
3.1.2 EXISTING SYSTEM FLOWCHART

Fig 3.1 Flow chart of existing system

Figure 3.1 above is a flowchart of the current system. The flowchart

illustrates the process of responding to a fire outbreak, starting with the

event's occurrence, call for attention is made, either by bystander

intervention. If bystanders act, immediate action is taken; otherwise,

alternative communication methods like telephone, mass media, or a town

crier are utilized to spread the alert. If no call for attention is made, the

situation results in a disaster.

24
3.1.3 EXISTING SYSTEM DATA FLOW DIAGRAM

This dataflow diagram explains how the data flows work in the existing

system.

Fig 3.2 Diagram of existing system data flow

Figure 3.2 Above shows the existing system data flow diagram. The first

thing in the manual fire reporting system. First thing incident must happen,

then witness will report to the emergency call center, forward the request to

fire department, the fire department will allocate resource and take actions.

3.2 ANALYSIS OF THE NEW SYSTEM

The proposed Android-based Fire Incident Reporting System introduces

innovative solutions to enhance fire emergency management. Key features

such as real-time reporting, GPS integration, a user-friendly interface and

broad accessibility, the system surpasses traditional methods by offering

25
faster response times, improved accuracy, and enhanced coordination. By

facilitating faster reporting and response, the system has the potential to

reduce fire damage, improve emergency services, and foster public

engagement in fire prevention and response efforts.

3.2.1 NEW SYSTEM CHARACTERIZATION

In this system, it aiming to reduce fire damage, improve the operational

effectiveness of emergency responders. By leveraging mobile technology,

the system offers features such as real-time reporting, GPS-based location

tracking. Key components of the system include an incident reporting

module for capturing essential details, a centralized database for storing

and analyzing reports, and a dashboard for authorities to monitor and

manage responses. These functionalities collectively enhance efficiency,

scalability, and accessibility for emergency services. Its compatibility with

Android devices ensures widespread adoption, offering a reliable solution

to revolutionize fire incident reporting and management globally.

Some of the characteristics of the New System:

i. Real-Time Reporting: Immediate reporting of fire incidents via a

mobile app.

ii. GPS Location Tracking: Automatic and precise identification of

incident locations.

26
iii. User-Friendly Design: Intuitive interface for easy use by all

individuals.

iv. Database System: Centralized storage and analysis of fire incident

data.

v. Dashboard for Authorities: Real-time monitoring and management of

fire emergencies.

3.2.2 FLOW CHART OF THE NEW SYSTEM

Fi

g 3.3 Diagram of new system flow chart

27
Figure 3.3 Above shows the new system data flow diagram. This flowchart

begins with a user initiating the process start, and deciding whether they

want to register. If they register successfully, they proceed to log in. At the

decision point for valid logins, the system branches into two roles: Admin

and User. Admins are responsible for system management, including

viewing user requests, assigning the required fire response team, viewing

the location of incidents, responding to users, and updating fire team

members as necessary. These actions ensure that emergencies are handled

efficiently. While the User login can report emergency, can view the state

of the request, and add more detail to the incident occur

3.2.3 DATAFLOW OF A NEW SYSTEM

Fig 3.4 diagram of new system data flow

28
The data flow diagram (DFD) is an example of model used by system

analysis. Is a tool that describes the flow of data through a system analysis.

Its is a tool that describe the flow of data through a system and work

performed by the system, they are easy to read and consist of different

steps. The above diagram shows how data flow in the new system works

3.3 FEASIBILITY ANALYSIS

Feasibility analysis is used to assess the strength and the weakness of a

proposed project and present direction of activities in which it improves the

project and the achievement of a desired, the new system is having more

features and is user friendly very.

Strength of the software system

i. It’s utilized internet service and fast in response

ii. User friendly

iii. It allows GPS location

iv. A unique login system

Weaknesses of the software system

i. It must be connected to the internet to be effectively used

ii. This application is not useful if the user has not registered

iii. The economic requirement to develop the system and maintain it is

highly cost.

29
3.4 HARDWARE REQUIREMENT

i. Full computer set.

ii. Stable Internet connection

3.5 SOFTWARE REQUIREMENT

i. Operating system preferable (windows 10)

ii. Database: MySQL

iii. Browser (i.e chrome, firefox or uc browser)

iv. Tools: html, PHP, JavaScript, Css

v. Technology used: (App geyser) for android app conversion

30
 CHAPTER FOUR

SYSTEM DESIGN

4.0 OVERVIEW

The system is designed to meet a specific need. So, in this chapter we shall

focusing on how the system is designed talking about the software and

database design consisting of tables and interfaces of the new system

4.1 SOFTWARE DESIGN

The system is a mobile based app powered by android operating system

and developed using app geyser in order for any form of android mobile

system to be built in an efficient and use-friendly way, a highly structured

and well-engineered design has to be created. The design of a mobile

application has to follow certain steps in achieving its aims.

4.1.1 THE U.M.L DIAGRAM (UNIFIED MODELING LANGUAGE)

The UML (Unified modeling language) is a language for specifying

visualization and documentation the system. This is the step while

developing any product after analysis of the goal, is to produce a model of

the entities involved in the project which later need to be built. The

representations of the entities that are to be used in the product develop

31
need to be designed, there is various kind the method in software design

this are as follow:

i. Class diagram

ii. Interaction diagram

iii. Object diagram

iv. Use case diagram

4.1.2 CLASS DIAGRAM

Class diagram is uml diagram type. It a type of statics structure diagram

that describes the structure of a system by showing the system’s class, their

attributes, operations (or method), and the relationship.

Fig 4.1 class diagram of Android-based Fire Incident Reporting System

32
4.1.3 INTERACTION DIAGRAM

Interaction diagram is a society of class, interface and other element that

work together to provide some cooperative behavior that’s bigger than the

summery of all its part

Fig 4.2 Interaction diagram of Android-based Fire Incident Reporting

System

33
4.1.4 OBJECT DIAGRAM

The object diagram represents an instance of a class diagram. Object

diagram contains values and shows relationship between individual class.

Fig 4.3 Object diagram of Android-based Fire Incident Reporting System

4.1.5 USE CASE DIAGRAM

The is a use case diagram model at its simplest, it is a representation of

user’s interaction with the system that show the relationship between the

Actor and User.

34
Fig 4.4 use case diagram of Android-based Fire Incident Reporting System

ACTOR DESCRIPTION

Table explaining the actor and description

Table 4.1 Actor description

ACTOR DESCRIPTION

Admin The admin manages the system, add

team members, assigned then to

various activities and respond to the

user request

User User report emergency incident to

the admin and can view the request

35
 the sent to the admin.

ACTOR DESCRIPTION

Admin The admin manages the system, add team members, assigned then

to various activities and respond to the user request

User User report emergency incident to the admin and can view the

request the sent to the admin.

4.2 DATABASE DESIGN

Database design is a collection of process that facilitate the designing,

development, and implementation of data. Database design involves

classifying data and identifying interrelationships. User will sign up using

the app and all the Details are saved in the database. If a fire incident occur,

user fills out a form with details (location). The admin will be sent a

notification that an incident is happening, the admin will organize team to

resolve the problem. The data base table are presented below.

4.2.1 E-R DIAGRAM

An entity relationship is also called entity relationship mode, it is a

graphical representation of entities and their relationship with each other.

Entity relationship describe the structure of a database with the help of a

diagram which is show below.

36
ENTITY RELATIONSHIP DIAGRAM (E-R DIAGRAM)

Fig 4.6 E-R Diagram of Android-Based Fire Incident Reporting System

The ER diagram illustrates the Android Fire Incident Reporting System,

detailing entities like User, Admin, Report, and Team and their

relationships. Users can report emergencies through the app, while admins

manage these reports and assign them to response teams. Key attributes

include user details, admin credentials, report specifics (e.g., location,

status), and team information (e.g., team ID, leader name).

4.2.3 TABLE SHOWING ALL FIELD AND DATA TYPES

ADMIN TABLE

Table 4.2 Admin Table

S/N NAME TYPE NULL

37
1 Aid int (10) No

2 Aadminname varchar (50) No

3 Aadminusername varchar (50) No

4 Amobilnumber varchar (50) No

5 Aemail Date No

6 Apassword Int(10) No

7. Aregisterdate Date No

USER TABLE

Table 4.3 User Table

S/N NAME TYPE NULL

1 Uid int (10) No

2 Ufullname varchar (50) No

3 Uemail varchar (50) No

4 Uusername varchar (50) No

5 Upassword Date No

6. udatercreated Date No

VIEW HISTORY TABLE

Table 4.4 view history table

S/N NAME TYPE NULL

1 vhid int (10) No

2 Vhrequestid nt (10) No

3 Vhstature varchar (50) No

38
4 vremark varchar (50) No

5 Vhpostdate Date No

TEAM TABLE

Table 4.5 Team table

S/N NAME TYPE NULL

1 Tid int (10) No

2 Teamname varchar (50) No

3 Tleandername varchar (50) No

4 Teamleadernumber int (10) No

5 tteammembers Varchar (100) No

6 tpostingdate Date No

REPORT TABLE

Table 4.6 Report Table

S/N NAME TYPE NULL

1 Rid int (10) No

2 Rfullname varchar (50) No

3 Rmobilenumber int (20) No

4 Rlocation Mediumtext No

5 Rmessage Varchar (50) No

6 rstatues Varchar (20) No

39
 7 Rpostdate Date No

8. Rcompletdate Date No

4.2.3 SQL statement

<?php session_start();

include('includes/config.php');

if(isset($_POST['login']))

session_start();

include_once('includes/config.php');

if (strlen($_SESSION['user_id']==0)) {

header('location:logout.php');

} else{

?>

$username=$_POST['username'];

$password=md5($_POST['password']);

40
 $query=mysqli_query($con,"select user_id,username from tbluser where

username='$username' && password='$password' ")

if($result>0){

$_SESSION['user_id']=$result['user_id'];

header('location:index.php');

} else{

echo "<script>alert('Invalid Login Details.');</script>";

?>

4.3 USER INTERFACE

Once the interfaces are specified, they are designed in detail. Following is

the User Interfaces in the initial iteration of design.

ADMIN PAGE: This is the admin page also the dashboard of the admin

where all task that is required to be done by the admin.

41
 Fig 4.5 admin panel

MANAGE NEW FIRE REPORTING: this panel is also controlled by the

admin, it is used to manage, view the request for the user.

Fig 4.6 Manage new fire reporting

42
REPORT DATE: This parcel can only be seen and managed by the admin.

The admin can see the date by which a user reports an incident.

Fig 4.7 Report date

USER INTERFACE: When the incident happens, the user can report

thorough this media by clicking the fire reporting icon.

43
 Fig 4.8 User interface

REPORTING PANEL: This part is where the use fills the required form

and submit it to the admin so as to take an immediate action.

Fig 4.9 Reporting panel

4.4 SYSTEM DEPLOYMENT AND PACKAGING

System deployment is the process of installing a given software or system

of the purpose of usage the guild and information needed for the smooth

use of the system is documented in the user and maintenance guild. For this

system, the packaging is done in android studio as apk so the system is

installed in an android phone and it’s good to go.

44
 CHAPTER FIVE

TESTING AND IMPLEMENTATION

5.0 SYSTEM TESTING

The system testing tests the entire system to make sure that the system

meets the user’s requirement. Once the code has been generated, program

testing begins. The testing process focuses on the logical internal of the

application ensuring that tall the statement have been teste.

The system testing is a level of software testing where a complete and

integrated software is tested. The purpose of this test is to evaluate the

system’s compliance with the specified requirements.

Admin testing

S/N Test modules Objective Statues

1. Admin login To verify if the admin can access Successful
the dashboard with valid
credentials.
2. User To verify users can register and
Successful
Registration/Login log in to the system successfully.
3. Location Tracking Location Tracking Successful
4. Notification To verify that notifications are Successful
Dispatch sent to the appropriate
emergency services.
5. Error Handling To ensure the system handles Successful

45
 errors gracefully (e.g., invalid
input).
User testing

S/N Test modules Objective Statues

1. User registration To ensure users can create an Successful
account
2. User Login To verify that registered users can
Successful
log in to the system.
3. Fire Report To confirm users can submit fire Successful
Submission incident reports with all required
details.
4. To verify the app retrieves the Successful
Location
user’s GPS location for incident
Tracking
reports.
5. Error Handling To ensure the system provides Successful
proper feedback for invalid input
or actions.

5.1 CHANGE OVER PLAN

The changeover plan focuses on how the Android-based Fire Incident

Reporting System will replace traditional reporting methods to improve

operational efficiency and minimize delays. Unlike the existing systems,

which rely on manual processes and are often disconnected from each

other, the new system integrates GPS tracking and real-time data

transmission for seamless reporting.

46
The traditional methods, such as phone calls or manual alerts, often fail to

provide accurate location data or timely communication with emergency

services. However, with the proposed Android-based Fire Incident

Reporting System, reporting fire incidents becomes more efficient and

accurate. Using GPS-enabled smartphones, users can quickly share precise

locations and incident details, streamlining emergency response operations

and ensuring faster dispatch of resources.

5.1.1 DIRECTION CHANGE OVER PLAN

The direct changeover plan is feasible for implementing the Android-based

Fire Incident Reporting System, as it allows users to transition from

traditional reporting methods to the new system seamlessly. The application

is designed to simplify and enhance the user experience, ensuring that

individuals can quickly and efficiently report fire incidents with minimal

disruption. The Android-based system can fully replace the functions of the

existing manual or phone-based reporting methods. It leverages modern

mobile technology, such as GPS integration and real-time data sharing, to

address inefficiencies inherent in traditional systems.

The direct changeover approach was chosen because it is straightforward,

more efficient, and saves time by eliminating the delays associated with

phased or parallel implementation methods. This ensures that users can

immediately benefit from the improved features and functionalities of the

47
new system, such as faster reporting, precise location tracking, and

automated emergency notifications.

5.2 IMPLEMENT ENVIRONMENT

The Android-based Fire Incident Reporting System will be highly

beneficial to users who have access to an Android smartphone and need an

efficient way to report fire emergencies. By installing the application, users

can quickly report incidents from their location, providing real-time

information to emergency services without the stress and inefficiency

associated with traditional methods.

This system empowers users to engage in fire reporting with ease, ensuring

that critical details such as location and severity of the fire are

communicated effectively. Unlike traditional methods that may be

cumbersome or yield delayed responses, the Android-based system

simplifies the process, making it accessible and user-friendly for all.

48
 CHAPTER SIX

SUMMARY, CONCLUSION, AND RECOMMENDATION

6.0 SUMMARY

This project discussed the development of an Android-based Fire Incident

Reporting System aimed at providing an efficient and effective means of

reporting fire outbreaks. The system is designed with a user-friendly

interface to enhance usability and accessibility. By leveraging technology,

the application facilitates quick response to fire incidents, potentially

reducing property damage and saving lives.

6.1 PROJECT OUTCOMES, REQUIREMENTS, AND FULFILLMENTS

i. The application uses the internet to transmit fire incident reports to

relevant authorities.

ii. Users require a standard internet connection.

iii. The system ensures the accurate reporting of fire incidents, including

location details.

6.2 RECOMMENDATION

To maximize societal benefits, the following recommendations are

proposed:

49
The general public is encouraged to use this application to promptly report

fire incidents.

i. It is particularly recommended for organizations, schools, and

residential communities to enhance fire response measures.

ii. Security authorities such as fire service departments and emergency

response teams should adopt this system to improve their efficiency and

effectiveness.

iii. Future developers of this application should address any existing

limitations and introduce additional features to enhance its functionality,

such as offline capabilities or integration with emergency response systems.

6.3 CONCLUSION

An Android-based Fire Incident Reporting System has been successfully

developed to aid in reporting fire incidents quickly and efficiently. This

system has the potential to significantly reduce the loss of life, property

damage, and environmental harm caused by fire outbreaks. By providing an

accessible and reliable reporting platform, this application contributes to

improving emergency response efforts and promoting community safety.

50
51
 REFERENCES

Brown, R., & Smith, J. (2020). Challenges in Mobile Emergency Reporting

Systems. Journal of Emergency Management, 15(4), 289-305.

Chen, Y., Wang, Z., & Li, H. (2022). Future Trends in Mobile-Based

Emergency Reporting Systems: AI and ML Integration. International

Journal of Emergency Technology, 11(2), 56-72.

Chien, C., Hsu, C., & Liu, J. (2017). Real-Time Mobile Emergency

Reporting Systems: A Review. Computers in Human Behavior, 66, 280-

290.

Johnson, L., & Patel, R. (2021). Designing User-Friendly Mobile Reporting

Applications. Human-Centric Computing and Information Sciences, 11(1),

45-62.

Lee, S., Park, K., & Choi, M. (2019). Enhancing User Experience in

Mobile Emergency Reporting Applications. Journal of Usability Studies,

14(2), 90-105.

Nguyen, T., Lee, D., & Kim, S. (2019). Case Studies in Mobile Fire

Reporting Systems: Lessons from Singapore and Los Angeles. International

Journal of Public Safety, 7(4), 212-229.

52
Smith, A., & Liu, H. (2020). Advances in Mobile and GPS Technology for

Emergency Management. Technology in Emergency Services, 14(1), 34-

50.

Zhang, Q., Li, X., & Sun, Y. (2021). Integrating Mobile Reporting Systems

with Emergency Response Frameworks. Journal of Disaster Management,

17(3), 245-260.

53
 APPENDIX A

SOURCE CODE

<?php session_start();

include('includes/config.php');

if(isset($_POST['login']))

$uname=$_POST['username'];

$Password=md5($_POST['inputpwd']);

$query=mysqli_query($con,"select ID,AdminName,isActive from

tbladmin where AdminuserName='$uname' && Password='$Password' ");

$ret=mysqli_fetch_array($query);

if($ret>0){

$_SESSION['aid']=$ret['ID'];

header('location:dashboard.php');

} else{

echo "<script>alert('Invalid Details.');</script>";

<meta name="description" content="">

<meta name="author" content="">

<title>Admin Login</title>

<!-- Custom fonts for this template-->

<link href="vendor/fontawesome-free/css/all.min.css" rel="stylesheet"

type="text/css">

54
 <link

href="https://fonts.googleapis.com/css?
family=Nunito:200,200i,300,300i,400,400i,600,600i,700,700i,800,800i,90
0,900i"

rel="stylesheet">

<!-- Custom styles for this template-->

<link href="css/sb-admin-2.min.css" rel="stylesheet">

</head>

<body>

<div class="container">

<!-- Outer Row -->

<div class="row justify-content-center">

<div class="col-xl-10 col-lg-12 col-md-9">

<?php $query=mysqli_query($con,"select * from tblsite");

while($row=mysqli_fetch_array($query)){

$logo=$row['siteLogo'];

$wtitle=$row['siteTitle'];

} ?>

<p align="center">

<img

src="uploadeddata/<?php echo $logo;?>"

width="150"> </p>

<h3 align="center" style="margin-top:4%;color:#fff"><?php echo

$wtitle;?></h3>

55
 <div class="card o-hidden border-0 shadow-lg my-5">

<div class="card-body p-0">

<!-- Nested Row within Card Body -->

<form name="login" method="post">

<div class="row">

<div class="col-lg-6 d-none d-lg-block bg-login-

image"></div>

<div class="col-lg-6">

<div class="p-5">

<div class="text-center">

<h1 class="h4 text-gray-900 mb-4">Welcome

Back Admin!</h1>

</div>

<form class="user">

<div class="form-group">

<input type="text" class="form-control"

name="username"

id="username" placeholder="Enter
username" required="true">

</div>

<div class="form-group">

<input type="password" class="form-control"

name="inputpwd"

id="inputpwd" placeholder="Password">

</div>

56
 <input type="submit" name="login" class="btn btn-primary
btn-user btn-block" value="login">

</form>

<hr>

<div class="text-center">

<!-- <a class="small" href="password-

recovery.php" style="font-weight:bold">Forgot Password?</a> -->

</div>

<div class="text-center">

<a class="small" href="../logout.php" style="font-

weight:bold;"><i class="fa fa-home" aria-hidden="true"></i> Home
Page</a>

<!-- Bootstrap core JavaScript-->

<script src="vendor/jquery/jquery.min.js"></script>

<script src="vendor/bootstrap/js/bootstrap.bundle.min.js"></script>

<!-- Core plugin JavaScript-->

<script src="vendor/jquery-easing/jquery.easing.min.js"></script>

<!-- Custom scripts for all pages-->

<script src="js/sb-admin-2.min.js"></script>

<div class="content py-5 mt-5">

<div class="container">

<div class="card card-outline card-warning shadow rounded-0">

<div class="card-header">

<h4 class="card-title">My Booking List</h4>

57
</div>

<div class="card-body">

<table class="table table-striped table-bordered">

<colgroup>

<col width="5%">

<col width="20%">

<col width="20%">

<col width="30%">

<col width="10%">

<col width="15%">

</colgroup>

<thead>

<tr>

<th class="text-center">#</th>

<th class="text-center">Date Booked</th>

<th class="text-center">Ref Code</th>

<th class="text-center">Details</th>

<th class="text-center">Status</th>

<th class="text-center">Actions</th>

</tr>

</thead>

<tbody>

<?php

$i = 1;

58
 $qry = $conn->query("SELECT * FROM `booking_lists`
where cab_id = '{$_settings->userdata('id')}' order by
unix_timestamp(date_created) desc");

while($row = $qry->fetch_assoc()):

?>

<tr>

<td class="text-center"><?= $i++; ?></td>

<td><?= date("Y-m-d H:i",

strtotime($row['date_created'])) ?></td>

<td><?= $row['ref_code'] ?></td>

<td>

<p class="m-0 truncate-1">Pickup: <?=

$row['pickup_zone'] ?></p>

<p class="m-0 truncate-1">Dropoff: <?=

$row['drop_zone'] ?></p>

</td>

<td class="text-center">

<?php

switch($row['status']){

case 0:

echo "<span class='badge badge-secondary bg-

gradient-secondary px-3 rounded-pill'>Pending</span>";

break;

case 1:

echo "<span class='badge badge-primary bg-

gradient-primary px-3 rounded-pill'>Driver Confirmed</span>";

59
 break;

case 2:

echo "<span class='badge badge-warning bg-

gradient-warning px-3 rounded-pill'>Picked-up</span>";

break;

case 3:

echo "<span class='badge badge-danger bg-

gradient-danger px-3 rounded-pill'>Cancelled</span>";

break;

?>

</td>

<td class="text-center">

<button type="button" class="btn btn-flat btn-light

border btn-sm view_data" data-id="<?= $row['id'] ?>">View</button>

<a href="?p=map&id=<?php echo $row['id'] ?>">

<button type="button" class="btn btn-flat btn-light

border btn-sm view_data" data-id="<?= $row['id'] ?>">View
Map</button>

</a>

</td>

</tr>

<?php endwhile; ?>

</tbody>

</table>

<script>

60
 $(function(){

$('table th, table td').addClass('px-2 py-1 align-middle')

$('table').dataTable();

$('.view_data').click(function(){

uni_modal("Booking Details","view_booking.php?id="+$
(this).attr('data-id'))

})

})

</script>

</body>

</html>

61
 APPENDIX B

SNAP SHOTS

ADMIN PANEL

ENTERING REPORT

62
REPORTING PANEL

REPORT DATE

63