0% found this document useful (0 votes)
127 views19 pages

Architecture of Integrated Information Systems: Objectives Lecture 21.05.04

The document provides an overview of ARIS (Architecture of Integrated Information Systems), which is a framework for developing enterprise architectures. It describes the key components of the ARIS framework, including the ARIS House with five views (Function, Organization, Data, Output/Service, and Process/Control views) and how they relate to each other. The document also discusses how the ARIS Phase Model can be integrated into the ARIS House to transform business requirements into IT solutions in a step-by-step manner. Modeling methods like EPC, product diagrams, and others are mapped to different views. The ARIS framework aims to clearly and systematically represent business processes using these interconnected views and models.

Uploaded by

freshpomelo
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
127 views19 pages

Architecture of Integrated Information Systems: Objectives Lecture 21.05.04

The document provides an overview of ARIS (Architecture of Integrated Information Systems), which is a framework for developing enterprise architectures. It describes the key components of the ARIS framework, including the ARIS House with five views (Function, Organization, Data, Output/Service, and Process/Control views) and how they relate to each other. The document also discusses how the ARIS Phase Model can be integrated into the ARIS House to transform business requirements into IT solutions in a step-by-step manner. Modeling methods like EPC, product diagrams, and others are mapped to different views. The ARIS framework aims to clearly and systematically represent business processes using these interconnected views and models.

Uploaded by

freshpomelo
Copyright
© Attribution Non-Commercial (BY-NC)
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 19

ARIS Architecture of Integrated Information Systems

ARIS
Architecture of Integrated Information Systems

Objectives lecture 21.05.04:


-

The approach how to build ARIS


Modeling methods: EPC, Product diagram
Case studies

ARIS Architecture of Integrated Information Systems

Table of Content
1

Short Outline of ARIS........................................................................................................ 4


1.1
ARIS House and its views.......................................................................................... 5
1.2
Useful Definitions ...................................................................................................... 7
2
Developing approach of ARIS ........................................................................................... 8
2.1
Modeling Enterprise Business Processes ................................................................... 8
2.1.1
Interaction Flow ................................................................................................. 9
2.1.2
Function Flow .................................................................................................. 10
2.1.3
Output Flow...................................................................................................... 11
2.1.4
Consolidated Business Process Model ............................................................. 12
2.2
Abstraction level in modeling .................................................................................. 14
2.3
The Generalized Business Process Model ............................................................... 15
2.4
Building the ARIS Views......................................................................................... 16
2.4.1
Function View .................................................................................................. 16
2.4.2
Organizational View ........................................................................................ 16
2.4.3
Data View......................................................................................................... 17
2.4.4
Output/Service View ........................................................................................ 17
2.5
Integration of the generalized business process model segments into the ARIS
House .................................................................................................................................. 18
2.6
Integration of the ARIS Phase Model into the ARIS House.................................... 20
2.7
ARIS House with ARIS Phase Model...................................................................... 21

ARIS Architecture of Integrated Information Systems

Table of figures
Figure 1: System features........................................................................................................... 4
Figure 2: ARIS House ................................................................................................................ 5
Figure 3: ARIS House with ARIS phase model........................................................................ 6
Figure 4: Interaction flow........................................................................................................... 9
Figure 5: Function Flow........................................................................................................... 10
Figure 6: Categories of output................................................................................................. 11
Figure 7: Output Flow .............................................................................................................. 11
Figure 8: Consolidated business process model order processing....................................... 12
Figure 9: ARIS Business Process Model ................................................................................. 13
Figure 10: Level of model abstractions.................................................................................... 14
Figure 11: The general ARIS business process model............................................................. 15
Figure 12: ARIS Views ............................................................................................................ 18
Figure 13: ARIS Phase Model ................................................................................................. 20

ARIS Architecture of Integrated Information Systems

1 Short Outline of ARIS


ARIS stands for Architecture of Integrated Information Systems. An Architecture is a
designation generally used in building construction. In information technology (IT), it
describes the
type,
functional properties and the
interrelationship among
the individual building blocks of the information system. Beside that it delivers modeling
methods.

Definition of an architecture concerning of an information system (IS)


An architecture is a
description of an information system
its components and functional qualities (kind and size),
the relationships between the components.
It supplies methods to describe the components (business circumstances) and
process of developing of IS framework to build information systems

The ARIS is used to develop an enterprise architecture which supports a business framework.
To represent processes clearly and systematically, ARIS framework includes four static
views and one dynamic view. The figure below illustrates this fact.

System
features

Structure of
the system
Static view on the system
(organizational view,
function view, output view,
data view)

Behaviour of the
system
The dynamic flow in the
system
functions and events
(process/control view)

Regarding all structured connections of the views and the dynamic


behaviour of business process flow

Figure 1: System features

ARIS Architecture of Integrated Information Systems

ARIS House and its views


The ARIS House is divides into 5 views. All views have interaction view each other. There
are interrelationships.

Organization View

(Process)

Data
View

Control

Function
View

View

Product/Service View

Relationship
(Interaction)

Figure 2: ARIS House

1. Control view
The process view (or control view) displays the static connections between the objects of the
data, function, performance and organization views, and the dynamic, chronological process
flows.
Modeling method like: EPC (Event Process Chain) or eEPC (Extended Event Process Chain)
2. Product/Service view
The product/service view structures all material and non-material inputs and outputs that are
brought into, or performed by, the business process.
Modeling method like: product diagrams (gozinto graph)
3. Data view
Information objects and their attributes, as well as the relationships between information
objects are described in the data view. Because events represent the status of the process at a
certain point in time, they are also assigned to the data view.
Modeling method like: ERM (Entity Relationship Model) or UML (Unified Modeling
Language)
4. Function view
The transactions that transform performances and the static relationships between them are
described in the function view. The terms function, transaction and activity are used
here synonymously. Application systems are also included in the function view, because they
determine the computer-supported processing rules for activities.
Modeling method: Function tree
5. Organization view
Organizational elements and their relationships form the organizational structure are
described in the organization view. In addition to these human resources, operating resources
and computer hardware are also assigned to this view.
Modeling method like: Organigram

ARIS Architecture of Integrated Information Systems

The views 1 to 4 are static views, in that while they may imply a process flow, they do not
explicitly show how a process flow5. Consequently, the information captured in the static
views must be combined into the dynamic process view (views 1). The process view (or
control view) displays the static connections between the objects of the data, function,
performance and organization views (bilateral relationships/interactions), and the dynamic,
chronological process flows. All five views are combined into a construct known as the
ARIS House. The ARIS house is the framework within which ARIS architectures are
created. The central view, the control view, is the combination of the individual views. Each
of the ARIS views is supported by many model types (as mentioned like ERM, Organigram,
Function tree etc.)
The advantage of dividing business processes into individual views is that the complexity of
the business processes is reduced. One can look at one view without being overwhelmed with
information from the other views. However, the interrelationships created between
organizational, data-technical, performance-related, and functional aspects when designing
the views are stored and maintained so the components of the different views can be
reassembled in the process view when the whole picture is needed.
The next figure shows the ARIS House with the integrated ARIS phase model. It allows to
transform business related issues step by step into information technology solutions.

Organisation
View

Requirements
Definition
Design Specification
Implementation

Requirements
Definition

Design
Specification
Requirements

Requirements
Definition

Definition

Design
Specification

Design
Specification

Design
Specification

Implementation

Implementation

Implementation

Data
View

Control
View

Functions
View

Product/Service View
Figure 3: ARIS House with ARIS phase model

ARIS Architecture of Integrated Information Systems

1.1 Useful Definitions


Definition of a business process
Generally speaking, a business process is a continuous series of enterprise tasks,
undertaken for the purpose of creating output. The starting point and final product of the
business process is the output requested and utilized by corporate or external customers.

There are multiple reasons for creating business process models, such as:

Optimizing organizational changes, a by-product of BPR,


Storing corporate knowledge, in reference models,
Calculating the cost of business processes,
Leveraging process information to implement and customize standard software solutions or
workflow systems.

Business process reengineering (BPR) is the analysis and radical redesign of business
(processes) within and between enterprises. BPR reached its heyday in the early 1990's when
Michael Hammer and James Champy published their best-selling book, "Reengineering the
Corporation".
Reasons for Business Process Optimization (BPM):
Changing the process structure by introducing simultaneous tasks, avoiding cycles,
streamlining the structure,
Changing organizational reporting structures and developing employee qualification by
improving processing in its entirety,
Reducing the amount of documentation, streamlining and accelerating document and data
flow,
Discussing possible outsourcing measures (shifting from internal to external output
creation),
Implementing new production and IT resources to improve processing functions.

Further reasons for doing BPR

Design of efficient administration of resources


lower process costs
Engineering of high competitiveness processes
short process processing time

.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................

ARIS Architecture of Integrated Information Systems

2 Developing approach of ARIS


We are going to develop the ARIS House gradually.

At first we start with the general ARIS business process model.


Afterwards we are building the ARIS Views
Then we assemble the first version of the ARIS House
In order to get the final version of the ARIS House it is crucial to look at the ARIS
phase model
Integration of the ARIS phase model in to the ARIS House
Analysing the modeling methods especially on the requirement definition level

2.1 Modeling Enterprise Business Processes


There are many ways to model a process flow. You can design the flow according to the

Interaction Flow,
Function Flow or
Output Flow etc.

But almost none of them are able to reflect completely the real process flow. Therefore
usually a combination of these modeling method are necessary.

In order to describe the listed flow we will us the following business scenario:
A customer wants to order several items which need to be manufactured. Based on customer
and item information, the feasibility of manufacturing this item is studied. Once the order has
arrived, the necessary materials are obtained from a supplier. After arrival of the material and
subsequent order planning, the items are manufactured according to a work schedule and
shipped to the customer, along with the appropriate documentation.

.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................

ARIS Architecture of Integrated Information Systems

2.1.1 Interaction Flow

Interaction flow diagram describes units or persons who are responsible for an
assignment and their relationships (output- and communicational relationships) in the
business process.
Process logic direction of process flow is not clearly given (more a static view)

Reports
a Demand

Order
Purchasing

Pays Funds

Supplier

Delivers
Places an Order
Customer

Pays Funds

Sale

Places an Order

Manufacturing
Plans,
Manufactures

Checks
Order

Delivers Item

Shipping
Ships

Delivers
Legend:
Organizational Unit
Interaction

Figure 4: Interaction flow

.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................

ARIS Architecture of Integrated Information Systems

2.1.2 Function Flow

The business process is described by the activities (functions)


Dynamic processes are in frontline instead of persons and units
Dynamic view

Figure 5: Function Flow

.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................

ARIS Architecture of Integrated Information Systems

2.1.3 Output Flow

This modeling method focuses on the output which are produced during the process flow. It is
a static view.

Figure 6: Categories of output

The output flow looks as follows

Figure 7: Output Flow

ARIS Architecture of Integrated Information Systems

2.1.4 Consolidated Business Process Model


As before described none of the introduced flows reflects the complete business process flow entirely. We must therefore combine all these
perspectives. The function flow is closest to the definition of the business process, we will use it as foundation flow. We add the other flows to the
function flows.

Figure 8: Consolidated business process model order processing

ARIS Architecture of Integrated Information Systems

Customer

Enterprise

Supplier
Suppliers,
Materials

Purchasing

Supplier
Order

Write up Purchase Order


Short
Processing
Time

Order
arrived

Suppliers

Purchasing

Payment

Customer

Customer
Order

Suppliers

Write up Purchase Order

Demand
reported
PC

Ordering
Program

Customer

Suppliers

Accept
Merchandise

Merchandise
accepted
PC

Ordering
Program

Customer

Suppliers

Send
Payment
PC

Accounts
payable

Customers,
Suppliers

Sales

Order
accepted

Check
Order
Customer
Satisfaction

Deadlines
kept
Customer
Payment

Truck

PC

Shipping
Program

Accounts
payable

PPC
System

Manufacturing Plan
completed
Manufacturing Plan

Shop FLoor

Item
completed

Scheduler

Sales

PC

Item

Ship
Item

Merchandise
arrived
Shipping
Order

Short Lead
Time

Customers,
Items

Shipping

PC

Plan Manufacturing

Sales Infomation System

PC

Short Lead Time

Shippment
of Item

Order
accepted

Order
Documents

Suppliers

Customers

PC

Funds
accepted
Accounts
receivable

Work
Schedule

Manufacturing

Checked
Order

Sales Infomation System

Accept
Funds

Materials
Order
processed

PC

Payment
arrived

Pay
Keep Payment
Deadline

Process
Order

Ordering
Program

PC

Customers,
Materials

Supplier

Work
Schedule

Manufacture Item
High
Quality

Machine

Machine
Operator

Control
CPU

PPC
System

Customers

Legend:
Accept
Funds

Payment
arrived
Low
Transaction
Costs

PC

Funds
accepted
Accounts
receivable

PPC
PC

Organization Flow / Resource Flow


Control Flow
Information Flow
Information Sevices Flow
Material Output Flow
= Production Planning and Control
= Personal Computer

Figure 9: ARIS Business Process Model

Function

Event

Human
Output

Organizational Unit

Message

Goal

Environmental Data

Machine

Output

Computer
Hardware

Application
Software
Logical
Operator
AND"

ARIS Architecture of Integrated Information Systems

2.2 Abstraction level in modeling


Models can be modelled on different abstraction levels.

G
E
N
E
R
A
L
I
Z
A
T
I
O
N

S
P
E
C
I
F
I
C
A
T
I
O
N

Figure 10: Level of model abstractions

.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................

ARIS Architecture of Integrated Information Systems

2.3 The Generalized Business Process Model

Figure 11: The general ARIS business process model

.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................
.......................................................................................................................................................

ARIS Architecture of Integrated Information Systems

2.4 Building the ARIS Views


Why do we need the ARIS views?
Because
the grouping of classes and their relationships into views serves the purpose of structuring
and streamlining business process models.
splitting up views has the added advantage of avoiding redundancies which can occur
when objects in a process model are used more than once.
we can use view specific modeling methods.

2.4.1 Function View


Information
Services

Other
Services

Input
(Is Processed)

Environmental Data

Material
Input

Co
ntr
ols

Output
(Is Created)

Ingoing

Outgoing

Triggers

Other
Services

Material
Output

Transforms

Financial
Resources

Initial
Event

Information
Services

Goal

Financial
Resources

Result/
Event

Function
Message
Executes, Controls

Responsible Processes
Organizational Unit

Huma
Output

Us
es

Us
es
Machine
Resource

Computer
Hardwar

Softwar

2.4.2 Organizational View


Information
Services

Other
Services

Input
(Is Processed)

Environmental Data

Material
Input

Co
ntr
ols

Output
(Is Created)

Ingoing

Outgoing

Triggers

Executes, Controls

Organizational Unit

Huma
Output

Us
es
Machine
Resource

Financial
Resources

Result/
Event

Function
Message

Responsible Processes

Other
Services

Material
Output

Transforms

Financial
Resources

Initial
Event

Information
Services

Goal

Us
es
Computer
Hardwar

Softwar

......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................

......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................

ARIS Architecture of Integrated Information Systems

2.4.3 Data View


Information
Services

Information
Services

Goal

Other
Services

Input
(Is Processed)

Co
ntr
ols

Environmental Data

Output
(Is Created)

Transforms

Material
Input

Material
Output
Financial
Resources

Financial
Resources

Ingoing

Outgoing

Triggers

Initial
Event

Other
Services

Result/
Event

Function
Message
Executes, Controls

Responsible Processes
Organizational Unit

Us
es

Us
es

Compute
Hardwar

Machine
Resource

Human
Output

Softwar

2.4.4 Output/Service View

Information
Services

Other
Services

Input
(Is Processed)

Environmental Data

Material
Input

Co
ntr
ols

Output
(Is Created)

Ingoing

Outgoing

Triggers
Message

Executes, Controls

Organizational Unit

Huma
Output

Us
es
Machine
Resource

Financial
Resources

Result/
Event

Function

Responsible Processes

Other
Services

Material
Output

Transforms

Financial
Resources

Initial
Event

Information
Services

Goal

Us
es
Computer
Hardwar

Softwar

......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................

......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................
......................................................

ARIS Architecture of Integrated Information Systems

2.5 Integration of the generalized business process model


segments into the ARIS House
After the segmentation of the Generalized Business Process Model we can integrate the
segments and the complete process it into the ARIS House. Each view gets its own position.
The Control (Process) view is the view in the centre of the house. It combines all views
together. On top of this it also contains information about the relationship between the views.

Organization View

Organizational Unit

Machine

Resource
Computer
Hardware
Resource

Human
Output

Organizational

Machine

Human
Outpu

Event

Goal
Hardware

Message
Environmental Data

Goal

Function

Event

Event

Environmental

Application
Software
Input

Output

Data View

Control View

Function

Application
Software

Function View

Output

Output View
Figure 12: ARIS Views

Description of the
Function view
The processes transforming input into output are grouped in a function view in figure
12. The designations function, process and activity are used synonymously.
Due to the fact that functions support goals, yet are controlled by them as well, goals are
also allocated to function views - because of the close linkage. In application software,
computer-aided processing rules of a function are defined. Thus, application software is
closely aligned with functions, and is also allocated to function views.

ARIS Architecture of Integrated Information Systems

Organization view
The class of organization views creates the hierarchical organization structure, also
known as the organization view. Organization views are created in order to group
responsible entities or devices executing the same work object. This is why the
responsible entities human output, responsible devices, financial resources and
computer hardware are allocated to the organization view.
Data view
Data views comprise the data processing environment as well as the messages
triggering functions or being triggered by functions. Preliminary details on the function
of information systems as data media can also be allocated to the data names.
Information services objects are also implicitly captured in data views. However, they
are primarily defined in the output view. Fehler! Verweisquelle konnte nicht
gefunden werden.c illustrates data view objects.
Output / Service view
Output views contain all physical and non-physical input and output, including funds
flows (see Fehler! Verweisquelle konnte nicht gefunden werden.d).
Control / Process view
The views are where the respective classes with their view-internal relationships are
modeled. Relationships among the views as well as the entire business process are
documented in the control or process views, creating a framework for the systematic
inspection of all bilateral relationships of the views and the complete process
description.
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...

You might also like