Capturing and Structuring Interoperability Requirements: A Framework for Interoperability Requirements

Abstract

The main objective of this communication is to discuss and present a framework for interoperability requirements. M ore precisely, the here presented research focuses on the dimensions to consider in order to capture and structure interoperability requirements in a precise way for parnters that want, further, to verify the truthfulness of these requirements. First, the concept of interoperability is presented according its main characteristics and the need to express it as a requirement. Then, the dimensions of the framework are highlighted and related in order to be suitable and usable. Finally, some interoperability requirements and their positionning in the framework for interoperability requirements are introduced to show the interest of such approach.

Empirical assessment of the accuracy of an interoperability prediction language

“…The work most comparable to the one presented in this paper is that of Mallek et al (2012), (Daclin and Mallek 2014) which employs the same approach to interoperability, i.e. rule verification.…”

Eliciting end users requirements of a supportive system for tacit knowledge management processes in value networks: A Delphi study

“…This decision was made in order to structure and guide conversation between VN actors and the researchers during the elicitation process. Using a reference model-in the sense of conceptual framework as defined by Thomas [27]-for supporting and structuring the requirement elicitation process is a widely accepted approach in the requirement engineering literature [26,[28][29][30][31][32]. In this respect, some evidence from the literature is presented.…”

“…Alcazar and Monzón [31] highlight the importance of using a conceptual model to create common understanding of the end users' issues, to have a reference model, and to situate the issues in the context. Daclin and Mallek [32] contend that using a conceptual framework enables capturing and structuring requirements from a well-defined basis. In addition, reference models can speed up the development process of information systems and reduce the associated costs [33].…”

Towards a Sustainable Implementation of Interoperability Solutions: Bridging the Gap Between Interoperability Requirements and Solutions

“…test, expertise…). On the other hand, it is about to classify the interoperability requirements to ensure their management and traceability [18]. This aspect is strongly based on existing categorizations that are proposed by interoperability frameworks (Figure 2).…”

“…The reference model for interoperability solutions is a structure that embeds parameters aiming to make a set of solutions available (this set is fully related to those proposed in the enterprise interoperability framework [13]) according to a (or a set of) requirement considered and positioned in agreements with the dimensions of the enterprise interoperability requirements framework (interoperability viewsinteroperability lifecycle -interoperability problems) [18]. However, as mentioned hereinbefore, the simple relation "requirements-solutions" is not sufficient to define accurately if a solution is really a well candidate solution regarding to interoperability project between partners and more broadly the partnership itself.…”