Versions Compared

Key

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

...

  • Source domain (e.g. Strategy)

  • Target domain (e.g. Capabilities)

  • Relationship type (e.g. influencesfunds, enables, supportssupported)

  • Directionality (uni- or bi-directional)

Examples:

  • Strategy → Capabilities (influences)

  • Capabilities → Value Stream (enables)

  • Value Stream → Initiative (delivers)

  • Stakeholders → Services (owns)

  • Policy → Information (governs)

...

Directionality

Term

Description

Example

Outbound

The entity initiates or points to another entity

A Capability enables a Value Stream

Inbound

The entity is the target or receiving end of a relationship

A Capability is influenced by a Strategy

Bidirectional

Both entities relate mutually or have reciprocal influence

A Policy both governs and is shaped by an Initiative

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.

...

This diagram models how business architecture elements are linked across domains rather than across business units.

Description

  • 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 with data.pngImage Removed
Funds node.pngImage Added

funds

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

Quantifies node with data.pngImage Removed
Quantifies node.pngImage Added

quantifies

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

Reports on node with data.pngImage Removed
Reports on node.pngImage Added

reports_on

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

Forecasts node with data.pngImage Removed
Forecasts node.pngImage Added

forecasts

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

Organization node with data (14).pngImage Removed
Supporting node.pngImage Added

supported

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

Constrains node with data.pngImage Removed
Constrains node.pngImage Added

constrains

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

Enables node with data.pngImage Removed
Enables node.pngImage Added

enables

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

Mitigates node with data.pngImage Removed
701c21de-e77c-4913-bcf5-3c54ad4063a2.pngImage Added

mitigates

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

Monitors node with data.pngImage Removed
Monitors node.pngImage Added

monitors

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

Organization node with data (15).pngImage Removed
Governing node.pngImage Added

governing

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

Drives demand for node with data.pngImage Removed
Drives demand for node.pngImage Added

drives_demand

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

Responds to node with data.pngImage Removed
Responds to node.pngImage Added

responds_to

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

Organization node with data (12).pngImage Removed
Consuming node.pngImage Added

consuming

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

Aligns_with node with data.pngImage Removed
Aligns_with node.pngImage Added

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.pngImage Modified

oversee

For systematic traceability of oversight responsibilities.

Accountable to node.pngImage Removed
Accountable to node.pngImage Added

accountable_to

For a clear line of responsibility between entities

Use in document analysis

When documents are parsed, relationships between domains are inferred based on sentence structure, contextual clues, and declared associations (e.g. “This initiative improves customer engagement by enhancing CRM capabilities”).

...