Coverage expectation
Purpose
The CoverageExpectation
domain allows an organisation to define the level of business architecture documentation or insight it aims to achieve across each domain. These expectations may be defined at an enterprise or business unit level and help ensure strategic alignment and architectural maturity.
Usage
Coverage expectations form the basis of goal-setting and assessment in Orthogramic. They are typically established during organisation onboarding or during strategic review cycles. These expectations define how much visibility or rigour is expected for a particular business domain. They drive analytics, gap detection, recommendations, and prioritisation of work.
Core concepts
Target coverage level: A qualitative measure (e.g. Minimal, Documented, Optimised) that sets ambition for each domain.
Contextualisation: Expectations can be organisation-wide or refined for specific business units.
Justification: Helps clarify why a particular domain requires stronger architectural coverage—e.g. compliance, innovation, integration risk.
Example implementation
{
"id": "cexp-001",
"domain": "Capability",
"orgUnit": "OU-Finance",
"targetCoverageLevel": "Analysed",
"justification": "Required for budgeting accuracy and integration with forecasting process",
"linkedStrategy": "strat-2025-03",
"createdBy": "admin@org.com",
"createdAt": "2025-07-01T10:30:00Z"
}
Attributes
Property | Description | Example |
---|---|---|
| Unique identifier |
|
| Business architecture domain covered by the expectation |
|
| Optional unit the expectation applies to |
|
| Desired level: None, Minimal, Documented, Analysed, etc. |
|
| Indicates the lifecycle stage the expectation applies to |
|
| Reason the domain requires this coverage |
|
| Optional strategy linked to this expectation |
|
| User or system that created this record |
|
| Timestamp of creation |
|
Enumeration values
targetCoverageLevel
(within expectations)
Value | Meaning |
---|---|
| No documentation or awareness of the domain |
| Only high-level or incidental references exist |
| The domain is explicitly and intentionally documented |
| Relationships and implications of the domain are explored |
| The domain is managed via formal policies, rules, or oversight |
| The domain is continuously improved and used for decision-making |
lifecycleStage
Value | Description |
---|---|
| The initial concept or business case is being explored. |
| The domain element is being architected, scoped, or formally planned. |
| Implementation, construction, or build is in progress. |
| The element is active and in use across the organisation. |
| Performance or effectiveness is being measured and refined. |
| The element is being phased out, decommissioned, or transitioned. |
The Orthogramic Metamodel license: Creative Commons Attribution-ShareAlike 4.0 (CC BY-SA 4.0), ensuring it remains open, collaborative, and widely accessible.