Scribd
Upload
4 views5 pages

CHAPTER THREE

This chapter outlines the methodology for designing an emergency alert system, detailing data collection methods such as observation, questionnaires, and interviews to identify user needs and system requirements. It describes the use of UML diagrams for system modeling, the design of a relational database for data management, and the creation of user-friendly interfaces for efficient interaction. Additionally, it specifies the hardware, software, and user requirements necessary for the system's functionality and performance.

Uploaded by

Daniel Godwin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
4 views5 pages

CHAPTER THREE

This chapter outlines the methodology for designing an emergency alert system, detailing data collection methods such as observation, questionnaires, and interviews to identify user needs and system requirements. It describes the use of UML diagrams for system modeling, the design of a relational database for data management, and the creation of user-friendly interfaces for efficient interaction. Additionally, it specifies the hardware, software, and user requirements necessary for the system's functionality and performance.

Uploaded by

Daniel Godwin
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 5

CHAPTER THREE

METHODOLOGY

3.1 Introduction

This chapter presents the methodology employed in the system analysis and design processes
for the proposed emergency alert system. It details the methods and tools used for data
collection, system modeling, database design, output and input design, and system
requirements. The purpose of this chapter is to provide a clear and precise model of the system
to facilitate an understanding and effective future implementation. The methodology ensures
that the system design aligns with user needs and industry best practices while maintaining
efficiency, reliability, and scalability.

3.2 Methods of Data Collection

To ensure that the system requirements are well-defined, various fact-finding techniques were
employed to gather relevant information about emergency alert systems. The following
techniques were used:

3.2.1 Observation of the Work Environment Observation involves systematically watching the
activities and interactions within emergency response centers to understand existing workflows,
identify inefficiencies, and recognize areas where automation can improve operations. The
researcher observed emergency call centers, hospital emergency units, and fire response
departments. By analyzing how emergency alerts are currently handled, it was possible to
identify communication gaps, delays, and response inefficiencies. The insights gained from
observations were crucial in designing a more efficient and real-time emergency alert system.

3.2.2 Questionnaires Structured questionnaires were designed and distributed to emergency


response personnel, healthcare professionals, security agencies, and members of the public.
The questionnaire sought to understand their experiences, challenges, and expectations
regarding emergency alert systems. The questions covered aspects such as:

 The effectiveness of current emergency response systems.

 Challenges faced in emergency communication.

 Preferred methods of receiving emergency alerts.

 Suggestions for improving emergency alert systems.

The collected data provided quantitative insights into current system inefficiencies and guided
the development of features that cater to user needs.
3.2.3 Interviews Interviews were conducted with emergency responders, IT experts, and
government officials to gain deeper insights into the technological and operational
requirements for an effective emergency alert system. These interviews focused on:

 Understanding real-life challenges faced by emergency response teams.

 Identifying the technologies currently in use and their limitations.

 Gathering expert opinions on the integration of AI, IoT, and cloud computing in
emergency response.

The qualitative data obtained from the interviews was instrumental in refining the system
requirements and ensuring that the final design met the needs of all stakeholders.

3.3 System Modeling (Using UML Diagrams)

To represent the system design, Unified Modeling Language (UML) diagrams were used. These
diagrams provide a structured visualization of system interactions and workflows. The following
UML diagrams were developed:

 Use Case Diagram: Illustrates the interactions between users (emergency responders,
alert initiators, and administrators) and the system. It helps define the functional
requirements of the system.

 Activity Diagram: Shows the flow of activities from alert initiation to response execution.
This diagram ensures that the workflow is well-structured and logical.
 Class Diagram: Represents the system's data structure, defining the relationships
between different entities such as users, emergency cases, and response units.

3.4 Database Design

A well-structured database is crucial for efficient data storage and retrieval. The emergency alert
system's database was designed using a relational database management system (RDBMS) such
as MySQL to ensure data integrity and scalability. The database schema consists of the following
tables:

 User Table: Stores user information, including emergency responders, administrators,


and alert initiators.

 Emergency Reports Table: Contains records of reported emergencies, timestamps,


locations, and response statuses.

 Response Units Table: Stores details of available emergency response teams, their
locations, and readiness status.

 Logs Table: Maintains records of system activities for auditing and monitoring purposes.
3.5 Output Design

The system output design focuses on providing timely and accurate information to users. Key
output features include:

 Real-time Notifications: Emergency alerts are sent via SMS, email, and mobile app
notifications to ensure immediate awareness.

 Response Status Updates: Users receive live updates on the status of emergency
response actions, including estimated arrival times of response units.

 Reports and Analytics: Administrators can generate reports on response efficiency, alert
trends, and system performance, facilitating decision-making and improvements.

3.6 Input and User Interface Design

The user interface (UI) is designed to be intuitive and user-friendly. Key UI components include:

 Emergency Alert Form: Allows users to quickly report emergencies by filling out
essential details such as location, type of emergency, and additional comments.

 Dashboard: Provides emergency responders with an overview of active alerts, resource


availability, and response times, ensuring efficient dispatch.

 Admin Panel: Enables system administrators to manage users, monitor alerts, generate
reports, and configure system settings.

To enhance usability, the UI incorporates:

 Clear navigation menus.

 Real-time alert notifications.

 An interactive map for location tracking.

 A responsive design to ensure compatibility across different devices.

3.7 System Requirements

To ensure smooth functionality, the system requires specific hardware, software, and user
capabilities.

3.7.1 Hardware Requirements

 A dedicated server with at least 8GB RAM and 500GB SSD storage to handle system
requests efficiently.
 Internet-enabled devices (smartphones, tablets, and computers) for users to access the
platform.

 GPS-enabled devices for accurate location tracking and response unit navigation.

3.7.2 Software Requirements

 Operating System: Linux or Windows Server for hosting the backend services.

 Database Management System: MySQL for structured and reliable data management.

 Programming Languages:

o Frontend: React.js for developing an interactive and dynamic user interface.

o Backend: Node.js for handling server-side logic and API requests.

o Database Queries: SQL for data retrieval and manipulation.

 Notification System: Firebase Cloud Messaging for real-time alert notifications.

3.7.3 User Requirements

 Basic IT knowledge for system administrators and emergency responders.

 Access to a mobile device or computer to interact with the system.

 Internet connectivity for real-time communication and updates.

3.8 Choice of Programming Language

The choice of programming language was based on performance, scalability, and ease of
integration with other technologies. The selected technologies include:

 React.js for the frontend to provide a responsive and dynamic user experience.

 Node.js for the backend, allowing for asynchronous operations and efficient handling of
real-time data.

 Supabase for structured database management, ensuring data integrity and quick
retrieval.

You might also like