| Table of Contents | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
|
| Note |
|---|
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.
...
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 |
|---|---|
| Finance provides financial resources to another domain entity to enable its development, operation, or enhancement. |
| Finance allocates a planned amount of funding towards the ongoing or future activities of another domain entity. |
| Finance assesses the financial or economic value created by another domain entity. |
| Finance expresses the activities, outputs, or outcomes of another domain entity in measurable financial terms. |
| Finance distributes available financial resources among different domain entities based on priorities or strategic needs. |
| Finance monitors and records the expenditure associated with the operation or development of another domain entity. |
| Finance produces formal reports capturing the financial performance, costs, or returns associated with another domain entity. |
| Finance projects future financial needs, costs, or revenues associated with another domain entity. |
| Finance examines and evaluates the costs incurred by another domain entity in delivering its outputs or outcomes. |
| One domain entity provides necessary resources, services, or capabilities to enable another domain entity to deliver its intended outputs or outcomes. |
| One domain entity imposes limitations, standards, or compliance requirements on another domain entity’s design, operation, or evolution. |
| One domain entity is essential for the successful implementation, operationalisation, or fulfilment of another domain entity. |
| One domain entity actively reduces the risks or vulnerabilities associated with another domain entity. |
| One domain entity oversees, measures, or evaluates the performance or effectiveness of another domain entity. |
| One domain entity defines policies, standards, or decision rights that control the operation of another domain entity. |
| One domain entity generates, influences, or amplifies the demand for another domain entity’s outputs, services, or capabilities. |
| One domain entity is triggered, adapted, or activated in response to changes in another domain entity or external event. |
| One domain entity uses, relies upon, or draws from the resources, outputs, or services of another domain entity. |
| One domain entity is intentionally coordinated or harmonised with another domain entity in purpose, direction, or design without establishing a direct dependency. |
| For systematic traceability of oversight responsibilities. |
| For a clear line of responsibility between entities |
Enumeration values
Property | Allowed Values | Description |
|---|---|---|
|
| The relationship is critical and should be prioritised for attention, action, or analysis. |
| The relationship is important but not critical; it should be monitored and addressed as needed. | |
| The relationship has limited immediate significance and can be considered lower priority. | |
|
| The relationship affects the organisation’s strategic objectives, positioning, or long-term outcomes. |
| The relationship influences day-to-day business operations, efficiency, or delivery of services. | |
| The relationship impacts specific initiatives, projects, or time-bound goals within the organisation. |