What are the relevant application functions to support the stated work processes. These can then be linked to modules in the architecture tool or to requirements (during a selection process).

An encapsulation of application functionality aligned to implementation structure, which is modular and replaceable. It encapsulates its behavior and data, provides services, and makes them available through interfaces.

Naming Conventions Usage: verb. Example: Billing, Search, Indexing.

Description of the available or desired application functions within the scope of the architecture. Usually related to the description of the application landscape.

Example of a logical architecture model for a registry or MDM module. Provides an example of how you can combine application functions, interfaces and services in ArchiMate to describe the desired requirements. If you look at an architecture repository from the perspective of master data, you can actually use a number of building blocks to describe functionalities, application services and interfaces in a generic way.

Application functionality that supports Data Management and governance processes. Consider data quality processes, data ownership and data security policies, etc.

Based on the relevant application functions, determine which parts of the tool need to be configured in order to effectively use the tool as an architecture repository.

Goal : Providing insight into the relationship between applications and parts of applications and which application functions they realize. Obliged Landscape of the relationship between different applications. Use the Application layer of ArchiMate for this and use two types of views: the logical application view (application functions) and the implementation view with application components.

Description of the components and functionalities present within Enterprise Architect related to the hierarchy of application functions. The functions are in detail described in the previous chapter.

Goal : Providing insight into the relationship between applications and parts of applications and which application functions they realize. Obliged Landscape of the relationship between different applications. Use the Application layer of ArchiMate for this and use two types of views: the logical application view (application functions) and the implementation view with application components.

This model is relatively simple in design, there is an application service that is completed by one logical application function. However, in other situations this can be a more complex composition. If a register or portfolio is drawn up for the architectural building blocks, this is an additional form of aggregation. An alternative is to aggregate and group via the service portfolio. Is a point of discussion.

Enumeration and hierarchy of relevant application functions when working with an architecture repository. In other words, necessary functionalities for a tool to be selected for a repository.

This logical application model views the architecture repository as a master data registry and names the relevant application functions and interfaces that are relevant from the master data perspective and therefore also for an architecture repository. Each element is briefly described and provides an idea of which elements are relevant in its own context. Because in the initial situation of introducing an architecture repository, not all concepts will be relevant. However, with further development of working with an architecture repository, the register will increasingly fulfill a master data function in the application landscape of the organization.

Example of a logical architecture model for a registry or MDM module. Provides an example of how you can combine application functions, interfaces and services in ArchiMate to describe the desired requirements. If you look at an architecture repository from the perspective of master data, you can actually use a number of building blocks to describe functionalities, application services and interfaces in a generic way.