Securing Mobility in Bucaramanga Road Safety Control Based On A Mobile Application

Securing mobility in Bucaramanga:
Ingeniería Solidaria
Road safety control based on a
mobile application
Asegurando la movilidad en Bucaramanga: control de seguridad vial basado en
una aplicación móvil
Garantindo a mobilidade em Bucaramanga: controle da segurança viária a

partir de um aplicativo móvel
Fredy Angarita Reina1

Brayan Alfonso Aparicio Duran2
Pedro Alberto Arias Quintero3
Luis Gómez Salgado4
Richard De Jesús Gil Herrera5
Daniel Ricardo Delgado6
Received: September 15th, 2023

Accepted: December 4th, 2023
Available: March 8th, 2024
How to cite this article:

F. Angarita Reina, B.A. Aparicio Duran, P.A. Arias Quintero, L. Gómez Salgado, R.J. Gil Herrera, D.R. Delgado,
“Securing mobility in Bucaramanga: Road safety control based on a mobile application (Asegurando la
movilidad en Bucaramanga: control de seguridad vial basado en una aplicación móvil),” Revista Ingeniería
Solidaria, vol. 20, no. 1, 2024.
doi: https://doi.org/10.16925/2357-6014.2024.01.07
Research article. https://doi.org/10.16925/2357-6014.2024.01.07

1
Universidad Americana de Europa, Sede Cancún México, Av. Bonampak Sm. 6-Mz. 1, Lt. 1, 7, 77500 Cancún, Q.R., México.
Email: [email protected]
orcid: https://orcid.org/0000-0002-3590-593X
CvLAC: https://scienti.minciencias.gov.co/cvlac/visualizador/generarCurriculoCv.do?cod_rh=0001338072
2
Servicio Nacional de Aprendizaje - SENA, Calle 16 No.27 – 37, Bucaramanga, Santander, Colombia.
orcid: https://orcid.org/0000-0001-8794-5354
3
Universidad Cooperativa de Colombia, Sede Bucaramanga, Facultad de Ingeniería, Ingeniería de Sistemas, Grupo de
Investigación en Tecnologías de la Información GITI, Carrera 33 No 33 a-05, Bucaramanga, Santander, Colombia.
e-mail: [email protected]
4
Servicio Nacional de Aprendizaje - SENA, Calle 16 No.27 - 37, Bucaramanga, Santander, Colombia.
5
Universidad Americana de Europa, Sede Cancún México, Av. Bonampak Sm. 6-Mz. 1, Lt. 1, 7, 77500 Cancún, Q.R., México.
6
Sifati Group Ingeniería S.A.S., Grupo de Investigaciones Ciencia, Ingeniería e Innovación, Palermo, Huila, Colombia,
2 Securing mobility in Bucaramanga: Road safety control based on a mobile application
Abstract
Introduction: The smart city paradigm is made up of a set of actors who must operate jointly to guarantee road
flow. However, sometimes there are accidents, and they affect productive apparatus, cause minor or temporary
injuries and sometimes death of the individuals involved.
Problem: Events occur for multiple reasons and the authorities have difficulties in implementing controls that
minimize their occurrence since they do not have the necessary tools to capture and analyze timely information
on the claims that have been presented.
Objective: The objective is to increase road safety control and safeguard mobility in Bucaramanga. For this, a
mobile application is designed to capture accident data by implementing the Flutter framework and the Model-
View design pattern methodology. Controller (MVC).
Methodology: The development of software to analyze the large amount of information on road events. A da-
tabase is developed where said information is stored and processed using programming languages, coding
and data hosting. Design and process factors are also considered according to the user’s needs, which will
determine the interface and expected performance.
Results: A structured system for data capture with the ability to integrate the general community, streamline the
availability of information and facilitate decision making that deals with the problem in real time.
Conclusion: It is concluded that its implementation in the city fosters self-care for pedestrians and drivers,
facilitating the design of effective control measures by territorial entities, bringing the city of Bucaramanga
closer to sustainability.
Originality: This methodology for integrating events is unique in the country and is developed based on the
city’s own characteristics.
Limitations: The lack of information provided by the government actors.
Keywords: Road accidents, Road safety, mobility, sustainability, information / data management, App
Development.
Resumen
Introducción: El paradigma de la ciudad inteligente, está conformado por un conjunto de actores que deben
operar de manera conjunta para garantizar la fluidez vial, pero en ocasiones se presentan incidentes, que
afectan el sistema de movilidad, ocasionando lesiones leves o temporales y en ocasiones muerte de quienes
intervienen.
Problema: Los incidentes ocurren por múltiples motivos y las autoridades tienen dificultades para implementar
controles que minimicen su ocurrencia ya que no cuentan con herramientas suficientes para capturar y anali-
zar información oportuna sobre los reclamos que se han presentado.
Objetivo: El objetivo es incrementar el control de la seguridad vial y salvaguardar la movilidad en la ciudad

de Bucaramanga y para ello se diseña una aplicación móvil para capturar datos de incidentes mediante la
implementación del framework Flutter y la metodología de patrón de diseño Model-View. Controlador (MVC).
Metodología: El desarrollo de un software para analizar la gran cantidad de información sobre eventos viales,
se desarrolla una base de datos donde se almacena y procesa dicha información utilizando lenguajes de pro-
gramación, codificación y alojamiento de datos. También se consideran factores de diseño y proceso según las
necesidades del usuario, lo que determinará la interfaz y el rendimiento esperado.
Resultados: Como resultado se obtuvo un sistema estructurado para la captura de datos con capacidad de
integrar a la comunidad en general, agilizar la disponibilidad de información y facilitar la toma de decisiones
que atiendan el problema en tiempo real.
Ingeniería Solidaria e-ISSN 2357-6014 / Vol. 20, no. 1 / january-april 2024 / Bogotá D.C., Colombia
Universidad Cooperativa de Colombia
Fredy Angarita Reina, Brayan Alfonso Aparicio Duran, Pedro Alberto Arias Quintero, Luis Gómez Salgado, 3
Richard De Jesús Gil Herrera, Daniel Ricardo Delgado
Conclusión: Se concluye que su implementación en la ciudad de Bucaramanga fomenta el autocuidado de
peatones y conductores, facilitando el diseño de medidas de control efectivas por parte de las entidades terri-
toriales, acercando a la ciudad a la sostenibilidad.
Originalidad: Esta metodología de integración de eventos es única en el país y se desarrolla en base a las
características propias de la ciudad.
Limitaciones: La falta de información proporcionada por los actores gubernamentales.
Palabras clave: Incidentes viales, Seguridad vial, movilidad, sostenibilidad, gestión de información/datos,
Desarrollo de Apps.
Resumo
1. INTRODUCTION
In 2018, there were about 1.35 million deaths resulting from road accidents, of which
11%, i.e., almost 155,000 deaths, occurred in the Americas. This corresponds to a rate
of 15.6% per 10,000 people, according to the WHO report submitted at the end of the
aforementioned year [1]. These are similar rates to those submitted in Colombia in
2017, according to the report of road accidents in Ibero-America, where it was equal
to 13.8% per 100,000 inhabitants, leading to a fourth place ranking in the list of coun-
tries with more deaths in 2017, which is led by the Dominican Republic [2]. The above
figures are repeated year after year with few significant changes and this proves the
problems faced by today’s society in terms of mobility. Government administrations
have not been able to develop policies, plans, or programs that influence the causes
of the accidents that occur in the different territories due to the multiple factors such
as the condition of the roads, the weather, the condition of the vehicle, the traffic rules
of the area, the expertise of the driver, and the actions of the pedestrian. As one can
guess, a single strategy or action is not enough to deal with all the factors influencing
accidents, and if one implements any strategy without having the necessary knowl-
edge, one risks leaving aside important and high incidence factors[3]. Furthermore,
knowing the percentage of participation or the influence exerted by each factor is
only possible if reliable and timely information is available. This is difficult to achieve
because of the way in which the records are kept [4]–[6]. This is because with the cur-
rent system it takes a long time to receive the information, given that reports are made
manually by the traffic agents at the scene of the events. They are then taken on the
following days to the traffic control centers where the information is received and digi-
talized. All these steps cause investigations to start with delays due to factors external
to the incident itself, reducing the effectiveness and the efficiency of the investigative
groups and other actions that may occur after the analysis of the accident, such as
judicial, criminal, and governmental decisions. Therefore, the proposal is to formalize
in an experimental model the conceptual framework for road safety management
based on concrete data through the development of a system with a mobile applica-
tion that transforms road accident data into useful information for decision making.
Among its functions are the collection of relevant data from a road accident, by any
citizen, for processing, analysis of the accident rate, and subsequent publication of
results, facilitating decision making not only at the political-administrative level, but
also by the individual when the possible results of his/her actions are disclosed. This
information, generated by the implementation of the application, can also be useful
for academia as, throughout its study, it will be possible to design actions that have
a positive impact on society by reducing road accidents and increasing the safety of
road actors, making Bucaramanga a sustainable city.
The general purpose of this article is to safeguard mobility in Bucaramanga
through road safety control based on a mobile application. The specific objectives are:
1) To establish the functional requirements of the mobile subsystem for the collection
of information. 2) To design the relational database of the mobile subsystem for the
collection of information. 3) To structure the mobile application system for the capture
of information on road accidents in the city of Bucaramanga for the transformation of
data into useful information for decision making through a mobile application. 4) To
test the alpha and beta applications (real environment) for verifying its functionality
and making the recommended and/or convenient adjustments.
1.1. Theoretical framework

In the following section we will find a theoretical approach to the programming for
addressing the problems that many cities are currently experiencing with figures and
data from the latest road accident report. In addition, ICT will be introduced as an
effective tool for mobility management, showing models developed around the world
with their functions and the solutions they provide, to finally end up by detailing the
theoretical structure of the programming for the mobile application to be developed.
1.1.1. Road accident data

According to art. 2 of [7], road accidents are defined as “sudden and involuntary
events that are mostly predictable and produce affectations in the person generating
partial or permanent personal injuries and even death; regarding goods and vehicles,
such events produce damages that sometimes are irreparable and on the roads they
generate traffic jams and congestions causing delays when users try to reach their
destinations and an increased fuel consumption by the vehicles due to the time they
must operate to get out of the traffic jams.” Therefore, these are events that are to
be avoided at all costs, and to this end, the traffic departments of the cities have
to implement several plans and programs to improve mobility. At the national level,
the plans have not generated satisfactory results according to the forensic medicine
report where an increase of 1.85% of injured people between 2017 and 2018 are re-
ported; in addition, a rate of 13.8 in terms of death per 100,000 inhabitants is reported,
which is lower than the average of America (15.6) and higher than the statistic for
Europe (9.3) [8].
The report concludes emphasizing the importance of having performance indi-
cators and for that end it is vital to collect and analyze data and figures on road crashes
allowing the implementation of measures to improve mobility systems. In the local
context, the city of Bucaramanga presents several positive results compared to the
results for Colombia, since a decrease of 5% in the total number of accidents reported
for 2019 was shown, compared to the immediately previous period. This may be due
to specific efforts made by the local administration and the Traffic Department [9].
1.1.2. Mobility management through ICT application

The implementation of new information technologies has helped solve specific and
complex problems in different areas of a society up to the point of breaking para-
digms and becoming agents of change in a community. Urban mobility topics have
not been an exception. Outstanding studies of mobile applications that have enabled
significant changes have been reported, such as the following series of studies that
were conducted in Vietnam with the aim of knowing the incidence of factors such
as unhealthy lifestyles and risky behaviors in the traffic accidents of motorcycle cab
drivers based on applications [10]–[12]. The information was compiled from an on-
line survey where the data on demographics, the work patterns, and the incidence
factors of 600 drivers working in the three largest cities of Vietnam were obtained
by applying a binary linear regression model. Among drivers who suffer accidents,
the impact of factors was detected regarding education, distances traveled per day,
unhealthy habits such as smoking or drinking, risky driving behaviors such as the use
of cell phone, poor use of turn signals, lane encroachment, and others. The most out-
standing aspect is the amount of information obtained from the mobile application,
enabling real-time analysis, and a better understanding by the authorities, companies,
and users about their behaviors and risks [13], [14].
On the other hand, Celesti et al [15], looking for an alternative to monitor traffic
flow and alert notification based on OpenGTS and MongoBD, large amounts of traffic
data were processed in real time, allowing users to have the possibility of receiving alert
messages to avoid risks of possible accidents. Such alerts were useful for all kinds of
vehicle drivers, especially rescue vehicles such as ambulances. A similar application
along with a hardware prototype was developed by Ikram and Mahajan [16]. To prevent
traffic accidents, a technique based on information technologies was developed. It
alerts drivers with a buzzer and a message with the location of other vehicles that are
within the range of the application, allowing their real-time location. It is a useful tool
when maneuvers such as blind turns are required and/or when it’s necessary to know
whether a vehicle is traveling toward you at high speed. The main limitation of this
technique is the range of coverage, and the system only detects vehicles that also have
the application. Finally, in the development of the application performed by Nayak et
al [17], it was found that it overcomes the previous design limitation as the application
sends voice notifications when approaching or being around an accident-prone area
using a GPS system that specifies the virtual boundary (a geofence). It has Google’s
opensource API (Application Programming Interface) and Firebase as the backend,
which facilitates the storage of information in real-time databases. Such databases
are the starting point to configure accident-prone areas in Google maps and after the
areas are already configured, alerts can be sent to users who approach them. The user
must have the application to receive the notification. All these developments allow us
to appreciate the contributions made by the implementation of these technologies,
guaranteeing the collection of information in real time, timely alerts, and even the
handling of behavioral changes in users. Therefore, for this specific case we suggest
the development of a mobile application to allow any user to collect information of
road accidents, to centralize the information in a real- time database, analyze the com-
mon causes and patterns identifying areas more prone to accidents, and visualize the
results of the investigations [18], [19].
1.1.3. Design and programming of mobile applications

Nowadays, mobile applications are creating a new style of technology, differentiated
from desktop and web applications, which, although still important, have flaws in the
design and adaptability issues in devices such as digital tablets and smartphones
[20]. This has produced a considerable increase of device users to the extent that, by
August 2017, there were more than 4 billion internet users who use mobile devices,
who spend an average of 69% of their time using smartphones. This use covers more
than 70% of internet consumption in the world, and 50% of that time is spent on mo-
bile applications [21].
• Design Patterns. For the design and programming, a variety of factors such
as performance, technologies, graphics, and storage must be considered,
and they are aimed at providing a solution to the previously identified pro-
blem. In practice, solutions that start from scratch represent a considerable
investment in economic resources and time. Therefore, selecting require-
ments from previous solutions is a feasible option. Taking into account the
above, design patterns are introduced, which are defined as the description
of a problem that repeatedly occurs in the environment, to which a solution
can be applied an infinite number of times without doing the same thing
twice. Patterns are described in 11 elements, namely: pattern name, pur-
pose, applicability, structure, participants, collaborations, consequence, im-
plementation, example code, known uses, and relational patterns [22]. The
MVC design pattern is used to build user interfaces in Smaltalk-80. It covers

three aspects of a software application. Its acronym Model-View-Controller
(MVC) describes the separation of the application data (Model) from the
application interface (View) and the application logic (Controller) [23].
• Framework Flutter. This is a programming toolkit developed by Google. It
has a single opensource code for the development of applications and from
the same base and/or environments, it is compiled originally, for mobile,
web, and desktop devices. It allows the use of a set of widgets and its struc-
ture is distributed in layers, allowing for a fast customization and rendering,
with expressive and flexible designs [24].
• Performance. The performance of a mobile application is determined by
more than one measurement because it sometimes may refer to raw speed
and network speed or to UI (user interface) fluency and the lack of it. Jank
term occurs when the UI is not fluently rendered. For example, a frame
takes 10 times longer to be rendered, so it is discarded, and thus the ani-
mation is visibly shaken [25].
1.1.4. Design of the database

Databases are essential for the development of information systems, web applica-
tions, desktop applications, or any type of technological solution that is related to
data, where the data can be a text or an image. Large databases are the foundation
for the operation of applications such as Facebook, Twitter, and WhatsApp. There are
two types of databases, namely relational and nonrelational. The former type is also
known as SQL, which is an acronym for Structured Query Language [26]. As the de-
mand increased, the SQL standard was extended from the relational model to include
object-oriented language constructions, which is a programming methodology that
defines the autonomous collections of data structures and routines that are called
objects. However, with the increase of user demands, it became more noticeable
that the relational language was insufficient to meet the actual demand. This reality
makes data normalization a more complex process, as a result of this, nonrelational
or NoSQL databases were created [27]. In fact, NoSQL DBs are characterized by hav-
ing a collection of data that is similar but not the same, so there is no need to create
new relationships to add attributes to the database collection objects. This allows
them to be lighter and faster than relational databases [3], [28].
1.1.5. Database management system

The database management system (DBMS) is an application that allows users to de-
fine, create, and maintain the database, as well as provide controlled access. It deals
with the physical structure of data and their storage. DBMSs follow a model that is
similar to the one used for program development with object-oriented languages,
which makes an internal implementation of an object and a separate external speci-
fication. This means that users are not affected by internal implementation changes,
as they only see the external specification [29]. Currently, there are many DBMSs that
allow for the creation, the management, and the administration of databases, as well
as many that specify structures used for storing data and searches. According to
the management system, a certain number of tools can be used, such as serverless
transactions, security system, data integrity, and consistency. Among the best known
are MySQL, Baria Db, SQLite, PostgreSQL, SQL Server, and Firebase real-time data-
bases. The first one is the most used one because it is free, and the latter is exclusive
to Google, which is characterized by being opensource [30], [31]. Annex A shows a
comparison of the properties of the mentioned management systems.
2. MATERIALS AND METHODS

The development of a program that manipulates a considerable amount of data re-
quires a database where such information is stored and processed by programming
languages, coding and data hosting. Additionally, design and process factors must
be considered according to the user’s needs, which will determine the interface and
intended performance.
2.1. Design factors

The development should take into account functional design factors of the open data
processing system for road safety, which will be useful for research and administra-
tive decision making.
2.2. Process factors

A number of requirements are defined, such as power, for the system to operate on
any cell phone or tablet compatible with Android or IOS. The power consumption is
like the one used to check a chat application or to open Facebook. This has been
considered as a performance factor of the application. Through the Flutter applica-

tion, a performance of 60 frames per second (fps) or 120 fps is provided for devices
with 120 Hz refresh/updating needs. For 60 fps, frames are rendered approximately
every 16 minutes.
Input requirements: a form is needed to allow user registration to the system
and another one to report registrations to the database in real time.
Other requirements for the operation of the system are an arrangement or
DBMS, a database server, a backend and frontend developer, a server connection,
and a data hosting service to ensure the continuity in the supply. This service should
be obtained, but it is not very expensive. Additionally, as part of the operation, the labor
aspect must be considered, which is nothing more than users with the capacity to
interact with information and communication technologies.
2.3. Methodology
Through the MVC design pattern and using the Dart package, mvc_aplication in the
Google Flutter SDK, we obtain by default stocks of tools. This packaging provides a
reference of applications that offer common functions and features for the design
of cross-platform mobile applications. Thus, a new way is achieved for looking at
applications in terms of performance, since the use of Dart as Google’s application
language with a Framework Flutter enables a focused approach to improve the per-
formance of ATA time code (AOT).
In the development, an improvement between 10% and 20% in microbench-
marks can be observed with Dart 2 Common Front-End. The new language features
allow for performing functions when writing the script set using literal sentences.
Additionally, the load speed is improved during the execution and development pro-
cess due to improved code writing. Enhanced widgets from the code facilitate a clean
and native development of the application. In the application compilation, the efficien-
cy of perfect pixel IOS and Android is appreciated to help the native application. As the
coding progressed, the Dart language was applied to the set of material and Cupertino
widgets to test the UI.
2.4. Database selection

According to the types of use defined in Section 2.4, the NoSQL database is selected
because: It is multiplatform, it can be used in mobile devices, it allows database scal-
ing and the decentralization of information, it performs analytical tasks, and it does
not require a complex infrastructure. Additionally, this selection is made taking into
account future adaptations that the application may have within the framework of a
scaled project as it allows access to the creation, modification, and/or suppression of
parts that may eventually become unusable, generating an optimal performance on
the same data management.
2.5. Selection of DBMS

DBMS manipulates every aspect of the information without affecting the user, so
choosing an appropriate one facilitates tasks such as triggers, user management,
user authentication method and authentication recovery [32]. A review and compar-
ison were made of some nonSQL DBMSs [32], such as MongoDB [33], Apache [34],
Cassandra [35], CouchDB [36], Redis [37], Neo4j [38], and Firebase [39]. The compar-
ative summary can be found in Annex A. After comparing their properties, Firebase
was selected as the appropriate system, since Google provides all services, including
tools for failure analysis, testing, statistics, and projection. In addition, it has a wide
range of instructions and manuals that facilitate its implementation.
2.6. Implementation
For the design of the Road Accident Application, the users and ‘the behavior that each
user-role and their interactions should have’ were defined. Such roles are “administra-
tor”, who acts on the application permissions; creates the agent profiles; and modifies
incidents by some type of causality, and the traffic agent. The latter is an account
verified by the administrator with the permissions to create the claims, assign the
vehicles involved, and the penalties they can receive. The next role is accident verifier,
who is an actor with permissions to follow up incidents. They are typically represented
by the traffic agent verifying the process. The final role is the driver. This is a ge-
neric standard user with permissions to view the information and status of a claim
assigned to a license plate. The users and their functions according to the roles are
grouped in a “use case” diagram presented in Figure 1.
Administrator Creation of agents Cost Accident control
Moddification of
Follow-up
the type infraction
Creation of the Road accident

Traffic agent Driver
road accident information
To assing insolves Status of

vehicles road accident
Type of infraction
Figure 1. Diagram of the use case.

Source: own work
The initial structuring and modeling were based on a relational database, with
phpMyAdmin data manager with XAMPP control panel version 3.2.2, which was later
analyzed and compared with Google’s Firebase NoSQL database. The latter was con-
sidered the ideal one for the development of the application, so the Realtime engine
was migrated to Firebase’s Cloud-Firestore. This is because it offers better scaling
opportunities. It is important to highlight that the modeling of NoSQL databases is
not a common practice yet. The databases are related by means of an identifier, as a
JSON would do in programming having the Key=>Value. These can be dynamic data,
even in Firebase itself, due to the fact that it offers predetermined data types which
can be used in development. With Cloud-Firestore engines, the same document can
create a new collection that in turn can have other documents thus linking the data
that are necessary without the need to normalize data. Since they are within the same
“source,” they do not generate data redundancy.
The design of the relational model begins with the creation of the source code,
which can be seen in Annex B. The indicator table or primary key is the one that has
more relationships, such as the “road accidents” table as it is the one that is composed
of different fields that are annexes of other tables to complete the functional process.
This generates a logical order recorded in the data. Different tables that go along with
the process of generating the road accident claim can be seen. One of them is the “ve-
hicles” table. The license plate attribute is the main one of the tables, and it displays a
series of informative data such as the owner, model, vehicle type, color, and insurance
(SOAT) number. This set of data is part of the information history that will be saved
in the events to be recorded. Similarly, the interactions in the person and intervention
tables are set up, creating an optimal set of tables so that the database management
system does not display errors while performing operations. The entity-relationship
model shown in Figure 2 is then created.
Vehicle road accident Road accident

Road
Plate: Varchar Road accidentID: Int
Brand: Varchar Location: Varchar IRoad ID: Int
Color: Varchar Incident Date: Date and time Description: Varchar
Soat (Insurance): Varchar Type of record: Varchar
Technomechanics: Varchar Road Condition: Varchar
License: Varchar Environmental factor: Varchar Cause
Gender: Varchar Primary Cause: Varchar
Password: Varchar Affected property: Varchar Cause ID: int
Column Type affected property: Varchar Description: Varchar
affected property_value: Int
Evidence photo: mage
Diagram: image
Affected: int Enviroument
Description: Varchar
Actions undertaken: Varchar Environment ID: Int
Description: Varchar
Vehicle
Plate: Varchar
Brand: Varchar
Color: Varchar
Soat (Insurance): Varchar
Technomechanics: Varchar
License: Varchar Road accident Person
Gender: Varchar
Person
Password: Varchar
ID: int
ID: int Name: Varchar
Name: Varchar Condition: Varchar
Surname: Varchar Gender: Varchar
Age: int Plate: Varchar
Mail: Varchar
Occupation: Varchar
Follow-Up
City: Varchar
Gender: Varchar
Id Follow-up: Int Password: Varchar
Id Road accident: Int
Date Incident: date and time
Figure 2. Entity-relationship model.

Source: own work
According to the relationships established above, the following prototype of the

data collection is created:
• ROAD ACCIDENT,
cause_road accident city, environmental_conditions, road accident_descrip-
tion, path_description, road _status, date, time, road accident_ id:
• INJURED_PARTY/PERSON,
type_docum_id, id_injured_party, surname1, surname2, name1, name2, age,
sex, license_categoty, residence_address, education, resid_municip, ocuppa-
tion, type_actor_road,
expenses_health_by_road accident, is_hospitalized, survives_road accident,
days_hospitalization, alcohol_percentage, drugs, was using_cell phone, hel-
met_use, seat belt_use, medicines_uses,
• INVOLVED_VEHICLE,
color, vehicle_condition, tires, lights
• INSURANCES
non-contractual_insurer, soat_ insurer, non-contractual_policy_number, soat_
policy_number, non-contractual_policy, last_review, last_oilchange, id_vehicle,
brand, model, plate
• INTERVENTION
suggested_control, cost, review_date, intervention_id, other_accidents_
happened_insitu, post-intervention_review, road accidents_were avoided,
control_was implemented, re-intervention_was implemented
With the defined entities and models, the development of the mobile subsystem
of road accidents for Android devices is done following the MVC applied to mobile
devices implemented in the Framework Flutter, which provides facilities for the cre-
ation of multiplatform mobile applications with high performance using the same
source code, which optimizes the design time. The source code of the project logic is
located in the GitHub repository, at the following link: https://github.com/fredytellor/
siniestros_app
3. RESULTS
The social problem resulting from the accident rate on urban roads in cities is veri-
fied, and it produces a considerable number of injured people (39,537) and casualties
(6,879) in the country[8] compared to the previous year (40,115 and 6,754, respec-
tively), which evidences that it is a complex issue because many factors are involved
as described above. Therefore, a conceptual framework was developed through the
design of a mobile application for the management of road safety, which allows for
the collection of relevant data from a road accident by any citizen, to obtain, in an
agile way and in real time, data on road accidents, reducing the periods of process-
ing and the analysis of the corresponding entities. To verify its usefulness, alpha and
beta functionality tests were conducted by collecting information from some road
accident claims generated during the period from July 15, 2020 to July 21, 2020 to
be processed in the mobile application developed [40]. The data found can be seen
in Annex C.
To generate the road accident report, the data are recorded in a similar way to
the traditional paper format, which facilitates the transition from the traditional meth-
od due to the knowledge of the information to be entered. The difference lies in the
order of the information. The data are stored in the Firebase database together with
the evidence taken from the application about the incident and, as they are saved, they
are created with a unique incident code. Additionally, the application groups them by
order of entry or date, which is a mechanism that facilitates the search for the incident.
Upon entering the application, you will find a simple interface as shown in Figure 3, and
Figure 4 presents the list of searches for road accidents.
Figure 3. Interface for road accidents claims record.

Source: own work
Figure 4. History of reported claims.

Source: own work
As it can be observed, the interface contains only the necessary elements for
the recording of the incident, allowing the user to record each important aspect, such
as license plates, people involved, their condition, status, and probable cause. Also, by
including photographic entries as an integral part of the record, the user can corrobo-
rate any doubt or hypothesis based on this information. For each record it is possible
for the application to create a file in PDF format together with the photographic evi-
dence, if available, as shown in Figure 5. This file groups all the information recorded
for the incident, helping the user to check its details.
Description of the incident

or traffic accident
Identification of possible causes
Type of record
IDENTIFICATION Type of property affected
Class of property
Date and time of
affected
the incident
Economic impact Affected people

value
REMARKS Condition of affected people

UNDERTAKEN
Figure 5. Road accident report.

Source: own work
The user who generates the report will be able to have, in a single file, all the
information corresponding to the road accident, such as vehicle identification, road
condition, affected parties, their condition, and the actions that were taken or are being
taken at the moment. This way of summarizing information can streamline the report
and investigation process.
4. CONCLUSIONS
The literature surveyed and cases of applications found allowed us to demonstrate
the capacity of mobile applications to address the mobility problem in terms of road
safety for the city of Bucaramanga.
The developed application has the capacity to provide useful and timely data,
promoting the creation of effective measures and the generation of cultural changes
in the community, to increase road safety controls in the city of Bucaramanga.
The requirements were established in accordance with the current regulations
on accident reporting and investigation, identifying four roles for the application: ad-
ministrator, traffic agent, road accident verifier, and driver.
The database was created based on the definition of different roles, with their
attributes and relationships, and NoSQL databases were considered to be the most
suitable for the optimal functioning of the application.
The application system was designed using the MVC design pattern that
formed the basis for the development of the mobile application, which was essential
to ensure optimal operation and performance by implementing the Flutter framework

and Firebase database management system.
The functionality of the application was verified by registering road accidents
that occurred nearby, in the metropolitan area of Bucaramanga, within the framework
of the development of alpha and beta level tests. In these, users found an intuitive
system with similarities to the traditional method, something that would facilitate the
transition from one method to another. Additionally, some aspects that need to be im-
proved were identified, such as the possibility of registering two or more vehicles per
road accident and the personal information of the affected persons besides the driver.
5. REFERENCES
[1] World Health Organization, Global status report on road safety 2015. Ginebra, 2015. [Online].
Available: https://www.afro.who.int/publications/global-status-report-road-safety-2015
[2] United Nations, “Road Safety Performance Review Dominican Republic,” Santiago, 2018.
[Online]. Available: https://www.cepal.org/sites/default/files/project/files/cepal_rspr_dr.pdf
[3] O. R. Villar, O. R. Villar, F. C. Escobar, and G. P. Buitrago, “Vulnerable Road Users, Prioritization
of Urban Sectors with High Accident Rates: Review and Evaluation Of Methods,” Revista
Ingeniería Solidaria, vol. 15, no. 3, pp. 1–26, Sep. 2019. doi: https://doi.org/10.16925/2357
-6014.2019.03.04.
[4] S. Wilhelmsson, I. Arvidsson, P. H. Hemsworth, M. Andersson, J. Yngvesson, and J. Hultgren,

“Effects of a training intervention for Swedish pig transport drivers on physical workload and
time efficiency during loading,” Int J Ind Ergon, vol. 92, pp. 1–16, Nov. 2022. doi: https://doi.
org/10.1016/J.ERGON.2022.103356.
[5] H. Catalán, H. Lobel, and J. C. Herrera, “An automatic methodology to measure drivers’ beha-
vior in public transport,” J Intell Transp Syst, pp. 1–15, Jun. 2023. doi: https://doi.org/10.1080
/15472450.2022.2129019.
[6] L. Rosenda et al., “Working conditions and psicosocial risks in public transport drivers,”
Revista Cubana de Salud y Trabajo, vol. 18, no. 2, pp. 48–56, 2017. [Online]. Available: https://
www.medigraphic.com/cgi-bin/new/resumenI.cgi?IDARTICULO=76877
[7] G. A. Canal-Mora, Ley 769 de 2002. Senado, 2002, pp. 1–82. Accessed: Nov. 17, 2021. [Online].
Available: http://www.secretariasenado.gov.co/senado/basedoc/ley_0769_2002.html
[8] Instituto Nacional de Medicina Legal y Ciencias Forenses, Forensis, Datos para la vida. Bogotá,
2018. [Online]. Available: https://www.medicinalegal.gov.co/documents/20143/386932/
Forensis+2018.pdf/be4816a4-3da3-1ff0-2779-e7b5e3962d60
[9] N. González, “Informe de gestión enero a diciembre de accidentalidad,” Bucaramanga, 2020.

[Online]. Available: https://transitobucaramanga.gov.co/dtb/wp-content/uploads/2021/09/
230120-accidentalidad-inf-gest-control-vial.pdf
[10] D. Q. Nguyen-Phuoc, H. A. Nguyen, C. De Gruyter, D. N. Su, and V. H. Nguyen, “Exploring the

prevalence and factors associated with self-reported traffic crashes among app-based mo-
torcycle taxis in Vietnam,” Transp Policy (Oxf), vol. 81, pp. 68–74, Sep. 2019. doi: https://doi.
org/10.1016/J.TRANPOL.2019.06.006.
[11] D. Q. Nguyen-Phuoc, C. De Gruyter, H. A. Nguyen, T. Nguyen, and D. Ngoc Su, “Risky beha-
viours associated with traffic crashes among app-based motorcycle taxi drivers in Vietnam,”
Transp Res Part F Traffic Psychol Behav, vol. 70, pp. 249–259, Apr. 2020. doi: https://doi.or-
g/10.1016/J.TRF.2020.03.010.
[12] D. Q. Nguyen-Phuoc, O. Oviedo-Trespalacios, T. Nguyen, and D. N. Su, “The effects of unheal-

thy lifestyle behaviours on risky riding behaviours – A study on app-based motorcycle taxi ri-
ders in Vietnam,” J Transp Health, vol. 16, p. 100666, Mar. 2020. doi: https://doi.org/10.1016/J.
JTH.2019.100666.
[13] C. S. I. Cruz, C. S. I. Cruz, E. U. M. Flor, and M. I. V. Caicedo, “User-centered web accessibi-

lity: recommendations for ensuring access to government information for older adults,”
Revista Ingeniería Solidaria, vol. 19, no. 3, pp. 1–22, Sep. 2023. doi: https://doi.org/10.16925
/2357-6014.2023.03.02.
[14] L. Fernanda et al., “Sistema de drones para la gestión de riesgos,” Revista Ingeniería Solidaria,
vol. 19, no. 2, pp. 1–20, May 2023. doi: 10.16925/2357-6014.2023.02.06.
[15] A. Celesti, A. Galletta, L. Carnevale, M. Fazio, A. Lay-Ekuakille, and M. Villari, “An IoT cloud sys-
tem for traffic monitoring and vehicular accidents prevention based on mobile sensor data
processing,” IEEE Sens J, vol. 18, no. 12, pp. 4795–4802, Jun. 2018. doi: https://doi.org/10.1109/
JSEN.2017.2777786.
[16] N. Ikram and S. Mahajan, “A Hardware Based Technique with an Android Application to Avoid
Road Accidents,” Smart Innovation, Systems and Technologies, vol. 83, pp. 20–29, 2017. doi:
https://doi.org/10.1007/978-3-319-63673-3_3.
[17] B. Nayak, P. S. Mugali, B. R. Rao, S. Sindhava, D. N. Disha, and K. S. Swarnalatha, “GeoFencing-

Based Accident Avoidance Notification for Road Safety,” Advances in Intelligent Systems and
Computing, vol. 906, pp. 379–386, 2019. doi: https://doi.org/10.1007/978-981-13-6001-5_30.
[18] T. Shibayama and G. Emberger, “New mobility services: Taxonomy, innovation and the role
of ICTs,” Transp Policy (Oxf), vol. 98, pp. 79–90, Nov. 2020. doi: https://doi.org/10.1016/J.
TRANPOL.2020.05.024.
[19] M. Savastano, M. C. Suciu, I. Gorelova, and G. A. Stativă, “How smart is mobility in smart cities?
An analysis of citizens’ value perceptions through ICT applications,” Cities, vol. 132, p. 104071,
Jan. 2023. doi: https://doi.org/10.1016/J.CITIES.2022.104071.
[20] A. R. Wasil, E. H. Palermo, L. Lorenzo-Luaces, and R. J. DeRubeis, “Is There an App for That? A
Review of Popular Apps for Depression, Anxiety, and Well-Being,” Cogn Behav Pract, Oct. 2021.
doi: https://doi.org/10.1016/J.CBPRA.2021.07.001.
[21] A. N. Hannings, A. Darley, J. C. Kearney, B. L. Upchurch, and K. Groft, “Marketing mobile in-
fluenza vaccine clinics on a college campus,” Journal of the American Pharmacists Association,
Oct. 2021. doi: https://doi.org/10.1016/J.JAPH.2021.10.028.
[22] E. Gamma, R. Helm, R. Johnson, and J. Vilssides, Patrones de diseño: elementos de software
orientado a objetos reutilizable. Addison Wesley, 2017.
[23] I. Kim, E. Hacker, C. E. Ferrans, C. Horswill, C. Park, and M. Kapella, “Evaluation of fatigability
measurement: Integrative review,” Geriatr Nurs (Minneap), vol. 39, no. 1, pp. 39–47, Jan. 2018.
doi: https://doi.org/10.1016/J.GERINURSE.2017.05.014.
[24] P. Mainkar and S. Giordano, Google flutter mobile development quick start guide: get up and
running with iOS and Android mobile app development, vol. 1. Packt Publishing, 2019.
[25] J. M. J. Paulissen et al., “Performance and usability evaluation of a mobile health data capture
application in clinical cancer trials follow-up,” Tech Innov Patient Support Radiat Oncol, vol.
24, pp. 107–112, Dec. 2022. doi: https://doi.org/10.1016/J.TIPSRO.2022.10.005.
[26] R. A. Patton, J. Ogle, and T. Laird, Eds., Designing SQL Server 2000 Databases. London: Elsevier,
2001. doi: https://doi.org/10.1016/B978-1-928994-19-0.X5000-3.
[27] J. L. Harrington, SQL Clearly Explained. Elsevier, 2010. doi: https://doi.org/10.1016/

C2009-0-61592-0.
[28] “SQL Server 2000 Overview and Migration Strategies,” Designing SQL Server 2000 Databases,
pp. 1–56, Jan. 2001. doi: https://doi.org/10.1016/B978-192899419-0/50004-X.
[29] S. Santini, Exploratory Image Databases. Elsevier, 2001. doi: https://doi.org/10.1016/B978-0-

12-619261-2.X5000-4.
[30] A. Viloria, G. C. Acuña, D. J. A. Franco, H. Hernández-Palma, J. P. Fuentes, and E. P. Rambal,

“Integration of Data Mining Techniques to PostgreSQL Database Manager System,”
Procedia Comput. Sci., vol. 155, pp. 575–580, Jan. 2019. doi: https://doi.org/10.1016/J.
PROCS.2019.08.080.
[31] B. Yang, S. Wang, S. Yu, and T. Olofsson, “Soft-mobility in a winter-dominant city: A case study
by comparing Nordic and non-Nordic residents in Umeå,” Cities, vol. 102, p. 102727, Jul. 2020.
doi: https://doi.org/10.1016/j.cities.2020.102727.
[32] Y. Januzaj, J. Ajdari, and B. Selimi, “DBMS as a cloud service: Advantages and disadvanta-
ges,” Procedia Soc Behav Sci, vol. 195, pp. 1851–1859, Jul. 2015. doi: https://doi.org/10.1016/J.
SBSPRO.2015.06.412.
[33] A. Mailewa, S. Mengel, L. Gittner, and H. Khan, “Mechanisms and techniques to enhance the
security of big data analytic framework with MongoDB and Linux Containers,” Array, vol. 15,
p. 100236, Sep. 2022. doi: https://doi.org/10.1016/J.ARRAY.2022.100236.
[34] T. Singh, S. Gupta, Satakshi, and M. Kumar, “Performance Analysis and Deployment of
Partitioning Strategies in Apache Spark,” Procedia Comput Sci, vol. 218, pp. 594–603, Jan.
2023. doi: https://doi.org/10.1016/J.PROCS.2023.01.041.
[35] A. Herguth and S. Wilking, “CASSANDRA – a tool for analysis and prediction of time resolved
BO defect dynamic on lifetime and cell level,” Energy Procedia, vol. 124, pp. 60–65, Sep. 2017.
doi: https://doi.org/10.1016/J.EGYPRO.2017.09.340.
[36] G. Manyam, M. A. Payton, J. A. Roth, L. V. Abruzzo, and K. R. Coombes, “Relax with CouchDB
— Into the non-relational DBMS era of bioinformatics,” Genomics, vol. 100, no. 1, pp. 1–7, Jul.
2012. doi: https://doi.org/10.1016/J.YGENO.2012.05.006.
[37] J. Seo, K. Kim, S. Seo, and S. Park, “DARK: Deep automatic Redis knobs tuning system depen-
ding on the persistence method,” Expert Syst Appl, vol. 221, p. 119697, Jul. 2023. doi: https://
doi.org/10.1016/J.ESWA.2023.119697.
[38] A. Rajšp and I. Fister, “Neo4j graph dataset of cycling paths in Slovenia,” Data Brief, vol. 48, p.
109251, Jun. 2023. doi: https://doi.org/10.1016/J.DIB.2023.109251.
[39] M. Ohyver, J. V. Moniaga, I. Sungkawa, B. E. Subagyo, and I. A. Chandra, “The Comparison

Firebase Realtime Database and MySQL Database Performance using Wilcoxon Signed-Rank
Test,” Procedia Comput Sci, vol. 157, pp. 396–405, Jan. 2019. doi: https://doi.org/10.1016/J.
PROCS.2019.08.231.
[40] J. M. Gómez and S. M. Serna, “Metodología para un Plan Local de Seguridad Vial - Modos No
Motorizados - (PLSV-MNM): caso Medellín,” Revista Ingeniería Solidaria, vol. 10, no. 17, pp.
175–178, Dec. 2019. doi: https://doi.org/10.16925/IN.V10I17.878.

Securing Mobility in Bucaramanga Road Safety Control Based On A Mobile Application

Cargado por

Copyright:

Formatos disponibles

Securing Mobility in Bucaramanga Road Safety Control Based On A Mobile Application

Cargado por

Información del documento

Título original

Derechos de autor

Formatos disponibles

Compartir este documento

Compartir o incrustar documentos

Opciones para compartir

¿Le pareció útil este documento?

¿Este contenido es inapropiado?

Copyright:

Formatos disponibles

Securing Mobility in Bucaramanga Road Safety Control Based On A Mobile Application

Cargado por

Copyright:

Formatos disponibles

Securing mobility in Bucaramanga:

Garantindo a mobilidade em Bucaramanga: controle da segurança viária a

Fredy Angarita Reina1

Received: September 15th, 2023

How to cite this article:

Research article. https://doi.org/10.16925/2357-6014.2024.01.07

Limitations: The lack of information provided by the government actors.

Objetivo: El objetivo es incrementar el control de la seguridad vial y salvaguardar la movilidad en la ciudad

Limitaciones: La falta de información proporcionada por los actores gubernamentales.

1.1. Theoretical framework

1.1.1. Road accident data

1.1.2. Mobility management through ICT application

1.1.3. Design and programming of mobile applications

MVC design pattern is used to build user interfaces in Smaltalk-80. It covers

1.1.4. Design of the database

1.1.5. Database management system

2. MATERIALS AND METHODS

2.1. Design factors

2.2. Process factors

considered as a performance factor of the application. Through the Flutter applica-

2.4. Database selection

2.5. Selection of DBMS

Administrator Creation of agents Cost Accident control

Creation of the Road accident

To assing insolves Status of

Figure 1. Diagram of the use case.

Vehicle road accident Road accident

Figure 2. Entity-relationship model.

According to the relationships established above, the following prototype of the

Figure 3. Interface for road accidents claims record.

Figure 4. History of reported claims.

Description of the incident

Economic impact Affected people

REMARKS Condition of affected people

Figure 5. Road accident report.

to ensure optimal operation and performance by implementing the Flutter framework

[4] S. Wilhelmsson, I. Arvidsson, P. H. Hemsworth, M. Andersson, J. Yngvesson, and J. Hultgren,

[9] N. González, “Informe de gestión enero a diciembre de accidentalidad,” Bucaramanga, 2020.

[10] D. Q. Nguyen-Phuoc, H. A. Nguyen, C. De Gruyter, D. N. Su, and V. H. Nguyen, “Exploring the

[12] D. Q. Nguyen-Phuoc, O. Oviedo-Trespalacios, T. Nguyen, and D. N. Su, “The effects of unheal-

[13] C. S. I. Cruz, C. S. I. Cruz, E. U. M. Flor, and M. I. V. Caicedo, “User-centered web accessibi-

[17] B. Nayak, P. S. Mugali, B. R. Rao, S. Sindhava, D. N. Disha, and K. S. Swarnalatha, “GeoFencing-

[27] J. L. Harrington, SQL Clearly Explained. Elsevier, 2010. doi: https://doi.org/10.1016/

[29] S. Santini, Exploratory Image Databases. Elsevier, 2001. doi: https://doi.org/10.1016/B978-0-

[30] A. Viloria, G. C. Acuña, D. J. A. Franco, H. Hernández-Palma, J. P. Fuentes, and E. P. Rambal,

[39] M. Ohyver, J. V. Moniaga, I. Sungkawa, B. E. Subagyo, and I. A. Chandra, “The Comparison

También podría gustarte