aris.user guide it architect s en

1

ARIS IT Architect

User Guide

March 2010

ARIS IT Architect - Contents

I

Contents

1 Introduction ........................................................................................................ 1

2 Enterprise Architecture Management (EAM) ............................................................. 2 2.1 EAM as part of IT management .................................................................... 3 2.2 Roles in Enterprise Architecture Management ................................................. 4

3 Architecture levels in IT architecture management ................................................... 5

4 Business processes .............................................................................................. 7 4.1 Roles ........................................................................................................ 7 4.2 Description ................................................................................................ 7 4.3 Method details ......................................................................................... 11

5 Application architecture ...................................................................................... 12 5.1 IT system architecture .............................................................................. 12

5.1.1 Roles ............................................................................................ 12 5.1.2 Description .................................................................................... 12 5.1.3 Method details ................................................................................ 21

5.2 IT technology architecture ......................................................................... 23 5.2.1 Roles ............................................................................................ 23 5.2.2 Description .................................................................................... 23 5.2.3 Method details ................................................................................ 31

6 Process support map .......................................................................................... 34 6.1 Preliminary method comments on the process support map ........................... 34 6.2 IT landscape method system ..................................................................... 35 6.3 Roles ...................................................................................................... 38 6.4 Description .............................................................................................. 38 6.5 IT landscape macros ................................................................................. 40

6.5.1 IT landscape administration – Generate matrix ................................... 41 6.5.2 IT landscape administration – Complete matrix ................................... 44 6.5.3 IT landscape administration – Copy content ........................................ 45 6.5.4 IT landscape administration – Adjust names ....................................... 46 6.5.5 Update process support map ............................................................ 47 6.5.6 Edit process support unit ................................................................. 48 6.5.7 Delete process support columns ........................................................ 50 6.5.8 Remove IT system .......................................................................... 51 6.5.9 Add IT system ................................................................................ 52 6.5.10 Hide IT systems from a process support unit ...................................... 53 6.5.11 Change IT landscape view ................................................................ 55 6.5.12 Process support reports ................................................................... 57

6.6 Working in process support maps ............................................................... 58 6.6.1 General IT landscape planning .......................................................... 58 6.6.2 IT landscape planning using quadrants .............................................. 62

6.7 Method details ......................................................................................... 64 6.7.1 Process support map model type ...................................................... 65 6.7.2 Connections between PSU and cell objects in a map ............................ 66 6.7.3 Connections between PSU and column/row header objects in a map ...... 66 6.7.4 Connections between column/row header objects and cell objects in a map

.................................................................................................... 67 6.7.5 Process support map model attributes ............................................... 67 6.7.6 Process support unit (PSU) attributes ................................................ 68 6.7.7 Connection attributes ...................................................................... 69

ARIS IT Architect - Contents

II

7 Organization architecture .................................................................................... 70 7.1 Roles ...................................................................................................... 70 7.2 Description .............................................................................................. 70 7.3 Method details ......................................................................................... 72

8 Information architecture ..................................................................................... 73 8.1 Roles ...................................................................................................... 73 8.2 Description .............................................................................................. 73 8.3 Method details ......................................................................................... 74

9 System functions, requirements, project and portfolio management ......................... 75 9.1 Roles ...................................................................................................... 75 9.2 Description .............................................................................................. 75 9.3 Method details ......................................................................................... 80

10 Reports ............................................................................................................ 84 10.1 Redundant applications (visualization of redundancies) .................................. 84 10.2 System evaluations .................................................................................. 86 10.3 System list .............................................................................................. 87 10.4 Lifecycle management (report) .................................................................. 89 10.5 Lifecycle management (macro) .................................................................. 91 10.6 Display data flows .................................................................................... 92 10.7 System fact sheet .................................................................................... 94 10.8 System consolidation ............................................................................... 100 10.9 System portfolio analysis .......................................................................... 101

11 Further examples for the analysis of data ............................................................. 105 11.1 Use case: Which systems use a particular technology? ................................. 105 11.2 Use case: Which processes are affected by a specific technology? .................. 106

12 Method details (attribute table) .......................................................................... 107

13 Glossary .......................................................................................................... 110

ARIS IT Architect - Figures

III

Figures

Figure 1: ARIS House ......................................................................................................... 1

Figure 2: Illustration of the enterprise architecture level model ......................................... 2

Figure 3 : ARIS IT Architect - Relevant IT processes .......................................................... 3

Figure 4: Architecture levels in IT architecture management ............................................. 5

Figure 5: Comparison of IT system and IT components architecture .................................. 6

Figure 6: Navigation and assignment ................................................................................. 8

Figure 7: Representation of an EPC section ........................................................................ 9

Figure 8: Capabilities as a link between processes and IT systems .................................... 10

Figure 9: IT systems (domain view) .................................................................................. 13

Figure 10: Description of the 'PRO-ORDER' IT system ....................................................... 14

Figure 11: Assignment of attributes to connections ........................................................... 15

Figure 12: Display and specification of attributes in the Properties window ...................... 16

Figure 13: Interface modeling ........................................................................................... 17

Figure 14: Linking of system functions (capabilities) to an IT system ............................... 18

Figure 15: System functions library ................................................................................... 19

Figure 16: Representation of relationships using properties .............................................. 20

Figure 17: Architecture set ............................................................................................... 24

Figure 18: Architecture element detail model .................................................................... 25

Figure 19: States in the standardization cycle ................................................................... 26

Figure 20: Documentation of the standardization phases .................................................. 26

Figure 21: Versioning of an IT component ......................................................................... 27

Figure 22: Lifecycle maintenance of IT components .......................................................... 27

Figure 23: Reference architecture illustration ................................................................... 29

Figure 24: IT landscape method system ............................................................................ 35

Figure 25: IT landscape method system – Connection attributes ....................................... 36

Figure 26: IT landscape views and color representation .................................................... 37

Figure 27: Process support map ........................................................................................ 39

Figure 28: IT landscape administration macro – Generate matrix 1 ................................... 42

Figure 29: IT landscape administration macro – Generate matrix 2 ................................... 43

Figure 30: Select and edit multiple process support units 1 ............................................... 48



Figure 33: Reduced view of process support map .............................................................. 54

Figure 34: Define IT landscape view ................................................................................ 56

Figure 35: Edit process support unit macro 1 .................................................................... 58


ARIS IT Architect - Figures

IV


Figure 38: Quadrant view of IT system portfolio ............................................................... 63

Figure 39: System portfolio analysis ................................................................................. 63

Figure 40: New object types. Previous version left, new object types right. ...................... 64

Figure 41: Specify the order using modeling conventions .................................................. 71

Figure 42: Example of an information architecture ............................................................ 73

Figure 43: Relationship between function, IT system, and system function ....................... 75

Figure 44: Technical requirement of IT ............................................................................. 76

Figure 45: Example of a requirements tree........................................................................ 76

Figure 46: Example of a project description ...................................................................... 77

Figure 47: Connection between process support unit and task .......................................... 77

Figure 48: Example of a program description .................................................................... 78

Figure 49: Example of a project schedule .......................................................................... 79

Figure 50: Sample output of the System evaluation report ................................................ 86

Figure 51: Wizard for System list report ............................................................................ 87

Figure 52: Example output for System list report .............................................................. 88

Figure 53: Wizard for Lifecycle management report .......................................................... 90

Figure 54: Sample output for Lifecycle management report .............................................. 90

Figure 55: Sample output for lifecycle management of IT components .............................. 90

Figure 56: IT components (operating systems) - Color highlighting by macro ................... 91

Figure 57: Connection assignment for specifying IT system interfaces .............................. 92

Figure 58: Output of the Display data flows macro ............................................................ 93

Figure 59: Output of the Display data flows report ............................................................ 93

Figure 60: Example of a system fact sheet ........................................................................ 99

Figure 61: Quadrant view of IT system portfolio ............................................................. 101

Figure 62: System portfolio analysis ............................................................................... 102

Figure 63: Quadrant attribute of the application system class ......................................... 103

Figure 64: Configuration file for the system portfolio quadrants ...................................... 103

Figure 65: Configuration of the Quadrant attribute ......................................................... 104

Figure 66: Configuration of colors ................................................................................... 104

Figure 67: Relationships of the Oracle IT component ...................................................... 105

Figure 68: Result of a search query ................................................................................. 106

ARIS IT Architect - Tables

V

Tables

Table 1: Conventions for business processes - Models and objects .................................... 11

Table 2: Conventions for business processes – Relationships ............................................ 11

Table 3: IT system architecture conventions – Models and objects .................................... 21

Table 4: IT system architecture relationship conventions .................................................. 22

Table 5: IT technology architecture conventions – Models and objects .............................. 31

Table 6: IT technology architecture conventions – Relationships ...................................... 33

Table 7: Object types in Process support map model type ................................................. 65

Table 8: Process support map conventions – Connections I ............................................... 66

Table 9: Process support map conventions – Connections II ............................................. 66

Table 10: Process support map conventions – Connections III .......................................... 67

Table 11: Process support map conventions – Process support map model attributes ....... 67

Table 12: Process support map conventions – PSU attributes ............................................ 68

Table 13: Process support map conventions – Connection attributes ................................. 69

Table 14: Conventions for organization architecture ......................................................... 72

Table 15: Conventions for information architecture - Models and objects .......................... 74

Table 16: Information architecture conventions – Relationships ....................................... 74

Table 17: Projects, capabilities, and requirements conventions – Models and objects ....... 81

Table 18: Projects, capabilities, and requirements conventions – Relationships ................ 83

Table 19: Description of the Redundant applications report .............................................. 84

Table 20: Sample result of the 'Redundant applications' report ......................................... 85

Table 21: Description of the System evaluation report ...................................................... 86

Table 22: Description of the System list report .................................................................. 87

Table 23: Description of the Lifecycle management report ................................................ 89

Table 24: Description of the Lifecycle management macro ................................................ 91

Table 25: Description of the System fact sheet report ....................................................... 94

Table 26: Attribute table ................................................................................................. 109

ARIS IT Architect - Introduction

1

1 Introduction

Complex structures combined with redundant and insufficiently integrated IT systems are the core

problem of evolved IT landscapes. Another consequence of using monolithic systems is the lack of flex-

ibility to adjust applications to ever-faster changing business requirements. Intransparency leads to

high costs in relation to company-wide IT planning. The scope for action becomes increasingly smaller,

as available budgets are already eaten up through maintenance and servicing.

The only way out of this dilemma is to implement long-term-oriented enterprise architecture manage-

ment, which must succeed in gradually harmonizing the IT, making it flexible and aligning it with the

business process requirements.

ARIS IT Architect, one of the core products of the ARIS Enterprise Architecture Solution, supports all

necessary strategic planning processes, starting from the documentation of the as-is architecture and

its analysis through to design and publication of to-be architectures.

In this way, it is possible to set up company-wide application and technology landscapes, as well as

specify, document, and roll out IT standards. Existing system landscapes can be described and ana-

lyzed, from the strategic overview through to the detailed representation of the infrastructure.

Figure 1: ARIS House

To enable efficient and effective IT architecture management and to achieve objectives such as the

standardization of the IT landscape, the elements of the architecture framework are mapped in a cen-

tral repository, as are the relevant relationships. The ARIS Method for IT architectures is based on an

object-oriented approach for the re-use of architecture artifacts, which applies across all views. The

interaction of business processes and IT architectures can be documented and managed based on an

integrated approach. Using ARIS IT Inventory, the browser-based tool for decentralized maintenance of

IT system information, you can ensure that your IT information is always up-to-date. Role-based

access allows all enterprise areas to access the published information. IDS Scheer Customized Solu-

tions will be pleased to help you in creating ARIS IT Inventory.

ARIS IT Architect - Enterprise Architecture Management (EAM)

2

2 Enterprise Architecture Management (EAM)

Within an enterprise architecture, four architecture views are generally differentiated, which are shown

in Figure 2: Illustration of the enterprise architecture level model:

A business architecture framework defines business goals, strategies, and KPIs and describes

organizations and business processes.

The application architecture describes the services and application systems that support the

business processes, including the technologies used.

An information architecture describes the business objects and data that are processed and ex-

changed by process participants and IT systems.

The infrastructure architecture forms the lowest level. It is used to describe the physical land-

scape, the hardware, and the networks that are used for operation of the application systems.

Figure 2: Illustration of the enterprise architecture level model

Enterprise Architecture Management is the process-oriented description, analysis, and development of

corporate IT using the views specified above.


3

2.1 EAM as part of IT management

IT processes are traditionally divided into three phases: planning, implementation, and operation (plan,

build, and run). The individual phases are shown graphically in the following model. The relevant

processes whose most important relationships are visualized reside within the phases. ARIS IT Archi-

tect and this user guide focus on processes and the following topics:

IT architecture management

IT landscape planning

IT portfolio management

Reference to business process management (business process analysis and design)

Reference to program and project management (IT project management)

Reference to requirements management

In addition to the descriptions and examples for the individual theme blocks, method information re-

garding the model, connection, and object types used and their IT-specific attributes may also be found

in this user guide. These conventions are included as tables in the relevant chapters.

Figure 3 : ARIS IT Architect - Relevant IT processes


4

2.2 Roles in Enterprise Architecture Management

In Enterprise Architecture Management, there are different participant roles. The most important roles

and their definition:

Application system manager: Lifecycle manager from the relevant department. Responsible for

the planning, development, and further development of the application over its entire lifecycle. The

application system manager is the contact person for application developers and application support

staff, and supports them.

Architecture manager: Responsible for further strategic development of the architecture frame-

work, for merging standards and system registers, and for specifying the system design.

IT architect: Responsible for further operational development of the architecture framework based

on the strategic context provided, for maintenance of the architecture set, and for further develop-

ment and approval of IT standards.

IT landscape planner: The IT landscape planner records and maintains the as-is process support

map for systems in relation to the business processes supported and organizational structure. Other

tasks of this role include development of the to-be process support map based on the current situa-

tion and strategic requirements.

Process manager: This role represents staff in the company who work within Business Process

Management (BPM). They may be process managers in the individual departments, process mod-

elers or staff in process management competence centers of central IT.

ARIS IT Architect - Architecture levels in IT architecture management

5

3 Architecture levels in IT architecture management

The architectures described in the following chapters:

business architecture

application architecture

information architecture

technical architecture

are divided into several architecture levels. The interrelationship between the architecture levels of the

business architecture, application architecture, and technical architecture is shown in more detail be-

low.

Figure 4: Architecture levels in IT architecture management

The application architecture consists of an IT system architecture and an IT components architecture.

The technical architecture forms the lowest level of the IT system and IT components architecture.

The process architecture is described in the first three levels through value-added chains. One or more

process support maps are assigned to each of these levels. The process support maps contain IT sys-

tems and enterprise areas along with their locations in addition to the processes.

ARIS IT Architect - Architecture levels in IT architecture management

6

Figure 5: Comparison of IT system and IT components architecture

The architecture levels of the IT system architecture are represented on the top level by system do-

mains, to which the individual IT systems can be assigned. The second level covers IT system man-

agement, while the third level is used to describe the IT systems in detail. Level four represents the

transition from the logical to the physical level, that is, the transition from the type level to the in-

stance level. The infrastructure is described in level five.

In the IT components architecture, all technologies or IT components used in the company are ma-

naged. The IT components of the architecture set are available for describing the IT system architec-

ture on the different levels. In analogous form to the IT systems, we find on the top level a division of

IT components by logical viewpoints, followed by description level, instance level and infrastructure

level.

ARIS IT Architect - Business processes

7

4 Business processes

4.1 Roles

Process managers

IT landscape planner

4.2 Description

The main task of IT is the support and optimization of business processes. The IT strategy should

therefore be derived from the corporate strategy, as the reasons for heterogeneous IT landscapes in

various enterprise areas often lie in evolved structures and process flows that result from mergers and

acquisitions of companies. If harmonization of the processes and systems is absent, not only are ex-

pected synergy effects lost, but additional costs are also incurred in the long term due to redundant

development, lack of standardization, and lack of interoperability.

For a detailed analysis, it is vital to know how the processes run in the company units and why they

differ. The key to harmonizing IT systems ultimately lies in harmonization of the process landscape.

An integrated approach must therefore be used to record, analyze, and optimize information about IT

systems and IT technologies with information about supported business processes. The relevant busi-

ness processes are recorded with ARIS Business Architect by business process management staff, for

example.

The core business processes of a company (level 0) are represented in the form of value-added chains

in a value-added chain diagram. The individual core business processes, in turn, can have value-added

chain diagrams assigned to them which specify them in more detail (levels 0-3). To be able to plan and

implement a later harmonization of supporting IT systems across various enterprise areas, a company-

wide harmonization of the processes must already take place on this level as well.


8

Figure 6: Navigation and assignment

In general, process chains (such as EPC, EPC as row display, Office process) are used from level 4 and

lower for a more detailed and area-specific examination of the process flows. More information on this

is available in the ARIS Method manual.


9

Figure 7: Representation of an EPC section

Within the scope of harmonization, the processes (value-added chains) on level 3 are described addi-

tionally by function allocation diagrams, which are assigned to the objects. They contain further infor-

mation that is important for IT architecture management:

Objects of the Cluster/Data model type are used to describe the business objects that are processed

in the processes and exchanged between systems. They are provided as a master data hierarchy to

process management and IT architecture management.


10

Figure 8: Capabilities as a link between processes and IT systems

System functions (capabilities) are the link between business processes and IT systems (Figure 8

). Using these objects, a system is described in respect of its supported features. System functions

result from technical requirements which are based on business processes. Therefore, the IT system

functions required by a business function are documented (Figure 15

). The system functions can be arranged in hierarchies and dependencies can be documented – their

structure is based on the structure of the business objects (see Information architecture chapter). They

can be grouped and managed in libraries (Service architecture diagram model type) and structured

according to their use (Figure 15: System functions library

). More details on this topic are available in the ARIS Method manual (IT City Planning chapter).

This master data is also used by both process management and IT architecture management and

serves as an analysis tool for subsequent system consolidations and replacements (see chapter Table

16: Information architecture conventions – Relationships

).


11

4.3 Method details

The method conventions (model, object, and connection types) used in the above explanations are

listed below.

Model type Object type

Value-added chain diagram

Value-added chain

Function allocation diagram

Function

Capability

Organizational unit

Position

Person

Cluster

Application system type

Table 1: Conventions for business processes - Models and objects

Model type Source object Target object Connection type


Value-added chain Value-added chain is process-oriented

superior

Value-added chain Value-added chain is predecessor of

Function allocation diagram

Capability Function supports

Organizational unit Function is technically re-sponsible for

Position Function is technically re-sponsible for

Person Function is technically re-sponsible for

Cluster Function is input for/has output of


Function supports

Table 2: Conventions for business processes – Relationships

ARIS IT Architect - Application architecture

12

5 Application architecture

5.1 IT system architecture

5.1.1 Roles

Application system manager

IT architect

Architecture manager

5.1.2 Description

The entry point for the IT system architecture is the application map or the application portfolio. Here,

all IT systems in a company are represented in a model of the Application system type diagram

type and, if necessary, grouped into application domains. The IT systems are described in more detail

in assigned models (level 3-n of architecture pyramid).

The division into domains is made possible by the Application system class object type, to which the

corresponding IT systems or IT subsystems are assigned. The assignment of IT systems to individual

domains and the division of an application into several subsystems can be specified in more detail

across several levels. Architecture projects often begin with recording and documentation of the cur-

rent application map.


13

Figure 9: IT systems (domain view)

The application system manager is responsible for the currency of the information about an IT system.

The type level (also called the 'logical view') contains information about the underlying operating sys-

tem, the programming language, the database used, the hardware type, the organizational unit re-

sponsible, and about the application system manager himself, for example. The information is

represented in an access diagram assigned to the system (Figure 10

).

The architecture set (see chapter IT technology architecture) serves as a library, from which the sys-

tem manager takes all IT components in order to describe a system. This ensures that only IT compo-

nents recorded and evaluated by the IT architect role are used and thus guarantees a high level of

standardization.


14

Figure 10: Description of the 'PRO-ORDER' IT system

People and organizational units responsible are taken from the models in the Organization view and

can be linked to the IT system (application system type) by a corresponding relationship. By assigning

attributes to the relationship (Support type attribute), the application manager obtains a precise spe-

cification of the respective role of the person or organizational unit.


15

Figure 11: Assignment of attributes to connections

Other characteristic features of an IT system can be specified by assigning corresponding attributes to

the system itself.


16

Figure 12: Display and specification of attributes in the Properties window

Heterogeneous IT landscapes are characterized by a multitude of interfaces between IT systems. Inter-

faces are mapped at two levels of abstraction. The first level always represents an IT system with all

other IT systems that are connected by interfaces. The program flow chart is used for this purpose. The

transmits data to relationship is used to show that an interface exists between two systems.


17

Figure 13: Interface modeling

The interface can be specified in detail in a model of the Program flow chart type assigned to the

transmits data to connection. In addition to the data flows via the interface, the relevant transmis-

sion protocol is taken into account. A new relationship, including another assigned model, is created for

each protocol and direction.

As already explained in the business architecture, system functions (capabilities) form the bridge be-

tween the IT system landscape and the business processes. Each system is therefore specified in re-

spect of the supported system functions. This is done either in the above-mentioned access diagram

(Figure 10

) along with other relevant system information, or in an application system type diagram provided spe-

cially for this purpose (Figure 14: Linking of system functions (capabilities) to an IT system

).


18

Figure 14: Linking of system functions (capabilities) to an IT system

The system functions are ideally taken from a library. The service architecture diagram can be used to

map this library.


19

Figure 15: System functions library

If all systems are described using system functions from this library, a wide range of analysis options

are available to the architecture manager. For example, the architecture manager can determine IT

system redundancies or identify system requirements. This can either be done by simply using the Re-

lationships properties tab or by running the corresponding standard report.

In Figure 16

, the Relationships tab shows that the Price calculation system function is provided by three IT sys-

tems, namely A-PLAN, HLPN-1, and PRO-ORDER).

To document the required system support from a business process perspective, system functions can

also be derived from processes. They are therefore an essential component of requirements manage-

ment (see chapter Table 16: Information architecture conventions – Relationships

).


20

Figure 16: Representation of relationships using properties


21

5.1.3 Method details


listed below.


Access diagram


Hardware component type

Document

Technical term

Organizational unit

Group

Person

Cluster

Location

Architecture element

Capability

Application system type diagram


Application system class

Capability

Program flow chart


Cluster

Protocol

Service architecture diagram

Zone

District

Capability

Table 3: IT system architecture conventions – Models and objects


22


Access diagram

Application system type Application system type uses (IT component)

Application system type Architecture element is relevant for

Application system type Architecture element is not relevant for

Application system type Hardware component type

can run on

Application system type Document creates output to

Application system type Organizational unit is responsible for (attribute as-signed(!)), e.g. Support type attribute System responsibility

Application system type Person is responsible for (attribute as-signed(!)), e.g. Support type attribute System responsibility

Application system type Cluster uses

Application system type Location can be located at

Application system type Capability supports


Application system class Application system type belongs to class


Program flow chart

Application system type Application system type transmits data to

Application system type Cluster has output of

Cluster Application system type is input for

Application system type Protocol uses

Service architecture diagram

Zone District encompasses

District Capability encompasses

Table 4: IT system architecture relationship conventions


23

5.2 IT technology architecture

5.2.1 Roles


IT architect

5.2.2 Description

The IT technology architecture is represented by the so-called architecture set. The architecture set

represents the entry point for the company-wide technology portfolio, which consists of IT components

and is structured by the following elements:

Reference architectures

Architecture building blocks

Architecture elements

The architecture set is set up in layers, each of which covers a strategically relevant IT topic. 1-n archi-

tecture elements are assigned to each layer, which provides thematic refining. The individual architec-

ture elements are detailed in an IT architecture matrix describing the assigned IT components. Using

standard software products to a high degree and only a minimum proportion of individual development

are important harmonization criteria.

To support the concept of IT component standardization, ready-to-use building blocks are provided as

operationally running subcomponents in addition to the architecture elements. They are subordinated

to the thematically relevant architecture elements.

In order to describe to-be architectures of application platforms, the ready-to-use building blocks and

individual IT components are combined into a reference architecture, in which they are assigned to the

various layers and levels (tiers). An architecture set can consist of the following layers, for example:

Business process-specific components & services: IT components that already include busi-

ness logic, such as ERP systems, are mapped in this layer.

Standard technology & basic solutions: This layer generally covers standard software products

(or custom developments) that provide generic functionality used in different kinds of business

processes, such as office products, e-mail systems, DMS, CMS, DBMS, etc..

Infrastructure: Operating systems, hardware types, network components, and other infrastruc-

ture components may be found in this layer.

Development: This layer includes programming languages, development environments, procedural

models, etc.


24

Figure 17: Architecture set

For architecture set modeling, the IT architecture mapping model type is used on the top level, with

the associated architecture elements assigned directly to the individual layers. For the detailed repre-

sentation of an individual architecture element, a model of the IT architecture matrix type is as-

signed.

Architecture elements consist of 1-n IT components and/or architecture building blocks and cover spe-

cific topics. In this context, it is important that IT components differ from IT systems in the sense that

IT components support an IT system, while an IT system in turn supports a (business) process. This

can be clarified by using the System type attribute. For example, for an application system type used

as an IT component, the attribute has the value Component. This must be specified manually. In the

course of architecture management, the libraries of the architecture elements are set up, in which the

IT components are kept. They provide the basis for the detailed description of the IT systems (see

chapter IT technology architecture). Use of occurrence copies in access diagrams (Figure 10

) raises the degree of standardization of the IT architecture since only technologies specified in the IT

libraries can be used to describe new IT systems.


25

Figure 18: Architecture element detail model

Technologies can be structured by technology status. The IT architect defines the portfolio of IT com-

ponents and specifies the standardization status of the relevant IT component. This ensures that, in the

long term, only IT standards (to be implemented or active) are used as possible.

The type and naming of the IT component libraries are governed by the architecture elements defined

in the architecture set. For every architecture element that is created in the architecture set, an as-

signed model of the IT architecture matrix type is created, which describes the architecture element

in more detail.

For example, in Figure 18

, management of the database systems is represented. Each IT component listed has information on

manufacturer and version, links to manuals, and much more, and it can be reused in various views.

The IT components have a colored icon indicating the status of the standardization. The coloring de-

pends on the value of the Standardization status attribute and the associated time intervals, if speci-

fied. This can be evaluated in text form and graphically by using a report or the Lifecycle manage-

ment.


26

The following states are differentiated in the standardization cycle of IT components:

Figure 19: States in the standardization cycle

To be able to assign time intervals to the states, the duration of the individual phases in the standardi-

zation cycle can be documented using attributes of the IT component.

Figure 20: Documentation of the standardization phases

Individual versions of the IT component can be managed in an application system type diagram as-

signed to the IT component, such as major, minor, and bugfix releases.


27

Figure 21: Versioning of an IT component

The objective is not only to manage, but also to standardize the IT components. To achieve this objec-

tive, the IT components must be examined, e.g., in respect of their penetration (impact analysis). For

this purpose, the Relationships tab provides initial information, such as all IT systems that depend on

the IT component. Thus, navigation across the various levels of the corporate landscape delivers all

information required for carrying out a standardization of the elements. In the following figure, IBM

DL1 is set to the status To be phased out as an example.

Figure 22: Lifecycle maintenance of IT components

Oracle

Oracle 9 Oracle 10gOracle 8i

Oracle 8.1.7 Oracle 9.2.5 Oracle 10.1


28

Besides IT components of the Software or Hardware type, other IT components, such as develop-

ment processes (RUP, V model, etc.) or standardized documents (e.g. security policies, project tem-

plates), can be managed.

The objective of standardization is the reduction of maintenance and servicing costs. By reducing the

variety of technologies used, costs in relation to staff training or the procurement of hardware and

software can also be saved.


29

Reference architectures

The objective of reference architectures is the re-use of concepts and software components. They pro-

vide specifications in order to reduce the heterogeneity of the IT system landscape. Software suppliers

must fulfill these specifications in respect of design principles, infrastructures, and technologies.

Figure 23: Reference architecture illustration

In this way, reference architectures help harmonize the IT system landscape and thus reduce operating

costs.

A reference architecture is a set of architecture building blocks and IT components. Each reference ar-

chitecture is mapped in a model of the IT architecture matrix type. The various objects, such as IT

components, IT systems, etc., are each assigned to an architecture layer and an architecture tier. The

horizontal layers correspond to those in the architecture set.


30

Architecture building block

Architecture building blocks consist of 1-n IT components (possibly of different architecture elements)

and have the following properties:

Architecture building blocks provide standardized, encapsulated services, which are supported by a

fixed set of IT components.

Architecture building blocks correspond to IT components in their use, and are therefore assigned

thematically to architecture elements.

Models of the IT architecture matrix type can be used to assign architecture building blocks in

order to specify the structure in more detail.

The provision of services takes place via a standardized interface.

An example of an architecture building block is Single Sign-On (SSO), a solution that typically con-

sists of several IT components and can be used repeatedly in modular form.

Architecture building blocks are subdivided thematically into:

Architecture building block (SW): An architecture building block (SW) represents a set of IT

components (also of different types) that corresponds to a software component in its use.

Architecture building block (HW): An architecture building block (HW) represents a set of IT

components that corresponds to a hardware component in its use.

Architecture building block (processes & guidelines): This type of architecture building block

corresponds in its use to those of processes and guidelines.

Architecture building blocks are thematically subordinate to architecture elements. The detailed compo-

sition of an architecture building block is modeled using the IT architecture matrix model type and,

comparable to the reference architectures, comprises solely layers, levels (tiers) and their IT compo-

nents, but no architecture elements.


31

5.2.3 Method details

The model, object, and connection types used in the above explanations are listed below. The IT-

specific attribute types are listed in a separate table in chapter Figure 68: Result of a

.


IT architecture mapping

Architecture layer


IT architecture matrix


Architecture layer

Tier

Application system class


Hardware component class

Hardware component type

Technical term

Product/Service

Protocol

Function

Software service type

Document

Table 5: IT technology architecture conventions – Models and objects


32


IT architecture map-

ping

Architecture layer Architecture element encompasses/belongs

to

IT architecture matrix

Architecture element Application system class encompasses/belongs

to

Architecture element Application system type encompasses/belongs

to

Architecture element Hardware component class encompasses/belongs

to

Architecture element Hardware component type encompasses/belongs

to

Architecture element Technical term encompasses/belongs

to

Architecture element Product/Service encompasses/belongs

to

Architecture element Protocol encompasses/belongs

to

Architecture element Function encompasses/belongs

to

Architecture element Software service type encompasses/belongs

to

Architecture element Document encompasses/belongs

to

Tier Application system class encompasses/belongs

to

Tier Application system type encompasses/belongs

to

Tier Hardware component class encompasses/belongs

to

Tier Hardware component type encompasses/belongs

to

Tier Technical term encompasses/belongs


33


to

Tier Product/Service encompasses/belongs

to

Tier Protocol encompasses/belongs

to

Tier Function encompasses/belongs

to

Tier Software service type encompasses/belongs

to

Tier Document encompasses/belongs

to

Architecture layer Application system type encompasses/belongs

to

Table 6: IT technology architecture conventions – Relationships

ARIS IT Architect - Process support map

34

6 Process support map 6.1 Preliminary method comments on the process support map

If you select the convenient method using process support units, maps are automatically created using

the IT landscape administration – Generate matrix macro.

The model is edited exclusively through a wizard, using the macros described below. Connections are

created in the background, and you select attributes in the individual dialog boxes. This means that the

values are automatically specified and updated. The lifecycle of each IT system is represented by traffic

light colors, depending on the IT landscape view. The maps are then in Macro control operation

mode. You can then use the process support map to ensure intelligent IT landscape planning. The re-

quired method conventions are automatically complied with. Therefore, all elements are protected

against manual editing. You can only read attributes for orientation. Models can also only be opened in

read-only mode. Except for editing by the corresponding macros, only the following functions are

enabled, which are controlled by the macros in the background:

Add, delete, or move columns and rows in a process support map

Add new objects (drag and drop or copy and paste)

Move objects

Delete objects

To guarantee optimum performance, make sure that the memory setting for the ARIS clients is set to

512 MB. Please refer to the Installation and Administration Guide for more information.

If a process support map is created using the standard New/Model function from the pop-up menu, it

is a model like any other. The type of use does not differ from the other ARIS model types. You can

model as you wish, but you cannot place any process support units and you must specify all attributes

yourself. The map is then in Default operation mode. Once Macro control or Default operation mode

has been specified, it cannot be reversed. You must therefore decide on the operation mode for a

process support map before you create the model.


35

6.2 IT landscape method system

The IT landscape plan is set up based on the Process support map model type. Each map consists of

column header and row header objects. The central construct – the process support unit PSU – is uni-

quely defined by these objects in the cell at the relevant intersection. The assignments are also in-

cluded in these cells.

Figure 24

illustrates the structure of the process support map on the left-hand side. The objects are highlighted

in color and thus do not correspond to their representation in the actual program interface. In the ex-

ample shown, the process support map (overall IT landscape view) is made up of column header ob-

jects of the Function type, row header objects of the Organizational unit and Location type, and as-

signment objects of the Application system type. The PSU is indicated by the red square in the map. In

this example, it is defined by the Create contract function and the Frankfurt location. The relationships

are highlighted in green in the column and row titles. The A-PLAN assignment was entered using the

Add IT system macro.

The right-hand section of the figure shows the interrelationships and relationships for the PSU sche-

matically.

Figure 24: IT landscape method system


36

The lifecycle of an IT system, A-PLAN in this case, related to an organizational unit or a location,

Frankfurt in this case, and a process, Create contract in this case, is documented at the belongs to

process support unit connection between A-PLAN (application system type) and the PSU (object of

Process support unit type).

Figure 25: IT landscape method system – Connection attributes

If the database is reorganized, all connections between process support units and IT systems, and to

row and column header objects, are protected and are not deleted, even if they only exist at the defini-

tion level.

The process support type of a process support unit determines whether and, if so, what support is pro-

vided for a combination of row and column header objects.


37

The status of process support is a property of the relevant assignment, which is described in the

attributes of the connection and is evaluated during shading in the various IT landscape views. The

status is displayed for each assignment at the symbol occurrence, depending on the IT landscape view.

Further information is available in the individual chapters relating to the IT landscape macro, e.g.,

Change IT landscape view or Lifecycle management.

An IT system is classed as deleted from the process support map if the Status of process support

attribute at the connection from the system to the process support unit is not specified, i.e., undefined.

The occurrences of these IT systems are deleted when the maps are updated. This is completely con-

trolled by the macros.

During a reorganization of the database, these connections are deleted if they only have the status

logically deleted, and if occurrences of IT systems still exist at this time, they will also be deleted.

Figure 26: IT landscape views and color representation


38

6.3 Roles


IT landscape administrator

Enterprise architect

6.4 Description

An IT landscape plan documents current and future IT systems of a company to support its business

processes at various locations or in various organizational units. Based on these assignments, an IT

landscape planner can, for example, analyze how removal and implementation of particular IT systems

effect business and can derive measures to facilitate change in the IT landscape.

An IT landscape plan is always required because it provides a central guideline for implementing the IT

strategy in line with business. It ensures that the entire IT landscape is developed in a controlled man-

ner.

High-quality assessment of the current organizational structure, business process model, and applica-

tion system landscape of a company and of the links between them form the basis of the IT landscape

plan and allow the target (reference process support map) to be derived from the current situation.

Comparisons between the as-is and to-be process support maps enable the requirements, measures,

and tasks needed to achieve the reference process support map to be derived. Derived tasks and

measures can then be structured, evaluated, and implemented in projects (IT project and portfolio

management).

The objective is to establish an integrated IT governance process that drives the standardization and

harmonization of the IT landscape and simultaneously ensures cost reductions in planning, implemen-

tation, and operation. ARIS IT Architect provides a variety of functions that support the work of IT

landscape planners and are described in more detail below.


39

Figure 27: Process support map


40

6.5 IT landscape macros

To make it as convenient as possible for users to create, maintain, and manage process support maps,

process support maps can be generated in ARIS IT Architect using macros as described. The map is

then in Macro control operation mode. Attributes are protected against manual editing, which is why

the models can then be edited exclusively in this mode.

The IT landscape macros available in ARIS IT Architect support users in complying with the method

conventions described, which are essential for using the macros. Basically, we differentiate between

macros that can be run manually and those that respond to specific events. In addition, macros that

are used for administrative purposes have special names. These are to be used exclusively by IT land-

scape administrators and require an in-depth knowledge of the method and functions.

The basic principle of all macros is “all or nothing”. The operation can either be performed successfully

or there is a rollback. For example, if a map has a state that is inconsistent with the method, the up-

date mechanism aborts with an error message.

Warning

The macros guarantee that the method conventions are complied with within the model to be edited.

However, it is possible to manipulate the objects and connections used in the process support map at

the definition level, e.g., in the Explorer module. If such manipulation causes inconsistencies in the IT

landscape method, the macros are aborted with a corresponding error message. For example, this is

the case if there is more than one process support unit per cell. In certain cases, repairs are carried out

automatically. These cases are documented in the macro descriptions. In all other cases, the method

conventions must be manually restored before editing using the macros can be continued, e.g., by de-

leting a duplicated process support unit.

Consolidation of the objects involved in the process support map, a merge, or an XML import, can also

undermine the method conventions required to process the macro. The effects of a consolidation,

merge or XML import on the process support map should therefore be checked in detail before using

the corresponding function. An unfavorable choice of objects, such as consolidating two functions that

are used in a process support map, can necessitate significant manual rework to restore the method

conventions of the process support map.

The individual macros and their use are described below.


41

6.5.1 IT landscape administration – Generate matrix

Description Type of

execution

Event Visible to

users

This macro generates a new process support map.

This is either done interactively after selecting column

and/or row header objects in an existing model to

create a part of the model, or using dialogs after se-

lecting models or functions in the Explorer module.

After model generation is complete, existing process

support information of the new model is automatically

loaded and displayed.

Manual / Yes

Special features

The new matrix generated is completed based on the following algorithm: if a process support unit al-

ready exists for a cell, an occurrence copy of it is inserted. If a process support unit exists for which the

user does not have read privileges, a message is output and the corresponding cell remains blank. If

no process support unit exists yet for a blank cell, a new process support unit is created in the group of

the new process support map.

To create the process support map, the relevant section (e.g., processes/organizational units) must

first be defined. The macro can be started for selected 1-n processes (Function object type), e.g., for:

selected object occurrences in the model, in an existing process support map, for example

selected results of an object search

selected models (VACD, EPC, process support map)


42

Figure 28: IT landscape administration macro – Generate matrix 1

After selecting the relevant processes, you can decide whether only processes from a particular process

level will be included.

The next step is to select the corresponding section of the organizational structure. The corresponding

organizational models must be created in advance. After selecting the corresponding model, all objects

of the Organizational unit type occurring are displayed in the selection window and are available.

Locations can also be selected. The locations must also occur in the organizational model and be con-

nected to the corresponding organizational object by an is located at connection.


43

Figure 29: IT landscape administration macro – Generate matrix 2

The final step is to select the group in which the new process support map is to be saved and to specify

the model name.

The new (blank) process support map is created and available for further processing. This method can

also be used to create partial sections or different views of an existing process support map.

If it is necessary to extend an existing matrix, this can only be done by inserting columns and rows.

Note that the default column must never be selected here. It is not suitable for processing using ma-

cros. If a new row or column has been inserted, the required object (e.g., Function, Organizational

unit or Location) can be copied into the row or column header. The normal default functions such as

drag and drop or copy/paste are used. The IT landscape administration – Complete matrix

macro can then be used to complete the blank cells. If a process support unit already exists for a cell,

an occurrence of it is created along with its content. If no process support unit exists yet, a new one is

created and an occurrence created. New process support units are always created in the group contain-

ing the model in which they are inserted.


44

6.5.2 IT landscape administration – Complete matrix

Description Type of ex-

ecution

Event Visible to

users

This macro adds missing process support units to a

process support map. It may also be used to insert

rows or columns and define headers for them. If gaps

occur in a process support map as a result of deleting

process support units from the Explorer tree, you can

use this macro to add matching process support units

to new rows or columns.

Manual / Yes

Special features:

Completion is based on the following algorithm: if a process support unit already exists for the blank

cell, an occurrence copy of that process support unit is inserted. If a process support unit exists for

which the user does not have read privileges, a message is output and the cell remains blank. If no

process support unit exists yet for a blank cell, a new process support unit is created in the group of

the corresponding process support map.


45

6.5.3 IT landscape administration – Copy content


ecution

Event Visible to us-

ers

This macro copies process support of processes. It

is irrelevant whether a process support column is

distributed over several process support maps. All

relevant process support maps are automatically

opened and the entire process support information

of a source process is transferred to any required

number of target processes. If required, the entire

target column is created, or it is updated. The

source and target process are selected in a dialog.

Optionally, you can specify that all source

processes including their support are deleted from

the models in a final step.

Manual / Yes

Special features

At present, only columns can be copied. A process support map is relevant if it is supported by a macro

and contains at least one affected function. All relevant process support maps are opened invisibly. A

dialog shows the number of affected models before the start. The copy operation can be canceled at

this point. If an error occurs when opening the relevant models, e.g., because write access to the mod-

el is impossible, an error message is displayed and the operation is canceled. The initial state is pre-

served.

This macro can be used to prepare for merging or splitting process steps or functions.


46

6.5.4 IT landscape administration – Adjust names

Description Type of

execution

Event Visible to

users

This macro adjusts the names of process support

units according to the pattern 'Name of organization-

al unit/Name of function'.

Manual / Yes

Special features

In addition, the GUIDs of the column and row header objects involved in each process support unit,

e.g., Organizational unit, Location, or Function, are also saved in each process support unit using

the Source attribute. The full names of the objects involved are also recorded using the Full name

attribute of the process support units.


47

6.5.5 Update process support map

ARIS generally differentiates between an occurrence and a definition level. Due to this basic concept,

the process support universe resides at definition level whereas individual process support maps mere-

ly represent views of it. If two IT landscape planners work on the same process support map section in

different models, the changes need to be updated in such a way that they are shown in both process

support maps.

The Update process support map macro synchronizes the process support information in a model

with the current state that may have changed. Application systems that no longer exist are removed,

and application systems that were added are created as a new occurrence in the model. For the up-

date, this macro takes into account the specified view settings, such as Complete, Plan, As-is and

To-be, and the corresponding analysis time.

Warning

If the Read access privilege is missing for an existing process support unit, the macro outputs a cor-

responding message instead of creating an occurrence of the existing process support unit. The cell

remains blank.

This keeps the data in each model consistent at the occurrence level. The macro is started automatical-

ly if a process support map is opened in Macro control operation mode. This means that a process

support map is automatically updated immediately after it is opened.


ecution

Event Visible to

users

This macro updates the process support information

in a model. Application systems that no longer exist

are removed, and new application systems are

created as an occurrence in the model. In addition,

for analysis purposes you can generate the views

'Complete', 'Plan', 'As-is', and 'To-be' at differ-

ent points in time.

Event/Manual Open model No

Special features

The macro is started automatically when a map is opened. No new process support units are generat-

ed. If no process support units exist for particular cells, they remain blank. The macro also includes

repair mechanisms. These identify isolated IT systems with no reference to the underlying process

support unit and output a message. Running of the macro is stopped. Duplicate process support units,

i.e., two occurrences of the same definition in a cell, are also identified. Here too, a message is output

and the occurrences are automatically deleted after you click on OK. The macro also identifies if several

process support units (occurrences) with different definitions or ambiguous assignments are located in

a cell. A message is displayed and running of the macro is canceled.


48

6.5.6 Edit process support unit

Description Type of

execution

Event Visible to

users

You can use this macro to edit the process support

information of any number of process support units

in a model. Different attribute values in the various

process support units are identified in the display.

You can also extend the occurrence of application

systems from a few to all of the selected process

support units.

Event or

Manual

Double click

on PSU

Yes

Special features

Editing of an individual process support unit is started by double-clicking on the object. In this case,

the macro responds to the event. If several process support units are to be edited simultaneously, the

macro must be started manually for the selection. For example, if several process support units are

edited simultaneously, in addition to the system assignment, the manual status can be set for all se-

lected objects. The undefined status can also be specified in the Edit process support unit dialog.

Figure 30: Select and edit multiple process support units 1


49




50

6.5.7 Delete process support columns

Description Type of

execution

Event Visible to

users

This macro supports fast deletion of all occurrences

in a horizontal or vertical lane.

Event Delete col-

umn or row

using pop-up

menu

No

Special features

This macro is based on an existing default function, supplemented by a subsequent Save operation.


51

6.5.8 Remove IT system

Description Type of

execution

Event Visible to

users

This macro removes the corresponding occurrence

from the process support unit and deletes the

attributes of the connection between process support

unit and application system. Thus, the application

system is considered as deleted and can also be re-

moved if the process support unit has occurrences in

other models.

Event Delete (select

and remove)

also using pop-

up menu

No

Special features

The macro also prevents functions, organizational units, locations, process support units and connec-

tions from being deleted. Thus, only the occurrences of the IT systems (application system types) in-

cluding the attributes of the associated connections to the corresponding process support units can be

deleted.


52

6.5.9 Add IT system

Description Type of

execution

Event Visible to

users

This macro places or moves application systems. Op-

tionally, you can directly edit connection attributes

for each application system. If you copy application

systems, the current attribute values are transferred.

Error messages indicating multiple copying or miss-

ing access privileges ensure data consistency.

Event ObjOcc is to

be moved

ObjOcc is to

be copied

Object is to

be copied

No

Special features

In a process support map that is in Macro control operation mode, only IT systems (application sys-

tem types) can be added. No other object types are allowed. If an IT system is added to a process

support unit that is hidden, all available content of process support units is first displayed and then the

IT system is added. The IT landscape view of the process support map must always be taken into ac-

count. For example, if the map is in the As-is IT landscape view, not all hidden systems may be visi-

ble.

This macro also prevents process support units from being placed within a normal process support

map.


53

6.5.10 Hide IT systems from a process support unit

Large process support maps with a large number of IT systems for each process support unit can be-

come complex. For this reason, the IT systems for one or multiple process support units can be hidden

in ARIS IT Architect.

Hide IT system

Description Type of

execution

Event Visible to

users

This macro hides the application systems contained in

each of the selected process support units and creates

occurrences of them in an assigned model. The process

support unit is then displayed with a special symbol indi-

cating that the application systems are hidden in this

process support unit.

Manual / Yes

Show IT system

Description Type of

execution

Event Visible to

users

This macro retrieves the connected application systems

for each selected process support unit and creates occur-

rences of them in the process support unit.

Manual / Yes


54

Figure 33: Reduced view of process support map


55

6.5.11 Change IT landscape view

To be able to observe how the IT landscape changes over time in line with planning, time-dependent

views of the process support maps can be generated.


ecution

Event Visible to

users

This macro updates the current process support map

based on the selected 'process support type' and the

'analysis date'.

Manual / Yes

Various types of views are distinguished:

Complete (default): Maintenance view. All content is displayed, regardless of the set analysis

date. The traffic light color corresponds to the value of the Status of process support attribute.

As-is: Only systems that exist or existed on the analysis date are displayed (green and orange traf-

fic lights). The traffic light color is calculated based on the lifecycle information. The analysis date

can be in the past or the current date, but never a date in the future.

Plan: The analysis date can be set for any date. Phased out systems, indicated by a red traffic light

in the complete view, are hidden if the phase-out date is before the analysis date. Systems that

would only have been phased out on the analysis date are displayed. Systems that change their

traffic light color in respect of today’s view are shown with a dashed outline. The traffic light color is

calculated based on the lifecycle information.

To-be: All systems that have a blue border are displayed. These are the systems whose To-be

attribute is maintained for the connection between the IT system and the process support unit.


56

The macro adjusts the views using the Analysis date and IT landscape view model attributes.

Figure 34: Define IT landscape view (plan view for 11/30/2009) The lifecycle for IT systems is indicated in color depending on the IT landscape view.


57

6.5.12 Process support reports

The following reports are used internally by the macros and cannot be started by users in the Report

Wizard.

Name Description Executed by Visible to us-

ers

IT landscape administration

– Copy content

This report cannot be run by users.

The report is started by the macro

of the same name.

Macro No

IT landscape administration

– Generate matrix

This report cannot be run by users.


of the same name.

Macro No

Edit process support unit This report cannot be run by users.


of the same name.

Macro No

Add IT system This report cannot be run by users.


of the same name.

Macro No


58

6.6 Working in process support maps

6.6.1 General IT landscape planning

Based on the created and updated process support map, the IT landscape planner starts to document

and plan the process-oriented IT support in individual business areas. This is done by accessing the

existing IT system register, which is managed by the IT architecture manager in the ARIS IT Architect

repository. Double-clicking on the process support unit starts the Edit process support unit macro.

The IT landscape planner first decides on the type of process support for a process support unit. The

following statuses are distinguished:

No processing (process step is not relevant)

Manual (manual support)

System (support by an IT system)

Figure 35: Edit process support unit macro 1

The Add button can be used to add existing IT systems to the cell.


59


The relevant IT system can now be selected in the search result, and information about the lifecycle

can be saved if required. The system becomes the projected system if the To be checkbox is enabled.

As soon as all IT systems that are relevant for this cell have been entered, the dialog can be closed by

clicking on OK.


60

The IT systems are now displayed in the corresponding cell.


The shaded circle (traffic light) in the top right corner of the symbol indicates the appropriate phase in

the lifecycle. A blue outline indicates projected systems.

The procedure to remove IT systems from a process support cell and to change data for the relevant

lifecycle is analogous to the one described above. When a system is deleted from a cell, all connection

attributes (Status of process support, Phase-in planned since, etc.) for the connection between the IT

system and the process support unit are deleted, while only the occurrence in the model is deleted

from the IT system. As a result, the Update model macro no longer includes these IT systems.

In the configuration file psmReportConfig.xml (report directory, IT architecture management cat-

egory), the system selection list can be filtered by particular criteria in the Edit process support unit

dialog. For example, this is useful if the Application system type object type is used not only for IT

systems but also for IT components. The configuration can be used to prevent IT components that are

not relevant for the process support map from appearing alongside the IT systems. By default, these

are differentiated by the System type attribute.

61

By default, the preset configuration is as follows:

<?xml version="1.0" encoding="UTF-8"?>

<ReportRegistry>

<AST>

<OT>OT_APPL_SYS_TYPE</OT>



<AT>AT_SYSTEM_TYPE</AT>



<AVT>AVT_SYSTEM_TYPE_SYSTEM,AVT_SYSTEM_TYPE_SERVICE</AVT>

</AST></ReportRegistry>

Any user-defined attribute can be used instead of the System type attribute.


62

6.6.2 IT landscape planning using quadrants

The IT landscape that is documented in process support maps can be best standardized in line with

strategic specifications if you build an IT system portfolio. In such a portfolio, quadrants can be used to

structure systems.

In ARIS IT Architect, application system type diagrams are used to build portfolios. Application system

classes represent the quadrants. The Quadrant attribute is used to identify an application system class

as a quadrant. In addition to the four quadrants, a total of five intermediate areas can be defined. The

following is a suggestion for the semantic meaning of the four quadrants:

Quadrant 1 (Q1) Enforce/Recommend standard

This quadrant contains the strategically important IT systems that are to be developed further and

rolled out in the future. Therefore, a large portion of the available IT budget is invested here.

Quadrant 2 (Q2) Freeze

The IT systems in this quadrant are to be operated as economically as possible for the remainder of

their lifecycle and see only limited further development. Therefore, investment is to be reduced

here.

Quadrant 3 (Q3) Phase out/Replace

IT systems in this quadrant will be phased out and replaced by new IT systems. Therefore, operat-

ing costs are kept as low as possible here. No investment in adjustments is made.

Quadrant 4 (Q4) Tolerate

The Tolerate quadrant holds all IT systems that only fit in with the strategic IT plan to a limited ex-

tent, e.g., due to outdated technology, but cannot be retired in the short or medium term for par-

ticular reasons. Investment is made here only in individual cases; the basic strategy is 'no invest-

ment'.


63

Figure 38: Quadrant view of IT system portfolio

In addition to the quadrants described, transition areas exist that are used to map the transfer of an IT

system to a different quadrant.

The data stored here can be evaluated graphically. The System portfolio analysis macro is used to

visualize the quadrant status in the process support map by setting the margin color of the IT system

symbol.

Figure 39: System portfolio analysis


64

6.7 Method details


listed below. These are automatically used in Macro control operation mode and cannot be edited ma-

nually. Further information can be found in the Administration module (Conventions/Method), in the

Method help, and in the Methods Manual.

Figure 40: New object types. Previous version left, new object types right.


65

6.7.1 Process support map model type

In addition to objects of the Process support unit (PSU) type, which are each placed at the intersection

of the column and row header objects that define them, the method also allows the following objects.

Object types

Column header Row header Assignments

Function

Capability

Service type

Group

Organizational unit

Organizational unit type

Person

Person type

Location

Position

Performance


Table 7: Object types in Process support map model type


66

6.7.2 Connections between PSU and cell objects in a map

Source object Target object Connection type

Application system type Process support unit belongs to process support unit

Table 8: Process support map conventions – Connections I

6.7.3 Connections between PSU and column/row header objects in a map


Group Process support unit can be user

Organizational unit Process support unit can be user

Organizational unit type Process support unit can be user

Person Process support unit can be user

Process support unit Location can be located at

Process support unit Capability supports

Process support unit Function supports

Process support unit Performance supports

Process support unit Service type supports

Table 9: Process support map conventions – Connections II


67

6.7.4 Connections between column/row header objects and cell objects in a map

These connections have no functional significance in IT landscape planning. They are created automati-

cally for analysis purposes when you place objects in a map.


Application system type Location is located at


Application system type Function supports

Application system type Performance supports

Application system type Service type supports

Group Application system type can be user

Organizational unit Application system type can be user

Organizational unit type Application system type can be user

Person Application system type can be user

Person type Application system type can be user

Position Application system type can be user

Table 10: Process support map conventions – Connections III

6.7.5 Process support map model attributes

Name Meaning

IT landscape view Complete

As-is

Plan

To-be

Analysis date Defines the date on which an IT landscape view is to be analyzed. It is

only evaluated in conjunction with the As-is and Plan views, as the other

views are not time-dependent. For the As-is view, the current date or a

date in the past are valid.

Last update of process

support map

Time stamp of the last update. This attribute supports you in deciding

whether the content of the PSU should be updated.

Last generated view of

process support map

Contains the code of the last generated view followed by the date of

generation. This is used to determine whether the view has been

changed. In this case, the entire map has to be updated.

Table 11: Process support map conventions – Process support map model attributes


68

6.7.6 Process support unit (PSU) attributes

These attributes are used as part of macro-based IT landscape planning. System attributes cannot be

edited manually.

Name Meaning

Description/Definition A comment is saved as the description. This is displayed if the PSU has

no assignments and the processing type has neither the Manual nor No

processing status.

Processing type No processing

Manual

System

Last change This system attribute is updated at every change. This information is

required to determine the update time of a PSM view.

Change history This system attribute is automatically updated and provides an overview

of changes made.

Table 12: Process support map conventions – PSU attributes


69

6.7.7 Connection attributes

These attributes control the traffic light colors for the lifecycle.

Connection type Attribute Meaning

belongs to process

support unit

Description/Definition The text characterizes the assignment.

State of process sup-

port

Phased out

To be phased out

Start phase-out

To be phased in

Start phase-in

Phased in

Phase-in planned

since

Start time of the planning to phase in an assign-

ment.

Phase-in (plan) Planned date on which an assignment is to be

phased in.

Phased in since Date of phase-in.

Phase-out planned

since

Start time of the planning to phase out an assign-

ment.

Phase-out (plan) Planned date on which an assignment is to be

phased out.

Phased out since Date of phase-out.

To-be If the value true is maintained, the assignment de-

fines a default support for the process support unit.

Table 13: Process support map conventions – Connection attributes

ARIS IT Architect - Organization architecture

70

7 Organization architecture

7.1 Roles

Process manager


7.2 Description

In the organization architecture, the organizational structures of the company are described. A typical

way of representing organizational structures is the organizational chart. It shows the formed organiza-

tional units as task performers and the links between them according to the selected structuring crite-

ria.

Definition

Organizational units are the performers of the tasks required to attain the business objectives.

Organizational units are linked via relationships. For a more precise specification of the hierarchical

relationships, various connection types between organizational units are differentiated. In this context,

a connection may have one of the following meanings:

is technical superior to

is disciplinary superior to

is a component of

While the functional responsibilities are recorded in boxes, the organizational chart maps the allocation

of the business tasks.

The Position object type is provided to represent individual positions within the company, for example,

positions for which descriptions exist. Multiple positions can be assigned to an organizational unit. The

meaning of the connections corresponds to that between organizational units. Individual persons who

hold positions in the company can be assigned to these positions and to the organizational units. Sepa-

rate objects are also available for persons. The assignment of an individual person to an organizational

unit shows that this person is assigned as an employee to this organizational unit, whereas the as-

signment to an individual position defines the current staffing in the company.

Organizational units and persons can be typified. For example, this means that you can define whether

an organizational unit is a subdepartment, department, or group. Persons can be assigned to the De-

partmental manager, Group manager, or Project manager person types, for example.

This typification is represented by the Organizational unit type and Person type objects provided

for this purpose. Using these object types enables general business rules that abstract from concrete

organizational units or persons of the company to be mapped. Thus, it is possible in process chains to

define that only specific person types may carry out a function or have access to an information object.

The modeling of the organizational structure of the company is the starting point for the network topol-

ogies to be defined at the design specification level, which are to provide the best possible support for

this organizational structure. Included in the definition of the network topology are network connec-

tions and network nodes, which may be found at particular locations of the company. The location of


71

an organizational unit is therefore the most important link between requirements definition and design

specification of the organization view. Thus, the location of every organizational unit can already be

assigned in the requirements definition.

Locations may be arranged in any required hierarchy. A location can be an entire plant, a building or,

for a more detailed examination, an office through to an individual workstation in an office room. This

makes it possible, in the design specification, to assign network nodes of a network to individual

workstations of the organizational unit.

When creating process support maps, organizational charts are used in the selection dialogs as source

for the organizational structure, i.e., for the rows in the map. The order in which the rows are created

in the process support map is subject to a particular convention, which should be observed when creat-

ing the organizational charts. The figure below shows the reading direction that the algorithm uses to

populate the selection lists in the dialogs for creating a process support map.

Figure 41: Specify the order using modeling conventions

ARIS IT Architect first extracts the root objects (left-aligned, of Organizational unit or Location

type) of a column from top to bottom. A search is then performed horizontally for the root – once again

of the Organizational unit type – of the next column, and the column is extracted from top to bot-

tom, etc. Afterward, locations connected by relationships are extracted in the same order.

Further information on the organization architecture is available in the ARIS Method manual.


72

7.3 Method details

Model types Object type

Organizational chart Organizational unit type

Organizational unit

Location

Workstation

System organizational unit type

System organizational unit

Group

Cost center

Position type

Position type

Position description

Person type

Internal person

External person

Organizational chart

Table 14: Conventions for organization architecture

ARIS IT Architect - Information architecture

73

8 Information architecture

8.1 Roles

Process manager

8.2 Description

In the information architecture, the data view of the company is represented. For this purpose, an

eERM model is used as the model type. The business objects are represented by clusters and can be

reused in the interface descriptions of the IT systems, for example (see Figure 13: Interface model-

ing

).

A refinement of the description can be made using assigned eERM models or class diagrams. Further

information on this topic is available in the Methods Manual.

Figure 42: Example of an information architecture

ARIS IT Architect - Information architecture

74

8.3 Method details


listed below.


eERM Cluster

Table 15: Conventions for information architecture - Models and objects

Model type Source object Target ob-

ject

Connection type

eERM Cluster Cluster has link to

Table 16: Information architecture conventions – Relationships

ARIS IT Architect - System functions, requirements, project and portfolio management

75

9 System functions, requirements, project and portfolio management

9.1 Roles



IT project manager

9.2 Description

System functions (capabilities) represent the link between the relevant department or business process

and the IT or IT system. It is therefore not only possible to document which IT system supports the

process, but also how it is done, i.e., which system function of the IT system is used for process execu-

tion. The relation is illustrated in the following figure:

Figure 43: Relationship between function, IT system, and system function

The system functions are managed in a separate model of Service architecture diagram type (see

Figure 15: System functions library

) and can be divided into technical domains if required. This guarantees a uniform description of IT sys-

tems with respect to their functions. As a result, system redundancies can be identified, alternative IT

systems found, and optimum support provided for migration projects.

However, system functions can also be derived from a business process and thus represent technical IT

requirements. If none of the available IT systems support a system function derived from the

processes, it can be linked with a requirement.

ServiceService‘Provides’‘Provides’

Process Service, System

InvoicingInvoicingsupportssupports

Example

EPC Access diagram

supportssupports

Capability‘Requires’

CapabilityCapabilityCapability‘Requires’

supportssupports

calculate price

Process step

Calculate pricesupports

Calculate priceCalculate priceCalculate pricesupports


76

Figure 44: Technical requirement of IT

All functional and non-functional requirements are structured and managed in requirements trees.

Figure 45: Example of a requirements tree

In contrast to system functions (capabilities), requirements are temporary in nature. After successful

implementation of a requirement, the functionality is available in accordance with the system functio-

nality requirement.


77

The project necessary for implementation can also be represented in ARIS IT Architect. Projects can be

structured using project tasks. The individual project tasks, for example, can be described in terms of

objectives pursued, affected organizational units, people responsible, and affected IT systems.

Figure 46: Example of a project description

Individual cells in a process support map can also be linked to a task. This indicates that a particular

cell or process support unit within a project is processed, for example as part of a migration scenario.

Figure 47: Connection between process support unit and task


78

The individual tasks can then be grouped in programs.

Figure 48: Example of a program description

A project schedule is used to represent the chronological dependency of individual tasks. The place-

ment of tasks on a timeline and the mapping of dependencies result in a detailed project schedule as

shown in the figure below.


79

Figure 49: Example of a project schedule


80

9.3 Method details


listed below.


Access diagram Application system type

Capability

EPC Function

Capability


Requirements tree Requirement

Target

Requirement allocation diagram Requirement

Capability

Service type


Component

Function

Cluster

Technical term

Organizational unit

Group

Person

Target

Risk

KPI instance

Document

Work breakdown structure Function

Task

Program

Project

Requirement


81


Project schedule* Task

Person

Organizational unit

Location


Milestone

Quality gate

Line

KPI instance

Target

Relationship

* Only the most common object types are listed here - see ARIS Method help for a complete listing.

Table 17: Projects, capabilities, and requirements conventions – Models and objects


Access diagram Application system type Capability supports

EPC Function Capability supports

Requirements tree Requirement Requirement encompasses

Requirement Requirement is dependent on

Target Requirement is supported by

Requirement allocation

diagram

Requirement Application system

type

relates to

Requirement Capability realizes

Requirement Service type realizes

Requirement Component relates to

Requirement Function relates to

Requirement Cluster relates to

Requirement Technical term relates to


82


Requirement Organizational unit* is technically re-

sponsible for

Requirement Organizational unit* is IT responsible

for

Requirement Organizational unit* must be informed

on cancellation

Requirement Group* is technically re-

sponsible for

Requirement Group* is IT responsible

for

Requirement Group* must be informed

on cancellation

Requirement Person* is technically re-

sponsible for

Requirement Person* is IT responsible

for

Requirement Person* must be informed

on cancellation

Target Requirement is supported by

Requirement Risk is exposed to

Requirement KPI instance is measured by

Work breakdown structure Task Function is of type

Project Task is process-oriented

superior

Program Project is process-oriented

superior

Task Requirement realizes

Project schedule* Organizational unit Task carries out

Person Task carries out

Task Quality gate creates

Quality gate Task activates

Task Relationship has output of

Relationship Task is input for


83


Task Task is predecessor of

Task Task is successor of

Task Task relates to

Task Task belongs to

Task Milestone instance creates

Task Milestone instance activates

Task Milestone instance is predecessor of

* Only the most common connection types are listed here – see ARIS Method help for a complete listing.

Table 18: Projects, capabilities, and requirements conventions – Relationships

ARIS IT Architect - Reports

84

10 Reports

The information managed in the database can be evaluated in different ways. In addition to the con-

ventional navigation options and the standard search, IT Architect provides a selection of reports and

macros specially tailored to the requirements of IT architecture management. The individual reports

and macros are explained below. Furthermore, various examples are given to show how the IT-specific

data can be navigated and searched.

10.1 Redundant applications (visualization of redundancies)

Category IT architecture management

Name Redundant applications

Description This report determines the redundancies in the use of functions, capabilities, and/or

data objects for the selected application system types. Optionally, the information

can be output exclusively for redundant applications.

Context Objects (see below)

Output RTF/Word, PDF, HTML, Excel

Table 19: Description of the Redundant applications report

The report determines redundancies of application system types in respect of the following object

types:

Functions

Capabilities

Data objects

The following connections from/to the application system type are evaluated:

supports function

supports capability

is input for/has output of data objects

That is, a redundancy exists if there is more than one application system type with the same relation-

ship to specific functions, capabilities, or data objects.


85

Sample output

Application system Capabilities Is additionally supported

by

Redundancy

A plan Order management ProOn order processing 1.0

A plan Price calculation ProOn order processing 1.0

A plan Product data management ProOn order processing 2.0

ProOn resource planning

ProOn Bill of materials for CKD

kits

0.0

ProOn Billing of CKD shipments 0.0

ProOn order processing Order management A plan 1.0

ProOn order processing Order tracing 0.0

ProOn order processing Price calculation A plan 1.0

ProOn order processing Product data management A plan 2.0

ProOn resource planning

ProOn resource plan-

ning

Aggregation of amounts

per part number and fixed

date

0.0


ning

Product data management A plan 2.0

ProOn order processing

Table 20: Sample result of the 'Redundant applications' report


86

10.2 System evaluations


Name System evaluation

Description Based on the application system types within the selected

application system type diagrams, this report creates a sys-

tem portfolio with regard to Data center costs and Criticality.

Context Models



Output HTML

Table 21: Description of the System evaluation report

Below, a sample output of the System evaluation report is shown.

Figure 50: Sample output of the System evaluation report


87

10.3 System list

The System list report enables various system lists to be created depending on the selected elements.

The following system lists can be created:

System list for the associated IT standard

System list for the associated business process

List of IT standards for the associated business process


Name System list

Description This report optionally creates the following output:

Based on the selected IT components: all application systems using these

IT components.

Based on the selected processes: all application systems used in the

process.

Based on the selected processes: all application systems used in the

process, as well as the IT components used by these application systems.

If the report is run for processes, the processes in the assigned

models can also be evaluated up to a specified assignment level.

Context Models, objects (see below)

Output RTF/Word, PDF, HTML, Excel

Table 22: Description of the System list report

This report provides wizard support.

d

Figure 51: Wizard for System list report


88

In Figure 52

, an example list of IT components for a selected business process is shown.

The data is output in a table, with the objects sorted alphabetically. In the following example, only the

application system APST_1 has Standard status set in the options (Include standardization status

option). For this reason, the other application systems including the used IT components are shown in

grey italics.

If processes in assigned models are additionally evaluated, this is visualized by indentation of the

process name in the first column.

Figure 52: Example output for System list report


89

10.4 Lifecycle management (report)


Name Lifecycle management

Description Depending on the selected context, the report visualizes the lifecycle man-

agement of IT components (application system type) or IT system instances

(application system). Optionally, this can be done in the form of a table out-

put. For selected models or object occurrences it is also possible to color the

occurrences contained in the model according to their current status. In addi-

tion, the occurrences can be reset to the default.

Context Models, objects, and object occurrences; restricting contexts according to the

object type (application system type or application system).

Output RTF/Word, PDF, Excel

Table 23: Description of the Lifecycle management report

The Lifecycle management report relates to either the standardization of an IT component or the

operation of an IT system (instance). The selected element is used to decide which lifecycle is used as

a basis. If application system types are selected, those attributes that relate to standardization are

evaluated. If application systems are selected, the report relates to operation attributes.

A table can be output if desired, which contains not only the text output of the relevant start times of

the individual statuses, but also a time bar and graphical output.


90

Figure 53: Wizard for Lifecycle management report

As a further option, it is possible to display the current statuses of the IT components or IT system in-

stances at any time (dynamic simulation of an IT map). The objects that have occurrences are colored

according to their attribute values in relation to a comparison date entered by the user. This compari-

son date is indicated by an arrow ( ) in the output. The period under consideration can also be speci-

fied if desired. To obtain a coloring of objects in the open model, it is necessary to start the associated

macro in the model.

Sample output for lifecycle management of IT system instances:

Figure 54: Sample output for Lifecycle management report

Sample output for lifecycle management of IT components (standardization):

Figure 55: Sample output for lifecycle management of IT components


91

10.5 Lifecycle management (macro)

Category Macros/IT architecture management

Name Lifecycle management

Description The 'Lifecycle management' report can also be started as a ma-

cro for a model.

Table 24: Description of the Lifecycle management macro

Running this macro either runs the 'Lifecycle management' report or color-codes the IT components or

IT system instances in an open model according to the lifecycle status if the Color objects option is

set.

Figure 56: IT components (operating systems) - Color highlighting by macro

ARIS

10

Ca

Na

De

Figu

In t

ing

IT Architec

.6 Disp

tegory

me

escription

ure 57: Co

he table, a

order: Syst

ct - Reports

play data

M

M

D

U

a

s

t

a

onnection

ll objects a

tem, Conne

s

a flows

Macros/IT a

Macro/IT ar

Display data

Using the D

a table of

system type

the model.

adhered to.

assignme

re output w

ected syste

architecture

rchitecture

a flows

Display da

data flows

es. This rep

The conve

ent for spe

with their n

ems, Data,

92

e managem

manageme

ta flows r

on the ba

port can al

entions des

ecifying IT

name, with

Protocol an

ment

ent

report, the

asis of one

so be run a

scribed in

T system in

the entries

nd Direction

user is abl

e or more

as a macro

chapter 5.

nterfaces

s sorted alp

n.

e to create

application

o directly in

1 must be

phabetically

e

n

n

e

y in the folloow-


93

As a macro

Figure 58: Output of the Display data flows macro

As a report

System

Connected sys-

tems Data Protocol Direction

ProOn order

processing A plan <--

ProOn order

processing MatReq/1 Material data DDF 567 -->

ProOn order

processing MatReq/1 Order data DDF 567 -->

ProOn order

processing

ProOn resource

planning -->

ProOn order

processing ProOn billing -->

Figure 59: Output of the Display data flows report


94

10.7 System fact sheet

Category Report/IT architecture management

Name System fact sheet

Description The system fact sheet describes a system with respect to the

following aspects:

System description

Contact (person, organizational unit)

Service level agreements

Capabilities

Processes

Information architecture

Architecture set

Operation

Context Objects

Application system type object type

Output RTF, PDF, HTML, DOC, XLS

Table 25: Description of the System fact sheet report

All information that describes an IT system (application system type) can be output in condensed form

in a system fact sheet.


95

Sample output for system fact sheet:


System description:

System name:


Short description:

Order processing for CKD shipments

Full name:

ProOn software order processing module

Description:

The Order processing module is part of the ProOn software sys-

tem and provides functionality for CKD shipments.

Manufacturer of the

application:

Proprietary system

Number of internal us-

ers:

Up to 1000

Number of external us-

ers:

0

Criticality (importance

of the application sys-

tem):

Very high

Individual develop-

ment/Standard soft-

ware:

Yes

Standardization status:

Standard


96

Individual develop-

ment/Standard soft-

ware:

Yes

Standardization status:

Standard

Contact (person):

Name:

John Smith

Telephone number:

+1-212-371-9435

E-mail address:

[email protected]

Department:

UK4-P1

Contact (organizational unit):

Name:

Sales

Service level agreements:

Max. downtime per month:

Less than 1 hour

Availability:

99.9 percent

Guaranty/Warranty until:

12/31/2009


97

Documents and links:

User Guide:

http://dms.ids.com/usman.pdf

Administration Guide:

http://dms.ids.com/adman.pdf

Capabilities:

Arrangement of monthly programs

Order management

Order tracing

Price calculation

Product data management

The system is used in the following processes:

Process customer order

Deliver


Check credits


Create customer order


Create products


Customer needs created


98

Customer needs created


Fix and edit conditions



Replicate customer order


Schedule order

Information architecture

Managed data:

Material data

Order data

System interfaces

Connected systems

Data Protocol Direction

A plan

<--

MatReq/1

Material data

DDF 567

-->

MatReq/1

Order data

DDF 567

-->


ning

-->

ProOn billing -->


99

Architecture set:

Architecture layer


IT components

Business process-specific

components & services

Programming languages

---

Hardware server

---

Operating systems

---

Development

Databases (DBMS)

IBM DB2

Oracle

Figure 60: Example of a system fact sheet

ProOn OrderProcessing

A plan

MatReq/1ProOn

resourceplanning

ProOnBilling

ProOn Order Processing


100

10.8 System consolidation

Category Report/IT architecture management

Name System consolidation

Description This report enables you to analyze IT systems in terms of the process support

they provide. The report analyzes business processes with regard to redun-

dancies in its IT support. It shows which IT systems potentially provide the

functions required by the processes, and which IT systems really do supply

processes with the required functions. Thus, the to-be architecture can be

derived and IT projects can be initiated. The objective is to minimize redun-

dant IT support in the future.

Context Objects

Function object type

Output RTF, PDF, HTML, DOC, XLS

Sample output

Legend

X A particular IT system capability is required for a process to run. No IT system sup-

ports the required capability.

An IT system supports a particular process with a specific capability.

An IT system supports a specific capability that a process requires. This capability is

also supported by another system. Therefore, this IT system represents an alternative

system.

Support by an IT system is not required for a process to run.


101

10.9 System portfolio analysis

The IT landscape that is documented in process support maps can be best standardized in line with

strategic specifications if you build an IT system portfolio. In such a portfolio, quadrants can be used to

structure systems.

Figure 61: Quadrant view of IT system portfolio

The data stored here can be evaluated graphically. The System portfolio analysis macro is used to

visualize the quadrant status or the quadrant assignment of IT systems in a process support map by

setting the margin color of the IT system symbol.


102

Figure 62: System portfolio analysis

To do this, it is necessary to mark the quadrant objects (application system classes) defined in the ap-

plication system type diagram (Figure 61: Quadrant view of IT system portfolio

) by using the Quadrant attribute. Nine attributes are available, and their names can be adapted in

the method configuration if required.

Attribute values of the Quadrant attribute at the application system class:

Q1

Q2

Q3

Q4

Q1/Q2

Q2/Q3

Q3/Q4

Q1/Q4

Q1/Q2/Q3/Q4

Specify the attributes on the tab of the same name in the Designer module.


103

Figure 63: Quadrant attribute of the application system class

For the System portfolio analysis report to color-code IT system symbols correctly according to qua-

drant assignments in the process support map, it is necessary to set the mapping between quadrant

and color in a configuration file.

Figure 64: Configuration file for the system portfolio quadrants


104

First, the attribute used to identify the application system classes as quadrant must be specified in the

configuration file. In the figure below, the default attribute Quadrant is specified. This can be replaced

with a user-defined attribute.

Figure 65: Configuration of the Quadrant attribute

The attribute values are then mapped to color values. The Properties dialog for the Quadrant attribute

can be used as a template. The settings in the configuration file are done manually:

Figure 66: Configuration of colors

Once all settings have been correctly specified, the System portfolio analysis macro can be started

for any process support map. The borders of all IT systems (application system types) are colored ac-

cording to their quadrant assignment (Figure 62: System portfolio analysis

).


105

ARIS IT Architect - Further examples for the analysis of data

106

11 Further examples for the analysis of data

11.1 Use case: Which systems use a particular technology?

Example: Which systems use Oracle?

Solution

Figure 67: Relationships of the Oracle IT component

The Relationships tab for a particular technology can be used to determine which IT systems use

Oracle, for example. In this way, the effects of a change in technology, supplier, or version can be ana-

lyzed, and the application managers concerned can be informed and get involved.

ARIS IT Architect - Further examples for the analysis of data

107

11.2 Use case: Which processes are affected by a specific technology?

Example: Which processes depend indirectly on Oracle?

Solution

Figure 68: Result of a search query

Complex analyses that require navigation across several relationships can be supported using custo-

mizable search queries. Once defined, the search queries are then available to the users at any time.

Further information on the creation of search queries is available in the help topics under the keyword

Queries.

ARIS IT Architect - Method details (attribute table)

108

12 Method details (attribute table)

The following table contains typical IT-specific attributes of ARIS IT Architect that are used within IT

architecture management. Further information can be found in the Administration module (Conven-

tions/Method), in the Method help, and in the Methods Manual.

Object type Attribute type

name/Attribute type

group

Attribute values

Programming language, Product/Service,

Information carrier, Application system

type, Operating system type, Cluster/Data

model, DBMS type, Function, Technical

term, Hardware component type, Hard-

ware component class, Protocol

Life cycle attributes Evaluation (start)

Evaluation (end)

Request (start)

Request (end)

Phase-in phase (start)

Phase-in phase (end)

Standard (start)

Standard (end)

Phase-out phase (start)

Phase-out phase (end)

Guaranty/Warranty

Application system

Life cycle attributes Planning phase (start)

Planning phase (end)

Procurement phase (start)

Procurement phase (end)

Development phase (start)

Development phase (end)

Test phase (start)

Test phase (end)

Operation phase (start)

Operation phase (end)

Shut-down phase (start)

Shut-down phase (end)

System status In procurement, In develop-

ment, In testing, In operation,

In shut-down, Shut down, In

planning

Application system type, Operating system

type, Cluster/Data model, DBMS type,

Technical term, Function, Hardware com-

ponent class, Hardware component type,

Information carrier, Product/Service, Pro-

gramming language, Protocol

Standardization status No standard, Standard, In

evaluation, Rejected, To be

phased in, Phased out, Re-

quested for standard, To be

phased out, Standard - limited

use


109


name/Attribute

type group

Attribute values


Manufacturer

Data center costs

Criticality Very low

Low

Normal

High

Very high

Number of external

users

0

Over 10000

Up to 10000

Up to 5000

Up to 2500

Up to 1000

Up to 500

Up to 100

Number of internal

users

0

Over 10000

Up to 10000

Up to 5000

Up to 2500

Up to 1000

Up to 500

Up to 100

Availability 99.9 percent

99.6 percent

97.5 percent

92.5 percent

83 percent

Individual develop-

ment

Yes, No


110


name/Attribute type

group

Attribute values

Maximum downtime 3 days to 1 week

24 hours to 3 days

4 hours to 24 hours

1 hour to 4 hours

Less than 1 hour

System type System, Component, Service

Hardware component Operating state Semi-productive

Test

Productive

Location Location details Data center

Room

Protocol, Architecture element, Cluster/Data

model, Technical term, Function, Hardware

component class, Information carrier, Prod-

uct/Service, Application system class


(*)

Application system, application system type Port

Network node

Host name

IP address

Organizational unit, Person

LDAP user ID

Distinguished name

Table 26: Attribute table

(*) Language-independent identification characteristic for classification of object types. For example,

using the databases identification characteristic for an application system class indicates that the as-

signed application system types are databases.

ARIS IT Architect - Glossary

111

13 Glossary

Architecture set The architecture set forms the approach to, and the framework for, standardized IT architecture man-

agement. The architecture layers are the base element of the architecture set.

Architecture building block An architecture building block consists of 1-n IT components and provides standardized, encapsulated

services. The service functionality is made available via defined interfaces. Architecture building blocks

are subject to a lifecycle.

Architecture element Architecture elements are objects that enable a finer thematic subdivision of the contents of the archi-

tecture layers. They therefore represent the link to the IT standards. Architecture elements can be di-

vided into further architecture elements. On the last structural level, architecture elements contain only

IT components and/or architecture building blocks.

Architecture layer Reference architectures and architecture elements can be assigned to an architecture layer. The archi-

tecture layer in the IT architecture set therefore forms the structural element on the top level.

IT architecture management IT architecture management covers all control activities that concern the entire lifecycle of IT systems,

from the ascertainment of the business requirements through to decommissioning. The objective of

architecture management is to create and maintain an appropriate standardized information infrastruc-

ture for cost-effective achievement of strategic business objectives.

IT component IT components describe parts of IT systems, for example, the technologies used. IT components are

stored in object libraries. They always support a productive IT system, but do not directly support a

process.

IT standard An IT standard is an IT component that is identified as a generally valid standard within the company.

This distinguishes it from a non-standard component.

IT system An IT system is a set of functions implemented using information technology for the solution of particu-

lar (business) tasks. IT systems or their functions always support a process, and are themselves sup-

ported by IT components.

ARIS IT Architect - Glossary

112

Reference architecture Reference architectures are elements of the architecture set. A reference architecture comprises a set

of architecture building blocks and IT components. IT systems can also be part of a reference architec-

ture.