Architecture of Interoperable Information Systems: Difference between revisions

Content deleted Content added
No edit summary
Line 1:
{{AFC submission|d|reason|3=Thanks for your efforts, but I believe the article needs a better lead and tone for viewers unfamiliar with the subject. Consider visiting [[Wikipedia:Writing better articles]].|declinets=20120722003316|decliner=SwisterTwister|ts=20120715171112|u=ISresearcher|ns=2}}
The '''Architecture of Interoperable Information Systems (AIOS)''' is a reference architecture for the development of interoperable [[enterprise information systems]]. If enterprises or public administrations want to engage in automated business processes with other organizations, their IT systems must be able to work together, i.e. they need to be [[interoperability|interoperable]]. The AIOS represents a bluegeneric building printplan for these organizations to systematicallydevelop adjustan and extend their internalinteroperable information systems inby ordersystematically toadjusting makeand themextending interoperabletheir withinternal thoseinformation of collaboration partnerssystems.
The AIOS was described in a doctoral thesis and is based on the results of various research projects on interoperability <ref>Ziemann (2010): Architecture of Interoperable Information Systems - An enterprise Model-based Approach for Describing and Enacting Collaborative Business Processes. Logos, 2010</ref> It is independent from specific products or vendors but describes generically the different layers, views, relationships and technical means needed to efficiently establish interoperable information systems. To this aim it combines well concepts from [[Service-oriented Architecture]], Collaborative Business and [[Business Process Modelling]]. It can be seen as complementary to [[Architecture of Integrated Information Systems|ARIS]], a wide-spread architecture for internal information systems and business processes.
 
== Definition ==
The automation of cross-organizational [[business process]]es is one of the most important trends of the information age. Instead of a tight [[integration]], collaborating organizations rather strive for a loose coupling of their information systems: information systems should be able to work together but retain as much independency as possible. This characteristic is also called '''[[interoperability]]''', or in the context of of collaborating organizations, [[Business Interoperability Interface#Business Interoperability|Business Interoperability]], referring toi.e. the capability of autonomous organizations to execute a collaborative business process among them.
 
'''[[Information systems|Information system]]''' are systems that process information, i.e. they capture, transport, transform, store and offer information. Following the conception prevailing in information systems research, an information system comprises not only the hardware and software of an enterprise, but also the related human actors, business functions and processes as well as organization structures.<ref>Compare for example Becker & Schütte (2004, p. 33): Handelsinformationssysteme – Domänenorientierte Einführung in die Wirtschaftsinformatik 2nd Edition, Redline Wirtschaft, Frankfurt or Gabriel(2008): Informationssystem. Enzyklopädie der Wirtschaftsinformatik, Online Lexikon. Oldenbourg Wissenschaftsverlag, Germany. </ref> This broad understanding is for example also embodied by the [[Zachman Framework]].
 
'''[[Architecture]]''' is defined as the “fundamental organization of a system, embodied in its components, their relationships to each other and the environment, and the principles governing its design and evolution”<ref>IEEE (2007): IEEE 1471 Website, IEEE Std. 1471 Frequently Asked Questions (FAQ) - Version 5.0, 19 July 2007. Http://www.iso-architecture.org/ieee-1471/ieee-1471-faq.html, ac-cessed: May 2009</ref>. Sinz defines an information system architecture as the building plan of an information system in the sense of a specification and documentation of its components and their relationships covering all relevant viewpoints as well as the constructions rules for the creation of the building plan<ref> Sinz (2002): Architektur von Informationssystemen. In: Rechenberg, P., Pomberger, G. (eds.): Informatik-Handbuch. 3rd Edition, Hanser, München, pp. 1055-1068</ref>.
Line 15:
Following the work on interoperable information systems conducted in European Research Projects<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 primarily at large organizations whothat 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. ThoughThe themain AIOS comprises all models needed for the enactmentelements of collaborative business it focuses on '''design time''' aspects, e.g. the systematic development and adjustment of interoperable information systems. The infrastructure to execute themAIOS are not described by AIOS.
# Description of the different data types comprised in interoperable information system as well as their relationships. This is also called the '''static''' part, or the ''structure'' of the architecture.
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.
# Description of different building paths for implementing or adjusting interoperable information systems. This is also called the '''dynamic''' part of the architecture.
# Concept for the technical '''components needed to implemenent''' the architecture, for example design tools, internal and externally visible repositories.
 
However,One aelement conceptcomprised forin the technical components needed to implmenent interoperable inforamation systems is provided. For example, one '''run time''' component of thethird AIOScategory 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 ==
[[File:Architecture of Interoperable Information Systems.gif|thumb|right|Architecture of Interoperable Information Systems]]
The static part of the architecure builds on three orthogonal axes: Enterprise Dimensions, Levels of technical Granularity and Colloborative Views. The latter provides a public view on private information system elements. Thus, the architecture provides a comprehensive [[Business Interoperability Interface]], which describes the information system boundaries of one organization to its collaboration Partners and connects internal and external information systems.
 
=== Enterprise dimensions===
Line 41 ⟶ 45:
 
 
[[:Category:Interoperability]]
 
[[:Category:Operations research]]
[[:Category:Business]]