Cross-domain relationships

1 Introduction
2 Example
3 Relationship types descriptions
- 3.1 Enumeration values

This is an experimental schema, not yet tested in Orthogramic.

Introduction

In the Orthogramic Metamodel, cross-domain relationships articulate the interactions between elements across distinct business architecture domains. These relationships are pivotal for understanding how components such as strategies, capabilities, value streams, and policies interconnect, thereby enabling a cohesive and comprehensive view of the enterprise.

By delineating these interdependencies, cross-domain relationships facilitate strategic alignment, operational efficiency, and informed decision-making. They serve as the connective tissue that binds various domains, ensuring that changes or developments in one area are appropriately reflected and managed across others.

This section provides a structured overview of the defined cross-domain relationships within the Orthogramic Metamodel. It supports practitioners in mapping and analysing the complex web of interactions that underpin organisational performance and strategic execution.

Example

This cross-domain relationship example illustrates how the Finance domain plays a critical role in enabling the Capability domain by providing funding. Funding is essential for the development, enhancement, and sustainability of organisational capabilities, ensuring that key competencies are aligned with strategic priorities. By explicitly linking finance to capabilities through a 'funds' relationship, organisations can strengthen the connection between financial planning and strategic execution, ensuring that investments are directed towards the areas of highest strategic value. This relationship is classified as high priority and strategic in impact, highlighting its importance in driving long-term organisational success.

{
  "crossDomainRelationships": [
    {
      "domain": "Capability",
      "relationshipType": "funds",
      "description": "Finance provides funding to capabilities to enable the development and enhancement of organisational competencies aligned with strategic objectives.",
      "metadata": {
        "priority": "high",
        "impact": "strategic"
      }
    }
  ]
}

Relationship types descriptions

Each cross-domain relationship type defines a specific way in which two business architecture domains interact. To ensure consistency and clarity across modelling activities, this section provides detailed descriptions of each relationship type. These descriptions help users correctly interpret and apply relationships when linking domain entities, supporting more accurate analysis, governance, and decision-making. Understanding the intent behind each relationship type is critical to maintaining the semantic integrity of the overall business architecture model.

Relationship Type	Description

Relationship Type	Description
`funds`	Finance provides financial resources to another domain entity to enable its development, operation, or enhancement.
`quantifies`	Finance expresses the activities, outputs, or outcomes of another domain entity in measurable financial terms.
`reports_on`	Finance produces formal reports capturing the financial performance, costs, or returns associated with another domain entity.
`forecasts`	Finance projects future financial needs, costs, or revenues associated with another domain entity.
`supported`	One domain entity receives necessary resources, services, or capabilities from another domain entity to deliver its intended outputs or outcomes.
`constrains`	One domain entity imposes limitations, standards, or compliance requirements on another domain entity’s design, operation, or evolution.
`enables`	One domain entity is essential for the successful implementation, operationalisation, or fulfilment of another domain entity.
`mitigates`	One domain entity actively reduces the risks or vulnerabilities associated with another domain entity.
`monitors`	One domain entity oversees, measures, or evaluates the performance or effectiveness of another domain entity.
`governing`	One domain entity defines policies, standards, or decision rights that control the operation of another domain entity.
`drives_demand`	One domain entity generates, influences, or amplifies the demand for another domain entity’s outputs, services, or capabilities.
`responds_to`	One domain entity is triggered, adapted, or activated in response to changes in another domain entity or external event.
`consuming`	One domain entity uses, relies upon, or draws from the resources, outputs, or services of another domain entity.
`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`	For systematic traceability of oversight responsibilities.
`accountable_to`	For a clear line of responsibility between entities

Enumeration values

Property	Allowed Values	Description

Property	Allowed Values	Description
`priority`	`high`	The relationship is critical and should be prioritised for attention, action, or analysis.
	`medium`	The relationship is important but not critical; it should be monitored and addressed as needed.
	`low`	The relationship has limited immediate significance and can be considered lower priority.
`impact`	`strategic`	The relationship affects the organisation’s strategic objectives, positioning, or long-term outcomes.
	`operational`	The relationship influences day-to-day business operations, efficiency, or delivery of services.
	`tactical`	The relationship impacts specific initiatives, projects, or time-bound goals within the organisation.