Architecture of Interoperable Information Systems: Difference between revisions

Revision as of 08:24, 31 December 2012

Revision as of 15:20, 31 December 2012

Line 13:

== Background and Application ==

Following the work on interoperable information systems conducted in European Research Projects (e.g. <ref>Interop NOE (2004 to 2007, project number IST-2004-508011), ATHENA (2004 to 2007, “Advanced Technologies for Interoperability of Heterogeneous Enterprise Networks and their Application”, project number IST-2004-507849) or R4eGov (2006 to 2009, project number IST-2004-026650)</ref>), in 2010 the Architecure of Interoperable Information Systems (AIOS) was published as a reference for the construction of loosely coupled, interoperating information systems and for the systematic, model-based enactment of collaborative business processes.

The AIOS originally aims at large organizations who want to interoperate with each other. To this aim it describes how internal information system elements can be systematically connected with the information systems of collaboration partners.

The AIOS originally aims at large organizations who want to interoperate with each other. To this aim it describes how internal information system elements can be systematically connected with the information systems of collaboration partners. Though the AIOS comprises all models needed for the enactment of collaborative business it focuses on '''design time''' aspects, e.g. the systematic development and configurationadjustment of interoperable information systems. The deployment of these models and the infrastructure to execute them are not described by AIOS.
However, a concept for the technical components needed to implmenent interoperable inforamation systems is provided. For example, one '''run time''' component of the AIOS is a '''"BII-repository"''', in which each organization publishes the content of its [[Business Interoperability Interface]] (BII) to collaboration partners. Since it comprises external views on information system elements, it can support (runtime) publishing and discovery functionalities as needed in [[Service-oriented Architecture]]: In the BII, the externally relevant processes, services, organization structures etc. are described on various levels of technical granularity, enabling other organizations to search also for business-level concepts and not only for technical artifacts. Here, different from the traditional SOA approach, instead of one central service directory, various partner-specific repositories are implemented.

== Structure ==