IT technology architecture

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:

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, thus providing thematic refinement. 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:

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 shown 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 IT systems (see chapter IT system architecture). Using occurrence copies in access diagrams raises the degree of IT architecture standardization since only technologies specified in IT libraries can be used to describe new IT systems.

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 wherever possible.

The type and naming of the IT component libraries are determined by the architecture elements defined in the architecture set. For every architecture element that is created in the architecture set, a model of the IT architecture matrix type is generated and assigned, which describes the architecture element in more detail.

In the following figure the management of database systems is represented. Each of the IT components listed provides information on manufacturer and version, links to manuals, etc., and can be reused in various views.

IT components have a colored symbol indicating the status of the standardization. The coloring depends on the value of the Standardization status attribute or on the associated time intervals, if specified. This can be evaluated in the form of text or graphics by the Lifecycle management report or macro.

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

To be able to assign time intervals to the states it is possible to document the duration of individual phases in the standardization cycle by using attributes of an IT component.

Individual versions of an IT component, such as major, minor, and bugfix releases can be managed in an application system type diagram assigned to the IT component. 

The objective is not only to manage, but also to standardize IT components. To achieve this objective, IT components must be examined, for example, with regard to their penetration (impact analysis). For this purpose, the Relationships tab provides initial information, such as a list of all IT systems that depend on an IT component (see chapter Reports). Thus, navigation across the various levels of the corporate landscape delivers all information required for standardizing the elements. In the following figure, IBM DL1 is set to the status To be phased out, for example.

Besides IT components of the Software or Hardware type, other IT components, such as development processes (RUP, V model, etc.) or standardized documents (for example, security policies, project templates), can be managed. 

The objective of standardization is the reduction of maintenance 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.

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 meet these specifications with regard to design principles, infrastructures, and technologies.

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

A reference architecture is a set of architecture building blocks and IT components. Reference architectures are represented in models 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.

Architecture building block

Architecture building blocks consist of 1-n IT components (possibly of different architecture elements) and have the following properties:

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 multiple IT components and can be used repeatedly in modular form.

Architecture building blocks are thematically subdivided into:

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 reference architectures, comprises only layers, tiers and their IT components, but no architecture elements.