Relationship Model
– Visualize and Describe your Relations

What is a Relationship Model?

A relationship model describes the relationship between one or more stakeholders (or interested parties) to (or within) a company or organization. In addition to the requirements and counter-requirements that two parties have, it is also possible to describe the objects that are sent between the stakeholders. The items in question can be orders, payments, and complaints from the customer. Further, it can deliver products, services, documentation, and invoices to the customer. Objects from stakeholders in the relationship model are inputs to our processes, and objects to stakeholders are the outputs created by our processes. You can read more about the process model by clicking here. The relationship model is also a direct consequence of the Interested Party Model, which you can read more about by clicking here.

Why should you use a Relationship Model?

The relationship model visualizes and describes the relationship between one or more stakeholders (or interested parties) to and within the organization. This brings several benefits.

1. Clarity of Requirements
   An organization, business, or project has various stakeholders, each with different requirements. These requirements are important for the survival of the business. The relationship model gives us clear insight into the requirements that are made and from which stakeholder the requirement comes. This helps us ensure that we actually meet the requirements in our processes.
2. Prioritize Requirements
   The clear picture of the demands placed on us in the relationship model makes it easier to prioritize them. Prioritization is easier when we also put it in perspective to other parts of the business.
3. Visualize how we follow Requirements
   The relationship model further helps us to show how we follow up on the requirements placed on us. By using object types such as “Goals” and “Indicator” we can make this visible.

How do you create a Relationship Model?

In this fictitious example, we start with the stakeholders “Customers” and “Company” to clarify relationships and requirements. We begin by reusing the objects “Customers” and “Company” from the Interested Party Model that we assume we have already created.

After this, we place the objects from the customers and what is expected to be delivered from the company. In this case, it is about the business objects “Order” and “Request” coming from the customer, while the company delivers the objects “Proposal” and “Delivered order” to the customer.

After this, we place the customer’s requirements on the company. There may also be counter-requirements, such as the company needing delivery data from the customer. In this example, however, we focus on the customers’ requirements for the company. At this stage, we can also place target objects and indicator objects that show how we will fulfill one of the requirements.

Now, we have a clear insight into stakeholder relationships and the requirements in a specific scenario. The business objects can then be reused as input and output when mapping the delivery process.