Diamond Do explains how to design and offer a service in multicontextual environment. This diamond is very complex and it is needed to take to account that the diamond is three dimensional. The diamond's third dimension is made up of agent and model elements, which are in an upper layer above other elements and interact with each of them.
Closer analysis of agent element is possible with diamond Organize. The model element serves for recording all steps and results when analazing and designing a service. The vertical axis of the diamond represents service creation. The service is created to solve the requirements that are part of the fulfillment of the goal. This relationship is important for the system to be resistant. Many stakeholders tend to protect the service in the event of a change or a problem, instead of protecting the requirements and goals that create those requirements. Requirements are the central point of the Do diamond. The horizontal axis of the diamond helps to better understand the adaptability of the system and describing its contextual behavior. It is based on the context in which functional requirements - use cases - are identified. If a service is to be useful, we must look at it from a contextual perspective, because services can influence each other in different contexts. It is important to keep the context, use cases (horizontal axis), agents and model in concrete connections with given requirements, goals and services (vertical axis) because only together they create a true picture of predictable agent behavior. This highlights the second name of the Do diamond, which is the Diamond of Predictive Behavior.
Agent
One or more agents which are connected with other elements of the diamond (all blue lines)
Requirement
Requirement that was created by the agent's will. Requirements are the central point of the Diamond
Goal
Goal for requirement creation. Requirement fulfills the goal (connection through "fulfilling" line)
Service
A set of solutions (services) with the help of which the request can be solved (connection through the "solved by" line).
Context
A set of environments (contexts) in which a request can be identified (linking through the "occurring within" line). It also defines whether a specific goal can be achieved in a given context (connection via the "achievable within" line) or a service created (connection via the "creatable within" line).
Use case
A set of implemented solutions (functional requirements) that provide value to users. These solutions shape the request or are shaped by it ("forming/formed by" connection). Use cases are defined in the current or other context (linking through the "identified within" line). They help create services, and services help create them ("creatable by" line). They are also used to achieve a specific goal (connection through the "achievable by" line).
Model
An element that is used to record all the steps taken to serve as a model. It is connected to the other elements of the diamond (all red lines). It is created gradually from the beginning and is completed only last. The model can have several components and different forms.
-composite lines
Lines that can be used for closer analysis of a specific element.
-BS lines
Lines that allow the breakdown of a particular element into a hierarchical structure.
R0n-lines
Selected elements may fulfill the role of a request in another context.
Rnn-lines
A specific element may also appear in another context.
TODO