Data Management System Design of Disaste

International Research Journal of Computer Science (IRJCS) ISSN: 2393-9842
Issue 04, Volume 5 (April 2018) www.irjcs.com
DATA MANAGEMENT SYSTEM DESIGN OF DISASTER

EVENTS REPORT CASE STUDY: WEST JAKARTA FIRE
DEPARTMENT
Laurentius Supandi,
Faculty of Computer Science
Universitas Mercu Buana , Indonesia
laurentiustius@gmail.com
Yaya Sudarya Triana
Faculty of Computer Science
Universitas Mercu Buana-Indonesia
yaya.sudarya@mercubuana.ac.id
Manuscript History
Number: IRJCS/RS/Vol.05/Issue04/APCS10083
https://doi:/10.26562/IRJCS.2018.APCS10083
Received: 04, April 2018
Final Correction: 16, April 2018
Final Accepted: 21, April 2018
Published: April 2018
Citation: Supandi & Triana (2018). DATA MANAGEMENT SYSTEM DESIGN OF DISASTER EVENTS REPORT CASE
STUDY: WEST JAKARTA FIRE. IRJCS:: International Research Journal of Computer Science, Volume V, 151-159.
doi://10.26562/IRJCS.2018.APCS10083
Editor: Dr.A.Arul L.S, Chief Editor, IRJCS, AM Publications, India
Copyright: ©2018 This is an open access article distributed under the terms of the Creative Commons Attribution
License, Which Permits unrestricted use, distribution, and reproduction in any medium, provided the original author
and source are credited
Abstract —West Jakarta Fire Department in the process of storing the disaster event report still use the file in
manual format. The subject becomes less effective given the large number of missing files or the difficulty of
finding files. On the other hand, there are also limitations of the number of telephone offices, then required a
system that can manage reports while handling the limitations of the number of telephone offices by using
descriptive methods. So from these problems built the design of Disaster Management Report Management
System and is expected to simplify the management of reports and handle the limitations of the number of
telephone.
Keywords: Fire Department; Disaster Report; Disaster Relief;
INTRODUCTION
Firefighting is a very stressful job with unique physical, clothing and environmental challenges that increase the
potential for dehydration [1].Firefighters are stressed out every day in their workplace. Their ability to cope with
stress affects their capacity to function effectively in emergency situations. Communities also have the ability of
fire-fighting personnel to carry out their responsibilities effectively. Given the threat of natural disasters, threats
of terrorist attacks, mass casualties, and major environmental incidents, communities rely on fire-fighting
personnel services that work long hours with little help in this situation. Fire departments and personnel working
in those settings need to understand the stress involved and identify and develop effective coping
strategies[2].Fire may be caused by natural factors such as lightning, earthquakes, volcanic eruptions and
droughts, while fires can also be caused by human factors usually caused by negligence, such as improper
installation of electrical installations, and excessive use of electrical equipment beyond safe loads [3].Some
research, especially in rescue services, deals with professional learning of firefighters. In this case, four themes
can be identified.
_________________________________________________________________________________________________
IRJCS: Impact Factor Value – SJIF: Innospace, Morocco (2016): 4.281
Indexcopernicus: (ICV 2016): 88.80
© 2014- 18, IRJCS- All Rights Reserved Page -151
All of which can be termed as learning in practice and the fourth as training-based learning about practice: i)
Personal experience of training and rescue initiatives can realize knowledge and skills; ii) Through experienced
firefighters about solving problems during rescue initiatives, inexperienced firefighters can partake from a shared
experience base consisting of interpretation and assessment frameworks, iii) By participating in less-experienced
day-to-day activities can take part of collective and silent knowledge embodied in work methods, procedures, and
equipment at work and iv) Training including textual sources such as training guides and safety prescriptions can
provide knowledge of practice. What is common to this study is that professional learning is closely related to
work life, where actual learning should occur[4].
The rapid growth of data collection gives us a lot of data, making manual analysis harder to do. The majority of
data consists of spatial elements. In addition, the need to analyze the data increases as the amount of available
data continues to grow, mostly containing the (spatial) location element. The rapidly growing applications of
spatial data include the following areas: (1) mobile communications data, (2) internet data, (3) data on utilization
of Global Positioning System (GPS), (4) weather data, and (5) migration data population. Two attributes of spatial
data are object descriptions (referred to as non-spatial attributes) and information relating to spatial elements
(referred to as spatial attributes). Both are important components of spatial data[5]. Technological advances are
something that cannot be avoided in this life, because technological advances will go according to the progress of
science. In the beginning, technology grew slowly. But along with the advancement of cultural level and human
civilization, the development of technology developed rapidly. The more advanced the culture, the more
developed the technology because the technology is a cultural developer to progress by leaps and bounds[6]. In
the management of disaster report data in West Jakarta Fire Department still use the file in manual format. The
subject becomes less effective given the large number of missing files or the difficulty of finding files. On the other
hand the limitations of the number of telephones at the office became one of the causes of the difficulty of
reporting it entered. For that we need to build the design of the Management System Report Disaster Events West
Jakarta Fire Department.
I. METHOD OF DESIGNING
The method used in search data descriptively, that is by giving a clear and precise picture in accordance with
actual conditions to the object of research and data obtained used as material in the preparation of this report[7].
Here are some phases in the disaster management cycle[8] :
(1) Mitigation: Activities that reduce the likelihood of a hazard or a hazard that turns into a disaster.
(2) Risk Reduction: Anticipatory measures and actions that seek to avoid future risks as a result of disasters.
(3) Prevention: Prevent disaster.
(4) Preparedness: A plan or preparation designed to save lives or possessions, and assist in the response and
rescue service operations. This phase includes execution / operation, system early warning and capacity
building so that residents will react appropriately when early warning is issued.
(5) Response: Includes actions taken to save lives and prevent property damage, and preserve the environment
during an emergency or disaster. The response phase is the implementation of the action plan.
(6) Recovery: Includes actions that help people to return to normal after a disaster.
Based on summary reports of each death, will be grouped according to specific tasks performed during the onset
of symptoms or immediately before sudden death. This category is fire fighting; alarm response; alarm back;
physical training; emergency medical services, rescue, and other non-fire emergencies; and non-emergency tasks.
Death is classified as related to the suppression of fire if it occurs when the person is fighting fire or in a fire place
after his oppression. The alarm response involves a response to an emergency, including an incorrect alarm. The
alarm return includes all occurrences during the return of events and incidents that occur within hours of an
emergency call. Physical training includes all physical fitness related activities, physical ability testing, and
simulation or direct fire, rescue, emergency, and search exercises[9]. Attached shoulder press exercises are a
substitute for lifting weights completed on solid body power racks using standard Olympic bars with standard
Olympic size weights at a speed of 2.5 kg[10]. For system development using Pressman method, like Figure 1 [11]:
Figure 1- Waterfall Pressman.
________________________________________________________________________________________________
_
Here is an explanation of the Figure 1[11] :
a. Communication (Project Initiation & Requirements Gathering)
Before starting a technical work, it is necessary to communicate with customers to understand and achieve
the goals to be achieved. The results of such communications are project initialization, such as analyzing the
problems encountered and collecting the necessary data, and helping to define the features and functions of
the software.
b. Planning (Estimating, Scheduling, Tracking)
Planning stages that explain the estimation of technical tasks to be performed, the risks that can occur, the
resources required in making the system, the product work to be produced, scheduling work to be
performed, and tracking the process of system work.
c. Modeling (Analysis & Design)
Design stage and system architecture modeling that focus on designing data structure, software architecture,
interface display, and program algorithm.
d. Construction (Code & Test)
The process of translating design forms into code or forms / languages that can be read by machines. After
the coding is complete, testing the system and also the code that has been made. The goal is to find errors
that may occur to be fixed later.
e. Deployment (Delivery, Support, Feedback)
Stages of software implementation to the customer, software maintenance periodically, software
improvement, software evaluation, and software development based on feedback provided for the system
can keep running and developing in accordance with its function.
From several stages of the SDLC using the waterfall method contained in Figure 1, the data management
system on the disaster occurrence report in West Jakarta will use the method up to the Design stage.
In the design of this system required a system modeling process using Unified Modeling System (UML)
diagram that is Use Case Diagram, Class Diagram technique for designing DataBase and Activity Diagram for
workflow depiction (activity)..
a) Current Use Case Diagram
Figure 2 Current Data Management System of Disaster Events Report.

The current system in Figure 2 is the community actors reporting via telephone and the fire department staff
receive reports via telephone and manually input reports.
b) Use Case Diagram Proposed
Figure 3 Proposed Data Management System of Disaster Events Report.
________________________________________________________________________________________________
_
The system to be proposed in Figure 3 is the community actors login to the website, can input the report, and view
the report while the firefighter actor can login into the system, manage the report data and print report.
c) Class Diagram
Class Diagram is a diagram that can be used to present class, class components, and relationships between each
class.In addition Class diagrams describe the types of objects in the system and various kinds of static
relationships [12]. So in the design of a DataBase required a Class Diagram.
Figure 4 Class Diagram of data management of Disaster Events Report.

The data management class diagram shown in Figure 4 shows the three classes and relationships between the
classes. The three classes are admin, community and disaster report.
d) Activity Diagram
Activity Diagram is a flow chart, consisting of a set of vertices interconnected by the directed edge. Activity
Diagram is used for modeling the flow of various types of systems independently of its implementation[13].
Figure 5 Activity Diagram of Disaster Events Report.

Activities that will be executed in Figure 5 is the public can open the website and can register the account and the
system stores the account then the community can create reports and systems to store the report and admin
firefighters to process the report, the process will take a maximum of 5 minutes and the system will send the
verification report to the e-mail that has been registered.
________________________________________________________________________________________________
_
If there is no report verification e-mail within less than 5 minutes then the community can make a re-report. After
getting the e-mail verification report admin sending officers to the location reporting time travel officer to the
location of approximately 30 minutes if within 30 minutes the officer did not come then the public can telephone
call center contained in the website and notify the reporting number contained in the e-mail, but if the officer has
arrived then the fire extinguisher can print the report.
Database specifications
Table 1 Table of Admin.
No Field Data Type Long Information
1 Username Varchar 25 NIP Admin
2 Password Varchar 25 Password Admin
The admin table consists of two fields, namely: username and password.
Table 2 Table of Community
1 NIK Char 35 NIK Community
2 Name Varchar 35 Name of Society
3 Address Varchar 55 Address Community
4 Phone_Number Varchar 12 Phone Number Community
5 Email Varchar 35 E-mail Community
6 Username Varchar 35 Registration Code Account
7 Password Varchar 35 Password Account Community
The community table consists of seven fields, namely: nik, name, address, telephone number, e-mail, username,
and password.
Table 3 Table of Disaster Events Report
1 Report_Date Date Reporting date
2 Report_Number Varchar 35 Reporting number
3 Complainant Varchar 35 Name of the complainant
4 NIK_Complainant Varchar 35 Nik of the complainant
5 Disaster_Address Varchar 55 Address of disaster
6 Replacement_Address Varchar 55 Address replacement of disaster
7 Disaster_Type Char 1 Disaster type consists of two categories : Fire and Non Fire
8 Categories_Place Char 1 Place categories consist of four categories : housing, public
and trading, industry, and vehicles
9 Type_Building Char 1 Type of building consist of three categories : low, medium,
and high
10 Disaster_Object Varchar 45 The object of a disaster
Disaster event report table consists of ten fields, namely: date of report, reporting number, name of the
complainant, reporter, address, replacement address, disaster type, disaster category, building type, and disaster
object.
II. RESULTS
In designing this system there are 3 display design, that is before login; after login; and how to login, register and
forget the password. That can be distinguished from some usable menus. To find out more please see the picture
and explanation below.
Display Before Login
Figure 6 Home.
________________________________________________________________________________________________
_
On the main menu screen, the user can select the home menu: news portal running, profiles, disaster reports, and
call center. On the main menu screen there is also a news portal of disaster events that occurred in West Jakarta or
Indonesia. On the other hand there is also a menu to register an account located on the right side above.
Figure 7 Profile.
On the profile menu screen, the user can select the history menu of firefighters and the fire fighting organization
structure. If the user chooses the history of fire extinguishers there will be a history of firefighters from the
beginning to the latest, but if the user chooses the structure of the firefighting organization it will appear the
structure of the fire fighting organization.
Figure 8 Disaster Report.

On the disaster report menu screen there are reports of disasters ever entered by the community and have been
resolved by firefighters.
Gambar 9 Call Center.

On the call center menu screen there is the address of the office or post fire service station located in West Jakarta.
_________________________________________________________________________________________________
- Display After Login
Figure 10 Home Menu.

On the home menu screen shown in Figure 10 has a difference in Figure 6 which is on the top right side there is a
setting button that can be used to set changes to e-mail, username and password other than that the user can not
change it and button out to remove the account already registered.
Figure 11 Disaster Report Menu.

The disaster report screen shown in Figure 11 is different from Figure 8 which lies in the process of adding data
and editing data that can be done after the user logs in.
Figure 12 Button Add Data.

In the form of additional data users can fill in reports such as names, nik, address events, types of disasters,
catastrophic categories, building types and building objects. Each time the user adds data, the user can not change
the reporting date because the date is obtained from the reporting date and the user receives a reporting number
which can be used if the officer has not arrived within the specified time.
________________________________________________________________________________________________
_
Gambar 13 Button View

In the form view report the user can see the reporting results that have been entered by the user itself.
- Sign In, Sign Up and Forgot Password
Figure 14 Login Form.

In the entry form, the user can enter into the system with the condition that the user must have a registered
account if the user does not have a registered user account can press the register button to register, but if user
forgot to his account the user can press the forgot password.
Figure 15 Account Registration Form.

In the registration form, the user is required to fill in nik, name, residential address, telephone number, e-mail,
username and password. With the condition of e-mail must be active because it is required in the process of
changing passwords or account verification when forgotten password.
________________________________________________________________________________________________
_
Figure 16 Forgot Password Form.

In the forgotten password form, the user can type the e-mail that has been registered before and the user will get
the id and password sent to the e-mail.
III. CONCLUSION
The design of data management system of disaster event report in West Jakarta can help the admin to
facilitate the search data and can produce the output according to the need.
IV. REFERENCES
1. K. J. Dennison, D. R. Mullineaux, J. W. Yates, M. G. Abel. “The Effect Of Fatigue And Training Status On Firefighter
Performance.” Journal of Strength and Conditioning Research. vol. 26 (4). pp. 1101-1109. 2012.
2. D. Milen. “The Ability of Firefighting Personnel to Cope With Stress”. Journal of Social Change. vol. 3. pp. 38-56.
2009.
3. Y. Adilla, S. Adyatma, D.Arisanty. “Faktor Penyebab Kerentanan Kebakaran Berdasarkan Persepsi Masyarakat
Di Kelurahan Melayu Kecamatan Banjarmasin Tengah.” Jurnal Pendidikan Geografi. vol. 3 (4). pp. 40-57. 2016.
4. Robert H. “Reformed firefighter training program in Sweden: conflicting instructor conceptions of professional
learning”. Nordic Journal of Vocational Education and Training. vol. 4. 2014.
5. Arief F. Huda, Ito Wasito, T. Basaruddin, Mujiono S. “Spatial Clustering Algorithm Based on Neighboring
Structure Approach”. Journal of Convergence Information Technology (JCIT). vol.8, (16). pp. 25-38. 2013.
6. Yaya S. Triana, Indah S. “Implementation Floyd-Warshall Algorithm for the Shortest Path of Garage”.
International Journal of Innovative Science and Research Technology. vol. 3, (2). pp. 871-878. 2018.
7. Riwidikdo, Handoko. 2008. Statistik Kesehatan. Jogjakarta : Mitra Cendikia Press.
8. T. D. Indriasari, K. Anindito, E. Julianto. “Analisis dan Perancangan Sistem Pengumpulan Data Bencana Alam.”
Jurnal Buana Informatika. vol. 6, (1). pp. 73-82. 2015.
9. S. N. Kales, E. S. Soteriades, C. A. Christophi, D. C. Christiani. “Emergency Duties and Deaths from Heart Disease
among Firefighters in the United States.” The New England Journal of Medicine. vol. 356, (12). pp. 1207-1215.
2007.
10.Stevenson et al. 2017. “Physical Employment Standards for UK Firefighters : Minimum Muscular Strength and
Endurance Requirements.” JOEM. vol. 59, (1). pp. 74-79. 2017.
11.Pressman, R.S. 2015. Software Engineering : a practitioner’s approach, McGraww-Hill, New York.
12.Mulyani, Sri. 2016. Metode Analisis dan Perancangan Sistem. Bandung : Abdi Sistematika.
13.J. Qin, T. Fahringer. 2012. Scientific Workflows : Programming, Optimization, and Synthesis with ASKALONand
AWDL. Springer, New York.
________________________________________________________________________________________________
_

Data Management System Design of Disaste

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Data Management System Design of Disaste

Uploaded by

Copyright:

Available Formats

International Research Journal of Computer Science (IRJCS) ISSN: 2393-9842

Issue 04, Volume 5 (April 2018) www.irjcs.com

DATA MANAGEMENT SYSTEM DESIGN OF DISASTER

Figure 1- Waterfall Pressman.

Figure 2 Current Data Management System of Disaster Events Report.

Figure 3 Proposed Data Management System of Disaster Events Report.

Figure 4 Class Diagram of data management of Disaster Events Report.

Figure 5 Activity Diagram of Disaster Events Report.

Figure 8 Disaster Report.

Gambar 9 Call Center.

Figure 10 Home Menu.

Figure 11 Disaster Report Menu.

Figure 12 Button Add Data.

Gambar 13 Button View

Figure 14 Login Form.

Figure 15 Account Registration Form.

Figure 16 Forgot Password Form.

You might also like