Content deleted Content added
Disambiguated: framework → Enterprise architecture framework; Unlinked: Approach |
m →Existing Interoperability Frameworks: clean up, typo(s) fixed: Consequently → Consequently, using AWB |
||
Line 11:
# Interoperability concerns defined the content (or aspect) of interoperation that may take place at various levels of the [[Business|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]]
| |||