Content Comparison

Introduction

In the Orthogramic, cross domain relationships between business architecture elements are inherently directional, conveying the flow of influence, typically flowing from active domains—such control, or dependency.

Cross Domain Relationships

Cross domain relationships connect elements across different domains (e.g., Strategy, Capability, Initiative) within the same organizational context. These relationships are typically modeled from active domains—such as Strategy, Capability, Initiative, Policy, and Stakeholder—to passive domains like Information, Performance, Product, and Service. This directionality ensures semantic clarity and consistency in modeling, visualization, and reasoning.

Inter-Domain Relationships

Inter-domain relationships illustrate how elements from different domains interact across organizational units. While directionality remains important—indicating, for example, that a Capability in Unit A depends on a Service in Unit B—the strict active/passive domain distinction is less rigid. In this context, the focus shifts to organizational dependencies and the flow of responsibility between units, rather than solely on domain roles.

This page outlines the principles and best practices for modeling these directional relationships, helping you maintain structural integrity and enhance the interpretability of your business architecture.

...

The following Orthogramic domains are considered passive:

...

• It’s more accurate to say a Capability uses Information than to say Information informs Capability.

• A Policy governs Information — not the other way around.

• A Performance metric is influenced by Initiatives, not vice versa.

...

Cross domain relationship Directionality

Passive domains must not initiate cross domain relationships
Applies to: Cross domain relationship definition and visualisation

...