Describing Applications
To access characteristics that enable identification of an application:
In the properties pages of an application, select
Characteristics.
General characteristics of the application
You can specify:
• application Name
• the internal Code
Type of application
Technologies can be of the following types:
• Office system
• In House Application
• Middleware
• Office System
• System
Functional scope of the application
To view the objects that define the functional coverage of an application:
In the application properties pages, select
Characteristics then
Functional Scope.
The types of data that define functional coverage of the application are:
• The business lines that use the application
A business line is a high level classification of main enterprise activities. It corresponds for example to major product segments or to distribution channels. It enables classification of enterprise processes, organizational units or applications that serve a specific product and/or specific market. Regulation frameworks of certain industries impose their own business lines.
• The business processes that use the application
A business process represents a system that offers products or services to an internal or external client of the company or organization. At the higher levels, a business process represents a structure and a categorization of the business. It can be broken down into other processes. The link with organizational processes will describe the real implementation of the business process in the organization. A business process can also be detailed by a functional view.
• The business capabilities covered by the application
A business capability is a component of information system processing. Processing can for example correspond to an activity or an enterprise business.
Responsibilities concerning an application
Local application owner
An application owner is responsible for managing the application throughout its lifecycle. The application owner ensures that the application is correctly defined.
The term "owner" identifies a person or an entity who has accepted responsibility for creating, maintaining and using assets. This term does not mean that the person that person has, strictly speaking, ownership rights over the asset.
To specify one or more owners:
1. In the properties page of the application, expand the Responsibilities section.
2. Select the Local Application Owner and connect one or more users.
Local IT Risk Manager
The "Local IT Risk Manager" is the local contact for risk at the application level.
The applications that are linked to a Local IT Risk Manager local or local application owner appear in the
Home navigation tab, in
To-Do list > My Responsibilities > My IT Assets.
Technologies linked to applications
In the properties page of an application, you can connect existing technologies or create new technologies.
To access technologies from an application:
In the properties page of an application, expand the
Technologies section.
Data exchanged
This information is derived from HOPEX IT Portfolio Management.
Flows, their direction and their content exchanged between applications can be defined. This information enables creation of exchange mapping.
A message flow is information flowing within an enterprise or exchanged between the enterprise and its business environment. A message flow can carry a content.
Business data represents the content of a flow.
A business data indicates content of a message flow. A Business data can be used by several message flows, since it is not associated with a sender and a destination. The same business data can be used by several message flows.
Vulnerabilities of an application
To view the vulnerabilities of an application:
In the application properties page, select the
IT Risks page then expand the
Vulnerabilities section.
Controls connected to an application
To view the controls for an application:
In the application properties page, select the
Controls page.