2023 International Conference on Converging Technology in Electrical and Information Engineering (ICCTEIE)

Development of ORM Modules for Public

Administration Service Request Business Processes
Using Open ERP
Abdurrahman Al-amin Buluatie Teguh Bharata Adji Igi Ardiyanto
Department of Electrical and Department of Electrical and Department of Electrical and
Information Engineering Information Engineering Information Engineering
Gadjah Mada University Gadjah Mada University Gadjah Mada University
Yogyakarta, Indonesia Yogyakarta, Indonesia Yogyakarta, Indonesia
abdurrahmanal- adji@ugm.ac.id igi@ugm.ac.id
aminbuluatie490136@mail.ugm.ac.id

Abstract— The role of information technology is increasingly
vital in transforming governance and public services in the era
of globalization. It compels public organizations in developing
countries to pursue optimal service through Internet
applications. However, regional autonomy policies pose a
significant challenge in integrating information technology. This
study draws insights from Jayawijaya Regency, illustrating how
local governments address autonomy challenges. The
Population and Civil Registry Office is pivotal in citizen
administration within this context. Encountered problems
include inadequate data integration, and complex
administrative processes, resulting in difficulties accessing and
consolidating data. Administrative processes can be intricate
and time-consuming, encompassing employee performance
management and services. Consequently, public services and
business processes are impeded.
In response to challenges, adopting an enterprise resource
planning (ERP) system emerges as a solution. While proprietary
ERP systems solve issues, they have drawbacks, like high
licensing costs and vendor dependency. Open ERP uses ORM
for a flexible, efficient, and secure data approach. This research
deploys ORM methods to develop public service and
administration modules in the Population and Civil Registry
Office of Jayawijaya, including Administration Mail
Management, Service Submission, and Employee e-
Performance, streamlining tasks like digital documentation,
service submission, and incoming/outgoing mail.
We test our application modules to assess the system
functionality. The testing results demonstrate that 90.04% of the
modules exhibit validity. Specifically, out of 231 test cases, 208
successfully passed without encountering any failures. However,
a defect rate of 9.96% is observed, where 23 out of 231 test cases
are identified as defective.
Keywords— Open ERP, ORM, Odoo, Black-box testing,
Boundary Value Analysis, Equivalence Class Partitioning
I. INTRODUCTION
In the era of globalization and advances in information
technology, access to internet facilities is becoming more
accessible and more equitable in developing countries. This
phenomenon has significantly impacted social interactions
and the transformation of public services provided by the
government. In responding to this phenomenon, governments
at various levels and regions compete to deliver good public
services [1]. However, this increasing effort also brings
increasingly complex challenges. Some countries face
difficulties in planning and implementing information
technology, mainly because of the various autonomy policies
implemented in each region [2, 3].
The case study of Jayawijaya Regency serves as a
compelling representation of how local governments shoulder
extensive responsibilities in governing according to the
principles of autonomy. In this context, the Population and
Civil Registry Office (DISDUKCAPIL) plays an important
role as a Local Government Agency (OPD) tasked with
auxiliary functions in the domain of population
administration, management of population administration
information, and civil registration. This role is governed by
the Regional Regulation of Jayawijaya Regency number 24 of
2019, which amends the Jayawijaya Regency Regent
Regulation number 53 of 2016, outlining the structure and
functions of the Population and Civil Registry Office of
Jayawijaya Regency [4]. However, despite the comprehensive
regulatory framework guiding this role, its implementation is
not exempt from challenges.
One of the problems that arises is the lack of integrity
between data flows and business processes that occur. This is
due to the use of conventional applications in the development
of each application, which includes a stand-alone database,
backend, and frontend. As a result, data becomes fragmented
and spread across different platforms. As a result, data
integration becomes difficult, and data related to population
administration is spread across various systems that operate
separately. This results in the inability of various business
functions and data flow to develop in parallel, which
ultimately makes it difficult to achieve effective integration of
data and business processes.
The significance of public service transformation directs
attention to Enterprise Resource Planning, which plays a
crucial role in integrating business units and operational
processes. They offer seamless integration of information
flows, making every organizational element visible [5]. ERP
technology addresses data separation and data separation,
supporting business processes, enhancing efficiency, and
integrating public services [6]. Employing ERP systems in
governmental contexts can yield substantial benefits in
efficiency, cost reduction, and improved public service
delivery. The development of ERP fosters the creation of

979-8-3503-7064-5/23/$31.00 ©2023 IEEE 110

 2023 International Conference on Converging Technology in Electrical and Information Engineering (ICCTEIE)
integrated application modules for public services aligned
with business processes [7].
Many ERP software options are available, each featuring
unique attributes, versions, scopes, and functionalities tailored
to cater to diverse sectors. SAP is a well-recognized ERP
software used globally to effectively manage various
corporate operations, including but not limited to finance,
shipping, manufacturing, and sales. In contrast, Oracle Cloud
offers a cloud-based ERP solution that exhibits characteristics
of scalability and security. This comprehensive system
includes finance, supply chain, and manufacturing modules.
Another software solution that focuses on the manufacturing,
distribution, and retail sectors is Epicor. Epicor provides many
modules, such as production, inventory management, and
finance. Nevertheless, it is important to note that these
different ERP variations involve a fee-based licensing
framework [8, 9].
Proprietary ERP systems have drawbacks, such as high
licensing, implementation, support, and maintenance costs.
According to a 2022 study, the base ERP system installation
cost could average around $7,200, or around Rs 10,000.
Depending on the organization’s business needs, $17,000,000
per user for a perpetual license [10]. Vendor dependencies can
limit flexibility and affect the sustainability of ERP system
usage. Additionally, failure rates for ERP implementation
projects can reach up to 90% [11]. The fact shows that many
companies fail to implement an ERP system, resulting in
costly implementation expenses [12]. In this context, choosing
an open-source ERP is a promising solution. Next is the
example of several proprietary ERPs, as shown in Table 1.
TABLE I. COMPARISON OF PROPIETARY ERP
SAP Oracle Cloud Epicor
A global ERP software A cloud-based An ERP tailored
used by companies to ERP solution for manufacturing,
manage business that provides distribution, and
processes across scalability, retail industries,
various functions such security, and aiding companies
as finance, logistics, flexibility with in enhancing
manufacturing, and finance, supply efficiency with
sales. chain, and modules like
manufacturing manufacturing,
modules. inventory, and
finance.
To address the challenges within the study's scope, we
propose developing open ERP modules that utilize the ORM
method. This involves connecting object-oriented
programming objects with entities in relational databases [13],
this approach streamlines communication between
applications and databases, offering protection against
security vulnerabilities like SQL injection attacks[14].
Consequently, ORM ensures continuous usage and
accelerates development by reducing the need for complex
SQL queries. This allows developers to concentrate on
programming core application features. Moreover, the use of
ORM significantly improve adaptability, accelerates
development, and heightens overall data security and
management effectiveness [15].
This research aims to outline the development of ERP
modules that facilitate the business process of public service
administration. Additionally, the research includes conducting
software testing on the evolving modules to ensure the
functionality, quality, and reliability of the developed system
111
[16] [17]. The testing process encompasses conducting
functional tests on the development module, utilizing a
combination of BVA and ECP techniques. The results are then
assessed using standard evaluation metrics. The objective is to
assess the feasibility of implementing the developed
application modules, minimize the risk of failure, and ensure
the functionality of the tested modules.
II. LITERATURE STUDY
A. Object Relational Mapping (ORM)
ORM refers to techniques or approaches to connect object
models with relational models in databases [18]. This
technique aims to mediate and automate data transformation
between the two models. In other words, ORM creates a
bridge between object representations in applications and
table structures in relational databases. It allows interaction
and manipulation of data in a more object-oriented format. It
can be considered a software solution to address the
incompatibility problem between object and relational
concepts.
An ORM maps an object layer, such as an object instance,
to a relational layer, like a set of rows in a table. Objects have
properties not directly compatible with databases, such as
temporary and instantiated at runtime, while data in a
relational model is persistent. Objects do not have a fixed
schema, and a particular non-object-oriented programming
language (SQL) is used to interact with relational databases,
unlike object-oriented programming languages (OOPLs),
which have built-in syntax for standard method calls [14] [15].
B. Open-source Enterprise Resource Planning (ERP)
ERP is an information system that allows a company to
automate and unify different processes of its core business
[17]. Open-source ERP means enterprise resource planning
software with an open-source license, and its source code is
publicly available. Open-source ERP systems are developed
publicly or collaboratively by an exclusive group of
developers [18].
ERP systems integrate data from multiple lines of
business, making it easier for management to assess overall
company performance and make informed decisions. ERP
systems encompass software products that fulfil daily
business requirements and facilitate decision-making. They
are functionally integrated into various models, such as supply
chain management, production and manufacturing schedules,
sales support, finance and cost accounting, and human
resources management. Overall, ERP systems provide a
comprehensive solution for managing all aspects of a business
process [19].
C. Odoo Module Development
A module is a set of data and logic in an MVC model,
containing models, user interfaces, access-control lists, and
static files for a graphical screen. It may depend on other
modules, requiring additional logical processes or capabilities.
These components may not be contained within the module
but may be included in one or more [19].
Developing a module for Odoo involves using command
lines to create files with code snippets and writing code using
the steps below. Developers must then write their code to
complete the process, following a sequence of steps as 1) Set
 2023 International Conference on Converging Technology in Electrical and Information Engineering (ICCTEIE)
up the module directory. 2) Create Python models, inheriting
from Odoo's API and model classes, to define data objects. 3)
Design XML views for user interface components. 4) Ensure
security by specifying access rights in a CSV file. 5) Define
module details in a manifest.py file in the module's root
directory. 6) Integrate the module's directory in Odoo server
settings and restart the server for the module to be functional.
III. METHODOLOGY
This section explains the full method used in this study to
deal with the problems caused by fragmented administrative
data systems and improve the quality and efficiency of public
services in Jayawijaya Regency. The research stages are
shown in “Fig. 1”.
Fig. 1. Research Stage
A. ERP Selection and ORM Implementation
We started our research by choosing an open source ERP
solution that fits Disdukcapil's specific needs. The proposed
solution uses Open-source ERP (odoo framework) which
presents a cost-effective alternative to proprietary systems,
eliminating high licensing and maintenance costs. The
selected ERP system using the ORM methodology. It bridges
the gap between object-oriented programming and relational
databases, facilitating smooth communication and interaction
between applications and databases.
B. Module Development
At this stage, we develop the modules to meet the specific
needs of the Disdukcapil in population administration, data
management, and public service delivery. These modules are
designed to integrate seamlessly with the selected open-source
ERP system, enhancing its functionality and adaptability. We
employ a prototyping approach to module development,
enabling the creation of preliminary versions of the custom
modules before their final implementation.
C. Black Box Testing with ECP dan BVA:
After prototyping, the focus shifts to black box testing.
This method verifies module functionality without delving
into the internal code details. We conduct ECP and BVA
techniques for systematic testing. ECP categorizes input data
into classes with equivalent values and creates diverse test
cases. BVA targets inputs at class boundaries to uncover edge
case issues. Combining these techniques can enhance
thoroughness and reliability. Standard testing metrics,
including test coverage, and error detection rate, evaluate
module functionality, quality, and reliability.
D. Report and Analysis:
Data related to module functionality and testing results are
collected and analyzed throughout the development and
testing phases. This data-driven approach ensures evidence-
based decision-making and continuous improvement.
112
E. Validation and Iterative Refinement
The developed modules are validated against the initial
requirements and user expectations. Any discrepancies are
addressed through iterative refinement and adjustment.
IV. RESULT AND DISCUSSION
In this section, we present the outcomes of our module
development for dukcapil and its testing results.
A. Module Development for Disdukcapil
The development of the LayananAdminduk module was a
process aimed at addressing the specific needs of the
Disdukcapil while ensuring seamless integration with the
Open ERP framework. This section delves into the
architecture and design principles behind the module,
including an integrated class diagram, an ORM diagram, and
a snippet of code exemplifying the Python ORM class model.
We have designed and implemented a custom module
named layanan.adminduk (we call it LayananAdminduk
module), which encompasses various functionalities to
facilitate streamlined public service administration. The
design of LayananAdminduk (ORM Class diagram) is
illustrated in “Fig. 2”. The diagram shows the object as well
as the data relation scheme.
Fig. 2. The relation scheme of the "layanan.adminduk" class
In “Fig. 2”, the orange diagram illustrates the database
tables while the blue diagram represent the ORM class
models. Each ORM class model to link the programming
codes with the corresponding database tables. ORM employs
metadata to generate layers between the programming
language and the relational database.
For instance, the ORM class model "layanan.adminduk"
will link several methods such as called method
_check_nomor() and _generate_nomor_surat() to
"service_adminduk" table. In the ORM class model, the
method _check_nomor() will validate a document number
which is directly connected to “nomor” field in
“layanan_adminduk” table.
The diagram also illustrates how model class components
such as “LayananAdminduk” class, “PengajuanLayanan”
class, “ProdukLayanan” class, and others interact and
 2023 International Conference on Converging Technology in Electrical and Information Engineering (ICCTEIE)

collaborate. Each table in the database is associated with an methods serve the purpose of validating data and performing
ORM class model, as described in “Fig. 4”. calculations. The example of this code can be seen in “Fig. 5”.

TABLE II. TABLE LIST AND ORM CLASS MODEL

No Table ORM Class model
1. layanan_adminduk layanan.adminduk class
2. pengajuan_layanan pengajuan.layanan class
3. jenis_layanan jenis.layanan class
4. jenis_penerbitan jenis.penerbitan class
5 produk_layanan produk.layanan class
6 dokumen_berkas dokumen.berkas class
7 dokumen_adminduk dokumen.adminduk class

The ORM diagram in Table 2 display the mapping

between object-oriented concepts and relational database
entities within the LayananAdminduk module. This visual
representation highlights how objects, classes, and attributes
are translated into database tables, fields, and relationships.
Next comes the module coding process. First and
foremost, we need to set up the development environment. In
this case, our module project was set up correctly, allowing
for efficient building and testing in a controlled environment.
We selected Pycharm code editor for Python programming, as
modules are typically developed using this language. This
ensures efficient module development and prepares us for the
next stage in our project. Fig. 4. The layanan.adminduk ORM class model

The next step is to configure the module by creating a

specific directory within the "addons" directory to keep all the
files related to this module. Then we define the module's
metadata by creating a manifest.py file. This file plays a
crucial role in identifying the module, including its name,
version, developer's name, and dependencies on related
modules. The directory structure can be seen in Fig 3.

Fig. 5. The ORM class function on calculation based on business logic

In "Fig. 4," we have a glimpse of some ORM class models

Fig. 3. The layanan.adminduk ORM class model
The next step is to establish the structure of the module's
database. To begin with, we create a Python class that mirrors
the structure of the "layanan.adminduk" table. Within this
class, we define various attributes such as "nik," applicant's
name, email address, phone number, date, and other related
data points. These attributes correspond to the fields in the
input form. The example of this code can be seen in “Fig. 4”.
Furthermore, we implement business logic or business
rules within this ORM class. This is achieved by developing
Python methods in the model class, allowing us to execute
necessary business logic. This encompasses tasks such as data
validation, automated calculations, and custom behaviors
tailored to the specific requirements of our module. These
within the "Layanan.Adminduk" module. These models are
like architectural blueprints but for data based on ORM
methodology. They define how data should be structured in
tables and how these tables connect within the database
infrastructure. Essentially, these classes provide instructions
for how data should be stored in the database. Each class
definition, like "LayananAdminduk," "PengajuanLayanan,"
"ProdukLayanan," and "FileBerkas," directly influences the
creation of corresponding tables in the database.
For instance, within these classes, we found the "fields"
object, which includes elements like Many2one or One2many.
This "fields" object is responsible for automatically managing
relationships between tables. It handles tasks like handling
foreign keys and creating associations between different
pieces of data.
Let's take the "nik" object in the script as another example.
It represents a data field with a character/string data type. It
comes with attributes like "string," which define how the field
should be labeled. Additionally, this field enforces certain
constraints, such as requiring data to be present (non-null
validation) and specifying a maximum data size of 16

113
 2023 International Conference on Converging Technology in Electrical and Information Engineering (ICCTEIE)
characters. When we execute this script, the ORM takes
charge of interacting with the database table, effectively
creating a "nik" column with a "varchar" data type. It also
ensures that this column adheres to the non-null requirement
and the specified 16-character data size.
"Fig. 5" reveals a piece of code embedded within the
module. This code is responsible for computing and storing
data related to another entity, primarily based on its
connection with an object named "jumlah_produk" within the
model.
The `_compute_number_of_products()` function does the
math, calculating the count of objects in the
"pengajuanlayanan_ids" relationship and then saving this
count in the "jumlah_produk" field. On the other hand, the
`_compute_product_service()` function takes on the task of
gathering details, such as the names of service products and
their publication types, from the associated
"pengajuan_layanan" object. Next, it records this information
in the "produk_layanan" field.
B. Application screenshoot
In addition to the comprehensive textual analysis in the
previous sections, we present visual evidence of the custom
module's development and functionality through a series of
application screenshots.
Fig. 6. Application panel dashboard
“Fig. 5” is an overview of the LayananAdminduk
module’s applications within the Open ERP interface.
Fig. 7. Data entry of the “LayananAdminduk” service submission form
“Fig. 5” shows the data entry form. It is allows to input
essential details related to population administration requests.
The form has fields for NIK, name, email, and more. The
integration of validation checks ensures accurate data entry
and streamlines the information collection process.
Fig. 8. Tracking and status
114
“Fig. 6” can provide real-time tracking and status updates
for various service requests. its display the user interface for
tracking the progress of submitted requests.
Fig. 9. Document upload
“Fig. 7” is the module that supports document upload
functionalities.
Fig. 10. Reporting and Analytics
“Fig. 8” displays a reporting dashboard that offers insights
into trends related to service requests, processing times, and
other pertinent metrics.. These visualizations empower
administrators to make informed decisions and optimize
service delivery [20].
C. Testing Results
Black box testing phase analysis and quantification
provided valuable insights into module performance and
alignment with predefined standards. Our testing uses the ECP
and BVA techniques that applied to “entry form” menu
elements. Testing focuses on pre-designed test cases,
including data input values and test rules. So that the results
of the fun test are in accordance with the test cases.
The test results of the "entry form" menu elements can be
categorized as pass if the functionality of the menu elements
successfully runs according to the specifications. On the other
hand, the results are categorized as defect if the functionality
of the menu elements does not work according to the
specifications.
For example, the NIK column was tested on the “Layanan
Adminduk” application entry form (see Fig. 6) with the BVA
and ECP methods to see how the column responded to various
inputs. The testing is based on the rule that the NIK column
must be in a number format with a maximum length of 16
digits.
The ECP and BVA testing process uses 231 test cases. The
BVA implements the data input with the minimum value (15
digits), maximum value (16 digits), and minimum+1 value (17
digits). Testing results show that inputs of 15 and 17 digits are
rejected (not meet the specification), and 16 digits are
accepted properly. Meanwhile, ECP divides input into two
classes, valid input (16 digit numbers) and invalid (less than
 2023 International Conference on Converging Technology in Electrical and Information Engineering (ICCTEIE)

16 digits, more than 16 digits, or non-numeric characters). An reliability and robustness. Even so, there are still defective test
example of valid input is "1234567890123456", which is cases (9.96%) that need further improvement to improve the
accepted fine. Examples of invalid input include "12345" and overall quality of the software.
"123A56790123456". Testing using the BVA and ECP
methods shows that the NIK column responds well to valid
and invalid input. through this test, we evaluate all REFERENCES
possibilities from the data input. The overall test results from
[1] S. ElMassah and M. Mohieldin, "Digital transformation and localizing
this research are shown in Table 3. the Sustainable Development Goals (SDGs)," Ecological Economics,
vol. 169, pp. 106490-106490, 2020.
TABLE III. TEST RESULT RECAPITULATION
[2] R. Hartanto and S. Fauziati, "Hambatan-Hambatan Dalam Implemetasi
Module Menu Pass Fail Defect Tota Layanan Sistem Pemerintahan Berbasis Elektronik (Spbe) Pada
Feature element l Pemerintah Daerah," JIKO (Jurnal Informatika dan Komputer), vol. 5,
Submission no. 3, pp. 215-223, 2022.
8 95 0 11 106
Service [3] R. Stewart and S. Mohamed, "Barriers to Implementing Information
Mailing 10 113 0 12 125 Technology in Developing Countries," 2023.
Total 208 0 23 231 [4] Peraturan Daerah Kabupaten Jayawijaya nomor 24 tahun 2019
tentang Perubahan Atas Peraturan Bupati Jayawijaya Nomor 53 tahun
2016 Tentang Organisasi Dan Tata Kerja Dinas Kependudukan dan
From the resulting values in Table 3, will be calculated Pencatatan Sipil Kabupaten Jayawijaya.
standard metric measurements using the formula below: [5] L. Pratiwi, "Dampak Implementasi Sistem Enterprise Resource
Planning (Erp) Terhadap Kinerja Perusahaan: Sebuah Studi Literatur,"
= 100% (1) Akuntansi dan Teknologi Informasi, pp. 1-28, 08/08 2020.
[6] P. Chatzoglou, D. Chatzoudes, L. Fragidis, and S. Symeonidis,
= 100% = 90,04% "Examining the critical success factors for ERP implementation: an
explanatory study conducted in SMEs," 2017: Springer, pp. 179-201.
' (
$ %& = 100% (2) [7] S. Katuu, "Enterprise Resource Planning: Past, Present, and Future,"
New Review of Information Networking, vol. 25, pp. 37-46, 01/02 2020.
= 100% = 0% [8] R. Kenge, "A Research Study on the ERP System Implementation and
Current Trends in ERP," Shanlax International Journal of
- . /
* + , = 100% (3)
Management, vol. 8, pp. 34-39, 10/01 2020.
[9] [online]. "Best ERP Systems." https://www.g2.com/categories/erp-
= 100% = 9,96% systems (accessed 12/06/2023, 2023).
[10] [online]. "How much does ERP software cost?"
https://dynamics.folio3.com/blog/erp-cost-software-pricing/ (accessed
12/06/2023.
Based on the formula "(1)", the pass rate of the test cases [11] W. Agha, M. Ragheb, and A. Shawky, "Transformational Leadership
is 90.04%. This percentage shows that out of a total of 231 test as a Critical Success Factor for Enterprise Resource Planning System
cases carried out, 208 test cases passed. All the test rules for Implementation," OALib, vol. 06, pp. 1-28, 01/01 2019.
the expected conditions match the test output. [12] J. Wiratama and A. E. J. Egeten, "Modeling the Readiness
Measurement for Enterprise Resource Planning System
The formula "(2)" shows that the failure rate of test cases Implementation Success," Jurnal Nasional Teknik Elektro dan
is 0%, which indicates that there are no failed test cases among Teknologi Informasi, vol. 12, no. 3, pp. 159-166, 2023.
all the tests performed. This is because there is no disturbance [13] I. Dominte, "Introducing an ORM," in Web API Development for the
(troubleshooting) in the running of the application when Absolute Beginner: A Step-by-step Approach to Learning the
Fundamentals of Web API Development with .NET 7. Berkeley, CA:
testing. Apress, 2023, pp. 161-195.
The formula “(3)” shows that the test case defect rate is [14] V. Sivakumar, T. Balachander, Logu, and R. Jannali, "Object
9.96%, which implies that 23 out of 231 test cases were Relational Mapping Framework Performance Impact," (in English),
Turkish Journal of Computer and Mathematics Education, vol. 12, no.
identified as defective. One example of this defect test case 7, pp. 2516-2519, 2021.
occurs in testing the file upload entry form. The test rule is that
[15] D. Colley, C. Stanier, and M. Asaduzzaman, The Impact of Object-
it can store files with a maximum size of 2 Mb. The file can Relational Mapping Frameworks on Relational Query Performance.
be saved when given input data with a file size of 1.7Mb, but 2018.
when the input data is given a file with a size of 1.8Mb (which [16] M. A. Umar and C. Zhanfang, "A Comparative Study of Dynamic
is still less than 2Mb), the result is that the file fails to save. Software Testing Techniques," (in English), International Journal of
This condition is considered as a defective test case. Advanced Networking and Applications, vol. 12, no. 3, pp. 4575-4584,
2021-08-25 2020.
[17] G. J. Myers, C. Sandler, and T. Badgett, The art of software testing.
John Wiley & Sons, 2011.
V. CONLUSSION
[18] "IEEE Standard Glossary of Software Engineering Terminology,"
This research succeeded in developing a population IEEE Std 610.12-1990, pp. 1-84, 1990.
administration service module with an ORM module using [19] [online]. "Building a Module - Odoo 15 Documentation."
Open ERP. ORM methodology has been applied so that the https://www.odoo.com/documentation/15.0/developer/tutorials/backe
modules developed are safe from SQL injection. nd.html (accessed 28-08-2023).
[20] C. Gomez Llanez, N. Diaz-Leal, and C. Angarita Sanguino, "A
The test results also show a high test case pass rate comparative analysis of the ERP tools, Odoo and Openbravo, for
(90.04%), indicating good validation and performance of the business management," Aibi revista de investigación, administración e
tested module. No failed test cases demonstrate the system's ingeniería, vol. 8, pp. 145-153, 12/31 2020.

115