Chapter III

Methodology

This chapter presents the strategies that the developers

utilized in gathering and assessment of the information
prerequisite to understanding the objective of the study,
data processing, and its implementation.
Development Method

To create the project, the researchers used the Rapid

Application Development Model under Agile Methodology. RAD is
a methodology that emphasizes rapid application development
through frequent iterations and continuous feedback. It
enables the developers to get a look at any potential issues
that might arise during development. As a result, there are
less chances of errors and malfunctions in the finished
product.
In the evaluation process, the proponents relies on the
ISO 25010 to evaluate its purpose and design in its Functional
Suitability, Performance Efficiency, Compatibility,
Usability, Reliability, Security, Portability, and
Maintainability of the “Water Level and Weather Monitoring”
device.
The respondents of the study will be the Victoria
Municipal Disaster Risk Reduction Management Office,
residents of Victoria and the residents of the municipality.
The said respondents was chosen using nonprobability sampling
due to the selection of respondents with an equal opportunity.
 Gantt Chart

Months November December January February March

Weeks 1 2 3 4 1 2 3 4 1 2 3 4 1 2 3 4 12 3 4

Activities
1.Analysis and
Design
1.1
Brainstorming
1.2 Project
Concept
1.3 Title
Proposal
1.5 Interview
1.6
Brainstorming
of Design
1.7 Creation of
User Interface
Design
1.8 Materials
Preparation

4. Rapid
Development
4.1 Writing Code
4.2 Design to
Software
Conversion
4.3 Prototype
Designing
4.4. Hardware
Component
Creation
4.5 Prototype
Testing
4.6 Feedback
Gathering
4.7 Design
Modification
4.8 Finalization
of Design
5.Testing
A. Software
Testing
5.1 Program
Debugging
5.2 Application
Testing
B. Hardware
Testing
5.3 Prototype
Testing
C. System
Testing
5.4 Software to
Hardware
Connectivity
6.Evaluating
6.1 Software
Modification
6.2 Hardware
Modification
6.3 System
Testing &
Modification
6.4 Maintenance
6.5
Documentation
Legend: Done: To be Done:
Table 1. Gantt Chart

This table displays the tabular data of the monthly

allocation of system development activities. It depicts the
activities and tasks, which include planning, data collection
and analysis through observation, research, and interviews,
design, testing, and evaluation, and implementation.
Analysis and Quick Design
At this phase, the proponents conceptualized the topic
and led to the “e-LogMo: A Naujan Lake Water Level and Weather
Monitoring System with Mobile Notification Using Radio
Frequency for Victoria MDRRMO”.
The researchers began identifying societal issues and
conceptualizing solutions to the issues they found. The
proponents and the client has talked about the project
requirement and problem to address. This was created to help
the designers allocate the requirements for the project's
progress.
Rapid Development

During this phase, clients work hand in hand with

developers to ensure their needs are being met at every step
in the design process. All the bugs are worked out in an
iterative process. The developer designs a prototype, the
client tests it, and then they come together to communicate
on what worked and what didn’t. This method gives developers
the opportunity to tweak the model as they go until they
reach a satisfactory design.

Testing/Debugging

In this phase, after successfully writing the codes,

the programmer tests the program at this point to look for
complexities, gaps, and other issues that typically crop up.

Implementation
Here, the proponents will be implementing the project
to the adaptor or client, allowing them to use the project.
It is here where the final part of the development proceeds.
It is also where the developers analyze and evaluates whether
the system could meet the user’s expectation and demand of
function. It must abide by the software evaluation standard:
ISO 25010.
Requirements Specifications
This is where the specifications needed and required by
the development is discussed. The physical peripheral
requirements for the system's successful development were
established by the hardware specification. Software
requirements outlined what the development can and cannot do,
demonstrating its functionality.
Software Requirements
The system must be able to produce the minimum, maximum,
and average values of a specific weather parameter. The system
must provide information on temperature, pressure, wind
direction and speed, rainfall, and humidity. Significantly,
the system must also display the status of the Naujan Lake,
from its normal water level to the elevation, and the risks
it could give to the residents in the barangay. It also has
to accept account of the users, prompting them to input
personal information which will be saved to the database.
Furthermore, the system should also allow the users to click
a button for the request for community rescue team at any
times.
User Interface
This figure shows the user interface of the mobile
application of the system from where the interaction between
the user and the project takes place.

Figure 2. User Interface

 This figure shows the mobile application interface to be
operated by the user. It is the platform where the operator
connects with the system, enabling him to view its features
and navigate through its functionality.
Hardware Interface

Mobile
phone

GSM
Internet
Module

Solar- 16 Power Arduino

NodeMCU
charged Chanel Weather
ESP8266
battery Relay Shield

HCSR04
Arduino Ultrasonic
Mega Sensor

Figure 3. Hardware Interface

Figure 3 depicts the connectivity between the modules
and the system, the hardware's construction, and the hardware
peripherals used to complete the project, keeping in mind
that every other component was also connected to the
microcontroller.
Software Interface
The connection uses the internet to transmit data from
the sensors. These data were sent to the user’s notification
section, notifying the user of the actions taken by the
system. The application will then generate a Short Message
Service to be sent to the user’s contacts. Because it is a
calamity-driven project, the proponent made its access
available offline using modules, specifically for the radio
transmission of data.
Security Requirements
The system uses a cryptography algorithm that locks and
encrypts the data inputted by the user, which will be used
in securing their personal information. Furthermore, a mobile
number must be used in the anticipation of having little to
no signal at all. There is also a prompt for login
verification for the users.
Technical Background
This section displays the hardware and software
specifications for the system. It describes the abilities and
effectiveness of the parts used in the creation of the
project.
Hardware Specifications
The “e-LogMo: A Naujan Lake Water Level and Weather
Monitoring System with Mobile Notification Using Radio
Frequency for Victoria MDRRMO” was designed and developed
using the following hardware.
Table 2. Hardware Requirements
Hardware Minimum Recommended
Components Specification Specifications
Main Board NodeMcu ESP8266 NodeMcu ESP8266
+5V, 2cm-450cm +5V, 2cm-450cm
HC-SR04 Sensor measuring measuring
distance distance
3.3V, 40mA, SD 3.6V, 200mA, SD
RTC Data Logger
Card (2G, SDHC Card (4G), SDHC
Shield
card (<=16g) card (<=16g)
 Control via AT Control via AT
GSM Arduino
commands: GSM 07 commands: GSM 07
Module
and SIMCOM, 5V and SIMCOM, 5V
Female-to-Female, Female-to-Female,
Generic Jumper Male-to-Male, Male-to-Male,
Wires Female-to-Male Female-to-Male
Generic Wires Generic Wires
3V – 100v, 3V – 100v,
humidity humidity
Arduino Weather
accessory - ±2%, accessory - ±2%,
Shield
pressure - ±50, pressure - ±50,
±0.3% ±0.3%
Relay Module 4 Channel Relay 16 Channel Relay

Table 2 shows the minimum and recommended

specifications for hardware components required for the
development of the system.
Table 3. Laptop Specification
Minimum Recommended
Hardware
Specification Specification
Hard Disk 256GB 1 TB
Processor Intel Corei3 Intel Corei7
Memory 4GB memory 8GB memory
1366 x 768
Screen Resolution 1280 x 720 pixels
pixels
Generic PnP
Monitor Generic PnP Monitor
Monitor
AIO Motherboard AIO Motherboard
Motherboard
76ydp 76ydp

Table 3 shows the minimum and recommended requirements of

the laptop used in the development of the system.
Table 4. Mobile Specifications for System Development
Minimum Recommended
Hardware
Specifications Specifications
Smartphone OS Android 6.0 Android 12.0
LCD Screen
720x1480 Pixels 1080x2340 Pixels
Resolution
Processor 1.2 GHz 1.8 GHz
RAM 4GB 8GB
Storage 32GB 64GB

Table 4 illustrates the minimum and recommended

specifications the developers used for the development
of the system.

Software Specifications
The “e-LogMo: A Naujan Lake Water Level and Weather
Monitoring System with Mobile Notification Using Radio
Frequency for Victoria MDRRMO” was designed and
developed using the following software specifications.

Table 5. Software Specification for System Development

Minimum Recommended
Software
Specifications Specifications
Windows 11
Operating System Windows 8 64 bit
64 bit
Arduino 1.6.12
Arduino Platform Arduino 1.5 (or more updated
if available)
Adobe Photoshop Adobe Photoshop
Multimedia
CS3 CS6
 Table 5 shows the minimum and recommended
specifications for software used by the developers in
the development of the system.

System Analysis and Design

System Overview
The study “e-LogMo: A Naujan Lake Water Level and
Weather Monitoring System with Mobile Notification
Using Radio Frequency for Victoria MDRRMO” was developed
to address the lack of communication devices in times
of calamity in the Municipality of Victoria, Oriental
Mindoro. This system is generally conceptualized to
allow the users to view the status of the weather and
water level of the nearby lake, as well as the danger
posed relevant to the status, and the proper actions to
do with regards to it. It also comes with a notifying
siren that will blow the alarm once conditions of the
sensors are met. It serves as the medium of acquiring
safety amongst the people.
System Architecture

Connects to
uses

User
Mobile Internet
Phone

Connected to

GSM
Module
Arduino
NodeMCU Weather
ESP8266 Shield

Connected Channeled
to to

Power 4 channel
Motor Power Arduino
Relay Mega

Run using

charges

Solar
Panel Battery HC-SR04
Ultrasonic
Senor

Figure 4. System Architecture

The figure shows the system architecture of the system,
“e-LogMo: A Naujan Lake Water Level and Weather Monitoring
System with Mobile Notification Using Radio Frequency for
Victoria MDRRMO”. It displays the relevant information on the
water level and weather monitoring system for Victoria,
Oriental Mindoro. Significantly, the system is composed of
microcontrollers and processors, sensors, and power supply.
Prototype Architecture

Figure 5. Prototyoe Architecture

The figure shows the device architecture of the system,
“e-LogMo: A Naujan Lake Water Level and Weather Monitoring
System with Mobile Notification Using Radio Frequency for
Victoria MDRRMO”. It depicts the construction of the device
with the modules and materials shown. It is composed of the
sensors for gathering data and stimuli, solar panel and
battery as the power sources, sound horn, and water level
sensors.
Use Case Diagram

Figure 6. Use Case Diagram

The use case diagram shows the actor (clients) in the
application and the main process the user should do. Shown
on the figure is the processes that can be made by the users
in the system, including the login and create account,
configuration of settings and profile, mark themselves safe,
view water level and weather status, and request for response.
On the other hand, the admin can monitor the users and the
water level and weather status, generate reports, and update
response status.
Activity Diagram

Figure 7. Activity Diagram

Figure 7 illustrates the system's function in relation

to each project component in a systematic manner. This
clarifies the procedure as well as the connections between
all the components that are present.
Data Flow Diagram (DFD)
The Data Flow Diagram explains how the system and its
components work, and its relationship to each other, with the
flow lines indicating the process.

Context Diagram

Figure 8. Context Diagram

Figure 8 above illustrates the system's flow through a
well-organized context diagram to explain how the items are
connected to produce the intended system result. Data from
each entity flow through the other, allowing the system to
create a connection amongst the three.
Diagram 0

Figure 9. Diagram 0

Diagram 0 is shown in Figure 9, which also depicts the

system's flow in more detail. This diagram contains a data
store and supports multiple processes, in contrast to the
context diagram. It displays every process that makes up the
entire system. It also displays the information flow to and
from each process.
Database Schema

Figure 10. Database Schema

This figure shows the relationship of the data entity in

the database schema. It depicts that the entity User is in
1:1 relationship with the Application, and the admin has a
1:N relationship with both the users and sensors.

Testing and Evaluation

Developers are required to run tests during the
development stage to look for errors in the code and the
wiring connecting the hardware. Evaluation was carried out
to gather what needed to be changed and to identify errors
in order to make improvements to the system possible. This
stage aims to evaluate the system's performance and user
acceptability using ISO 25010 Quality Model.
Table 6 below shows the list of criteria used in
evaluating the system.
RATING
5-Very Acceptable 4-Acceptable 3-Moderately Acceptable
2- Not Acceptable 1- Very Not Acceptable

Table 6. Evaluation Tabular

1 Functional Suitability 5 4 3 2 1
1.1 The project can successfully detect
weather and water level.
1.2 The project is able to give accurate
measurement/ or parameters with the use
of different sensors.
1.3 The project provides the users with
specific data and information.
1.4 The project enabled the users to
experience a quicker access to disaster
responses.

2 Performance Efficiency 5 4 3 2 1
2.1 The project prototype is working even
without electricity.
2.2 The project can be utilized by the user
with or without internet connection.
2.3 The project notifies the end user based
on the default value of measurement or
parameters.

3 Compatibility 5 4 3 2 1
3.1 The project can perform its function in
different android operating system not
later than 7.0 android version.
 3.2 The project is accessible on android
mobile devices with or without internet
connection.
3.3 The project mobile application runs in
4GB memory and fits in 4.5 inches screen
resolution and above.

4 Usability 5 4 3 2 1
4.1 The project meets the necessities of the
target users.
4.2 The project is accessible, reliable, and
can be operated by the end users.
4.3 The project user interface is user-
friendly.
4.4 The project can be used to sound siren
in terms of weather conflicts.

5 Reliability 5 4 3 2 1
5.1 The project works properly.
5.2 The project is relevant and provides
accurate information to the end user.
5.3 The project can operate as intended
despite the presence of hardware or
software faults.
5.4 The project facilitates recovery
procedure in the event of system failure.

6 Security 5 4 3 2 1
6.1 The project can be accessed only by the
authorized users.
 6.2 The project is secured and protected in
terms of data transmission.
6.3 The project resources can be modified
only by those who have an authorized
access.
6.4 The project provides its unique account
to each end user.

7 Maintainability 5 4 3 2 1
7.1 The project is easy to install and
maintain.
7.2 The project can be modified to improve,
correct or adapt it to changes in
environment, and in requirements.
7.3 The project can be modified without
introducing defects or degrading
existing product quality.
7.4 The project resources can be updated and
modified easily.

8 Portability 5 4 3 2 1
8.1 The project has access to easy
modification.
8.2 The project can be transferred to another
location.
8.3 The project is adaptive to any given
environment.
8.4 The project’s mobile application is
compatible with different android
processor.
Functional Suitability. This refers to how well, under
specific circumstances, the system or product meets the needs
of the users.
Performance Efficiency. This speaks to the system's capacity
to deliver effective performance in relation to the available
resources.
Compatibility. The device or component is compatible with
the environment and with various mobile versions.
Usability. The device or system can be used by the target
users to a carry out purpose with effectiveness, efficiency
and satisfaction in an intended context of use.
Reliability. This refers to a component's ability to reliably
perform specified functions over a specified time period.
Security. The project or system protects information and data
that is only accessible through a single account
authorization.
Maintainability. The system or device can be modified and
maintained to be corrected, allowing it to adapt to changes
in the environment and requirements.
Portability. This refers to the project's or component's
ability to be transferred from one hardware, software, or
operational environment to another.

Mean Scale
Scale Statistical Limit Verbal Description
5 4.50-5.00 Very Acceptable
4 3.50-4.49 Acceptable
3 2.50-3.49 Moderately Acceptable
2 1.50-2.49 Not Acceptable
1 1.00-1.49 Very Not Acceptable
Table 7. Mean Scale
 The Table 7 shows the mean in the quantitative scaling
with its corresponding qualitative description. It suggests
that five (5) is the highest and one (1) as the lowest.