Architecture of Interoperable Information Systems: Difference between revisions

Revision as of 05:17, 31 December 2012

Revision as of 08:16, 31 December 2012

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 IT[[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 blue print for these organizations to systematically adjust and extend their internal information systems in order to make them interoperable with those of collaboration partners.
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><ref>R4eGov, Interop, ATHENA</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 Inin the context of of collaborating organizations, the[[Business termInteroperability Interface#Business Interoperability|Business was proposedInteroperability]]. In comparison to technical interoperability notions, this term refers to 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 also embodied by the [[Zachman Framework]].