Versions Compared

Version Old Version 14 New Version Current
Changes made by

damian.hickey

damian.hickey

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents
stylenone

...

For modelling clarity, relationships should originate from active domains and target passive ones.
For guidance on relationship directionality, see: Directionality in cross domain relationships

Example

This example that represents cross-domain relationships, organised logically from strategy to execution and support domains.

...

  • Strategy → Capability: Strategic objective shapes capability investment.

  • Capability → Value Stream → Initiative → Service → Product: Core delivery chain.

  • Initiative → Performance: Execution linked to measurable outcomes.

  • Policy and Information: Support governance and data dependency relationships.

  • Stakeholder: Shows ownership and accountability.

Relationship type list

Icon

Relationship Type

Description

Funds node.png

funds

Finance provides financial resources to another domain entity to enable its development, operation, or enhancement.

Quantifies node.png

quantifies

Finance expresses the activities, outputs, or outcomes of another domain entity in measurable financial terms.

Reports on node.png

reports_on

Finance produces formal reports capturing the financial performance, costs, or returns associated with another domain entity.

Forecasts node.png

forecasts

Finance projects future financial needs, costs, or revenues associated with another domain entity.

Supporting node.png

supported

One domain entity receives necessary resources, services, or capabilities from another domain entity to deliver its intended outputs or outcomes.

Constrains node.png

constrains

One domain entity imposes limitations, standards, or compliance requirements on another domain entity’s design, operation, or evolution.

Enables node.png

enables

One domain entity is essential for the successful implementation, operationalisation, or fulfilment of another domain entity.

701c21de-e77c-4913-bcf5-3c54ad4063a2.png

mitigates

One domain entity actively reduces the risks or vulnerabilities associated with another domain entity.

Monitors node.png

monitors

One domain entity oversees, measures, or evaluates the performance or effectiveness of another domain entity.

Governing node.png

governing

One domain entity defines policies, standards, or decision rights that control the operation of another domain entity.

Drives demand for node.png

drives_demand

One domain entity generates, influences, or amplifies the demand for another domain entity’s outputs, services, or capabilities.

Responds to node.png

responds_to

One domain entity is triggered, adapted, or activated in response to changes in another domain entity or external event.

Consuming node.png

consuming

One domain entity uses, relies upon, or draws from the resources, outputs, or services of another domain entity.

Aligns_with node.png

aligns_with

One domain entity is intentionally coordinated or harmonised with another domain entity in purpose, direction, or design without establishing a direct dependency.

Oversee node.png

oversee

For systematic traceability of oversight responsibilities.

Accountable to node.png

accountable_to

For a clear line of responsibility between entities

...