Intro to business architecture terms
- damian.hickey
The Orthogramic Metamodel uses a structured set of terms to describe how an organisation works, what it delivers, and how it adapts to change. Each term is defined precisely to support clarity, automation, and traceability.
This guide introduces key terms in plain language and explains how they relate to one another in practice.
Core terms and definitions
Term | Definition |
|---|---|
Domain | A category of knowledge used to describe a part of how the business operates (e.g. Strategy, Capability, Organization, Policy). Each domain has a consistent structure and schema. |
Attribute | A property that describes a characteristic of a domain element (e.g. title, purpose, owner). |
Element | A key part or sub-section within a domain (e.g. a Capability has Components, Processes, and a Function). |
Sub-element | A further breakdown within an element that describes detailed content (e.g. a Capability Process includes Inputs, Outputs, and Performance Metrics). |
Key domains explained
Domain | Purpose and usage |
|---|---|
Strategy | Describes what the organization aims to achieve (strategic goals, priorities, and drivers). |
Capabilities | Defines what the organization is able to do, regardless of how it is done. It is the bridge between strategy and operations. |
Organization | Represents the structure of the organization, including units, roles, and relationships. |
Stakeholders | Identifies individuals or groups who influence or are affected by the organization’s work. |
Value Streams | Describes the stages of value creation—from initial input to final outcome—for customers or internal stakeholders. |
Initiatives | Captures major programs, projects, or investments that drive change and execute strategy. |
Information | Refers to critical data and assets needed to support operations and decision-making. |
Policy | Formal rules or guidelines that govern how decisions are made or actions are taken. |
Performance | Defines how success is measured, including KPIs and outcome metrics. |
Products | Tangible or intangible items created or delivered to customers. |
Services | Activities or processes that deliver value through interaction or ongoing engagement. |
Relationship and structure terms
Term | Definition |
|---|---|
Inter-unit domain relationships | Defines how different organizational units interact with the same capability, service, or domain artefact (e.g. one unit owns a capability, another consumes it). |
Relationship role | The type of connection a unit has to a domain element (e.g. owning unit, providing unit, consuming unit, custodian, governing unit). |
Trigger | An external or internal event that causes the business to respond (e.g. a new regulation, customer feedback). |
Rationale | A reason for action, often linked to a trigger and connected to specific strategies, initiatives, or policies. |
Strategic Response Model (SRM) | A structured way to link triggers, rationales, and the organisational responses across domains. |
Governance | The oversight structures and processes that ensure decisions are consistent with strategy and compliant with rules. |
Example of how terms relate
A Trigger (e.g. regulatory change) leads to a Rationale for change.
The Strategic Response Model defines how the business will respond—via Initiatives, Policy updates, or changes to Capabilities.
The affected Capabilities are owned by specific Organization Units, which may be supported or influenced by others via Inter-unit domain relationships.
Success is tracked via Performance KPIs, and relevant Stakeholders are kept informed.
All elements are structured, versioned, and traceable via the JSON schema definitions of each domain.
Related content
© Orthogramic 2024