Enterprise Interoperability IV 2010
DOI: 10.1007/978-1-84996-257-5_41
|View full text |Cite
|
Sign up to set email alerts
|

Towards a Conceptualisation of Interoperability Requirements

Abstract: Enterprises that aim to work together want, prior to any effective collaboration, to know if they are able to interoperate. On the one hand, this induces to be able to define the particular needs having to be taken into account in order to demonstrate if an enterprise can be or must be interoperable. On the other hand, it requires techniques and approaches allowing to formalise these needs as a set of unambiguous and, as formal as possible, requirements called here interoperability requirements. Finally, verif… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
7
0

Year Published

2011
2011
2023
2023

Publication Types

Select...
2
2
1

Relationship

1
4

Authors

Journals

citations
Cited by 7 publications
(7 citation statements)
references
References 7 publications
0
7
0
Order By: Relevance
“…This allows interoperability problems to be highlighted. One of these proposals was put forward by Mallek, Daclin, and Chapurlat (2010), who developed an approach to define and formalise interoperability needs as interoperability requirements. These requirements are broken down into three classes called compatibility, interoperation and reversibility requirements.…”
Section: • Enumeration Of the Processes That Involve Collaborations (mentioning
confidence: 99%
“…This allows interoperability problems to be highlighted. One of these proposals was put forward by Mallek, Daclin, and Chapurlat (2010), who developed an approach to define and formalise interoperability needs as interoperability requirements. These requirements are broken down into three classes called compatibility, interoperation and reversibility requirements.…”
Section: • Enumeration Of the Processes That Involve Collaborations (mentioning
confidence: 99%
“…However, maturity models do not provide a precise indication of the causes of noninteroperability and mainly focus on general qualitative notions. 25 Once the distributed information system is put into production, its components are able to share and exchange information without depending on a particular actor and operate independently of each other, we speak of interoperable systems. 7 Interoperability has become an important business asset and is now proposed as a key performance indicator for business process performance management systems.…”
Section: Related Workmentioning
confidence: 99%
“…A monitoring system should provide elements to maintain a good level of interoperability based on the interoperability requirements. 25 We therefore propose to combine the information provided to perform advanced monitoring and querying. This would provide indicators which determine maintenance actions.…”
Section: Objectivesmentioning
confidence: 99%
“…To tackle this first obstacle, a requirement reference repository is proposed and is described as a causal tree, as illustrated in Fig. 1 (for more details, we refer the reader to [9]).…”
Section: Interoperability Requirements Definitionmentioning
confidence: 99%
“…The objective of the verification is to demonstrate that a set of selected interoperability requirements is satisfied. Indeed the reference repository presented in [9] allows users to select relevant requirements to be checked. In order to be able to perform this verification before the runtime of the collaborative process, this one is done on a model of the collaborative process.…”
Section: Interoperability Requirements Verificationmentioning
confidence: 99%