/

Definition

A software solution that provides functionality for the organisation or the IT environment.

Description

Application is an object in the IT landscape – something that is. It is classified by type as Business application or Infrastructure application.

Identifying key

Key
Application ID
Defined by
The application catalogue
Example
APP-003

Assigned when the application is registered in the catalogue and kept across versions.

The key identifies the object but is not the object. It should be stable over time and never carry meaning that can change.

Application type

The types below are classifications of Application, not separate information building blocks.

  • Business application

    An application that primarily supports the organisation's processes, functions or information management.

    Examples: finance system, CRM, HR system, case management system

  • Infrastructure application

    An application primarily used to support, administer, monitor or enable the IT environment.

    Examples: solutions for monitoring, backup, identity management and technical administration

Architecture role

The types below are classifications of Application, not separate information building blocks.

  • Client application

    An application with a user interface installed on or streamed to an operating system on the user's device. It connects to zero, one or several backend applications; without a backend it uses only the local operating system.

    Examples: finance client, mobile app for field work, web browser, terminal emulator, PDF reader

  • Backend application

    An application that runs centrally and holds the organisation's information and business logic. Web and terminal-based systems are reached through an installed web browser or terminal emulator and have no client part of their own.

    Examples: finance system, medical records system, e-mail service, web application

Has access right

The application provides one or more access rights.

Managed by unit

The application is owned and managed by exactly one unit in the organisation tree. Its operating, support and base licence costs are charged to the unit's base cost center.

  • ApplicationManaged by unit →Unit

Connects to backend

The client application is the interface to a backend application where the information lives.

Supports process

The application supports one or more processes. General tools may have no process link.

  • ApplicationSupports process →Process

Relationships from other areas

Application is the shared information object that other building blocks point to – the meaning lies in the relationship.

  • AccountExists in →Application

    The account exists in a specific directory service or application.

  • EmployeeManagerOwns application →Application

    Application owner is a process role held by an employee or a manager.

  • OrganizationPublishes application →Application

    The organisation has developed and owns the software. Can be an external organisation or the own one for in-house development.

  • Process roleNeeds application →Application

    The process role needs the application as a tool in its work. Drives deployment and licence, not access rights.

  • Business serviceSupported by application →Application

    Shows which applications support or digitally deliver the business service.

  • EmployeeAssigned application →Application

    The employee gets access to the application based on internal position and unit.

  • ManagerApproves access →Application

    The manager, derived through the manager code, approves requested access for their employees.

  • Cost centerBears licence cost →Application

    The cost center bears the cost of the application's licences.

Reference data

Reference data referring to Application.

Internal code list

IT environment

Property: IT environment

Internal code list for the logical or physical environments where applications are used or run.

PROD · TEST · DEV

View code list

Internal code list

Application architecture

Property: Application architecture

Internal code list for how an application is built: client only, client and backend, or backend only reached through a browser, terminal or machine to machine.

STANDALONE · CLIENT_SERVER · WEB_APPLICATION · TERMINAL_APPLICATION · SERVICE_API

View code list

Internal code list

Client type

Property: Client type

Internal code list for how a client application reaches the user.

INSTALLED · MOBILE · VIRTUAL · ADDIN

View code list

Internal code list

Platform

Property: Platform

Internal code list for operating system or runtime.

WINDOWS · MACOS · LINUX · IOS · ANDROID

View code list

Internal code list

Assortment level

Property: Assortment level

Internal code list for how an application is offered at the workplace.

BASE · SELF_SERVICE · ORDER · SPECIALIST

View code list

Internal code list

Software lifecycle status

Property: Lifecycle status

Internal code list for whether a version may be used.

STANDARD · ALLOWED · DEPRECATED · PROHIBITED

View code list

Internal code list

Licence model

Property: Licence model

Internal code list for how the licence is counted.

NAMED_USER · DEVICE · CONCURRENT · SITE · OPEN_SOURCE

View code list

External code list

UNSPSC

Property: UNSPSC classification

External, global code list for categorising products in four hierarchical levels: segment, family, class and commodity. Maintained by GS1 US. Used here to classify Product and Application – never Business service. Software is classified in the information technology segment, so applications can be linked to purchasing, contracts and licences. The classification is separate from identity: a changed UNSPSC code never creates a new product or application. Code values are not listed here but retrieved from the source.

View code list

Source Governance

Source governance describes where information should come from. Source rules are defined centrally and shown here where they concern Application.

Used in information patterns

Business rules