Name: Interaction template

Reference: A template for describing the interactions included in the Interaction Dictionary.

Need to Act?

Due to "unfinished collaborative planning" and "process documentation" journeys of many organisations, interaction repositories (for instance, such as the Interaction Dictionary) are often missing.

Often the process modelling is part of the requirements engineering, but the resulting models are not an integral part of the process and solution documentation.

If this situation looks familiar to you, then check the Blueprint section and the #2030library case.


Name Name of the interaction
Domain Domain of the interaction. The domain is expressed via one or more hashtags from these topic dimensions: economic activities (isic), sustainable development targets (sdg or sdt), functions of government (cofog), and Addis Ababa Action Agenda (aaaa).
Target Outcome The high-level end results that must be achieved by the interaction.
See also outcome (Ens Dictionary).
Social actors and roles The social actors and roles that are typically involved in the interaction.
If the actor or role is described in the Actor Atlas then its page will be referenced.
Trigger or preceding interaction The event that triggers an interaction, or the interaction or process that precedes the interaction. If either the event or the interaction has a separate page in the Interaction Dictionary, then it will be referenced.
Interfaces and services The interface specifies how the service can be accessed by other social actors in the environment where the interaction is prevalent.
Often the interface will be the place where events trigger the interaction. An event typically carries a token.
Inputs and outputs Inputs are tokens that the interaction obtains or receives from its "customer roles", and outputs are tokens that it provides or delivers to them.
Stores and tools Stores such as Repositories, and tools such as Services and Tokens that are typically used in the interaction so that it can provide or deliver its services and outputs.
Other characteristics
Part of Another interaction of which the defined interaction is a part
Parts Other interactions that are part of the defined interaction
Succeeding Interactions Interactions, these could be more than one, that may typically succeed the interaction
Alternatives Similar outcomes may result from different interactions. In such a case, those interactions would be considered alternatives, one for the other
Action Realm One of the three realms in which an interaction is positioned Operations, Monitoring & Evaluation or Change.
Risks The risks that are typical for the interaction and should be monitored.
Further reading

Further reading about the interaction.

For the meta-model supporting the definitions in this template, see the work system pattern (interaction = Event(s) chain or bundle) and the business service pattern (token=Business Object).

For the systems engineering optimizations that are pursued by means of the Interaction Dictionary, see [1]


The Interaction Dictionary provides completed interaction templates for a small number of "abstract" interactions. As part of the Partner livelihoods chapter of some requirements engineering cases the templates will be completed for more concrete interactions.

Variants: business use case (BUC) template and product use case (PUC) template

Call to Action - #ACT4SDGs

In the #2030library case we will demonstrate how the process documentation is built up as part of the Interaction Dictionary, and how requirements articulation for the library stakeholders proceeds via annotations with respect to the interaction (or process) models. The annotations per stakeholder are elaborated in the #2030library case.

1. Jan BM Goossenaerts, Alexander T.M. Zegers, J. M. Smits: A multi-level model-driven regime for value-added tax compliance in ERP systems. Computers in Industry 60(9):709-727 · March 2009 DOI: 10.1016/j.compind.2009.05.013