This is the development of a products and services catalog for application services that are offered to the environment within and outside the organization.

Naming Conventions Usage: Noun in the ing form. For example: Transaction processing, Indexing.

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.

Office automation is an application service that supports almost every role in an organization in their daily work. Namely offering functionalities such as word processing, creating presentations and the like.

This is about an application service and the link to a business function

Statement Services are the description of a combination of functionalities and services between provider(s) and customer(s). Description Services are a form of encapsulation of the functionality and implementation of a composition of building blocks. Services, just like ABB and SBB, are used as a means of communication between provider and customer to indicate which service will be provided by the provider to the customer. Services can also be defined internally within the organization (also in a provider and customer context), for example infrastructural services for an application service or customer. A service can be a composition of a building block that implements functionality within the ICT landscape. In addition, a service can consist of providing more structured (ICT) work processes in relation to the above-mentioned IT landscapes, for example a service desk. In this document we have limited the scope to that of the ICT architecture, ICT work processes are not elaborated here but are certainly relevant within other parts of the organization (service management). This building block model can be applied in several ways if desired and not only in the IT field. Here we limit ourselves to ICT architecture. Services can be composed of underlying services. In addition, they can be composed of one or more architectural building blocks. These compositions can create constellations of building blocks that ensure standardization of reusable applied services. Consider a standard application server with services (such as backup and restore) and ABB (for example relational storage) Services are related to requirements, constraints and principles. This is preferably elaborated to indicate which needs are met from a customer perspective and which are not. There is a lot of confusion around the term service. To avoid a discussion about the definition with each composition of persons, the term service is chosen, which is based on the characteristics below. In addition, a list of synonyms has been formulated that refer to the same characteristics below. Characteristics

• A repeatable activity or behavior that is requested to be performed.
• A service offers one or more solutions to ICT needs that are understandable to the customer.
• Combination of an implementation of a functionality in one or more ABBs.
• Possibly in combination with one or more ICT work processes as a service.
• Services are offered to customers by providers.
• Services have a commercial and a financial (cost) aspect.
• Services have conditions for use and/or implementation.

Application service for creating, managing and editing texts and documents.

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.

The composite service model shows how a service at a higher level of abstraction is composed of smaller services with a more specific character. This office automation model includes an intermediate layer of services, but that is not necessary, you could also make a direct link to Microsoft Office, depending on the context. In this elaboration, only application services are modeled and included in the composition. However, in addition to application services, you can also define business services here. Consider the combination of the implementation of Office and a service desk for questions in case of problems. That is currently out of scope, but will become relevant at some point. Relevant here is that this creates a bottleneck in the ArchiMate modeling. If desired, this bottleneck can be resolved with serving relationships. Embedding ICT business services in the lower architectural layers.

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.