Aris - User Guide It Architect S en

ARIS IT Architect User Guide
March 2010
ARIS IT Architect - Contents
Contents
1 2 Introduction ........................................................................................................ 1 Enterprise Architecture Management (EAM) ............................................................. 2 2.1 2.2 3 4 EAM as part of IT management .................................................................... 3 Roles in Enterprise Architecture Management ................................................. 4
Architecture levels in IT architecture management ................................................... 5 Business processes .............................................................................................. 7 4.1 4.2 4.3 Roles ........................................................................................................ 7 Description ................................................................................................ 7 Method details ......................................................................................... 11 IT system architecture .............................................................................. 12 Roles ............................................................................................ 12 Description .................................................................................... 12 Method details................................................................................ 21 Roles ............................................................................................ 23 Description .................................................................................... 23 Method details................................................................................ 31 34 35 38 38 40 41 44 45 46 47 48 50 51 52 53 55 57
Application architecture ...................................................................................... 12 5.1 5.1.1 5.1.2 5.1.3 5.2 5.2.1 5.2.2 5.2.3
IT technology architecture ......................................................................... 23
Process support map .......................................................................................... 34 6.1 6.2 6.3 6.4 6.5 Preliminary method comments on the process support map ........................... IT landscape method system ..................................................................... Roles ...................................................................................................... Description .............................................................................................. IT landscape macros ................................................................................. IT landscape administration Generate matrix ................................... IT landscape administration Complete matrix ................................... IT landscape administration Copy content........................................ IT landscape administration Adjust names ....................................... Update process support map ............................................................ Edit process support unit ................................................................. Delete process support columns........................................................ Remove IT system .......................................................................... Add IT system ................................................................................ Hide IT systems from a process support unit ...................................... Change IT landscape view ................................................................ Process support reports ...................................................................
6.5.1 6.5.2 6.5.3 6.5.4 6.5.5 6.5.6 6.5.7 6.5.8 6.5.9 6.5.10 6.5.11 6.5.12 6.6 6.6.1 6.6.2 6.7 6.7.1 6.7.2 6.7.3 6.7.4 6.7.5 6.7.6 6.7.7
Working in process support maps ............................................................... 58 General IT landscape planning .......................................................... 58 IT landscape planning using quadrants .............................................. 62 Process support map model type ...................................................... 65 Connections between PSU and cell objects in a map ............................ 66 Connections between PSU and column/row header objects in a map ...... 66 Connections between column/row header objects and cell objects in a map .................................................................................................... 67 Process support map model attributes ............................................... 67 Process support unit (PSU) attributes ................................................ 68 Connection attributes ...................................................................... 69
Method details ......................................................................................... 64
ARIS IT Architect - Contents 7 Organization architecture .................................................................................... 70 7.1 7.2 7.3 8 8.1 8.2 8.3 9 9.1 9.2 9.3 10 10.1 10.2 10.3 10.4 10.5 10.6 10.7 10.8 10.9 11 11.1 11.2 12 13 Roles ...................................................................................................... 70 Description .............................................................................................. 70 Method details ......................................................................................... 72 Roles ...................................................................................................... 73 Description .............................................................................................. 73 Method details ......................................................................................... 74 Roles ...................................................................................................... 75 Description .............................................................................................. 75 Method details ......................................................................................... 80 Redundant applications (visualization of redundancies) .................................. 84 System evaluations .................................................................................. 86 System list .............................................................................................. 87 Lifecycle management (report) .................................................................. 89 Lifecycle management (macro) .................................................................. 91 Display data flows .................................................................................... 92 System fact sheet .................................................................................... 94 System consolidation ............................................................................... 100 System portfolio analysis.......................................................................... 101 Use case: Which systems use a particular technology? ................................. 105 Use case: Which processes are affected by a specific technology? .................. 106
Information architecture ..................................................................................... 73
System functions, requirements, project and portfolio management ......................... 75
Reports ............................................................................................................ 84
Further examples for the analysis of data ............................................................. 105
Method details (attribute table) .......................................................................... 107 Glossary .......................................................................................................... 110
II
ARIS IT Architect - Figures
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 31: Select and edit multiple process support units 2 ............................................... 49 Figure 32: Select and edit multiple process support units 3 ............................................... 49 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 Figure 36: Edit process support unit macro 2 .................................................................... 59 III
ARIS IT Architect - Figures Figure 37: Edit process support unit macro 3 .................................................................... 60 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
IV
ARIS IT Architect - Tables
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 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 flexibility 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 management, 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 analyzed, 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 central 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 Solutions will be pleased to help you in creating ARIS IT Inventory.
ARIS IT Architect - Enterprise Architecture Management (EAM)
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 exchanged by process participants and IT systems. The infrastructure architecture forms the lowest level. It is used to describe the physical landscape, 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.
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 Architect 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 regarding 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
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 framework, 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 development 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 situation 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 modelers or staff in process management competence centers of central IT.
ARIS IT Architect - Architecture levels in IT architecture management
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 below.
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 systems and enterprise areas along with their locations in addition to the processes.
ARIS IT Architect - Architecture levels in IT architecture management
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 domains, to which the individual IT systems can be assigned. The second level covers IT system management, 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 instance level. The infrastructure is described in level five. In the IT components architecture, all technologies or IT components used in the company are managed. The IT components of the architecture set are available for describing the IT system architecture 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
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 expected 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 business 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 companywide harmonization of the processes must already take place on this level as well.
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.
Figure 7: Representation of an EPC section
Within the scope of harmonization, the processes (value-added chains) on level 3 are described additionally by function allocation diagrams, which are assigned to the objects. They contain further information 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.
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 ).
10
4.3
Method details
The method conventions (model, object, and connection types) used in the above explanations are listed below. Model 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 Value-added chain diagram Value-added chain Value-added chain is processoriented superior Value-added chain Function allocation diagram Capability Organizational unit Position Person Cluster Application system type
Table 2: Conventions for business processes Relationships
Object type
Source object
Target object
Connection type
Value-added chain
is predecessor of
Function Function Function Function Function Function
supports is technically responsible for is technically responsible for is technically responsible for is input for/has output of supports
11
ARIS IT Architect - Application architecture
5 Application architecture 5.1 5.1.1 IT system architecture 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 current application map.
12
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 system, the programming language, the database used, the hardware type, the organizational unit responsible, 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 system manager takes all IT components in order to describe a system. This ensures that only IT components recorded and evaluated by the IT architect role are used and thus guarantees a high level of standardization.
13
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 specification of the respective role of the person or organizational unit.
14
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.
15
Figure 12: Display and specification of attributes in the Properties window
Heterogeneous IT landscapes are characterized by a multitude of interfaces between IT systems. Interfaces 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.
16
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 transmission 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 between the IT system landscape and the business processes. Each system is therefore specified in respect 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 specially for this purpose (Figure 14: Linking of system functions (capabilities) to an IT system
).
17
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.
18
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 Relationships 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 systems, 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 management (see chapter Table 16: Information architecture conventions Relationships ).
19
Figure 16: Representation of relationships using properties
20
5.1.3
Method details
The method conventions (model, object, and connection types) used in the above explanations are listed below. Model type Access diagram Application system type Hardware component type Document Technical term Organizational unit Group Person Cluster Location Architecture element Capability Application system type diagram Application system type Application system class Capability Program flow chart Application system type Cluster Protocol Service architecture diagram Zone District Capability
Table 3: IT system architecture conventions Models and objects
Object type
21
Model type Access diagram
Source object
Target object
Connection type
Application system type Application system type Application system type Application system type Application system type Application system type
Application system type Architecture element Architecture element Hardware component type Document Organizational unit
uses (IT component) is relevant for is not relevant for can run on creates output to is responsible for (attribute assigned(!)), e.g. Support type attribute System responsibility is responsible for (attribute assigned(!)), e.g. Support type attribute System responsibility uses can be located at supports
Application system type
Person
Application system type Application system type Application system type Application system type diagram Application system class Application system type Program flow chart Application system type Application system type Cluster Application system type Service architecture diagram Zone District
Cluster Location Capability
Application system type Capability
belongs to class supports
Application system type Cluster Application system type Protocol
transmits data to has output of is input for uses
District Capability
encompasses encompasses
Table 4: IT system architecture relationship conventions
22
5.2 5.2.1
IT technology architecture Roles
Architecture manager 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 architecture elements are assigned to each layer, which provides thematic refining. The individual architecture 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 business 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 infrastructure components may be found in this layer. Development: This layer includes programming languages, development environments, procedural models, etc.
23
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 representation of an individual architecture element, a model of the IT architecture matrix type is assigned. Architecture elements consist of 1-n IT components and/or architecture building blocks and cover specific 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.
24
Figure 18: Architecture element detail model Technologies can be structured by technology status. The IT architect defines the portfolio of IT components 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 assigned 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 depends on the value of the Standardization status attribute and the associated time intervals, if specified. This can be evaluated in text form and graphically by using a report or the Lifecycle management.
25
ARIS IT Architect - Application architecture 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 standardization 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 assigned to the IT component, such as major, minor, and bugfix releases.
26
Oracle
Oracle 8i
Oracle 9
Oracle 10g
Oracle 8.1.7
Oracle 9.2.5
Oracle 10.1
Figure 21: Versioning of an IT component
The objective is not only to manage, but also to standardize the IT components. To achieve this objective, 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
27
ARIS IT Architect - Application architecture Besides IT components of the Software or Hardware type, other IT components, such as development processes (RUP, V model, etc.) or standardized documents (e.g. security policies, project templates), 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.
28
ARIS IT Architect - Application architecture Reference architectures The objective of reference architectures is the re-use of concepts and software components. They provide 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 architecture 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.
29
ARIS IT Architect - Application architecture 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 consists 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 composition 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 components, but no architecture elements.
30
5.2.3
Method details
The model, object, and connection types used in the above explanations are listed below. The ITspecific attribute types are listed in a separate table in chapter Figure 68: Result of a . Model type IT architecture mapping Architecture layer Architecture element IT architecture matrix Architecture element Architecture layer Tier Application system class Application system type 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 Object type
31
Model type IT architecture mapping
Source object
Target object
Connection type
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 32 encompasses/belongs
Model type
Source object
Target object
Connection type to
Tier
Product/Service
Tier
Protocol
Tier
Function
Tier
Software service type
Tier
Document
Architecture layer
Table 6: IT technology architecture conventions Relationships
33
ARIS IT Architect - Process support map
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 required 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.
34
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 uniquely defined by these objects in the cell at the relevant intersection. The assignments are also included 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 example shown, the process support map (overall IT landscape view) is made up of column header objects of the Function type, row header objects of the Organizational unit and Location type, and assignment 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 schematically.
Figure 24: IT landscape method system
35
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 definition level. The process support type of a process support unit determines whether and, if so, what support is provided for a combination of row and column header objects.
36
ARIS IT Architect - Process support map 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 controlled 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
37
6.3
Roles
IT landscape planner 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 manner. High-quality assessment of the current organizational structure, business process model, and application 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, implementation, 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.
38
Figure 27: Process support map
39
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 landscape 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 update 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 deleting 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.
40
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 selecting 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 already 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)
41
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 connected to the corresponding organizational object by an is located at connection.
42
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 macros. 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 containing the model in which they are inserted.
43
6.5.2
IT landscape administration Complete matrix

Description Type of execution Event Visible to users / Yes
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
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.
44
6.5.3
IT landscape administration Copy content

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
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 model is impossible, an error message is displayed and the operation is canceled. The initial state is preserved. This macro can be used to prepare for merging or splitting process steps or functions.
45
6.5.4
IT landscape administration Adjust names

This macro adjusts the names of process support units according to the pattern 'Name of organizational unit/Name of function'.
Manual
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.
46
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 merely 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 update, 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 corresponding 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 automatically 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.
Description
Type of execution
Event
Visible to users
This macro updates the process support information Event/Manual 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 different points in time.
Open model
No
Special features The macro is started automatically when a map is opened. No new process support units are generated. 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.
47
6.5.6
Edit process support unit

Description Type of execution Event Visible to users Double click on PSU Yes
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
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 selected 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
48
49
6.5.7
Delete process support columns

Description Type of execution Event Visible to users Delete column or row using pop-up menu No
This macro supports fast deletion of all occurrences in a horizontal or vertical lane.
Event
Special features This macro is based on an existing default function, supplemented by a subsequent Save operation.
50
6.5.8
Remove IT system
Description Type of execution Event Visible to users Delete (select and remove) also using popup menu No
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 removed if the process support unit has occurrences in other models.
Event
Special features The macro also prevents functions, organizational units, locations, process support units and connections from being deleted. Thus, only the occurrences of the IT systems (application system types) including the attributes of the associated connections to the corresponding process support units can be deleted.
51
6.5.9
Add IT system
Description Type of execution Event Visible to users ObjOcc is to be moved ObjOcc is to be copied Object is to be copied No
This macro places or moves application systems. Optionally, 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 missing access privileges ensure data consistency.
Event
Special features In a process support map that is in Macro control operation mode, only IT systems (application system 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 account. For example, if the map is in the As-is IT landscape view, not all hidden systems may be visible. This macro also prevents process support units from being placed within a normal process support map.
52
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 become 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 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 indicating that the application systems are hidden in this process support unit. Manual / Event Visible to users Yes
Show IT system Description Type of execution This macro retrieves the connected application systems for each selected process support unit and creates occurrences of them in the process support unit. Manual / Event Visible to users Yes
53
Figure 33: Reduced view of process support map
54
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. Description Type of execution This macro updates the current process support map based on the selected 'process support type' and the 'analysis date'. Manual / Event Visible to users 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 traffic 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 todays 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.
55
ARIS IT Architect - Process support map 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.
56
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 users IT landscape administration Copy content This report cannot be run by users. The report is started by the macro of the same name. IT landscape administration Generate matrix This report cannot be run by users. The report is started by the macro of the same name. Edit process support unit This report cannot be run by users. The report is started by the macro of the same name. Add IT system This report cannot be run by users. The report is started by the macro of the same name. Macro No Macro No Macro No Macro No
57
6.6 6.6.1
Working in process support maps 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.
58
Figure 36: Edit process support unit macro 2 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.
59
ARIS IT Architect - Process support map The IT systems are now displayed in the corresponding cell.
Figure 37: Edit process support unit macro 3 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 category), 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.
60
ARIS IT Architect - Process support map 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.
61
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, operating 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 extent, e.g., due to outdated technology, but cannot be retired in the short or medium term for particular reasons. Investment is made here only in individual cases; the basic strategy is 'no investment'.
62
ARIS IT Architect - Process support map 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
63
6.7
Method details
The method conventions (model, object, and connection types) used in the above explanations are listed below. These are automatically used in Macro control operation mode and cannot be edited manually. 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.
64
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 Function Capability Service type Group Organizational unit Organizational unit type Person Person type Location Position Performance Application system type Table 7: Object types in Process support map model type Row header Assignments
65
6.7.2
Connections between PSU and cell objects in a map

Target object Process support unit Connection type belongs to process support unit
Source object Application system type
Table 8: Process support map conventions Connections I
6.7.3
Connections between PSU and column/row header objects in a map

Target object Process support unit Process support unit Process support unit Process support unit Location Capability Function Performance Service type Connection type can be user can be user can be user can be user can be located at supports supports supports supports
Source object Group Organizational unit Organizational unit type Person Process support unit Process support unit Process support unit Process support unit Process support unit
Table 9: Process support map conventions Connections II
66
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 automatically for analysis purposes when you place objects in a map. Source object Application system type Application system type Application system type Application system type Application system type Group Organizational unit Organizational unit type Person Person type Position Target object Location Capability Function Performance Service type Application system type Application system type Application system type Application system type Application system type Application system type Connection type is located at supports supports supports supports can be user can be user can be user can be user can be user can be user
Table 10: Process support map conventions Connections III
6.7.5
Name
Process support map model attributes

Meaning Complete As-is Plan To-be
IT landscape view
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 Last generated view 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. 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
67
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 Description/Definition Meaning 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
68
6.7.7
Connection attributes
These attributes control the traffic light colors for the lifecycle. Connection type belongs to process support unit State of process support Phased out To be phased out Start phase-out To be phased in Start phase-in Phased in Phase-in planned since Phase-in (plan) Start time of the planning to phase in an assignment. Planned date on which an assignment is to be phased in. Phased in since Phase-out planned since Phase-out (plan) Date of phase-in. Start time of the planning to phase out an assignment. Planned date on which an assignment is to be phased out. Phased out since To-be Date of phase-out. If the value true is maintained, the assignment defines a default support for the process support unit. Attribute Description/Definition Meaning The text characterizes the assignment.
Table 13: Process support map conventions Connection attributes
69
ARIS IT Architect - Organization architecture
7 Organization architecture 7.1 Roles
Process manager Architecture 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 organizational units as task performers and the links between them according to the selected structuring criteria.
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. Separate 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 assignment 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 Departmental 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 topologies 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 connections and network nodes, which may be found at particular locations of the company. The location of 70
ARIS IT Architect - Organization architecture 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 creating 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 bottom, 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.
71
ARIS IT Architect - Organization architecture
7.3
Method details
Object type 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
Model types Organizational chart
Table 14: Conventions for organization architecture
72
ARIS IT Architect - Information architecture
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 modeling ). 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
73
ARIS IT Architect - Information architecture
8.3
Method details
The method conventions (model, object, and connection types) used in the above explanations are listed below. Model type eERM Object type Cluster
Table 15: Conventions for information architecture - Models and objects
Model type
Source object
Target ject
ob-
Connection type
eERM
Cluster
Cluster
has link to
Table 16: Information architecture conventions Relationships
74
ARIS IT Architect - System functions, requirements, project and portfolio management
9 System functions, requirements, project and portfolio management 9.1 Roles
Architecture manager IT landscape planner 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 execution. The relation is illustrated in the following figure:
Process
Service, System
Requires
Process step
Provides
Capability Service
supports
Example
supports
calculate price
supports
Calculate price Invoicing
supports
EPC
Access diagram
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 systems 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.
75
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 functionality requirement.
76
ARIS IT Architect - System functions, requirements, project and portfolio management 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
77
ARIS IT Architect - System functions, requirements, project and portfolio management 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 placement of tasks on a timeline and the mapping of dependencies result in a detailed project schedule as shown in the figure below.
78
Figure 49: Example of a project schedule
79
9.3
Method details
The method conventions (model, object, and connection types) used in the above explanations are listed below. Model type Access diagram Object type Application system type Capability EPC Function Capability Application system type Requirements tree Requirement Target Requirement allocation diagram Requirement Capability Service type Application system type Component Function Cluster Technical term Organizational unit Group Person Target Risk KPI instance Document Work breakdown structure Function Task Program Project Requirement
80
Model type
Object type
Project schedule*
Task Person Organizational unit Location Application system type 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
Model type Access diagram EPC Requirements tree
Source object Application system type Function Requirement Requirement Target
Target object Capability Capability Requirement Requirement Requirement Application system type
Connection type supports supports encompasses is dependent on is supported by relates to
Requirement allocation diagram
Requirement
Requirement Requirement Requirement Requirement Requirement Requirement
Capability Service type Component Function Cluster Technical term
realizes realizes relates to relates to relates to relates to
81
Model type
Source object Requirement
Target object Organizational unit*
Connection type is technically responsible for
Requirement
Organizational unit*
is IT responsible for
Requirement
Organizational unit*
must be informed on cancellation
Requirement
Group*
is technically responsible for
Requirement
Group*
Requirement
Group*
Requirement
Person*
is technically responsible for
Requirement
Person*
Requirement
Person*
Target Requirement Requirement Work breakdown structure Task Project
Requirement Risk KPI instance Function Task
is supported by is exposed to is measured by is of type is process-oriented superior
Program
Project
is process-oriented superior
Task Project schedule* Organizational unit Person Task Quality gate Task Relationship
Requirement Task Task Quality gate Task Relationship Task
realizes carries out carries out creates activates has output of is input for
82
Model type
Source object Task Task Task Task Task Task Task
Target object Task Task Task Task Milestone instance Milestone instance Milestone instance
Connection type is predecessor of is successor of relates to belongs to creates activates 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
83
ARIS IT Architect - Reports
10 Reports
The information managed in the database can be evaluated in different ways. In addition to the conventional 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 Name Description IT architecture management Redundant applications 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 Output Objects (see below) 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 relationship to specific functions, capabilities, or data objects.
84
ARIS IT Architect - Reports Sample output Application system Capabilities Is additionally supported by A plan A plan A plan Order management Price calculation ProOn order processing ProOn order processing 1.0 1.0 2.0 Redundancy
Product data management ProOn order processing ProOn resource planning
ProOn
Bill of materials for CKD kits
0.0
ProOn
Billing of CKD shipments A plan
0.0 1.0 0.0 A plan 1.0 2.0
ProOn order processing Order management ProOn order processing Order tracing ProOn order processing Price calculation
ProOn order processing Product data management A plan ProOn resource planning ProOn resource planning Aggregation of amounts per part number and fixed date ProOn resource planning ProOn order processing Table 20: Sample result of the 'Redundant applications' report Product data management A plan
0.0
2.0
85
10.2 System evaluations

Category Name Description IT architecture management System evaluation Based on the application system types within the selected application system type diagrams, this report creates a system portfolio with regard to Data center costs and Criticality. Context Models Application system type diagram Value-added chain diagram 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
86
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 Category Name Description IT architecture management System list 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 Output Models, objects (see below) 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
87
ARIS IT Architect - Reports 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
88
10.4 Lifecycle management (report)

Category Name Description IT architecture management Lifecycle management Depending on the selected context, the report visualizes the lifecycle management of IT components (application system type) or IT system instances (application system). Optionally, this can be done in the form of a table output. For selected models or object occurrences it is also possible to color the occurrences contained in the model according to their current status. In addition, the occurrences can be reset to the default. Context Output Models, objects, and object occurrences; restricting contexts according to the object type (application system type or application system). 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.
89

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 instances 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 comparison date is indicated by an arrow ( macro in the model. Sample output for lifecycle management of IT system instances: ) in the output. The period under consideration can also be specified if desired. To obtain a coloring of objects in the open model, it is necessary to start the associated
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
90
10.5 Lifecycle management (macro)

Category Name Description Macros/IT architecture management Lifecycle management The 'Lifecycle management' report can also be started as a macro 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
91
ARIS IT Architec - Reports ct s
10.6 Disp play data flows a

Category Macros/IT a M architecture managem e ment Macro/IT ar M rchitecture manageme ent Name De escription Display data flows D a Using the D U Display data flows report, the user is able to create r e a table of data flows on the ba asis of one or more application e n system type This rep s es. port can also be run a a macro directly in as o n the model. The conve t entions des scribed in chapter 5.1 must be e adhered to. a
Figu 57: Co ure onnection assignme ent for spe ecifying IT system in T nterfaces In the table, all objects are output w with their n name, with the entries sorted alp s phabetically in the followy o tem, Conne ected syste ems, Data, Protocol an Direction nd n. ing order: Syst
92
ARIS IT Architect - Reports As a macro
Figure 58: Output of the Display data flows macro
As a report Connected sysSystem ProOn order processing ProOn order processing ProOn order processing ProOn order processing ProOn order processing ProOn billing --> MatReq/1 ProOn resource planning --> Order data DDF 567 --> MatReq/1 Material data DDF 567 --> A plan <-tems Data Protocol Direction
Figure 59: Output of the Display data flows report
93
10.7 System fact sheet

Category Name Description Report/IT architecture management System fact sheet 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.
94
ARIS IT Architect - Reports Sample output for system fact sheet:
ProOn order processing

System description: System name: ProOn order processing
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 system and provides functionality for CKD shipments.
Manufacturer of the application:
Proprietary system
Number of internal users:
Up to 1000
Number of external users:
Criticality (importance of the application system):
Very high
Individual development/Standard software:
Yes
Standardization status:
Standard
95
Individual development/Standard software:
Yes
Standardization status:
Standard
Contact (person): Name: John Smith
Telephone number:
+1-212-371-9435
E-mail address:
j.smith@unicorp.com
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
96
ARIS IT Architect - Reports 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
Process customer order Check credits
Process customer order Create customer order
Process customer order Create products
Process customer order Customer needs created
97
Customer needs created
Process customer order Fix and edit conditions
Process customer order
Process customer order Replicate customer order
Process 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
-->
ProOn resource planning
-->
ProOn billing
-->
98
ProOn Order Processing
A plan
ProOn Order Processing
ProOn resource planning
MatReq/1
ProOnBilling
Architecture set: Architecture layer Architecture element 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
99
10.8 System consolidation

Category Name Description Report/IT architecture management System consolidation This report enables you to analyze IT systems in terms of the process support they provide. The report analyzes business processes with regard to redundancies 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 redundant 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 supports 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.
100
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.
101
Figure 62: System portfolio analysis
To do this, it is necessary to mark the quadrant objects (application system classes) defined in the application 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.
102
Figure 63: Quadrant attribute of the application system class For the System portfolio analysis report to color-code IT system symbols correctly according to quadrant 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
103
ARIS IT Architect - Reports 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 according to their quadrant assignment (Figure 62: System portfolio analysis ).
104
105
ARIS IT Architect - Further examples for the analysis of data
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 analyzed, and the application managers concerned can be informed and get involved.
106
ARIS IT Architect - Further examples for the analysis of data
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 customizable 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.
107
ARIS IT Architect - Method details (attribute table)
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 (Conventions/Method), in the Method help, and in the Methods Manual. Object type Attribute type name/Attribute type group Programming language, Product/Service, Information carrier, Application system type, Operating system type, Cluster/Data model, DBMS type, Function, Technical term, Hardware component type, Hardware 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 development, In testing, In operation, In shut-down, Shut down, In planning Application system type, Operating system Standardization status type, Cluster/Data model, DBMS type, Technical term, Function, Hardware component class, Hardware component type, Information carrier, Product/Service, Programming language, Protocol 108 No standard, Standard, In evaluation, Rejected, To be phased in, Phased out, Requested for standard, To be phased out, Standard - limited use Attribute values
Object type
Attribute type 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 development
Yes, No
109
Object type
Attribute type name/Attribute type group Maximum downtime
Attribute values
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, Product/Service, Application system class Application system, application system type Network node
Architecture element (*)
Port 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 assigned application system types are databases.
110
ARIS IT Architect - Glossary
13 Glossary
Architecture set
The architecture set forms the approach to, and the framework for, standardized IT architecture management. 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 architecture layers. They therefore represent the link to the IT standards. Architecture elements can be divided 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 architecture 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 infrastructure 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 particular (business) tasks. IT systems or their functions always support a process, and are themselves supported by IT components.
111
ARIS IT Architect - Glossary
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 architecture.
112

Aris - User Guide It Architect S en

Diunggah oleh

Informasi Dokumen

Judul Asli

Hak Cipta

Format Tersedia

Bagikan dokumen Ini

Bagikan atau Tanam Dokumen

Opsi Berbagi

Apakah menurut Anda dokumen ini bermanfaat?

Apakah konten ini tidak pantas?

Hak Cipta:

Format Tersedia

Aris - User Guide It Architect S en

Diunggah oleh

Hak Cipta:

Format Tersedia

ARIS IT Architect User Guide

ARIS IT Architect - Contents

IT technology architecture ......................................................................... 23

Method details ......................................................................................... 64

Information architecture ..................................................................................... 73

System functions, requirements, project and portfolio management ......................... 75

Further examples for the analysis of data ............................................................. 105

Method details (attribute table) .......................................................................... 107 Glossary .......................................................................................................... 110

ARIS IT Architect - Figures

ARIS IT Architect - Tables

ARIS IT Architect - Introduction

ARIS IT Architect - Enterprise Architecture Management (EAM)

2 Enterprise Architecture Management (EAM)

ARIS IT Architect - Enterprise Architecture Management (EAM)

EAM as part of IT management

Figure 3 : ARIS IT Architect - Relevant IT processes

ARIS IT Architect - Enterprise Architecture Management (EAM)

Roles in Enterprise Architecture Management

ARIS IT Architect - Architecture levels in IT architecture management

3 Architecture levels in IT architecture management

ARIS IT Architect - Architecture levels in IT architecture management

Figure 5: Comparison of IT system and IT components architecture

ARIS IT Architect - Business processes

4 Business processes 4.1 Roles

Process managers IT landscape planner

ARIS IT Architect - Business processes

Figure 6: Navigation and assignment

ARIS IT Architect - Business processes

Figure 7: Representation of an EPC section

ARIS IT Architect - Business processes

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

ARIS IT Architect - Business processes

Function Function Function Function Function Function

ARIS IT Architect - Application architecture

5 Application architecture 5.1 5.1.1 IT system architecture Roles

Application system manager IT architect Architecture manager

ARIS IT Architect - Application architecture

Figure 9: IT systems (domain view)

ARIS IT Architect - Application architecture

ARIS IT Architect - Application architecture

Figure 11: Assignment of attributes to connections

ARIS IT Architect - Application architecture

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

ARIS IT Architect - Application architecture

Figure 13: Interface modeling

ARIS IT Architect - Application architecture

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

ARIS IT Architect - Application architecture

ARIS IT Architect - Application architecture

Figure 16: Representation of relationships using properties

ARIS IT Architect - Application architecture

ARIS IT Architect - Application architecture

Model type Access diagram

Application system type

Cluster Location Capability

Application system type Capability

belongs to class supports

Application system type Cluster Application system type Protocol

transmits data to has output of is input for uses

Table 4: IT system architecture relationship conventions

ARIS IT Architect - Application architecture

IT technology architecture Roles

Architecture manager IT architect