Enterprise interoperability framework: Difference between revisions

Revision as of 05:12, 19 June 2014

Latest revision as of 11:06, 29 June 2023

(40 intermediate revisions by 25 users not shown)

Line 1:

{{UnderlinkedTechnical|date=JuneMay 20142021}}

{{Use dmy dates|date=October 2017}}

The '''Enterpriseenterprise Interoperabilityinteroperability Frameworkframework''' is used as a [[guideline]] for collecting and structuring knowledge/solution for [[enterprise interoperability]]. The Enterprise Interoperability Frameworkframework defines the ___domain[[Domain (software engineering)|domains]] and [[Subdomain|sub-domains]] for [[interoperability]] research and development in order to identify a set of pieces of knowledge for solving enterprise interoperability problems by removing barriers to interoperability.

Enterprise Interoperability Framework

==Existing interoperability frameworks==

The '''Enterprise Interoperability Framework''' is used as a guideline for collecting and structuring knowledge/solution for [[enterprise interoperability]]. The Enterprise Interoperability Framework defines the ___domain and sub-domains for interoperability research and development in order to identify a set of pieces of knowledge for solving enterprise interoperability problems by removing barriers to interoperability.

Some existing works on interoperability have been carried out to define interoperability framework or [[Reference model|reference models]], in particular, the LISI <ref name="C4ISR1998"/> reference model, [[European Interoperability Framework]] (EIF),<ref name="EIF2004"/> IDEAS interoperability framework,<ref name=" IDEAS2003"/> [[Model Driven Interoperability|ATHENA]] interoperability framework,<ref name="ATHENA2003"/> and E-Health Interoperability Framework.<ref name="NEHTA2006"/> These existing approaches constitute the basis for the Enterpriseenterprise Interoperabilityinteroperability Frameworkframework.

==Existing Interoperability Frameworks==

The necessity to elaborate the Enterprise Interoperability Framework has been discussed in.<ref name="INTEROP"/> Existing interoperability frameworks do not explicitly address barriers to [[interoperability]], which is a basic assumption of this research; they are not aimed at structuring interoperability knowledge with respect to their ability to remove various barriers.

Some existing works on interoperability have been carried out to define interoperability framework or reference models, in particular, the LISI <ref name="C4ISR1998"/> reference model, European Interoperability Framework (EIF),<ref name="EIF2004"/> IDEAS interoperability framework,<ref name=" IDEAS2003"/> ATHENA interoperability framework,<ref name="ATHENA2003"/> and E-Health Interoperability Framework.<ref name="NEHTA2006"/> These existing approaches constitute the basis for the Enterprise Interoperability Framework.

The Enterpriseenterprise Interoperability framework has three basic dimensions:

The necessity to elaborate the Enterprise Interoperability Framework has been discussed in.<ref name="INTEROP"/> Existing interoperability frameworks do not explicitly address barriers to interoperability, which is a basic assumption of this research; they are not aimed at structuring interoperability knowledge with respect to their ability to remove various barriers.

# Interoperability concerns defineddefine the content (or aspect) of [[interoperation]] that may take place at various levels of the enterprise. In the ___domain of Enterprise Interoperability, the following four interoperability concerns are identified : Datadata, Serviceservice, Processprocess, and Businessbusiness.<ref name=" Guglielmina2005"/> [[File:Interoperability Concerns Data, Service, Process, and Business.jpg|thumb|Interoperability Concernsconcerns: Datadata, Serviceservice, Processprocess, and Businessbusiness]]

The Enterprise Interoperability framework has three basic dimensions:

# Interoperability barriers: Interoperability barrier is a fundamental concept in defining the interoperability ___domain. Many interoperability issues are specific to particular [[Application ___domain|application domains]]. These can be things like support for particular attributes, or particular access control regimes. Nevertheless, general barriers and problems of interoperability can be identified; and most of them being already addressed,<ref name="EIF2004"/><ref name=" Kasunic2004"/>,.<ref name="ERISA2004"/> Consequently, the objective is to identify common barriers to interoperability. By the term ‘barrier’ we mean an ‘incompatibility’ or ‘mismatch’ which obstructs the sharing and exchanging of information. Three categories of barriers are identified: conceptual, technological and organisational.

# Interoperability approaches representsrepresent the different ways in which barriers can be removed (integrated, unified, and federated)

# Interoperability concerns defined the content (or aspect) of interoperation that may take place at various levels of the enterprise. In the ___domain of Enterprise Interoperability, the following four interoperability concerns are identified : Data, Service, Process, and Business.<ref name=" Guglielmina2005"/> [[File:Interoperability Concerns Data, Service, Process, and Business.jpg|thumb|Interoperability Concerns: Data, Service, Process, and Business]]

# Interoperability barriers: Interoperability barrier is a fundamental concept in defining the interoperability ___domain. Many interoperability issues are specific to particular application domains. These can be things like support for particular attributes, or particular access control regimes. Nevertheless, general barriers and problems of interoperability can be identified; and most of them being already addressed,<ref name="EIF2004"/><ref name=" Kasunic2004"/>,.<ref name="ERISA2004"/> Consequently the objective is to identify common barriers to interoperability. By the term ‘barrier’ we mean an ‘incompatibility’ or ‘mismatch’ which obstructs the sharing and exchanging of information. Three categories of barriers are identified: conceptual, technological and organisational.

# Interoperability approaches represents the different ways in which barriers can be removed (integrated, unified, and federated)

[[File:Basic Approaches to Develop Interoperability.jpg|thumb|Basic Approaches to Develop Interoperability]]

The Enterprise Interoperability Frameworkframework with its three basic dimensions is shown.

[[File:Enterprise Interoperability Framework.jpg|thumb|Enterprise Interoperabilityinteroperability Frameworkframework]]

== Enterprise Interoperability Framework Use ==

== Use ==

The Enterprise Interoperability Framework allows to:

* Capture and structure interoperability knowledge/solutions in the framework through a barrier-driven approach

* Provide support to enterprise interoperability engineers and industry end users to carry out their interoperability projects.

The Enterpriseenterprise Interoperabilityinteroperability Frameworkframework not only aims at structuring concepts, defining research ___domain and capturing knowledge, but also at helping industries to solve their interoperability problems. When carrying out an interoperability project involving two particular enterprises, interoperability concerns and interoperability barriers between the two enterprises will be identified first and mapped to this Enterprise Interoperability Framework.

Using the [[Enterprise architecture framework|framework]], existing interoperability degreedegrees can be characterisedcharacterized and targeted interoperability degreedegrees can be defined as the objective to meet. Then knowledge/solutions associated towith the barriers and concerns can be searched in the framework, and solutions found will be proposed to users for possible adaptation and/or combination with other solutions to remove the identified barriers so that the required interoperability can be established.

== References ==

Line 34 ⟶ 33:

refs=

<ref name= C4ISR1998>C4ISR (1998), Architecture Working Group (AWG), Levels of Information Systems Interoperability (LISI), 30 March 1998.</ref>

<ref name= EIF2004>EIF (2004), European Interoperability Framework for PAN-European EGovernment services, IDA working document - Version 4.2 – January 2004.</ref>

<ref name= IDEAS2003>IDEAS (2003), IDEAS Project Deliverables (WP1-WP7), Public reports, www.ideas-road map.net.</ref>

<ref name= ATHENA2003 >ATHENA (2003): Advanced Technologies for Interoperability of Heterogeneous Enterprise Networks and their Applications, FP6-2002-IST-1, Integrated Project Proposal, April 2003. Deriverable.</ref>

<ref name= NEHTA2006>NEHTA (2006), Towards a Health Interop Framework, ({{cite web |url=http://www. providersedge.com/ehdocs/...ehr_articles/Towards_an_Interoperability_Framework.pdf) |title=Towards a Health Interop Framework |access-date=2011-05-24}}. </ref>

<ref name= INTEROP >INTEROP D1.1, Knowledge map of research in interoperability in the INTEROP NoE, WP1, Version 1, August 11th 2004.</ref>

<!-- Not in use

<ref name= INTEROP >INTEROP D1.1, Knowledge map of research in interoperability in the INTEROP NoE, WP1, Version 1, August11 11thAugust 2004.</ref>

Not in use-->

<ref name= Guglielmina2005>C. Guglielmina and A. Berre, Project A4 (Slide presentation), ATHENA Intermediate Audit 29.-30. September 2005, Athens, Greece.</ref>

<ref name= Kasunic2004>Kasunic, M., Anderson, W.,: Measuring systems interoperability: challenges and opportunities, Software engineering measurement and analysis initiative, April 2004</ref>

Line 47 ⟶ 49:

== External links ==

* [http://www.interop-vlab.eu INTEROP-VLab]

* [https://archive.today/20140616211358/http://interop-vlab.eu/ei_public_deliverables/interop-noe-deliverables/di-___domain-interoperability/di-2-enterprise-interoperability-framework-and-knowledge-corpus/ DI.2.Enterprise Interoperability Framework and knowledge corpus]

* [https://archive.today/20140616211337/http://interop-vlab.eu/ei_public_deliverables/interop-noe-deliverables/di-___domain-interoperability/di-3_enterprise-interoperability-framework-and-knowledge-corpus/ DI.3.Enterprise Interoperability Framework and knowledge corpus]

[[Category:Interoperability]]