This ArchiMate diagram example describes the relationships between applications components in terms of the information flows between them, or in terms of the services they offer and use. This example creates an overview of the application landscape of an organization and expresses the (internal) co-operation or orchestration of services that together support the execution of a business process.

This ArchiMate diagram example describes the internal behavior of an application; e.g., as it realizes one or more application services. This viewpoint is useful in designing the main behavior of applications, or in identifying functional overlap between different applications.

This ArchiMate example depicts the value that these products offer to the customers or other external parties involved and shows the composition of one or more products in terms of the constituting (business or application) services, and the associated contract(s) or other agreements. It may also be used to show the interfaces (channels) through which this product is offered, and the events associated with the product. A Product viewpoint is typically used in product development to design a product by composing existing services or by identifying which new services have to be created for this product, given the value a customer expects from it. It may then serve as input for business process architects and others that need to design the processes and ICT realizing these products.

This ArchiMate diagram example shows the relationships of one or more business processes with each other and/or with their environment. It can both be used to create a high-level design of business processes within their context and to provide an operational manager responsible for one or more such processes with insight into their dependencies. Important aspects of business process co-operation are:

1. Causal relationships between the main business processes of the enterprise
2. Mapping of business processes onto business functions
3. Realization of services by business processes
4. Use of shared data

Each of these can be regarded as a "sub-view" of the business process co-operation view.

The ArchiMate example shows the high-level structure and composition of one or more business processes. Next to the processes themselves, this viewpoint contains other directly related concepts, such as:

1. The services that a business process offers to the outside world, showing how a process contributes to the realization of the company’s products
2. The assignment of business processes to roles, which gives insight into the responsibilities of the associated actors
3. The information used by the business process

Each of these can be regarded as a "sub-view" of the business process view.

This ArchiMate diagram example shows the main business functions of an organization and their relationships in terms of the flows of information, value, or goods between them. Business functions are used to represent the most stable aspects of a company in terms of the primary activities it performs, regardless of organizational changes or technological developments. Therefore, the business function architecture of companies that operate in the same market often exhibit close similarities. The business function example provides high-level insight in the general operations of the company, and can be used to identify necessary competencies, or to structure an organization according to its main activities.

This ArchiMate diagram example puts an organization into its environment, consisting of external parties such as customers, suppliers, and other business partners. It is very useful in determining external dependencies and collaborations and shows the value chain or network in which the actor operates.

This ArchiMate diagram example describes on the (internal) organization of a company, a department, a network of companies, or of another organizational entity. We present models in this example as nested block diagrams, but also in a more traditional way, such as organizational charts.

The ArchiMate model here illustrates the use of the specialization relationship for a business process. In this case the Take out travel insurance and Take out luggage insurance processes are a specialization of a more generic insurance take out process.