Capture application group data

Because running applications usually constitute the largest part of IT spending, application portfolio governance is crucial to containing costs and to ensuring that the IT support to the business is consistent and reliable.

Application portfolios are defined in Alfabet via application groups that bundle applications. Each application can be assigned to multiple groups. The applications should be bundled in application groups that are relevant to the goals for the portfolio assessment process. For example, applications could be logically structured in application groups according to:

Alfabet allows you to evaluate and analyze applications in the context of various application portfolios in order to understand the technical and information architectures relevant to the applications, the use of the applications by the business as well as application costs, failure rates, and risks. Analysis is based on preconfigured indicators used to evaluate the applications as well as business questions to help you understand the use, performance, and criticality of the application portfolio in the IT landscape.

You can add a new application group from anywhere in the product via the orange New button in the header. Or go to Application Architecture > Application Groups:

Try to capture as much information as possible about the application because complete data considerably improves the results of business questions and other analytics.

Once an application group is in the repository, you can define more details about the application groups in the Application Groups data workbench . Or you can select an individual application group and navigate to its content area and specify and analyze the application in detail. In the data workbench, click the Navigate  Navigate button to open the application group's content area. Go to the Overview page.

Per default, the data workbench displays only a set of basic attributes. You can add more columns to capture other attributes directly in the data workbench via the Structure column or you can navigate to an application group's content area and define it in more detail there. Click to learn about how to use data workbenches.

Applications must already be in the repository in order to assign applications to an application group. Some business questions in Alfabet can only be answered if the relationships between applications and application groups are defined. Click to find out how to capture application data.

Application groups logically structure and bundle the applications and allow you to assess the technology portfolio. You can assign applications to multiple application groups in order to analyze your applications from various perspectives.

Click the navigate Navigate button of the application group to open the content area. Go to Overview > Asset Grouping. In the Applications field, enter the name of the application you want to assign to the application group. Or click in the field to open the selector and select each application that you want to assign to the application group. Click outside of the selector to close it and update the Asset Grouping field.

In Alfabet, responsibilities are documented via the concept of roles , whereby each role is based on a preconfigured role type or a custom role type defined by your company. In contrast to an authorized user who has read/write permissions, a person assigned a role for an asset will not have read/write permissions based on the role definition. The role is primarily for documentation purposes to provide information about stakeholders interested or responsible for the asset. If the user should have read/write permissions, they must either be the authorized user of the asset or assigned to an authorized user group associated with the asset.

Alfabet provides out-of-the-box role types that enable you to understand who is responsible for your IT assets in your IT portfolio. Additional role types that are relevant for your company can also be added.

Assigning users and organizations to roles is critical to understanding responsibility for assets in the IT and is required to answer the business question Who is responsible for our assets?

To define the users and organizations that have a role for an asset, click the navigate Navigate button of the asset you want to define. Go to the Overview page and scroll to the Responsibilities view and open it. Click in a column cell to open a selector to define a role for the asset. Depending on the role column, you may be able to select a person or an organization. Switch between Person or Organization in the selector.

A person can have one of the following roles or a custom role added by your company:

  • Architect: A person who is responsible for the governance of the asset.
  • Business Owner: A person or organization that owns the asset and is responsible for managing the functional requirements.
  • IT Owner: A person or IT organization that owns the asset and thus typically responsible for approval decisions.
  • Stakeholder: A person or organization that has an interest in the asset and therefore requires read-only access permissions.

An organization can have one of the following roles or a custom role added by your company:

  • Business Owner: A person or organization that owns the asset and is responsible for managing the functional requirements.
  • IT Owner: A person or IT organization that owns the asset and thus typically responsible for approval decisions.
  • Operations: An IT organization responsible for the operations of the asset.
  • Stakeholder: A person or organization that has an interest in the asset and therefore requires read-only access permissions.

The following business questions are relevant for the analysis of application groups: