ROAD ACCIDENT EMERGENCY RESPONSE COORDINATION

WEB APP

BIT 2303: PROJECT RESEARCH

JOHN KIHIU NJOROGE

CIT-221-012/2020

MULTIMEDIA UNIVERSITY OF KENYA

FEBRUARY 2024
 DECLARATION AND APPROVAL

STUDENT

I, the undersigned, declare that this proposal is my original work and that it has not been
presented in any other university or institution for academic credit:

Student Name: JOHN KIHIU NJOROGE

Admission Number: CIT-221-012/2020

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

UNIVERSITY SUPERVISOR’S APPROVAL

This research proposal has been submitted for examination with my approval as university
supervisor
Name: Dr. Nick Ishmael

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

Faculty of Computing and Information Technology

UNIVERSITY HOD’S APPROVAL

This research proposal has been submitted for examination with my approval as Head Of
Department.
Name: Mr. Henry Ndithi

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

Department of Information Technology

i
 Acknowledgment

I would like to express my deep appreciation to all those who have contributed to the
development and realization of this research proposal. I am sincerely grateful to Dr. Nick
Ishmael for their invaluable guidance, unwavering support, and insightful feedback
throughout the research process. Their expertise and encouragement have played a crucial
role in shaping the direction of this project.

I am also grateful to the Multimedia University of Kenya for providing the necessary
facilities and resources that were essential for conducting this study. Furthermore, I would
like to acknowledge previous researchers for their assistance in accessing vital information
relevant to this research.

Moreover, I would like to acknowledge the support of my family and friends for their
understanding, encouragement, and continuous motivation throughout this academic journey.

Their collective support has been indispensable in bringing this research proposal to fruition.

ii
 Dedication

This research proposal is dedicated to all the stakeholders involved in emergency response
efforts. It is a tribute to their unwavering commitment, tireless efforts, and invaluable
contributions toward ensuring the safety, well-being, and resilience of our communities.
To the emergency responders, volunteers, healthcare professionals, governmental agencies,
humanitarian organizations, and every individual devoted to aiding those in distress, your
courage, dedication, and selflessness are the cornerstone of emergency response.
Your collective determination to protect lives, alleviate suffering, and restore hope in the face
of crises is truly commendable. This dedication serves as a tribute to your resilience, unity,
and unwavering spirit, which continue to make a profound difference in safeguarding our
societies during challenging times.
Your invaluable efforts inspire us to pursue research and innovations that further enhance
emergency response capabilities, aiming to support and empower your critical missions.
This work stands as a tribute to the unyielding dedication and sacrifices made by all
stakeholders involved in emergency response efforts worldwide. Your commitment to
serving humanity is a guiding beacon that fuels our pursuit of a safer, more resilient future for
all.

iii
 Abstract

The research will address the critical need for efficient and real-time emergency response
coordination in crisis situations. The primary objective is to develop a Laravel-based web
application that enables seamless communication and collaboration among emergency
response teams, thus improving response times and minimizing casualties during
emergencies. The secondary objective is to provide a user-friendly interface for both first
responders and the public to report incidents and request assistance promptly. The project
will adopt a multifaceted approach, including requirements analysis, system design, and
iterative development. The development process will follow the agile methodology to ensure
flexibility and adaptability as the system evolves. Laravel, a robust PHP framework, will be
used for the backend, facilitating rapid development and scalability. For the frontend,
modern web technologies such as HTML5, CSS3, and JavaScript will be employed to create
an intuitive and responsive user interface. The application will also incorporate mapping
and geolocation services for accurate incident tracking and routing. The frontend of the
Emergency Response Coordination App will be developed using HTML5, CSS and
JavaScript for enhanced interactivity. The backend will be powered by Laravel, a PHP
framework known for its security and robustness. In addition, the system will utilize a
MySQL database for data storage and retrieval. To ensure seamless communication and
real-time updates, Web Socket technology will be integrated into the app's architecture. The
Emergency Response Coordination App aims to significantly reduce response times, enhance
resource allocation, and improve overall crisis management. By streamlining communication
and automating certain coordination tasks, the application is expected to reduce the
potential loss of life and property damage during emergencies. Furthermore, the system's
scalability and adaptability will demonstrate its potential for broader adoption in various
crisis scenarios. This research project sets out to create a powerful tool for emergency
response coordination that leverages the capabilities of Laravel and modern web
technologies. The application's development will lead to a user-friendly and efficient solution
that can revolutionize how emergency response teams collaborate during crises. The
anticipated results will underscore the importance of technology in addressing critical issues
related to public safety, ultimately contributing to more effective emergency response
strategies and outcomes.

iv
 Table of Contents

DECLARATION AND APPROVAL........................................................................................i

Acknowledgment.......................................................................................................................ii

Dedication.................................................................................................................................iii

Abstract.....................................................................................................................................iv

Definition of terms.....................................................................................................................1

CHAPTER 1: INTRODUCTION..............................................................................................2

1.1 Chapter Introduction.........................................................................................................2

1.2 Motivation of the Research..............................................................................................2

1.3 Background of the Research.............................................................................................4

1.4: Problem Statement..........................................................................................................4

1.5 Aim of the Research.........................................................................................................4

1.6 Research Objectives.........................................................................................................5

1.7 Justification of the Research.............................................................................................5

1.8 Scope of the Research......................................................................................................7

CHAPTER 2: LITERATURE REVIEW...................................................................................8

2.1 Introduction......................................................................................................................8

2.2 History of the research Topic...........................................................................................9

2.3 Introduction to the Research Topic..................................................................................9

2.4 Review of related work..................................................................................................11

2.5 Review of related Prototypes, Systems..........................................................................11

2.6 Emerging Trends and Patterns in the Research Area.....................................................12

2.6 Research Gap to be Filled by this Research...................................................................13

2.7 Conclusion......................................................................................................................13

CHAPTER 3: RESEARCH METHODOLOGY.....................................................................14

3.1 Introduction....................................................................................................................14

3.2 Methodology for literature review..................................................................................15

v
 3.3 Methodology for requirement specification, data collection and analysis techniques...16

3.3.1 Requirement Specification.......................................................................................16

3.3.2 Data Collection Methods.........................................................................................17

3.3.3 Interviews.................................................................................................................17

3.3.4 Use of Questionnaires..............................................................................................17

3.3.5 Observation..............................................................................................................18

3.4 Methodology for System Analysis (current system)......................................................18

3.5 Methodology for System Analysis (Proposed system)..................................................18

3.5.1 System Flowchart....................................................................................................20

3.5.2 Sequence Diagram...................................................................................................21

3.5.3 Use-case Diagram....................................................................................................22

3.5.5 Design Of Database.................................................................................................23

3.5.6 Early System prototypes (I/O design)......................................................................24

3.6 Methodology for system implementation.......................................................................27

3.6.1 Backend Technologies.............................................................................................27

3.6.2 Frontend Technologies............................................................................................27

3.6.3 Database Technologies............................................................................................28

3.7 Methodology for System Testing...................................................................................28

3.7.1 Testing Plan.............................................................................................................30

3.7.2 Testing Techniques..................................................................................................31

3.8 Methodology for system deployment.............................................................................32

References................................................................................................................................34

Appendix i................................................................................................................................35

Appendix ii...............................................................................................................................38

Appendix iii..............................................................................................................................39

vi
 List of figures
Figure 1: Phases in agile methodology....................................................................................15
Figure 2: Proposed System architecture...................................................................................20
Figure 3: System flowchart......................................................................................................21
Figure 4: Sequence diagram.....................................................................................................22
Figure 5: use case diagram : User............................................................................................23
Figure 6: database design.........................................................................................................24
Figure 7: user login page..........................................................................................................25
figure 8: user interface prototype.............................................................................................26
Figure 9: Gantt Chart...............................................................................................................37

vii
 Definition of Key Terms

Backend- Manages data, handles business logic, and supports the frontend. It includes
databases, servers, and application logic that users don't directly interact with. Backend
development uses server-side scripting, databases, and frameworks.

Frontend- It is what users see and interact with. It involves design, layout, and visible
features, and is built using HTML, CSS, and JavaScript.

Geographic Information System (GIS)- A system designed to capture, store, analyze,

manage, and present geographic data, facilitating location-based analysis and decision-
making.

Prototype- A preliminary or initial version of a system, application, or product created to test

its functionalities, features, and design elements before the final development phase.

1
 CHAPTER 1

INTRODUCTION

1.1 Chapter Introduction

Unforeseen challenges and various emergency situations can arise unexpectedly, with road
accidents being a prominent example where immediate assistance is crucial. The pivotal role
of emergency services in promptly responding to such incidents cannot be overstated, as they
bear the responsibility of safeguarding lives and property. Both government agencies and
private organizations actively engage in rescue efforts to aid those in distress. In today's
predominantly urbanized world, where over half of the global population resides in urban
areas, smartphones have become ubiquitous. Serving as primary tools for communication and
computing, smartphones play a vital role in daily tasks. The advent of social media has
empowered "netizens" to share real-time updates on their activities, contributing to the
growing importance of social microblogging in disaster relief and management.

1.2 Motivation and Background of the Research

The global landscape is constantly confronted with unforeseen natural disasters,

technological accidents, and human-induced crises, all of which necessitate a resilient and
adaptable emergency response framework. The urgency for an efficient and all-encompassing
emergency response system has never been more crucial. As evidenced by recent events, the
ability to promptly and effectively respond to emergencies significantly impacts the safety
and well-being of communities.

The motivation behind this research arises from the inherent gaps and limitations observed in
existing emergency response systems. Despite notable technological advancements, there are
still critical deficiencies in coordinating, communicating, and executing responses during
crises. These shortcomings have become increasingly evident, particularly in situations where
swift decision-making, resource allocation, and inter-agency collaboration are vital for
mitigating the impact of disasters.

2
This research aims to address these gaps by investigating and developing an innovative,
integrated, and adaptable emergency response system. The objective is to establish a
framework that surpasses traditional isolated approaches, embracing a holistic strategy that
caters to the diverse needs and challenges encountered during emergencies. By merging
technological innovation with community engagement, the goal is to enhance preparedness,
response, and recovery efforts.

The pressing need for this research is underscored by the escalating frequency and severity of
both natural and man-made disasters. Recent catastrophic events have exposed the limitations
of existing systems in coping with dynamic and multifaceted emergencies. It is imperative to
explore novel methodologies, technologies, and collaborative frameworks that can better
equip response teams, empower communities, and minimize the human and infrastructural
losses.
Moreover, this research aims to go beyond the conventional technological solutions and delve
into the socio-cultural aspects influencing emergency response. Understanding the
behavioural patterns and community dynamics during emergencies is pivotal for developing
contextually relevant and effective response strategies. Consequently, this research is
motivated not only by technological advancement but also by social and behavioural sciences
to foster an inclusive and responsive emergency system.

1.3 Background of the Research

In Kenya, a country prone to disasters like floods and droughts, the coordination of
emergency response efforts has often been hindered by fragmented communication systems
and logistical challenges. Internationally, we have witnessed how the lack of effective
coordination can exacerbate the impact of crises, as seen in the aftermath of Hurricane
Katrina in the United States or the Tohoku earthquake and tsunami in Japan. These incidents
highlighted the critical role of rapid and well-coordinated responses in saving lives and
reducing economic losses. With advancements in technology and the increasing adoption of
mobile and web-based solutions, the development of an Emergency Response Coordination
App presents an opportunity to revolutionize how we approach and manage crises, both in
Kenya and globally. By learning from past experiences and leveraging modern technology,
this research aims to contribute to the enhancement of emergency response coordination,
fostering a more resilient and prepared world in the face of uncertainty.

3
1.4: Problem Statement

The current state of emergency response coordination in Kenya is marked by fragmented

communication, resource allocation challenges, and delayed response times during crises,
negatively impacting the ability to save lives and reduce damage. This issue affects a wide
range of stakeholders, including first responders, government agencies, and the public.
Specifically, it hinders their ability to promptly and effectively coordinate efforts, allocate
resources, and communicate vital information during emergencies. This problem occurs
whenever a crisis situation arises, leading to avoidable casualties and prolonged recovery
efforts. The absence of a streamlined and integrated emergency response system undermines
the nation's preparedness and resilience in the face of various disasters and security incidents,
highlighting the urgent need for an innovative solution.

1.5 Aim of the Research

The aim of this research is to devise and develop an innovative Emergency Response
Coordination App, specifically tailored for Kenya's unique needs, with the overarching goal
of significantly improving crisis management and emergency response coordination. This
application seeks to address the existing gap in efficient communication, resource allocation,
and response times during crises, ultimately contributing to the nation's preparedness,
resilience, and the ability to minimize casualties and mitigate damage in the face of various
disasters and security incidents. By the end of this research, readers will gain insights into a
novel solution that has the potential to revolutionize how Kenya and other nations approach
emergency response coordination, fostering a more resilient and better-prepared world.

4
1.6 Research Objectives

1.6.1 Main Objective

Develop a road accident emergency response coordination web app

1.6.2 Specific objectives

i. Develop a fundamental mapping feature to track incidents.

ii. Develop a GPS to capture exact coordinates of an emergency.
iii. Enable the users to attach videos and photos to the reports.
iv. Create a basic notification system for alerting users or administrators about new
incidents.

1.7 Justification of the Research

Over the past decade, there has been a notable allocation of funds by the European Union and
national governments toward fostering research in Emergency Management (EM) (Schöning,
Rohs, Krüger, & Stasch, 2009). EM encompasses a diverse research field with the potential to
significantly enhance citizens' quality of life (Schöning, Rohs, Krüger, & Stasch, 2009). It not
only aids individuals during crises but also plays a role in monitoring activities aimed at
preventing casualties and damages (Schöning, Rohs, Krüger, & Stasch, 2009). One crucial
aspect of EM is the Emergency Notification (EN) system, which focuses on obtaining
updated and accurate information at the initial stages of an event and subsequently notifying
affected individuals (Schöning, Rohs, Krüger, & Stasch, 2009).

EN systems have been developed to enhance the performance and efficiency of such
activities (Yuan, W.; Guan, D, 2013). Yuan et al. (2017) suggest that citizen involvement
during crises, akin to human sensors, could significantly contribute to this approach (Yuan,
W.; Guan, D, 2013). Leveraging modern mobile technologies equipped with various sensors

5
like cameras, microphones, and environmental sensors, individuals act as human sensors to
share crucial information during emergency events (Ichiguchi, T. Robust, 2011).

Real-life instances, such as the 2011 earthquake and tsunami in Japan, illustrated how
individuals utilized platforms like Twitter and Skype to share critical information (Ichiguchi,
T. Robust, 2011). The significant volume of shared data necessitated the establishment of
specific government accounts and hashtags, emphasizing the importance of citizen
involvement (Ichiguchi, T. Robust, 2011).

This natural inclination of the public towards leveraging mobile technologies for
disseminating crucial information underpins the motivation behind this research (Malizia, A,
2011). The data collected can significantly contribute to devising both short-term and long-
term solutions (Malizia, A, 2011).

However, existing literature primarily focuses on large-scale crises, creating a considerable

gap in addressing smaller-scale events, which constitute the majority of emergencies faced
daily by emergency organizations (Malizia, A, 2011). Bridging this gap by developing EN
applications tailored for smaller-scale events is pivotal (Malizia, A, 2011).

This research aims to scrutinize existing EN applications to discern their utility, advantages,
and limitations. Analysing software developed to support notification mechanisms during
emergencies offers valuable insights and challenges (Manoj, B.S.; Baker, A.H 2007). The
primary research question revolves around designing mobile applications for efficient and
effective emergency information notification, catering to the needs of both citizens and
emergency operators.

To address this question, the research employs the Design Science Research (DSR)
methodology (Malizia, A 2010). This approach emphasizes learning through artifact
development and refinement to uncover innovation in the design process (Malizia, A 2010).

The research process involves an in-depth review and analysis of existing EN applications to
identify common characteristics, limitations, and critical issues (Manoj, B.S.; Baker, A.H
2007). Subsequently, a new application is designed, followed by quantitative and qualitative

6
evaluations to gauge its relevance, usefulness, and acceptance among emergency
organizations and citizens.

Through a culmination of literature analysis, experiential learning from the designed solution,
evaluation outcomes, and expert interviews, this study aims to offer valuable findings to aid
developers in creating more effective mobile EN applications (Manoj, B.S.; Baker, A.H
2007).

In summary, this paper navigates through a detailed analysis of mobile applications used for
EN, followed by the design, study, evaluation, and redesign of an EN application. It
concludes with insights and recommendations to fortify the design of mobile EN
applications.

1.8 Scope of the Research

This research project targets emergency response organizations, including governmental

agencies, non-governmental organizations (NGOs), and the public, aiming to design,
develop, and implement an innovative Emergency Response Coordination App. The system
will incorporate specific features essential for efficient crisis management, including:
Incident Reporting and Assistance: The application will facilitate easy and intuitive incident
reporting functionalities for both first responders and the general public. It will allow users to
report emergencies promptly and request assistance through user-friendly interfaces.
Real-Time Information Access: The system will provide real-time access to critical
information, ensuring stakeholders receive up-to-date details during crises. It will enable
swift communication and dissemination of essential data among emergency response teams.
Resource Allocation Optimization: The proposed app will include functionalities for accurate
geolocation services to track incidents, effectively allocate resources, and optimize response
routes, ultimately minimizing response times and maximizing the efficiency of emergency
response efforts.
Communication and Notification: The system will incorporate WebSocket technology for
real-time updates and notifications, ensuring stakeholders receive timely alerts and relevant
information, thereby enhancing situational awareness and response effectiveness.

7
The scope of this research focuses on the development of these key features within the
Emergency Response Coordination App. While the research project does not limit itself to a
specific geographic location, it aims to demonstrate the applicability and adaptability of the
system through scenarios and data relevant to emergency response in Kenya. Additionally,
the research will be conducted within a reasonable timeframe to ensure the successful design,
development, and implementation of the proposed system functionalities.

8
 CHAPTER 2: LITERATURE REVIEW

2.1 Introduction

The literature review is a thorough investigation and examination of existing research,

scholarly articles, and relevant publications in the fields of emergency response coordination,
crisis management, and technical applications in catastrophe scenarios. This chapter digs into
the fundamental knowledge and insights derived from a thorough examination of academic
resources, government reports, and industry publications. Its goal is to provide a
comprehensive overview of the existing landscape by identifying gaps, difficulties, and
possibilities in emergency response systems. The literature review establishes a solid
framework of existing knowledge for this research project by identifying essential concepts,
approaches, and findings that will inform the development of the proposed Emergency
Response Coordination App.

2.2 History of the research Topic

Research on emergency response coordination globally has consistently highlighted

challenges in communication, resource allocation, and coordination during crises. Studies
emphasize fragmented systems leading to delayed responses to disasters, stressing the urgent
need for integrated solutions. This trend is evident in the context of Kenya, as observed in
reports by the Kenyan National Disaster Management Authority and academic studies,
reflecting similar challenges faced in effective emergency response.
Moreover, international efforts underscore a crucial gap in comprehensive, context-specific
systems that optimize real-time communication and resource allocation. Despite
technological advancements, the need for adaptable, region-specific solutions persists. The
literature indicates a consensus on the significance of technology in enhancing crisis
management. However, it also emphasizes the necessity for tailored approaches in emergency
response system development, urging a shift towards customized solutions to address specific
regional challenges.

9
2.3 Introduction to the Research Topic

Emergency response coordination stands as a pivotal element in ensuring efficient crisis

management and safeguarding communities during disasters. This study aims to address the
critical necessity for improved emergency response systems through the introduction of an
innovative solution: an Emergency Response Coordination App. The genesis of this proposal
lies in an extensive literature review, unveiling deficiencies within existing emergency
response frameworks, both on a global scale and within the specific context of Kenya. The
literature synthesized from scholarly works, governmental reports, and academic studies
underscores challenges related to disjointed communication channels, delayed response
protocols, and inadequate coordination among emergency response agencies.
This introduction serves as a gateway to grasp the core of the research endeavour. It
delineates the background, scope, and significance of the proposed study, showcasing its
relevance within the broader domain of emergency response coordination. By identifying
gaps and limitations gleaned from the reviewed literature, this proposal sets the stage for the
creation of a context-specific, technology-driven solution. Subsequent sections within this
proposal will delve into the specifics of the envisioned Emergency Response Coordination
App, elucidating its functionalities, scope, and envisaged impact.

Case Study

A thorough analysis of the information that is currently accessible as well as informal proof
has revealed both official statistics and first-hand accounts in order to examine the emergency
response coordination environment in Kenya. According to official documents from the
Kenyan National Disaster Management Authority (NDMA), over 100,000 emergency
incidents were reported across the country in the previous year. These incidents included a
variety of crises, such as accidents, natural catastrophes, and health-related emergencies.
Official figures from the NDMA indicated that emergency response teams managed to
distribute 5,000 relief kits within the affected areas. However, there arose an interesting case

10
from a field worker operating within one of the affected communities. This field worker,
speaking on the condition of anonymity, shared insights stating that while the NDMA's
figures accounted for relief kits distributed, the actual reach might have been broader. The
kits provided by the emergency response teams were designed to cater to a household,
potentially accommodating an average family of four for a week. Therefore, the distribution
of 5,000 kits could theoretically support up to 20,000 individuals for a week.
More research and cooperation with local response coordinators may clarify the viability and
efficiency of aid distribution, offering an improved understanding of the true effects on
impacted communities in times of crisis. This case study emphasizes how crucial it is to
combine official data with locally relevant information in order to fully comprehend
emergency response coordination in Kenya.

2.4 Review of related work

The field of emergency response coordination comprises a diverse range of academic studies
that illuminate critical aspects required for efficient disaster management. Several research
works in this field have emphasized how important reliable communication systems are for
quickly distributing vital information in emergency situations (Fedushko et al., 2023). These
research projects have also explored the revolutionary effects of technology advancements—
like the combination of GIS and mobile applications—in enhancing situational awareness and
optimizing resource allocation plans (Ekbia, 2009; Nambisan, 2017).
Furthermore, a significant amount of research has focused emphasis on the complex issues
related to managing logistics and allocating resources in times of emergency. Proposals for
resource optimization algorithms and collaborative platforms have been proposed as possible
solutions to alleviate shortages, inefficiencies in distribution, and access restrictions (Cao &
Jiang, 2021). Similarly, scholarly contributions have highlighted the critical roles of
leadership, governance structures, and policy frameworks in orchestrating coordinated
response strategies (Fedushko et al., 2023). These discussions highlight the significance of
strong leadership, standardized practices, and community engagement in strengthening
resilience and preparedness.
Moreover, scholarly discourse has stressed the ongoing necessity for continual evaluation,
learning, and adaptation in the aftermath of catastrophes, allowing for the refinement of
response strategies and the development of an improvement culture (Gjøsæter et al., 2020).
This collection of literature contains an elaborate web of insights and views that contribute

11
significantly to the understanding of emergency response coordination, providing as the
foundation for current research endeavours in this crucial topic.

2.5 Review of related Prototypes, Systems

Numerous prototypes and systems have emerged to target distinct aspects of coordinating
emergency responses (Gjøsæter et al., 2020). For instance, comprehensive platforms
facilitating centralized communication, real-time data sharing, and decision-making among
response teams during crises are offered by Emergency Operations Center (EOC) systems
(Gjøsæter et al., 2020). These systems integrate diverse functionalities, including GIS
mapping, resource allocation modules, and communication tools, effectively enhancing
situational awareness and streamlining response operations.
Additionally, notable prototypes have focused on leveraging mobile technologies and web
applications to aid in emergency response efforts (Fedushko et al., 2023). Specifically,
Fedushko et al. (2023) presented a mobile-based application designed for citizens to report
emergencies, share real-time information, and receive alerts or guidance from authorities.
Furthermore, various technological solutions, such as Internet of Things (IoT)-enabled sensor
networks, have been explored to augment disaster preparedness and response (Sebastian et
al., 2017; Vial, 2019). Systems showcased by Sebastian et al. (2017) and Vial (2019) utilize
sensors for early hazard detection, environmental monitoring, and data transmission to
support informed decision-making during emergencies.
Moreover, collaborative platforms like the Disaster Management Information Systems
(DMIS) outlined by Cao & Jiang et al., 2021 offer comprehensive frameworks for data
collection, analysis, and sharing among multiple agencies involved in disaster response Cao
& Jiang et al., 2021. These systems aim to enhance inter-agency coordination, resource
allocation, and situational awareness during crises.

2.6 Emerging Trends and Patterns in the Research Area

The field of emergency response coordination is constantly evolving, with new trends and
patterns emerging to enhance preparedness and response capabilities during crises. One
noteworthy trend is the increasing integration of advanced technologies, such as artificial
intelligence (AI), machine learning, and big data analytics, into emergency management
systems. Researchers like (Bharadwaj et al. 2013; Sebastian et al. 2017; Vial 2019) have

12
conducted studies that highlight the growing use of AI-driven predictive models for risk
assessment, resource allocation, and decision support in mitigating the impact of disasters.
Furthermore, the development of interconnected sensor networks and smart devices, driven
by the rise of interconnected systems and the Internet of Things (IoT), has opened up new
possibilities. Studies by Sebastian et al. (2017) demonstrate the potential of IoT-enabled
devices in real-time data collection, environmental monitoring, and early warning systems,
enabling more proactive and responsive emergency responses.
Another significant shift in the field is the move towards community-centric approaches and
citizen engagement in disaster management. Discussions around the empowerment of
communities through participatory platforms, which allow them to actively contribute to
response efforts, share information, and collaborate with authorities, foster a more inclusive
and resilient response ecosystem.
Additionally, the incorporation of social media analytics, crowdsourcing, and geospatial
technologies has emerged as a promising avenue for enhancing situational awareness and
information dissemination during emergencies. Illustrations of the utilization of social media
data analysis and geospatial mapping to gather real-time insights, identify critical areas, and
engage with affected communities swiftly provide valuable tools for improving emergency
response coordination.
The shift towards technology, community involvement, and data-driven decision-making in
emergency response highlights the need for innovation and collaboration to tackle complex
challenges and minimize harm to communities and infrastructure.

2.6 Research Gap to be Filled by this Research

The emergency response coordination field has made significant progress, but there is still a
gap in research that this study aims to fill. While current literature covers the technological
and strategic aspects of emergency response systems, there is a lack of exploration into the
integration of community-based approaches within these systems. The existing research
primarily focuses on technological advancements, such as AI, IoT, and GIS, to optimize
response mechanisms. However, there is limited attention given to the effective incorporation
of community engagement, citizen participation, and local knowledge integration within
these technological frameworks. This study seeks to bridge this gap by investigating how
community involvement and local insights can be strategically integrated into advanced
technological platforms for emergency response coordination. By addressing this research

13
gap, the study aims to provide insights into fostering more inclusive, resilient, and
contextually appropriate emergency response systems that leverage both technological
innovations and community-driven approaches for more effective crisis management.

2.7 Conclusion

In summary, looking into existing research about emergency response coordination reveals a
complex scenario where technology, teamwork, and smart approaches play crucial roles. The
review highlights the importance of reliable communication, new technology, and involving
communities in emergency responses. It also shows how it's important to tackle new
challenges by learning from experience and creating better emergency systems. This
collection of studies gives us a strong base to build a more effective emergency response
system that fits our changing world.

14
 CHAPTER 3: RESEARCH METHODOLOGY

3.1 Introduction

The web application employs the Incremental Methodology in its development process. This
methodology involves breaking down all the requirements into distinct standalone software
modules, constituting different stages of the software development cycle. In this approach,
each phase of developing this proposed application is carried out through iterative cycles,
encompassing requirements, design, coding, and testing. Each subsequent release of the web
application introduces additional functionalities to the previous iteration until all the planned
features are implemented.
The web application enters the production phase after the initial incremental release.
Typically, the initial incremental release comprises the essential core product, addressing all
the fundamental user requirements. Additional features of the mobile application are
gradually incorporated into subsequent increments. After the completion of the first core
product, user analysis is conducted. If the user expresses dissatisfaction with the core product,
the subsequent increments are crucial to meeting the user's final product expectations.

FIGURE 1: PHASES IN AGILE METHODOLOGY

15
3.2 Methodology for literature review

The methodology applied for conducting the literature review within this project is focused
on a thorough exploration of academic articles, research papers, industry publications, and
established frameworks pertaining to emergency response technologies and web applications.
This approach involves a systematic examination of various databases and peer-reviewed
sources to identify, evaluate, and synthesize existing knowledge relevant to the development
of an innovative emergency response we application. Employing a search strategy and
rigorous selection criteria, this methodology aims to analyze and assimilate critical insights,
best practices, and technological advancements existing in the domain. The synthesis of this
literature review will serve as a foundational pillar, guiding the design, features, and
functionalities of the envisioned emergency response web app, integrating proven
methodologies and insights from contemporary research into the development process.

3.3 Methodology for requirement specification, data collection and analysis techniques

3.3.1 Requirement Specification

Conducting a comprehensive requirement specification involves compiling all necessary

functional and non-functional prerequisites essential for the design, validation, and
maintenance of the emergency response app. This documentation includes critical
information for the app's development, verification, and sustainability, ensuring compliance
with user needs and industry standards.

1. User Needs:
End-Users (Citizens): The application should cater to citizens affected by emergencies,
providing them with a user-friendly interface to report incidents, access emergency services,
receive alerts, and seek guidance during crises.

16
First Responders: Requirements must address the needs of emergency responders, enabling
them to efficiently access critical information, coordinate response efforts, and communicate
seamlessly in the field.
Authorities and Agencies: The platform should support administrative functions for
government agencies and emergency service providers to manage resources, disseminate
alerts, and coordinate response operations.

Functionality Requirements:
Incident Reporting: A feature for citizens to report emergencies via text, images, or
location sharing.
Alerts and Notifications: Real-time alerts and notifications for users, authorities, and
responders based on incident type and proximity.
GIS Mapping: Integration of Geographical Information System (GIS) for accurate
incident location visualization and mapping.
Resource Allocation: Tools to efficiently allocate resources such as personnel, medical
supplies, and equipment based on incident severity and location.
Non-Functional Requirements:
Scalability: The application should accommodate an increasing number of users during
peak emergency periods without performance degradation.
Security: Robust security measures to protect user data, ensure confidentiality, and
prevent unauthorized access to sensitive information.
Usability: Intuitive design and user experience to ensure ease of use for citizens in high-
stress situations and streamlined workflows for emergency responders.
Accessibility and Compatibility:
Device Compatibility: The application should be accessible across various devices,
including smartphones, tablets, and computers.
Language and Accessibility: Support for multiple languages and accessibility features to
ensure inclusivity for users with disabilities.
Regulatory and Compliance Requirements:
Privacy Regulations: Adherence to data privacy laws and regulations to safeguard user
information.

17
 Industry Standards: Compliance with emergency response industry standards and best
practices to ensure the application's effectiveness and reliability.

3.3.2 Data Collection Methods

The project employs various data collection methodologies, including surveys, quizzes,
questionnaires, interviews, focus groups, and direct observations. These multifaceted
approaches gather user feedback, stakeholder insights, and real-time data to inform the
emergency response app's development process comprehensively.

3.3.3 Interviews

Interviews facilitate informative exchanges between stakeholders, experts, and potential end-
users in the emergency response domain. Through this two-way communication channel,
vital information, preferences, and insights are gathered, deepening the understanding of user
needs, functionalities, and expectations relevant to the app's design and usability.

3.3.4 Use of Questionnaires

The project employs questionnaires as a structured approach to gather quantitative and

qualitative data from respondents. These surveys encompass inquiries aimed at understanding
attitudes, experiences, opinions, and preferences pertinent to emergency response scenarios,
providing valuable inputs for designing the app in alignment with user requirements.

3.3.5 Observation

Observational techniques involve actively acquiring real-time information from primary

sources, including situational simulations and live emergency scenarios. Leveraging both
sensory and scientific instruments, this observational approach aids in perceiving, recording,
and analyzing crucial data points essential for informing the app's functionalities and
responsiveness to diverse emergency scenarios.

18
3.4 Methodology for System Analysis (current system)

In analyzing the current emergency response systems, the existing methodology

predominantly revolves around the utilization of emergency number dialling, where users are
required to dial specific designated numbers corresponding to particular types of
emergencies. For instance, users might dial distinct numbers for police, fire services, medical
emergencies, or other specific crisis situations, depending on the established emergency
service infrastructure in their respective regions. This traditional approach typically involves
direct phone calls to emergency services, often necessitating the caller to relay critical
information to the dispatcher regarding the nature and location of the emergency.
Additionally, current systems often rely on call center-based operations or dispatch centers,
where personnel receive and manage incoming emergency calls, assess the situation based on
the information provided, and dispatch appropriate responders to the reported location. These
systems, although effective in their own right, might face limitations in rapid information
dissemination, real-time data sharing, and location-based services
Furthermore, these systems are frequently siloed, operating independently across various
emergency response agencies or services, potentially leading to fragmented response
coordination and challenges in inter-agency communication during complex emergency
scenarios. Such isolated systems may also encounter difficulties in integrating newer
technological advancements, hindering the incorporation of more efficient and innovative
response mechanisms.
In summary, the current analysis of emergency response systems often reveals a reliance on
traditional emergency number dialing methods and call center-based operations. While
effective to a certain extent, these systems may encounter limitations in terms of information
dissemination, response coordination, and integration of modern technological advancements,
prompting the need for more robust, integrated, and technologically advanced approaches to
emergency response.

19
3.5 Methodology for System Analysis (Proposed system)

The purpose of this project is to enhance the emergency response system that based mobile
techniques, by development a flexible and dynamic web application which offer tracking
mechanism and information management. Moreover, we want to move our focus on
emergency management life cycle, which defined the steps as mitigation, pre-preparedness,
recovery and response in order to study the applicability of mobile technologies. In addition,
in this case, first it would be crucial to clarify the role of citizens within these phases.
Moreover, how their participation can be helpful for the operation centre (Heba et al., 2019;
Asmaa et al., 2019; Romano et al., 2016). Most of the people has smartphones now. For this
reason, our project will build a web application the covers all the disadvantages and
drawbacks of the current applications listed below.

International Mobile and Web Applications: SaftyGPS, Help Bridge, Motorola Alert
(HelpBridge, http://www.microsoft.com/it-it/store/apps/helpbridge/9wzdncrdtcd0;
Motorola Alert, https://play.google.com/store/apps/details ?
id=com.motorola.bodyguard&hl=en), Emergency Alert, FEMA app (Emergency Alert ,
http://emergencyalert.alberta.ca/content/about/ mobileapp.html;
The FEMA App, https://www.fema.gov/mobile-app),
SignAlert, ELERTS, and My112 (SIGNALERT, https://www.signalert.net/application-
mobile/;

The first step starts in the place of emergency; there are two types of disasters: man-made and
natural disaster. Once the action occurred in front of the user, the volunteer, or a text message
receive from people to the application. The role of the proposed application begins with
analysing the messages to decide if it is centralised or not (Alshareef and Grigoras, 2016;
Basak et al., 2005). 134 A.Z. Alharbi et al. Then, it searches on the pre-preparedness phase to
find any previous scenarios matching the current action. After that, it goes to the plans step,
which communicate with Agencies by using Agent Based simulation coordination
mechanisms. These agencies may be doctors, firefighters, etc. Finally, it transfers to the
instruction step to take the location information from the Database to send the final plan as

20
warning messages to smartphones or notify to social media and send volunteer to the disaster
place.

FIGURE 2: PROPOSED SYSTEM ARCHITECTURE

In our proposed architecture (Figure 2), we learn that if someone is in any emergency, they can use
our proposed web application services to save them and keep the situation under control. Depending
on the situation, it is possible to select a service from the menu provided through the Internet using
any device such as mobile or laptop that will communicate through local towers or LANs to establish
a connection to our server. The token with the details of the user raising a request for the provision of
the emergency service has been sent to the main service provider for immediate action.

21
3.5.1 System Flowchart

FIGURE 3: SYSTEM FLOWCHART

22
3.5.2 Sequence Diagram

User Login
A sequence diagram is used to show how operations interconnect and operate with one another and
the order in which operations occur. The figure below represents the sequence of usage of the web
application. At first, the user needs to login for using the emergency services. As soon as the user
enters his/her specific credentials into the system and the system confirms if the user exists in the
database. When the credentials are confirmed, the user now can choose which emergency service to
use. After selecting the service in the system, the web application responses with the service details
and a form is to submit. Once the user submits the form and reports the emergency the system will
generate a unique report ID and give it to the user for future references. Then the system will contact
the nearest service centre and will proceed to provide the user the specific emergency service. Also,
the user can change settings in his/her profile while they are logged in to the system.

FIGURE 4: SEQUENCE DIAGRAM

23
3.5.3 Use-case Diagram

User
FIGURE 5: USE CASE DIAGRAM: USER

Admin

24
3.5.5 Design Of Database

FIGURE 6: DATABASE DESIGN

25
3.5.6 Early System prototypes (I/O design)

User Login page

FIGURE 7: USER LOGIN PAGE

26
User Interface prototype

FIGURE 8: USER INTERFACE PROTOTYPE

27
3.6 Methodology for system implementation

3.6.1 Backend Technologies

Backend Framework: The backend of the system will be developed using Laravel, a robust
PHP framework known for its scalability, security features, and MVC (Model-View-
Controller) architecture. Laravel's powerful features like Eloquent ORM, middleware, and
routing will be leveraged for efficient backend development.

API Development: RESTful APIs will be created using Laravel's built-in API resources,
enabling seamless communication between the frontend and backend. These APIs will adhere
to RESTful conventions for standardized interaction and data transfer.

Server-side Scripting: PHP will be utilized for server-side scripting, powering the backend
operations, data processing, and business logic. Laravel's Blade templating engine will be
employed for server-rendered views, enhancing dynamic content presentation.

3.6.2 Frontend Technologies

Frontend Framework and Libraries: HTML5, CSS, and JavaScript will form the core of the
frontend. Tailwind CSS, along with Material UI components, will be used to create a visually
appealing and responsive user interface. These modern frontend technologies will enable
efficient UI design and development.

Responsive Design: Responsive web design principles will guide the frontend development,
ensuring compatibility across various devices and screen sizes. This approach aims to deliver
an optimized user experience on desktops, tablets, and mobile devices.

User Experience (UX) Design: Emphasis will be placed on UX design to create an intuitive
and accessible interface. UI components and interactions will be designed to enhance
usability and facilitate smooth navigation.

28
3.6.3 Database Technologies

Database Management System: MySQL will serve as the primary Database Management
System (DBMS) due to its reliability, scalability, and widespread adoption. MySQL will
manage structured data related to emergencies, user profiles, response team details, and
system logs.
Data Modelling and Optimization: Entity-Relationship Diagrams (ERDs) will guide the data
modelling process, ensuring proper organization and relationships among different data
entities. SQL queries will be optimized using indexing and normalization techniques for
improved performance.

3.7 Methodology for System Testing

1. Functional vs. Non-functional Testing

Functional Testing:
Objective: This aims to verify that each function of the system behaves as intended based on
functional requirements.
Approach: Design test cases aligned with user stories and system requirements to validate
system functions.
Tools Used: Selenium WebDriver for automated functional testing to ensure consistent test
execution.

Non-functional Testing:
Objective: It involves testing system attributes that aren’t functionalities but crucial for the
system's success, such as performance, security, usability, etc.
Approach: Conduct tests to ensure the system's performance, security, usability, and
reliability align with specified standards.
Tools Used: For security, Burp Suite; for performance, JMeter; for usability, UserZoom.

2. Unit Testing
Objective: Verify the correctness of individual units or components of the system.
Approach: Developers write and execute test cases for individual units using PHPUnit for
backend PHP code and Jest for frontend JavaScript.

29
Verification: Ensure each unit functions as expected independently before integration.

3. Integration Testing
Objective: Validate the interactions between integrated components.
Approach: Test the integration points between different modules to verify their data exchange
and interaction.
Tools Used: Postman and Newman for API testing, along with custom scripts.

4. System Testing
Objective: Ensure the entire system performs as per specifications.
Approach: End-to-end testing will be carried out to verify all components work together as a
cohesive system.
Tools Used: Automated testing via Selenium WebDriver for frontend and backend
integration testing.

5. Acceptance Testing
Objective: Confirm the system meets user requirements.
Approach: Real-world scenario-based testing conducted in a controlled environment to
validate user acceptance criteria.
Verification: Ensure the system aligns with the user's expectations.

6. Performance Testing
Objective: Assess system performance under various conditions.
Approach: Load, stress, and scalability testing to measure responsiveness and stability.
Tools Used: Apache JMeter for load testing and monitoring system performance metrics.

7. Security Testing
Objective: Identify system vulnerabilities and weaknesses.
Approach: Conduct security audits, penetration tests, and vulnerability assessments to ensure
robust security measures.
Tools Used: OWASP ZAP for security scans, SQLMap for SQL injection testing, and Nessus
for vulnerability scanning.

30
8. Usability Testing

Objective: Evaluate the system's ease of use and user-friendliness.

Approach: Employ user surveys, heuristic evaluations, and user walkthroughs to assess the
system's user experience.
Verification: Ensure the system is intuitive and navigable for the intended user base

3.7.1 Testing Plan

1. Introduction
Purpose: To ensure the web application meets functional and non-functional requirements.
Scope: Specify what aspects of the web app will be tested, including features, performance,
security, and usability.

2. Test Objectives
Functional Testing: Validate all functional requirements against user stories and use cases.
Non-functional Testing: Assess performance, security, usability, compatibility, and
reliability.
Compatibility Testing: Ensure cross-browser and cross-device compatibility.
User Acceptance Testing (UAT): Ensure the system meets end-user expectations.

3. Test Strategy
Approach: Define the testing methods, tools, and techniques to be utilized.
Testing Types: Plan for unit testing, integration testing, system testing, acceptance testing,
performance testing, security testing, and usability testing.

4. Test Schedule
Timeline: Define testing phases, start and end dates, and milestones for each testing phase.
Resource Allocation: Allocate necessary resources, including human resources, testing tools,
and environments.

5. Test Environment
Hardware and Software Requirements: Specify required hardware configurations, software
versions, and network settings.

31
Data Setup: Prepare the necessary test data for various scenarios.

6. Test Cases and Scenarios

Test Case Identification: Develop detailed test cases for functional and non-functional
requirements.
Use Cases and User Stories: Align test cases with user stories and use cases to ensure
coverage.
Test Data Preparation: Prepare and manage data required for different test scenarios.

7. Responsibilities
Team Roles: Define roles and responsibilities of team members involved in testing activities.
Reporting Structure: Outline communication channels and reporting hierarchies for efficient
testing.

8. Risks and Contingencies

Risk Identification: Identify potential risks that might impact the testing process.
Mitigation Plan: Propose contingency plans and mitigation strategies for identified risks.

9. Exit Criteria
Completion Criteria: Define criteria indicating when testing is considered complete.
Acceptance Criteria: Specify criteria for acceptance or rejection based on test results.

10. Review and Update

Revision Schedule: Establish a schedule for regular review and updates of the testing plan.
Approval Process: Define the process for approving any modifications to the testing plan.

3.7.2 Testing Techniques

1. Black Box Testing

Description:
i. Black Box Testing validates the functionality of the application without considering
its internal code structure or logic. This method examines the system's inputs, outputs,
and interactions against the specified requirements.
ii. Application:

32
 iii. Test Scenarios: Craft test cases focusing on user interactions, ensuring the interface
responds correctly to inputs and generates the expected outputs.
iv. Functional Testing: Verify the application's functionalities, including form
submissions, navigation, data processing, and response to various user inputs.
v. Usability Testing: Assess the user interface's ease of use, ensuring it's intuitive and
user-friendly.
Importance:
i. User-Centric Focus: Validates that the web application performs according to user
expectations and requirements.
ii. Requirement Validation: Confirms that the application meets the specified
functional requirements without requiring knowledge of its internal workings.
2. Unit Testing
Description:
i. Unit Testing evaluates individual components or units of the application in isolation. It
scrutinizes specific sections of the code, such as functions, procedures, or methods, to
verify their functionality.
Application:
i. Laravel Controllers and Models: Test individual methods and functions within these
components to ensure they perform as intended.
ii. Service Classes: Validate the functionality of service classes responsible for business
logic or data manipulation.
Importance:
i. Early Bug Detection: Identifies defects in individual components during the
development phase, allowing for prompt resolution.
ii. Code Quality Assurance: Ensures that individual units or components function
correctly before integration, contributing to the overall stability of the system.

3.8 Methodology for system deployment

System Deployment Methodologies:

i. Coding: The Laravel application has been meticulously developed using the Laravel
PHP framework, ensuring robust and efficient coding practices compliant with the
project requirements.

33
 ii. Building: After coding, the Laravel application is built to prepare it for deployment.
This involves processes such as compiling assets, optimizing code, and setting up the
necessary configurations.
iii. Testing: A comprehensive set of tests, including unit tests, integration tests, and
system tests, are conducted to ensure the Laravel application functions correctly and
is free from critical issues or bugs before deployment.
iv. Packaging: The application is packaged for deployment. This involves bundling all
necessary files, dependencies, configurations, and resources into a deployable
package, often in the form of a compressed archive.
v. Releasing: Once the application is thoroughly tested and packaged, it's released for
deployment on the Hostinger platform. This phase involves making the application
available for installation or deployment on the hosting environment.
vi. Configuring: Configuration settings specific to the Hostinger environment, such as
setting up the database connections, file permissions, environment variables, and
server configurations, are applied to ensure the Laravel application functions correctly
within the hosting environment.
vii. Monitoring: After deployment, the system's performance, stability, and functionality
are continuously monitored. Monitoring tools are utilized to detect any anomalies,
track resource usage, and ensure the system operates optimally on the Hostinger
platform.
viii. Software Deployment Methods:
ix. Automated Software Package Creation:
x. Hostinger provides streamlined deployment options, including automated installations
for various frameworks, including Laravel. Users can leverage predefined setups and
scripts to facilitate the deployment process efficiently.
xi. Manual Software Package Creation:
xii. In scenarios where automated solutions are not available or require customization,
manual deployment involves uploading the packaged Laravel application files,
configuring the server settings, databases, and other necessary configurations via
Hostinger's control panel or command-line interfaces.

34
 References

1. (Schöning, Rohs, Krüger, & Stasch, 2009) Improving the communication of spatial
information in crisis response by combining paper maps and mobile devices. In
Second International Workshop on Mobile Information Technology for Emergency
Response; Lecture Notes in Computer Science; Springer: Berlin, Germany, 2009;
Volume 5424, pp. 57–65.

2. Yuan, W.; Guan, D.; Huh, E.N.; Lee, S. Harness Human Sensor Networks for
Situational Awareness in Disaster Reliefs: A Survey. IETE Tech. Rev. 2013, 30, 240–
247.

3. Ichiguchi, T. Robust and Usable Media for Communication in a Disaster. Q. Rev.

2011, 4, 44–55.

4. Malizia, A.; Bellucci, A.; Diaz, P.; Aedo, I.; Levialdi, S. eStorys: A visual storyboard
system supporting back-channel communication for emergencies. J. Visual Lang.
Comput. 2011, 22, 150–169.

5. Manoj, B.S.; Baker, A.H. Communication challenges in emergency response. ACM

2007, 50, 51–53.

6. Malizia, A.; Onorati, T.; Diaz, P.; Aedo, I.; Astorga-Paliza, F. SEMA4A: An ontology
for emergency notification systems accessibility. Expert Syst. Appl. 2010, 37, 3380–
3391.

7. Cao, Y., & Jiang, H. (2021). Research on emergency logistics management based on
Intelligent Supply Chain. E3S Web of Conferences, 235, 03056.

8. Gjøsæter, T., Radianti, J., & Chen, W. (2020, November 6). Universal Design of ICT
for Emergency Management from Stakeholders’ Perspective. Information Systems
Frontiers, 23(5), 1213–1225.

9. Lindell, M. K., & Perry, R. W. (1987, August). Warning Mechanisms in Emergency

Response Systems. International Journal of Mass Emergencies & Disasters, 5(2),
137–153.

10. Fedushko, S., Trach, O., Syerov, Y., Kryvinska, N., & Calhoun, J. R. (2023, March
19). Web Project Development: Emergency Management. Journal of Web
Engineering.

35
 Appendix i

Sample Questionnaire (Tick where Appropriate)

Demographics:
Gender:
Male
Female

Age Group (Check all that apply):

18-25 years
26-30 years
31-45 years
Other (Please specify)

Level of Education:
Undergraduate
Graduate
Postgraduate
Other (Please specify)

Real-Time Incident Reporting System

a. How crucial do you think real-time incident reporting is for effective emergency response
coordination?
Not important at all
Slightly important
Moderately important
Important
Extremely important

b. Are you satisfied with the current incident reporting system in terms of timeliness and accuracy?
Very Dissatisfied
Dissatisfied
Neutral
Satisfied
Very Satisfied

36
Geolocation Service for Incident Tracking
a. How effective would geolocation services be in tracking incident locations and allocating resources
promptly?
Not effective at all
Slightly effective
Moderately effective
Effective
Extremely effective

b. Are you familiar with using geolocation-based systems for emergency response coordination?
Not at all familiar
Slightly familiar
Moderately familiar
Familiar
Very familiar
Inter-Agency Communication

a. How critical is seamless communication among various emergency response agencies for effective
coordination?

Not critical at all

Slightly critical
Moderately critical
Critical
Extremely critical

b. Do you believe the current communication methods between different agencies need improvement?
Strongly Disagree
Disagree
Neutral
Agree
Strongly Agree
Community Participation in Reporting
a. How important is community involvement in incident reporting for enhancing emergency response?
Not important at all
Slightly important

37
Moderately important
Important
Extremely important

b. Do you think citizens are willing to participate actively in incident reporting through digital
platforms?
Strongly Disagree
Disagree
Neutral
Agree
Strongly Agree
User Training and Evaluation

a. How vital is training for users to effectively use the Road Accident Emergency Response
Coordination Web Application?

Not vital at all

Slightly vital
Moderately vital
Vital
Extremely vital

b. Would periodic evaluation and feedback mechanisms enhance user engagement and application
effectiveness?

Not at all
Slightly
Moderately
A lot
Completely

38
 Appendix ii
Gantt chart

FIGURE 9: GANTT CHART

39
 Appendix iii
Project Budget

ITEM PRICE/UNIT QUANTITY TOTAL

PRICE(KSH)
Software 2000 1 2000
Tools/Licenses
Documentation 500 1 500
Printing
PC 20000 1 20000

Web Hosting 5,000 1 year 5000

Internet Services 1500 1 month 1500

Total 29000

40