Content deleted Content added
ISresearcher (talk | contribs) No edit summary |
ISresearcher (talk | contribs) No edit summary |
||
| (8 intermediate revisions by 7 users not shown) | |||
Line 2:
[[File:Architecture of Interoperable Information Systems.gif|thumb|right|Architecture of Interoperable Information Systems]]
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 generic building plan for these organizations to develop interoperable information systems by systematically adjusting and extending their internal information systems.
The AIOS was described in a doctoral thesis and is based on the results of various research projects on interoperability.<ref>Ziemann (2010): [http://www.logos-verlag.de/cgi-bin/buch/isbn/2414 Architecture of Interoperable Information Systems - An enterprise Model-based Approach for Describing and Enacting Collaborative Business Processes.] Logos, 2010. Logos was so kind to permit the [https://eamfundamentals.com/wp-content/uploads/2024/01/Ziemann_AIOS.pdf free download of a copy here]. A summary can be found here: Ziemann (2012): Architecture of Interoperable Information Systems - Reference Architecture for Collaborations between Public Administrations. In: Krallmann, H., Zapp, A. (Eds.): Bausteine einer vernetzten Verwaltung. Berlin, Erich Schmidt Verlag, 2012, pp. 165.</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 concepts from [[
== Definition ==
Line 9:
'''[[Information system]]s''' 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 {{Webarchive|url=https://web.archive.org/web/20110828212832/http://www.iso-architecture.org/ieee-1471/ieee-1471-faq.html |date=2011-08-28 }}, 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>
Accordingly, an '''Architecture of Interoperable Information Systems''' can be defined as the building plan of a cross-organizational information system, which enables organizations to execute a collaborative business process among them.
Line 19:
# 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. It tells organizations which information elements (e.g. descriptions of messages, exchange sequences, roles and services) they have to provide to collaboration partners and how they can optimally correlate these to internal elements.
# Description of different building paths for implementing or adjusting interoperable information systems. This is also called the '''dynamic''' part of the architecture. It tells organization, how to iteratively develop the elements mentioned above.
# Concept for the technical '''components needed to
One element comprised in the third category 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 provides publishing and discovery functionalities as needed in [[
== Structure ==
The static part of the architecture builds on three orthogonal axes: Enterprise Dimensions, Levels of technical Granularity and
=== Collaborative views ===
Line 32:
=== Enterprise dimensions ===
[[File:AIOS Enterprise Dimensions.JPG|thumb|
To describe business processes comprehensively this axis provides distinct views on processes, functions, data, and organizational elements.
# In the '''organizational dimension''', roles, units and other organization elements relevant for the collaboration are described and related to internal elements. This ensures for example, that the collaboration partners have a common understanding of the interacting roles.
Line 53:
[[Category:Interoperability]]
[[Category:Service-oriented (business computing)]]
[[Category:Business software]]
[[Category:Collaborative software]]
[[Category:Software architecture]]
| |||