Software Interoperability Analysis in Practice

Abukwaik, Hadil; Rombach, Dieter

doi:10.1145/3084226.3084255

Cited by 8 publications

(10 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…16, no. 3 / 2020 / Bogotá D.C., Colombia Universidad Cooperativa de Colombia practice results in the development of isolated systems, frequently incompatible with the systems of other functional areas and inconsistent with the information use and exchange needs of business processes [24] [25] [26]. In turn, these systems give rise to information silos [13] [27], which occur when the functional areas of an organization do not share information or their communication is inefficient [28] [29] [30] [31].…”

Section: Introductionmentioning

confidence: 99%

A model for the elicitation of organizational system interoperability requirements

2020

View full text Add to dashboard Cite

Introduction: this article is the product of the research called a framework to support the elicitation of interoperability requirements (IR) based on the needs of an organization's business processes, developed at the Universidad del Cauca in 2019. Problem: within the requirements elicitation process, stakeholders generally fail to articulate IR according to the business needs, causing the development of systems incompatible with systems in other functional areas. Objective: to identify, define and classify a set of attributes that constitute the interoperability at the business level, which must be considered during the elicitation of an IR. Methodology: the development of the model followed these activities: (i) establishment of the aspects to be considered in the interoperability at the business level, (ii) identification of the attributes that make up each aspect, (iii) definition of the identified attributes and the options that can be obtained in response, and (iv) classification of the attributes. Results: a model that describes 21 attributes that constitute the interoperability at the business level, classified in the following views: emitters and receivers, types of interaction, data flow properties, and conditions to use the communicated data. Conclusion: from the application of the model in the elicitation of a set of IR of two functional areas of an organization, it was identified that the attributes favor the common understanding among members of different areas and support the analysis and planning of the exchanges of information. Originality: to identify and define a set of attributes that constitute interoperability at the business level. Limitations: the model must be used by a process that guides the elicitation of the attributes that make up the IR.

show abstract

Section: Introductionmentioning

confidence: 99%

A model for the elicitation of organizational system interoperability requirements

2020

View full text Add to dashboard Cite

show abstract

“…In this perspective, we conducted a survey, and we identified several challenges faced by practitioners in their integration projects (VALLE et al, 2021a): (i) the absence of documentation, architectural solutions used in practice, and directions to tackle interoperability issues in projects that need to exchange data, and (ii) the lack of understanding the vocabulary of the data exchanged among systems. Abukwaik and Rombach (2017) also carried out an online survey with experienced software engineers and identified the main concerns that must be overcome in integration projects: (i) misunderstanding of data formats, data semantic, procedures, contracts, standards, quality, and interfaces provided by individual systems; and (ii) absence of highlevel architectures to analyze, comprehend, and guide the way that interoperability can be considered. We intend to support software architects in decision-making to mitigate interoperability issues in software-intensive systems from these scenarios.…”

Section: Problem Statementmentioning

confidence: 99%

“…Software-intensive systems are composed of Individual systems participating in larger systems that have different life cycles, the operational environment, programming languages, platforms, goals, and business interests (MADNI; SIEVERS, 2014). Therefore, developers of this class of systems are encouraged to adopt solutions for integrating such heterogeneous, distributed, and independent software systems (ABUKWAIK; ROMBACH, 2017;KUBICEK et al, 2011). Therefore, interoperability has been considered an essential requirement for the successful establishment of software-intensive systems.…”

Section: Identification Of State Of the Art And Practice On Interoperability Strategiesmentioning

confidence: 99%

“…Software engineers have faced difficulties in the development of software-intensive systems due to collaborations among their individual systems (ZOPPI et al, 2017). In this sense, architects and developers of software-intensive systems are encouraged to adopt solutions to integrate heterogeneously, distributed, and independent software systems (ABUKWAIK; ROMBACH, 2017;KUBICEK et al, 2011). Therefore, interoperability has an essential role in the composition of complex software-intensive systems.…”

Section: Introduction 11 Context and Motivationmentioning

confidence: 99%

“…Interoperability is a complex task since it is far more than getting to communicate with each other. It requires the organizations involved to employ some degree of compatible semantics and common interpretations of the information exchanged (ABUKWAIK; ROMBACH, 2017). To enable the successful integration of systems and their meaningful data exchange and interactions, an analysis of technical, conceptual, and organizational constraints is required (NIELSEN et al, 2015).…”

Section: Introduction 11 Context and Motivationmentioning

confidence: 99%

See 2 more Smart Citations