The external and data loose coupling for the integration of software units: a systematic mapping study

Abstract

Integration of legacy and third-party software systems is almost mandatory for enterprises. This fact is based mainly on exchanging information with other entities (banks, suppliers, customers, partners, etc.). That is why it is necessary to guarantee the integrity of the data and keep these integration’s up-to-date due to the different global business changes is facing today to reduce the risk in transactions and avoid losing information. This article presents a Systematic Mapping Study (SMS) about integrating software units at the component level. Systematic mapping is a methodology that has been widely used in medical research and has recently begun to be used in Software Engineering to classify and structure the research results that have been published to know the advances in a topic and identify research gaps. This work aims to organize the existing evidence in the current scientific literature on integrating software units for external and data loose coupling. This information can establish lines of research and work that must be addressed to improve the integration of low-level systems.

Comprehensive evaluation of software system reliability based on component-based generalized G-O models

“…They are connected in a loosely coupled manner and there may be interaction dependencies in the actual running environment. However, excessive interaction dependencies are controlled and minimized by engineers to achieve component reusability ( Ruiz Ceniceros et al, 2021 ). Therefore, we can assume that the fault processes between components are independent, and the interaction processes between components are also independent; to ensure component quality, the components should undergo unit testing before delivery.…”

Dynamic Canonical Data Model: An Architecture Proposal for the External and Data Loose Coupling for the Integration of Software Units

“…Research has predominantly concentrated on achieving seamless data exchange among software components [1]. As a result, technological advancements have outpaced the original proposals to address the long-standing issues within EAI since its inception.…”

“…We illustrated a specific scenario in our prior research [1]. When a client requests a change in the data being sent or the data type within its database schema during a web service invocation, the consumer and the provider must reach a consensus on the message formats.…”

“…Specifically, rise-up problems arise regarding semantic incompatible issues when software uses distinct meanings for the same data. The integration is not easy to perform; it requires the expertise of the IT (Information Technology) department because challenges are made up of several business and technical issues, especially concerning interoperability, scalability, and maintenance [1].…”

“…Despite the required complexity in integrating software units in the real world, there is no reference guide in the context of EAI to assist in implementing architectures for the integration [1]. Consequently, it is essential to establish a baseline that can serve as a starting point when developing integration work to develop reliable proposals that can be applied to the real world.…”