Domain and Business Architecture
Document your business capabilities, value streams, organisational structure, and domain models. Bridge the gap between business and technology.
The Domain and Business Architecture directory is where you document the business context that drives your technology decisions. This bridges the gap between business stakeholders and technical teams.
What Belongs Here
This directory focuses on business-level architecture artifacts:
Recommended Content Blocks
Business architecture documentation benefits from these content blocks:
| Block Type | Use For |
|---|---|
| Diagram | Business capability maps, value stream diagrams, process flows |
| Graph Diagram | Domain relationship visualisations, organisational charts, capability dependencies |
| Principle | Business architecture principles, domain design rules |
| Assumption | Business assumptions about markets, customers, and operations |
| Constraint | Budget constraints, regulatory requirements, organisational limitations |
| Trade-off Matrix | Business case comparisons, investment decisions, vendor evaluations |
| Risk | Business risks, market risks, operational risks |
Framework Alignment
Domain and business architecture aligns with established frameworks:
Example Directory Structure
domain-and-business-architecture/
├── business-capabilities/
│ ├── capability-map-overview.cf.page.json
│ ├── customer-management/
│ │ ├── customer-acquisition.cf.page.json
│ │ └── customer-service.cf.page.json
│ └── order-fulfilment/
│ ├── order-processing.cf.page.json
│ └── shipping-logistics.cf.page.json
├── value-streams/
│ ├── customer-onboarding.cf.page.json
│ ├── order-to-cash.cf.page.json
│ └── product-development.cf.page.json
├── domain-models/
│ ├── bounded-contexts.cf.page.json
│ ├── customer-domain.cf.page.json
│ └── order-domain.cf.page.json
└── organisation/
├── team-topology.cf.page.json
└── ownership-matrix.cf.page.jsonExample: HR Domain Model
The following ERD shows an HR/People domain model with employees, departments, job titles, and employment history. This type of diagram helps business stakeholders understand how core business entities relate to each other.
Loading diagram: hr-employee-schema.diagram.json
Learn more
Create business capability maps and domain models showing hierarchical views of business capabilities and their boundaries.
Create value stream maps and IT operating model diagrams showing end-to-end value delivery flow and how IT delivers services.
Create domain-driven design diagrams including bounded context maps, event storming results, and API design documentation.
Map NeoArc Studio capabilities to TOGAF artifacts, ADM phases, and the Architecture Repository concept. Practical guidance for TOGAF practitioners.