Skip to end of metadata
Go to start of metadata

You are viewing an old version of this content. View the current version.

Compare with Current View Version History

Version 1 Next »

Directionality of Cross Domain Relationships

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

Definition:
Cross domain relationships must be modelled with active domains as the source and passive domains as the target. Passive domains must not initiate outbound relationships.

Passive domains include:

  • Information

  • Policy

  • Performance

  • Product

  • Service

Correct examples:

  • Strategy → Capability

  • Capability → Service

  • Initiative → Performance

  • Stakeholder → Policy

Incorrect examples:

  • Information → Capability : informs

  • Performance → Initiative : measured by

  • Policy → Stakeholder : constrains

Implementation guidance:

  • In diagrams, passive domains only appear as targets.

  • In JSON or RDF representations, relationships originate from active domains.

  • Verbs such as informs, measures, or describes are used only in documentation, not as relationship types sourced from passive domains.

Rationale:
This ensures semantic clarity, avoids visual clutter, and supports reasoning engines that depend on clear relationship directionality.

  • No labels