Article

Software Engineering

October 09, 2026

EngTT: software for road freight based on operational costs and ANTT parameters

Engtt: Software for Road Freight Motor Based on Operational Costs and Antt Parameters

Lucas Santos Villar Arias; Arthur Pinheiro de Araújo Costa

DOI: 10.22167/2675-6528-202603186

Article derived from a Course Conclusion Work (TCC), with content based on the student’s original work and adapted to the editorial format of the E&S Magazine with the support of the ResumeAI tool, an artificial intelligence solution developed by Instituto Pecege for textual synthesis and organization.

Summary

Road transport represents the main logistics modality in Brazil, with the composition of freight costs regulated by the National Land Transport Agency (ANTT). Given the absence of a structured methodology for freight calculation and the sector’s dependence on isolated spreadsheets, the EngTT software was developed. The objective was to create a decision support tool that integrated operational variables, calculated the total cost per route, and compared the results with the ANTT’s minimum floor, identifying non-compliance and margin compression scenarios before pricing. The adopted methodology was applied, quantitatively and experimentally, with incremental construction oriented towards the Minimum Viable Product (MVP) concept. The system was structured in three modes of use – Build Visual Route, Batch by spreadsheet, and Scrape routes – sharing a decoupled calculation engine and centralized parameters. The results obtained demonstrated that the software met the proposed objective, showing margin and regulatory compliance variations between the analyzed routes. It was observed that longer routes, such as Ribeirão Preto × Guarujá, presented an increase in cost due to the need for additional driver per diems, while shorter routes, such as Cajamar × Guarujá, showed greater adherence to the ANTT’s regulatory floor. It was concluded that the developed solution is applicable to the road freight transport sector as an effective tool for pricing and operational management.

Keywords: ANTT; Containerized cargo; Software engineering; Road freight; Python.

1. Introduction

Road freight transport is the main logistics modality in Brazil, being responsible for approximately 62% of the total cargo movement in the country (AGÊNCIA CIDADES, 2025). This structural dependence of the Brazilian economy is reflected in national logistics costs, which reach about R$ 940 billion annually, with an average growth of 7% per year (ASSOCIAÇÃO BRASILEIRA DE OPERADORES LOGÍSTICOS, 2024). The relevance of this modal imposes the need for efficient and transparent processes for its cost management.

The composition of road freight costs is complex, involving fixed and variable variables, such as fuel, maintenance, tolls, depreciation, insurance, taxes, and waiting time. To ensure compliance and fairness in operations, the minimum road freight is regulated by the National Land Transport Agency (ANTT), which updates its minimum floor table semi-annually or whenever there is a variation greater than five percent in the price of diesel oil (NATIONAL LAND TRANSPORT AGENCY, 2025). Furthermore, Law No. 10.209/2001 establishes the mandatory toll voucher, and Law No. 13.103/2015 regulates the professional driver’s journey, establishing eight daily hours with the possibility of up to two overtime hours and integrating waiting time into the journey (BRAZIL, 2001; BRAZIL, 2015).

Despite the regulation and complexity involved, a large part of the organizations in the sector still face significant challenges in calculating freight. The common practice is the use of isolated spreadsheets, which lack methodological standardization, traceability of premises, and systematic comparison with current regulatory parameters. This absence of a structured methodology compromises pricing accuracy, hinders operational and commercial decision-making, and exposes companies to risks of regulatory non-compliance.

Given this scenario, the need for a tool that integrates operational variables and regulatory parameters becomes evident, offering a standardized, auditable, and reproducible solution for freight calculation. The present work proposes the development of a software named EngTT, whose name combines the concept of a calculation engine, derived from the English word Engine, with a reference to the ANTT regulatory table, synthesizing its central purpose of structuring road freight calculation in accordance with the agency’s norms.

The research is justified by the practical and theoretical gap in the management of costs for containerized road freight, aiming to offer a decision support tool that addresses the absence of a structured methodology for freight calculation in organizations in the sector. To this end, the research objective is to develop a decision support software capable of resolving the absence of a structured methodology for calculating containerized road freight in organizations in the sector, which today operate with isolated spreadsheets, without traceability of premises and without systematic comparison with current regulatory parameters. To this end, the EngTT software integrates operational variables such as fuel, tolls, tires, driver’s daily wages, and layover times, calculates the total cost of the operation per route, and compares the result with the minimum floor established by ANTT, allowing the identification of scenarios of regulatory non-compliance and margin compression before pricing to the contractor.

2. Material and Methods

The research was characterized as applied, quantitative, and experimental, aiming to develop a standardized tool for the structured and auditable calculation of containerized road freight. Iterative development was adopted, oriented towards the Minimum Viable Product (MVP) concept, with cycles of review, testing, and refinement, following Software Engineering principles (PRESSMAN, 2016). The study used parameterized operational data, constructed from real industry references, without company identification, ensuring impartiality and replicability. The initial focus was on containerized cargo operations with six-axle vehicles, a common configuration in long-distance transport in Brazil.

The methodological process involved literature review, requirements definition, architecture modeling, software implementation, parameterization and data collection, module execution and validation, and results analysis. This iterative flow allowed for the progressive construction of the solution.

For the development of the EngTT software, Python (v3.11.9) was employed as the main language and the Django web framework for the local interface. The architecture was modular and layered (SOMMERVILLE, 2019), with Presentation, Application, Domain, Data, and Integration. Libraries such as Pandas (v2.2.3) and openpyxl handled Excel spreadsheets (.xlsx), and Selenium automated data capture from the QualP portal. PyInstaller was used for packaging into a Windows executable, and Visual Studio Code (v1.90.1) as the development environment.

The input data and operational parameters were centralized in Excel files. `config.xlsx` stored standard premises (base addresses, axes, ANTT table, markup, waiting hours), while `EngTT_Cost_Model.xlsx` consolidated vehicle economic parameters (consumption, tires, daily rates, insurance). `EngTT_RouteDatabase.xlsx` was used for batch processing.

The EngTT calculation engine, in the `engine/` directory, was structured to break down freight into traceable components. The route was modeled as a sequence of segments (base, depot, client, port, return to base), with associated distance and times. Variable costs were calculated based on fuel, tires, tolls (Law No. 10.209/2001), and layover. The driver’s journey and daily rates were parameterized according to Law No. 13.103/2015, with adjustments for excess operating times. ANTT’s minimum floor parameters were integrated as a regulatory reference for direct comparison with operational cost (NATIONAL AGENCY OF LAND TRANSPORT, 2025), applying a 92% empty return factor for sections without cargo.

The EngTT was structured into three usage modes. The Visual Route Builder allowed individual route simulation, configuring parameters to obtain total cost, selling price, and comparison with the ANTT floor. The Spreadsheet Batch processed multiple routes from a standardized input spreadsheet, generating an output file with history and comparative graphs. Route Scrape performed automated enrichment of the route database with data from the QualP portal (distance, toll, estimated time, minimum ANTT floor), operating as assisted integration via Selenium, with manual authentication. Files such as `EngTT_Scrape.xlsx` and `EngTT_Scrape_output.xlsx` were used for Scrape input and output, with final results stored in `runtime_exports/` with a timestamp.

3. Results and Discussion

The implementation of the EngTT software represented a functional and robust solution for the challenge of structured calculation of containerized road freight, according to the central objective of this research. The system demonstrated the ability to perform analyses both individually and in batch, integrating with the regulatory parameters of the National Land Transport Agency (ANTT) and offering a mechanism for automated enrichment of external data. The development process rigorously followed modern Software Engineering practices, with special attention to code modularity, centralization of operational premises, and clear separation of responsibilities by layers, ensuring the tool’s maintainability and scalability.

The architecture of EngTT, organized in Presentation, Application, Domain, Data, and Integration layers, facilitated the management of requirements and the incremental construction of the Minimum Viable Product (MVP). This approach allowed the system to be developed in Python, with a local web interface, and for the calculation engine to be decoupled, which contributes to flexibility and code reuse. The centralization of operational and regulatory parameters in a `config.xlsx` file eliminated the need for direct coding, making the model auditable and accessible to non-technical users for adjustments and validation of premises.

The EngTT calculation engine was designed to break down freight into traceable components, addressing route composition as a sequence of segments that include base departure, depot transit, customer service, port (if applicable), and base return. Each segment had its associated distance, travel time, and dwell time, distinguishing between productive movement and unproductive time. This granularity in calculation is fundamental for pricing accuracy and for identifying operational bottlenecks.

Regarding costs, the software calculated variable components, such as fuel per kilometer, based on the vehicle’s average consumption, and tire cost per kilometer. Tolls were treated as a mandatory and segregated component, in accordance with Law No. 10.209/2001, which establishes the toll voucher. The stay cost was determined by the vehicle’s dwell time at the shipper’s or consignee’s premises, a critical factor that frequently impacts the profitability of transport operations.

The driver’s journey and daily rates were parameterized based on Law No. 13.103/2015, which establishes a regular eight-hour workday, with the possibility of up to two overtime hours, and integrates waiting time into the workday. When the total operation time exceeded the legal daily limits, the system automatically increased the number of daily rates and, consequently, the total estimated cost. This functionality is crucial to ensure labor compliance and the correct allocation of labor-related costs.

The composition of the suggested selling price by EngTT was obtained by applying a commercial markup percentage, defined in the `config.xlsx` file, to the total estimated cost of the route. This selling price was then compared with the minimum freight floor established by ANTT, allowing the identification of scenarios of regulatory compliance, margin compression, or price underestimation. This direct comparison is one of the pillars of the tool, offering a clear view of the commercial and regulatory viability of each operation.

The execution of the computational model allowed simulating diverse route configurations, using as a case study the routes Cajamar × Guarujá, Guarulhos × Guarujá, Extrema (MG) × Guarujá, and Ribeirão Preto × Guarujá. These routes were selected because they represent different distance ranges and operational profiles, which enabled a comprehensive analysis of the impacts of cost variables. The results demonstrated significant cost variations among the routes, mainly influenced by the distance traveled, toll incidence, dwell time, and the need for additional daily allowances for the driver.

On longer routes, such as Ribeirão Preto × Guarujá, the total operation time frequently exceeded the driver’s legal daily working hours, resulting in a significant increase in the estimated total cost due to the need for additional daily allowances. This finding highlights the importance of considering labor legislation in freight calculation, as non-compliance can generate unforeseen costs and legal risks for transport companies.

On the other hand, shorter routes, such as Cajamar × Guarujá, showed greater adherence to the ANTT’s regulatory floor, with a lower probability of operational margin compression. This result corroborates the technical literature in the sector, which indicates the proportional incidence of tolls and waiting times for loading and unloading as the most critical factors on shorter routes, while the driver’s journey has a predominant impact on the total cost on longer routes (Ballou, 2016).

The comparative analysis between the cost calculated by EngTT and the ANTT’s minimum regulatory floor for the simulated routes revealed distinct scenarios. For the Cajamar × Guarujá route, the operational cost calculated by EngTT was R$ 3,045.91, with a suggested selling price of R$ 3,198.21 (applying a 5% markup), while the ANTT floor was R$ 3,398.58. Similarly, for Extrema (MG) × Guarujá, the EngTT cost was R$ 3,149.40, the selling price R$ 3,306.87, and the ANTT floor R$ 3,763.69. In both cases, the selling price suggested by EngTT was below the ANTT’s regulatory floor, indicating a scenario of potential non-compliance or the need for markup adjustment to meet the regulation.

In contrast, for the Guarulhos × Guarujá route, the EngTT cost was R$ 2,512.56, the selling price R$ 2,638.19, and the ANTT floor R$ 2,454.54. In this case, the selling price suggested by EngTT exceeded the minimum ANTT floor, indicating a positive margin and regulatory compliance. For Ribeirão Preto × Guarujá, the EngTT cost was R$ 5,791.68, the selling price R$ 6,081.26, and the ANTT floor R$ 8,468.47, again with the selling price below the regulatory floor. This distinction between operational cost, suggested selling price, and the ANTT regulatory floor is crucial for evaluating the economic and regulatory viability of each route, allowing for more strategic pricing decisions.

The execution of the Route Scrape module demonstrated the technical feasibility of assisted integration with the QualP portal for automated route base enrichment. The capture flow, after manual login confirmation by the user, successfully collected distance data, toll per axle, estimated travel time, and the minimum ANTT floor for the informed routes. The decision to maintain manual authentication proved to be correct, given the variability in the QualP portal’s login flows, which would make full automation fragile and difficult to maintain. The Scrape output file was generated in a standard format, allowing direct chaining with the Batch mode without the need for intermediate data transformations.

The layered architecture adopted in EngTT proved effective in separating responsibilities, facilitating system maintenance and incremental evolution. Centralizing parameters in the `config.xlsx` file eliminated the practice of “hardcodes” distributed throughout the code, making the model’s premises explicit and auditable, a valuable attribute for both the scientific validity of the research and traceability in professional use contexts. This approach aligns with the principles of cohesion and low coupling, fundamental in Software Engineering (Pressman, 2016; Sommerville, 2019).

The separation of the three usage modes – Visual Route Assembly, Batch by spreadsheet, and Route Scrape – allowed each workflow to be optimized for its specific purpose, without compromising the coherence of the underlying calculation engine. Practical validation of the `.exe` executable confirmed that the solution is technically distributable and accessible to users without technical knowledge in Python, which expands its application potential in the sector. In summary, the results obtained demonstrate that EngTT is capable of calculating the total operation cost per route, incorporating operational and regulatory variables, and comparing the values with the ANTT minimum floor, effectively responding to the objective of providing a structured methodology and a decision support tool for the pricing of containerized road freight.

4. Conclusion

The present study sought to develop a decision support software to address the absence of a structured methodology in the calculation of containerized road freight, integrating operational and regulatory variables for comparison with the ANTT minimum floor. It was verified that the EngTT software proved to be a functional and robust solution, capable of performing total cost analyses per route, both individually and in batch, and of incorporating regulatory parameters from the National Land Transport Agency. It was observed that the tool allowed for the identification of regulatory non-compliance scenarios and margin compression before pricing, by comparing the suggested selling price with the ANTT minimum floor. The analysis of simulated routes, such as Cajamar × Guarujá and Ribeirão Preto × Guarujá, highlighted significant cost variations, influenced by travel distance, toll incidence, dwell time, and the need for additional driver per diems, according to Law nº 13.103/2015. It was noted that longer routes showed an increase in cost due to per diems, while shorter routes showed greater adherence to the regulatory floor. The modular architecture and the centralization of parameters in the `config.xlsx` file ensured the maintainability and auditability of the model.

The main contribution of EngTT lies in its ability to transform a freight pricing process, previously dependent on isolated spreadsheets with low traceability, into a standardized, auditable, and reproducible methodology, offering strategic support to logistics and commercial management. However, the current model presents limitations, such as the dependence on manual authentication on external portals for the Route Scrape module, the inherent fragility of integrations based on third-party web interfaces, the need for Excel files in the execution environment, and the initial coverage restricted to containerized cargo. For future studies, it is suggested to publish the software in a production environment with a persistent database, expand the handling of the ANTT table for other vehicle configurations, develop management reports with logistic performance indicators, and integrate with application programming interfaces (APIs) for route and toll inquiries, aiming for a more complete desktop application experience.

Bibliographic References

AGÊNCIA CIDADES. Rodovias são responsáveis por 62% do transporte de cargas no Brasil. Brasília, 2025. Disponível em: https://www.agenciacidades.com.br/reportagens/rodovias-sao-responsaveis-por-62-do-transporte-de-cargas-no-brasil/697/. Acesso em: 1 nov. 2025.

AGÊNCIA NACIONAL DE TRANSPORTES TERRESTRES (ANTT). Tabela de Pisos Mínimos do Transporte Rodoviário de Cargas. Brasília, 2025.

ASSOCIAÇÃO BRASILEIRA DE OPERADORES LOGÍSTICOS (ABOL). Gastos com transportes no Brasil sobem 7% e chegam a R$ 940 bilhões. São Paulo, 2024. Disponível em: https://abolbrasil.org.br/noticias/noticias/gastos-com-transportes-no-brasil-sobem-7-e-chegam-a-r-940-bilhoes/. Acesso em: 1 nov. 2025.

BALLOU, Ronald H. Logística Empresarial: Transportes, Administração de Materiais e Distribuição Física. São Paulo: Atlas, 2016.

BRASIL. Lei nº 10.209, de 23 de março de 2001. Institui o vale-pedágio obrigatório sobre o transporte rodoviário de carga e dá outras providências. Diário Oficial da União, Brasília, 2001.

BRASIL. Lei nº 13.103, de 2 de março de 2015. Dispõe sobre o exercício da profissão de motorista; altera a Consolidação das Leis do Trabalho (CLT) e dá outras providências. Diário Oficial da União, Brasília, 2015.

PRESSMAN, Roger S. Engenharia de Software: uma abordagem profissional. 8. ed. Porto Alegre: AMGH, 2016.

SOMMERVILLE, Ian. Software Engineering. 10th ed. São Paulo: Pearson, 2019.

Article originating from the Final Course Work of the Specialization in Software Engineering of the MBA USP/Esalq

To learn more about the course, click here and access the MBX Academy platform

You may also like

Software Engineering

October 09, 2026

O papel da densidade de texto instrutivo na eficiência de uma aplicação web.

O desenvolvimento de aplicações web se conecta à experiência do usuário, e este trabalho investigou como o uso excessivo de textos instrutivos pode retardar a conclusão de tarefas e impactar a eficiência da aplicação. O objetivo foi identificar o impacto da densidade textual do conteúdo instrutivo na eficiência de uma aplicação web, utilizando como principal referência a terceira lei de usabilidade de Krug. A pesquisa, de caráter exploratório e delineamento experimental quantitativo, empregou um teste A/B em uma aplicação web responsiva, onde a única variável controlada foi a densidade textual (alta vs. baixa, definida pela contagem de palavras). Participaram 25 usuários, e os dados foram coletados via Datadog RUM, mensurando tempo de conclusão, erros de submissão e taxa de conversão. Os resultados revelaram que a variante com densidade textual reduzida (variante B) apresentou uma taxa de conversão superior (58,3% contra 33,3% da variante A) e um tempo médio de conclusão significativamente menor (1:38 minutos contra 4:58 minutos da variante A), representando um aumento de 67,12% na eficiência. O teste t de Welch (p=0,042) confirmou que a redução da densidade textual impactou a eficiência. Concluiu-se que a redução da densidade textual afeta a eficiência e a taxa de conversão, reforçando a importância de conteúdo objetivo e conciso. Contudo, a baixa densidade textual, por si só, não garantiu o pleno entendimento, sendo essencial a comunicação clara e objetiva das instruções, validando a relevância do UX Writing.

Palavras-chave: Eficiência; Experiência de usuário; Teste A/B; Texto Instrutivo; Usabilidade.

Software Engineering

October 09, 2026

Implementation of analytics systems in automation environments in the process industry

The digitalization of process plants depends on structured data collection and storage, without which there is no operational visibility. Industrial analytics is the name given to the chain that processes this data from signal acquisition in the field instrument, through time-ordered storage, to its availability for analysis and other systems. Proprietary industrial software currently covers this chain, and licensing and maintenance costs restrict its adoption. The study aimed to architect, implement, and validate a system of this nature, employing current software development techniques and components at no licensing cost. The system, named Sistema de Aquisição e Tratamento de Informações de Processo (SATIP) [Process Information Acquisition and Processing System], was structured in three independent layers, using a pharmaceutical reactor simulator as a data source. The simulator executed an eight-step recipe and generated time series with stochastic variation. The simulator was written in Go, a language adopted for generating self-contained binaries, suitable for execution on edge equipment. Storage used TimescaleDB, and data was made available through a REST interface with a web dashboard. The system processed approximately 414,000 records per execution, with multivariate trends, alarm logging, and temporal correlation between instruments. The architecture proved to be reproducible and without licensing costs, and the identification of degradation required only the readings already stored by the system.

Keywords: Software architecture; Digitalization; IT/OT integration; Predictive maintenance; Time series.

Software Engineering

October 09, 2026

Use of voice in conjunction with large language models as a tool for digital accessibility

Speech is an essential basis for human interaction, and for people with disabilities, it can represent the primary form of communication with the external environment. Given the growing technological influence, voice command identification has emerged as a promising strategy for human-machine interaction. The work explored how voice, in conjunction with Large Language Models (LLMs), can be used efficiently, naturally, and accurately. For this purpose, various design patterns and the Python language were employed, aiming for greater extensibility. Gemini was used as the LLM provider, sending audio directly and leveraging its function calling capability to interact with the device. A system was developed capable of understanding user intent and converting it into actions, whose differential was the computer vision capability based on screenshots and a mesh system for LLM guidance. Tests revealed a user intent comprehension rate of 91.81% and a success rate in execution of 75.45% with the “Flash-3” model (top p 0.5 and top k 5). The proposed system validated the premise that the integration of LLMs into voice interfaces increases the autonomy of users with motor disabilities, fulfilling the purpose of being a modern and effective Assistive Technology. However, questions were raised about the costs of AI and user data security, indicating the need for improvement.

Keywords: Function calling; Human-machine interaction; Voice recognition; Computer vision.

Software Engineering

October 09, 2026

ReasonGuard: A Reasoning Audit Platform for Language Models Based on Structured Thought Decomposition

ReasonGuard was presented, an Artificial Intelligence reasoning auditing platform, developed as an observability middleware between client applications and large language models (LLMs). The work aimed to offer transparency and traceability for AI-based decision-making processes, addressing the gap in operationalizing structured reasoning techniques for auditing purposes. The system intercepted, analyzed, and documented interactions with LLMs through five modules based on the Chain-of-Thought (CoT), Tree-of-Thought (ToT), and Graph-of-Thought (GoT) paradigms. These modules captured reasoning trails, detected structural logical flaws, evaluated response consistency, and generated audit reports targeted at different stakeholder profiles. The platform was implemented with FastAPI (Python) on the backend, React with TypeScript on the frontend, and PostgreSQL as a relational database, following a modularized architecture with multitenancy isolation per user. The results demonstrated the technical feasibility of the proposed approach, with all five modules operational and integrated. It was concluded that ReasonGuard contributes to AI governance by instrumentalizing structured reasoning paradigms as observability and auditing tools, filling a gap in the literature.

Keywords: AI Auditing; Chain-of-Thought; AI Governance; Large Language Models; Algorithmic Transparency.

Software Engineering

October 08, 2026

Data pipeline for stock monitoring considering the fundamentalist methodology

The Brazilian financial scenario faces challenges such as family indebtedness, low financial literacy, and the decentralization of information for investment analysis. Given this, the research objective was to develop a financial data pipeline, based on good Data Engineering practices, to structure, process, and make relevant information available to support individual investors’ decision-making in stock analysis. A medallion architecture was implemented, using MinIO S3 for bronze, silver, and gold layer storage, with Delta Lake for data governance. Apache Spark was employed for distributed processing, Prometheus for monitoring, and Power BI for analytical visualization. The data were mostly financial statements from the Securities and Exchange Commission (CVM). A theoretical investment portfolio was built based on Benjamin Graham’s (2017) principles, applying selection filters and data validation. The results indicated a positive return of 32.88% for the theoretical portfolio, outperforming the Ibovespa index (4.25%) in the period from 2021 to 2024, although lower than the Selic rate (46.96%). Qualitatively, the pipeline processed voluminous datasets, with significant reductions in redundancies, such as 99.27% in the BPA table and 94.29% in the DRE, after applying filters. Gains in data organization, traceability, and quality were evidenced, enabling structured and more robust financial analyses.

Keywords: Medallion Architecture; Data Engineering; Investments; Data Pipeline.

Software Engineering

October 08, 2026

Performance and Total Cost of Ownership of Cloud Databases and On-Premises Infrastructure

This study analyzed the performance of database operations in cloud and on-premises infrastructures, correlating technical behavior with Total Cost of Ownership projection. The research was characterized as a quantitative and experimental study, in which a test system subjected isolated database instances to progressive execution loads, measuring the impact of network latency and computational consumption. For financial analysis, an investment and operational expenses model was developed, diluted over a thirty-six-month cycle. Technical results revealed that the accumulation of internet latency caused severe time degradation in cloud executions, despite the remote infrastructure operating with high processing idleness, registering almost 98% CPU inactivity. In contrast, the on-premises environment achieved superior performance supported by almost instantaneous network communication. Financially, cost consolidation demonstrated an empirical tie between the physical acquisition model and the service subscription model within a three-year horizon, but the on-premises environment proved more advantageous in a sixty-month cycle. It was concluded that the degradation in the cloud was not due to computational capacity, but to the interaction between route latency and the application’s unitary communication pattern. Cloud adoption requires deep optimization of the system architecture to minimize dependence on constant communication with the remote server. Without this modernization, the on-premises infrastructure consolidated as the most viable strategy, ensuring high performance, budgetary predictability, and data sovereignty.

Keywords: Operational expenses (OPEX); Transactional scalability; Network latency; Legacy systems.

Software Engineering

October 08, 2026

Asynchronous Slack-Jira integration via message queue “middleware”: comparison of “cloud computing” solutions

The latency and interoperability between distributed corporate systems constituted the problem investigated, motivated by the costs and fragilities of manual integrations between collaboration and project management platforms. An asynchronous integration “middleware” between Slack and Jira was developed and validated, with the objective of reducing the perceived user response time and ensuring system stability under load. The methodology consisted of building an event-driven software architecture in Python, using the “producer-consumer” and “adapter” patterns to isolate the user interface from “backend” processing. The solution evolved into a cloud-agnostic architecture, based on “serverless” functions, and was subjected to stress tests in local, real network, and production environments on two clouds. The architecture reduced user waiting time from a synchronous estimate of 2,000 milliseconds to a local average of 8.96 milliseconds. Under a load of 50 simultaneous requests, both cloud providers proved viable: Amazon Web Services registered lower average latency in the reception layer (951.35 ms) and double the throughput, while Microsoft Azure executed background processing with a median of 113 ms. The application of “optimistic UI” ensured fluidity of use, and load leveling by queues eliminated the need for infrastructure over-provisioning. The “middleware” consolidated itself as a scalable, resilient, and protected corporate reference model against technological lock-in.

Keywords: Event-driven architecture; Temporal decoupling; Operational efficiency; Information technology service management; System interoperability.

Software Engineering

October 05, 2026

Using Generative AI for Database Selection: A Requirements-Driven Framework for Generating Architecture Decision Records (ADRs)

The growth of data-intensive applications and the adoption of microservices architecture have amplified the need for polyglot persistence, imposing a high cognitive load on software architects in choosing and justifying database technologies. This work aimed to propose and develop an Artificial Intelligence (AI) agent-based framework to guide technological selection and generate well-founded Architecture Decision Records (ADRs). An experimental and applied methodology was employed to build a technical knowledge base. The Retrieval-Augmented Generation (RAG) technique, along with the LangChain and LangGraph libraries, was used to orchestrate agents and anchor the responses of a Large Language Model (LLM). The framework extracted natural language requirements, enriched them with RAG, and sent them to the LLM, which generated ADRs to assist in evaluating theoretical trade-offs. The results demonstrated that the agent with RAG reduced generic responses, increasing theoretical grounding and traceability. The RAG approach proved its effectiveness against conventional prompts (zero-shot), favoring the generation of ADRs with a lower level of hallucination and a high level of theoretical traceability. It was concluded that the automated tool fulfilled the function of requirement mapping, resulting in empirically grounded technical documents and aiding governance and decision-making in software architecture.

Keywords: Databases; Artificial Intelligence; LangGraph; LLM; RAG.