Architecture of Integrated Information Systems

Last updated
Model of the ARIS Framework. ARIS Model EN.svg
Model of the ARIS Framework.

The ARIS concept (Architecture of Integrated Information Systems) by August-Wilhelm Scheer aims to ensure that an enterprise information system can completely meet its requirements.

Contents

This framework is based on a division of the model into description views and levels, which allows a description of the individual elements through specially designed methods, without having to include the entire model. The methodology serves as a systems development life cycle for mapping and optimizing business processes. These processes are mapped for each description view, starting with the business management question up to the implementation on data processing level. [1]

ARIS house (description views)

ARIS relies mainly on its own five-view architecture (ARIS house). These five views are based on function, organization, data, product or service views of a process, and the process view itself, that integrates the other views. The classification is made to break down the complexity of the model into five facets and thus make business process modeling simpler.

Each view of the ARIS concept represents the model of a business process under a specific aspect:

Description levels

Each description view of the ARIS house is divided into three description levels:

Concept

Structured representation of the business processes by means of description models that are understandable for the business side (depending on the view, e.g.: ERM, EPC, organization chart, function tree)

Data Concept (= data processing concept, IT concept)

Implementation of the technical concept in IT-related description models (depending on the view e.g. relations, structure charts, topologies)

Implementation

IT-technical realization of the described process parts (depending on the view, e.g. by creating program code, database systems, use of protocols)

The ARIS concept forms the basis of various software products, including the ARIS Toolset from Software AG, which has been the owner of ARIS trademarks since IDS Scheer AG was acquired. At the end of 2004, part of the concept was reflected in the graphical process integration of SAP Exchange Infrastructure.

Although ARIS is a well-known approach for the description of information system architectures, especially in German-speaking countries, it is not as well known on a larger scale. With in the Management Frameworks group it is one of over fifty existing frameworks for information management on the market. [3] The architecture of interoperable information systems (AIOS) was also published in 2010 at the Institut für Wirtschaftsinformatik (Institute for Information Systems) in Saarbrücken, which was founded by Scheer. While ARIS describes company-internal information systems and business processes, AIOS describes how cross-company business processes can be realized by adapting and loosely coupling information systems.

With the "Model-to-Execute" approach, business processes can be modelled in ARIS and automatically transferred to webMethods BPM for technical execution.

Applications

As one of the Enterprise Modeling methods, ARIS provides four different aspects of applications:

Examples

See also

Related Research Articles

<span class="mw-page-title-main">August-Wilhelm Scheer</span> German businessman

August-Wilhelm Scheer is a German Professor of business administration and business information at Saarland University, and founder and director of IDS Scheer AG, a major IT service and software company. He is known for the development of the Architecture of Integrated Information Systems (ARIS) concept.

Software AG is a German multinational software corporation that develops enterprise software for business process management, integration, and big data analytics. Founded in 1969, the company is headquartered in Darmstadt, Germany, and has offices worldwide.

<span class="mw-page-title-main">CIMOSA</span> Enterprise modeling framework

CIMOSA, standing for "Computer Integrated Manufacturing Open System Architecture", is an enterprise modeling framework, which aims to support the enterprise integration of machines, computers and people. The framework is based on the system life cycle concept, and offers a modelling language, methodology and supporting technology to support these goals.

<span class="mw-page-title-main">Business process modeling</span> Activity of representing processes of an enterprise

Business process modeling (BPM), mainly used in business process management; software development, or systems engineering, is the action of capturing and representing processes of an enterprise, so that the current business processes may be analyzed, applied securely and consistently, improved, and automated. BPM is typically orchestrated by business analysts, leveraging their expertise in modeling practices. Subject matter experts, equipped with specialized knowledge of the processes being modeled, often collaborate within these teams. Alternatively, process models can be directly derived from digital traces within IT systems, such as event logs, utilizing process mining tools.

Enterprise architecture (EA) is a business function concerned with the structures and behaviours of a business, especially business roles and processes that create and use business data. The international definition according to the Federation of Enterprise Architecture Professional Organizations is "a well-defined practice for conducting enterprise analysis, design, planning, and implementation, using a comprehensive approach at all times, for the successful development and execution of strategy. Enterprise architecture applies architecture principles and practices to guide organizations through the business, information, process, and technology changes necessary to execute their strategies. These practices utilize the various aspects of an enterprise to identify, motivate, and achieve these changes."

<span class="mw-page-title-main">Computer-integrated manufacturing</span> Manufacturing controlled by computers

Computer-integrated manufacturing (CIM) is the manufacturing approach of using computers to control the entire production process. This integration allows individual processes to exchange information with each part. Manufacturing can be faster and less error-prone by the integration of computers. Typically CIM relies on closed-loop control processes based on real-time input from sensors. It is also known as flexible design and manufacturing.

<span class="mw-page-title-main">Event-driven process chain</span>

An event-driven process chain (EPC) is a type of flow chart for business process modeling. EPC can be used to configure enterprise resource planning execution, and for business process improvement. It can be used to control an autonomous workflow instance in work sharing.

Process mining is a family of techniques used to analyze event data in order to understand and improve operational processes. Part of the fields of data science and process management, process mining is generally built on logs that contain case id, a unique identifier for a particular process instance; an activity, a description of the event that is occurring; a timestamp; and sometimes other information such as resources, costs, and so on.

<span class="mw-page-title-main">Enterprise modelling</span>

Enterprise modelling is the abstract representation, description and definition of the structure, processes, information and resources of an identifiable business, government body, or other large organization.

<span class="mw-page-title-main">Architecture domain</span> Broad view of an enterprise or system

An architecture domain in enterprise architecture is a broad view of an enterprise or system. It is a partial representation of a whole system that addresses several concerns of several stakeholders. It is a description that hides other views or facets of the system described. Business, data, application and technology architectures are recognized as the core domains in the most of proposed concepts concerned with the definition of enterprise architecture.

<span class="mw-page-title-main">Function model</span>

In systems engineering, software engineering, and computer science, a function model or functional model is a structured representation of the functions within the modeled system or subject area.

<span class="mw-page-title-main">Enterprise life cycle</span> Process of changing an enterprise over time

Enterprise life cycle (ELC) in enterprise architecture is the dynamic, iterative process of changing the enterprise over time by incorporating new business processes, new technology, and new capabilities, as well as maintenance, disposition and disposal of existing elements of the enterprise.

Process map is a global-system process model that is used to outline the processes that make up the business system and how they interact with each other. Process map shows the processes as objects, which means it is a static and non-algorithmic view of the processes. It should be differentiated from a detailed process model, which shows a dynamic and algorithmic view of the processes, usually known as a process flow diagram. There are different notation standards that can be used for modelling process maps, but the most notable ones are TOGAF Event Diagram, Eriksson-Penker notation, and ARIS Value Added Chain.

<span class="mw-page-title-main">View model</span> Framework for enterprise and system engineering

A view model or viewpoints framework in systems engineering, software engineering, and enterprise engineering is a framework which defines a coherent set of views to be used in the construction of a system architecture, software architecture, or enterprise architecture. A view is a representation of the whole system from the perspective of a related set of concerns.

<span class="mw-page-title-main">Business reference model</span>

Business reference model (BRM) is a reference model, concentrating on the functional and organizational aspects of the core business of an enterprise, service organization or government agency.

<span class="mw-page-title-main">Treasury Enterprise Architecture Framework</span>

Treasury Enterprise Architecture Framework (TEAF) was an enterprise architecture framework for treasury, based on the Zachman Framework. It was developed by the US Department of the Treasury and published in July 2000. May 2012 this framework has been subsumed by evolving Federal Enterprise Architecture Policy as documented in "The Common Approach to Federal Enterprise Architecture".

<span class="mw-page-title-main">IDS Scheer</span>

IDS Scheer was a software company that developed, marketed, and supported Business Process Management (BPM) software. It has been regarded as the founder of the BPM industry. The company was established in 1984 by August-Wilhelm Scheer who also served as supervisory board chairman and Chief Technology Advisor, as a spin-off from the Institute for Information Systems. The company was centered around selling products and services based on Dr. Scheer's early Y-Model, developed in the 1980s. In 2009 it was acquired by Software AG.

<span class="mw-page-title-main">NIST Enterprise Architecture Model</span> Reference model for enterprise architecture

NIST Enterprise Architecture Model is a late-1980s reference model for enterprise architecture. It defines an enterprise architecture by the interrelationship between an enterprise's business, information, and technology environments.

<span class="mw-page-title-main">Treasury Information System Architecture Framework</span>

The Treasury Information System Architecture Framework (TISAF) is an early 1990s Enterprise Architecture framework to assist US Treasury Bureaus to develop their Enterprise Information System Architectures (EISAs).

<span class="mw-page-title-main">Architecture of Interoperable Information Systems</span>

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 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. 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 service-oriented architecture, Collaborative Business and Business Process Modelling. It can be seen as complementary to ARIS, a well-known architecture for internal information systems and business processes.

References

  1. Dirk Matthes: . 2011. Auflage. Springer Science+Business Media, 2011, ISBN   978-3-642-12954-4, S. 44.
  2. Software AG (Hrsg.). "ARIS Platform" (PDF).
  3. Dirk., Matthes (2011). Enterprise Architecture Frameworks Kompendium Über 50 Rahmenwerke für das IT-Management. Berlin, Heidelberg: Springer-Verlag Berlin Heidelberg. ISBN   9783642129551. OCLC   723286135.

Further reading