EA - IT Portfolio Management > Drawing up an Application Inventory > Defining the Properties and the Environment of an Application > Defining Application Functional Scope
Defining Application Functional Scope
To indicate the objects that define application functional coverage:
1. Open the application properties.
2. Click the Characteristics page.
3. Expand the Functional Scope section.
*A report covers functional characteristics of a list of applications. See Inventory Portfolio Reports.
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.
• process categories and processes which use the application
*A process category defines a group of processes. It is linked to a Process Map or higher level Process Category. It regroups several processes and/or other categorized elements (e.g. Value Streams, Applications). It serves as an intermediate categorization level in the process hierarchy, so as to provide a guided and progressive access to finer grained processes.
*For more details on the list of available process categories, see Defining the Process Categories.
*A process is a set of operations performed by org-units within a company or organization, to produce a result. It is depicted as a sequence of operations, controlled by events and conditions. In the BPMN notation, the process represents a sub-process from the organizational point of view.
• The business capabilities covered by the application.
*For more details on business capabilities, see Defining Business Capabilities.
*An indicator enables to display the list of applications which are not connected to any business capability. See Scope Indicators.
• functionalities implemented by the application
*A functionality is a service required by an org-unit in order to perform its work. This functionality is generally necessary within an activity in order to execute a specific operation. If it is a software functionality, it can be provided by an application.
This data is used in the “Application Overview” and “Application Environment Graph” reports of the application.
Connecting a functionality to the application
To create a functionality and connect it to the application:
1. In the Functional Scope section, select Implemented Functions.
2. Click the + New button.
The new functionality appears in the list of functionalities of the application.
To connect an existing functionality to the application:
1. In the Functional Scope section, select Implemented Functions.
2. Click the Connect button.
The search wizard appears.
3. Click the Find button.
The list of repository functionalities appears.
4. Select the required functionality.
5. Click Connect.