Figure x1

Context – Free Diagram of the Study

Figure x1 shows the context free diagram of the proposed system, Disaster and

Accident response and Monitoring System. Three external entities interact with the

system: the system administrator, MDRRMO Administrator/Sub-admin and the mobile

app, Emergency. Emergency is a mobile application that collects location, disaster type

status of people and rescue update. The system administrator has the full control of the

system. The input to the system includes login details, deployment and system user

profiles. Reports and app user details and notification can be access by the system

administrator. On the other hand, the MDRRMO administrator or the sub-admin only

view the request and tracing report and deployment details.

 Figure x2
Data Flow Diagram (DFD) of the Proposed System

Figure x2 shows the Data Flow Diagram for the system. This diagram shows the

main sub-processes and database used in Disaster and Accident Response and

Monitoring System. As shown in figure x2, there are three entities interacting with the

system, the System administrator, the MDRRMO or sub-administrator and a mobile

application named Emergency.

 Emergency, a mobile app for users can sign-up and log in the app. Once verified,

the user can update the current location through the get location process, which results

in the current location. The next process, set disaster type, allows the user to set the

type of disaster or accident happening on the current location. Finally, the user sets the

status, together with current location and disaster type are used as request detail. The

information set by the users is saved as request detail in the DARMS database which is

the basis for the Disaster and Accident Response and Monitoring System in responding

to particular disaster and accident.

On the other hand, once the system administrator or MDRRMO administrator

logs in and verified by the system, both can view the request and tracing report, as seen

in process 4, which results in the request for deploy personnel process. As a result of

process 5, the deployment details is saved to the database. These details are used in

sending notification to the deployed personnel and administrators, both system admin

and sub-admin, for response and monitoring purposes. The deployment details will then

notify the deployed rescuer, as seen in process 6. Once the rescuer completed the task,

he/she has to update the rescue completion on the mobile app. The request and

deployment details are used in generating report in process 7, which results in analytic

report that can only be accessed by the system administrator. Moreover, the system

administrator can add system users that generates user profile.

 0
Login details

deployment
System User Profile
System
Administrator Report DISASTER AND
App Users detail ACCIDENT Location
Notifications
RESPONSE AND Disaster type
Emergency (Mobile
Login details MONITORING Status App)

Deployment SYSTEM Rescue Update

MDRRMO
Administrator/Sub- Report
admin
Notifications
Emergency (Mobile App)
1 2 3

Disaster
Current
Login details type
Get Location location Set Disaster Set Status
Mobile App User

Login details
Rescuer Request & Deployment
Details
Status
Update Rescue Update

Notification
Request
details
MDRRMO Admin Login details
(Sub-admin)
Request Details
DARMS DB
Deployment Details

Request &
4 5 7 Deployment
Details

Log-in
System Admin details View Request Deploy Generate
Request and Personnel Report
Tracing

Log-in details

Report (Analytics)

Log-in details Add System User Profile

Users

Notification