Document the application and information portfolio

MM_ApplicationInfoArch 

Establish a structured and reliable application portfolio to support an effective APM practice. Capture detailed information about every application in use to ensure strategic decisions are based on accurate, comprehensive data. Document each application's lifecycle, define its stakeholders, and evaluate its performance using preconfigured indicators to identify optimization opportunities and reduce risk.

Describe the information context of your application portfolio by capturing the relationships between applications and the data they exchange. Documenting information flows allows you to trace how information is used across the enterprise and uncover redundancies. Structure your portfolio by creating application groups and assigning applications to them for targeted analysis.

NUMB_1 

Capture information about your applications. All applications should be documented to ensure that the application portfolio is reliable to make good strategic decisions. Define the application stakeholders, the lifecycle of each application, and evaluate the applications based on preconfigured indicators.

NUMB_2 

Capture information about the application's relevance for the business. Document which business capabilities the applications provide, which business processes the applications support, etc.

NUMB_3 

Add application groups to the repository. Assign applications to the application groups for portfolio analysis.

NUMB_4 

Describe the information context of the application portfolio. Document the information flows between applications and the business objects that the information flows transfer.

Alfabet supports two use cases to manage the exchange of data. . The use cases Basic Data Management and Advanced Data Management are mutually exclusive and only one may be enabled. The use case Basic Data Management is available per default. The Advanced Data Management use case must be enabled by your solution designer.

With the Basic Data Management use case, Business Object Categories and Business Objects data workbenches can be accessed via the navigation pane. The transfer of data by information flows is captured via business objects, which are at the leaf level of the business object category > business object hierarchy. Data attributes and CRUD (Create, Read, Update, Delete) operations are captured for the business object.

The use case Advanced Data Management focuses on business data as the key asset to understand where data is stored, how it is transferred, and how it is used so that your company can ensure compliance with data protection regulations and enforce data governance policies. Business data are concrete, logical instances of business objects, which represent an abstract entity such as a customer or employee. For example, the high-level business object Employee might have two different business data Employee HR and Employee Reporting.

The Advanced Data Management use case adds the class Business Data to the leaf level of the hierarchy Business Object Category > Business Object > Business Data. Please note the following: