Nicolas Daclin

The application of interoperability requirement specification and verification to collaborative processes in industry

Interoperability is becoming a crucial issue for industry, and a lack of interoperability can be seen as an important barrier to collaborative work, in both public (inter-enterprise) and private (intra-enterprise) collaborative processes. Indeed, interoperability is generally defined as the ability of enterprises to interact within a collaborative process. Prior to any effective collaboration, it is necessary to inform enterprises, which aim to work together, whether or not they would be able to interoperate. Research on interoperability has shown the benefits of measuring and evaluating interoperability, by using several frameworks and maturity models. However, approaches for detecting and anticipating interoperability problems do not seem to exist. Our research proposes to use formal verification techniques to detect different types of interoperability problems. On the one hand, this means being able to define the particular interoperability needs to be considered. On the other hand, it requires these needs to be formalized as a set of unambiguous and, as formally stated as possible, requirements. Moreover, interoperability requirements can have temporal or a-temporal features. To detect interoperability problems in anticipative way, interoperability requirements must be checked by means of a target process model. Three complementary verification techniques are used to verify interoperability requirements in a collaborative process model. The verification technique used depends on the aspect and the level of abstraction of the requirement to be verified. This paper focuses and illustrates the detection of interoperability problems using verification techniques.

Enabling model checking for collaborative process analysis: from BPMN to ‘Network of Timed Automata’

Interoperability is a prerequisite for partners involved in performing collaboration. As a consequence, the lack of interoperability is now considered a major obstacle. The research work presented in this paper aims to develop an approach that allows specifying and verifying a set of interoperability requirements to be satisfied by each partner in the collaborative process prior to process implementation. To enable the verification of these interoperability requirements, it is necessary first and foremost to generate a model of the targeted collaborative process; for this research effort, the standardised language BPMN 2.0 is used. Afterwards, a verification technique must be introduced, and model checking is the preferred option herein. This paper focuses on application of the model checker UPPAAL in order to verify interoperability requirements for the given collaborative process model. At first, this step entails translating the collaborative process model from BPMN into a UPPAAL modelling language called ‘Network of Timed Automata’. Second, it becomes necessary to formalise interoperability requirements into properties with the dedicated UPPAAL language, i.e. the temporal logic TCTL.

Developing enterprise collaboration: a methodology to implement and improve interoperability

The aim of this article is to present a methodology for guiding enterprises to implement and improve interoperability. This methodology is based on three components: a framework of interoperability which structures specific solutions of interoperability and is composed of abstraction levels, views and approaches dimensions; a method to measure interoperability including interoperability before (maturity) and during (operational performances) a partnership; and a structured approach defining the steps of the methodology, from the expression of an enterprise’s needs to implementation of solutions. The relationship which consistently relates these components forms the methodology and enables developing interoperability in a step-by-step manner. Each component of the methodology and the way it operates is presented. The overall approach is illustrated in a case study example on the basis of a process between a given company and its dealers. Conclusions and future perspectives are given at the end of the article.

Writing and verifying interoperability requirements: Application to collaborative processes

Abstract Interoperability analysis is highly correlated with interoperability requirements, the ability to grasp, structure, author and verify such requirements has become fundamental to the analytical process. To this end, requirements must be: (1) properly submitted in a suitable and usable repository; (2) written correctly by stakeholders with relevance to the studied domain; and (3) as easily verifiable as possible on various models of the system for which interoperability capabilities are being requested. The purpose of this article is to present both a structured repository for interoperability requirements and a Domain Specific Language to write and verify interoperability requirements – within a collaborative process model – using formal verification techniques. The interoperability requirements repository, which serves to structure interoperability requirements and make them available, is itself structured through abstraction levels, views and interoperability life cycle dimensions. Additional parameters detailing the requested information and the known impacts of requirements on behavior of the studied system have also been included. The Domain Specific Language provides the means for writing interoperability requirements. Afterwards, these requirements − more specifically the temporal requirements − are re-written into properties by transforming the temporal logic TCTL to allow for their effective verification by using the model checker UPPAAL. The overall approach is illustrated in a case study based on a collaborative drug circulation process. The article also draws conclusions and offers an outlook for future research and application efforts

Interoperability as a Key Concept for the Control and Evolution of the System of Systems (SoS)

A coalition of enterprises wanting to collaborate, and more generally a Collaborative Network of Organizations (CNO), can conceptually be assimilated as a System of Systems (SoS) presenting a number of characteristics to respect all over its life cycle. Interoperability is one of these characteristics (both functional and non-functional), which is from our point of view, essential in order to guarantee the control of the SoS, its behavior and the fulfillment of its mission(s). Moreover, it ensures the reaction of the SoS to deal with some risky situations and with potential local or global deficits during its functioning. In this paper, we propose to determine the relation between the current level of interoperability of the SoS and its functioning whatever may be its situation. A matrix shows how this relation evolves taking into account several characteristics of the SoS, particularly its capacity to respect interoperability requirements (Compatibility, Interoperation, Autonomy and Reversibility) and the so-called analysis perspectives of the SoS: Performance, Integrity and Stability. This relation is requested in order to permit and to guide SoS behavioral simulation currently in development. Thus, a set of indicators is derived and formalized.

Towards a Conceptualisation of Interoperability Requirements

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, verification techniques can be used to detect how and where some of these requirements cannot be satisfied. This allows to highlight interoperability problems. This paper focuses on the two first phases and describes an approach to define and to formalise interoperability needs into interoperability requirements. These requirements are decomposed on three classes named compatibility, interoperation and reversibility requirements.

Embedding Interoperability in System of Systems: Definition and Characterization of Fundamental Requirements

The main objective of this communication is to discuss the engineering of a System of Systems (SoS), including interoperability concept. More precisely, the here presented research focuses on the fundamental requirements to consider in a System of Systems Engineering (SoSE) project and that have to be maintain during the entire life cycle of a SoS. First, the concept of interoperability, according to its definition and its characteristics, is presented. Then, the concept of SoS is presented in the same manner. This leads to introduce and present the possible links between System of Systems and interoperability. These links are (1) clarified and defined, (2) re-expressed to meet requirements’ definition and (3) not related to a given SoS in order to be generic.

Formalisation and Verification of Interoperation Requirements on Collaborative Processes

Abstract Interoperability is became a crucial question to improve success of a collaboration in a networked enterprise. Therefore, in a collaborative context, enterprises have to detect their interoperability problems to solve and to reach an efficient collaboration. This research work aims then to define, to formalise and to analyse a set of interoperability requirements that each partner of a collaborative process have to satisfy prior to any collaboration. This paper focuses and illustrates how interoperation requirements related to the dynamic aspect of the collaboration may be formalised and verified by the use of a formal verification technique.

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

The main objective of this communication is to present and discuss the need, for partners, to suitable interoperability solution according to their expectations. First, the problematic of the selection of a solution is presented and the stakeholders’ needs to tackle this statement are highlighted. Then, existing works related to interoperability requirements and interoperability solutions are briefly presented and discussed. Finally, criteria - and associated examples - that guide stakeholders in their selection are presented.

Interoperability analysis in critical collaborative processes: an application to the healthcare sector for complex patient assistance

Developing interoperability is a major issue in collaborative processes. For instance, interoperability is crucial for collaborative processes focused on crisis or healthcare-system management. Partners have to interact trustingly and efficiently. They need to share data, knowledge, best practices, resources and skills in terms of confidence, quality of exchanges and response times. They also need to be sure of the relevance and quality of their roles and actions throughout the process to achieve a desired outcome (crisis resolution, appropriate medical surgery, etc.). In this context, it is worthwhile trying to detect and solve interoperability problems prior to the execution of the process. This work focuses on interoperability in healthcare processes for complex patient assistance (diabetes, cardiovascular accidents, etc.), where different actors need to interoperate. The purpose is to show an approach for highlighting potential interoperability problems that can occur in a given process, with the support of formal verification techniques.