Author: vpadmin

In this ArchiMate model, a junction is used to denote an or-split (choice).

In the ArchiMate diagram example here, the grouping relationship is used to group business objects that belong to the same information domain, in this case Financial administration.

The ArchiMate diagram example here shows a Claim assessment business function, which forwards decisions about the claims to the Claim settlement business function. In order to determine the order in which the claims should be assessed, Claim assessment makes use of schedule information received from the Scheduling business function.

The ArchiMate diagram example here illustrates that triggering relationships are mostly used to model causal dependencies between (sub-)processes and/or events.

The ArchiMate diagram example illustrates a number of uses of the association relationship.

The ArchiMate diagram example here illustrates the access relationship: the Create invoice sub-process writes/creates the Invoice business object; the Send invoice sub-process reads the Invoice business object.

The ArchiMate diagram example here illustrates two ways to use the realization relationship. An application (component) Financial application realizes the Billing service (application); the Billing data object realizes the business object Invoice.

The ArchiMate diagram example here includes the two ways to express the assignment relationship. The Payment function (application) is assigned to the Financial application (component), and the Payment service (application) is assigned to the Application interface.

This ArchiMate diagram example shows the two ways to express that the product Car insurance aggregates a contract (Policy) and two business services.

This ArchiMate diagram example shows the two ways to express that the application component Financial application is composed of three other application components.