Content deleted Content added
ISresearcher (talk | contribs) |
ISresearcher (talk | contribs) No edit summary |
||
Line 15:
Accordingly, an Architecture of Interoperable Information Systems is the building plan of an cross-organizational information system, which enables the organization to execute a collaborative business process among them.
== Reference Architecture ==
The Architecture of Interoperable Information Systems (AIOS) represents a means for the comprehensive description of loosely coupled, interoperating information systems and for the systematic, model-based enactment of collaborative business processes. To this aim, it combines concepts from the areas of enterprise modeling, collaborative business and Service-oriented Computing. At the core of the architecture lies the Business Interoperability Interface, which describes the information system boundaries of one organization to its collaboration Partners and connects internal and external information systems.
<br />
The AIOS builds on three orthogonal axes: Enterprise Dimensions, Colloborative Views and Levels of technical Granularity.
=== Enterprise dimensions===
To describe business processes comprehensively, essential dimensions known from enterprise modeling are be covered, e.g. distinct views on processes, data, and organization elements. In the organization 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. In the data dimension, document types used in the collaboration are defined and related to internally used document types. In the function dimension, business functions and services offered in the collaboration are described. In the process dimension, the processes that each organization offers are described as well as how these public processes are related to adjacent processes of partner organizations.
=== Collaborative views ===
Similar to private, public and global views as known from business process and workflow modeling, in the AIOS, corresponding private, public and global views on information system elements are provided. The public view acts as an interface to the internal, private system elements; it protects internal systems and enables interoperability without the need for a significant change to the internal systems. The global view can be used to correlate and connect the public views of different systems.
=== Levels of technical granularity ===
The description of system elements on different levels of technical granularity supports a systematic development of collaborative information systems, starting with the business requirements definition and going all the way down to the code level. Apart from the construction aspect, a multi-dimensional interoperability description is also provided; describing the interacting systems on different levels of technical granularity enables the synchronization of the collaborating systems on each level. Similar to for example ARIS and MDA three levels are used:
# 1.
Business Level: Here the processes to be automated are described from a technique independent level. In MDA this level is referred to as CIM level.
# Numbered list item
Technical Level: Here the IT concept is described. Therefore, the models from the first level are technically enriched, for example, instead of business functions now components are described, but still on a coarse-grained, conceptual level. Since the models on the second level represent the basis for an automated generation of executable code, they might have to be further adapted to fit implementation level constraints.
3. Execution Level: Here the models are machine interpretable and can used during runtime in the execution of processes.
== References ==
| |||