# BA-T02 — Business architecture and relationships

Adrian Sutherland · Version 1.0 · Refreshed September 2026

© 2005–2026 Adrian Sutherland.
Source page: https://architectureportal.org/assets/business-architecture

Use stable identifiers where they make a decision or change easier to follow.

## Scope and states

- Decision / service / business area: [fill]
- Current operation and accepted baseline: [fill]
- Desired operation and proposed transitions: [fill]

## Relevant items and relationships

For each useful item, record its ID, meaning, owner and related IDs. Consider
outcomes, capabilities, value streams, processes, roles, information, rules
and supporting systems. Use the accompanying CSV for relationships if useful.

- Items and definitions: [fill]
- Relationships, direction and reason: [fill]
- Current / proposed / unresolved status: [fill]
- Unresolved ownership or dependencies: [fill]

## Methodology configuration

- Your method's terms and records: [fill]
- Several concerns in one record / one concern in several records: [fill]
- Differences in meaning or relationships to clarify: [fill]

## Change and handover

- Affected items, relationships and decisions: [fill]
- Accepted items that remain valid: [fill]
- Who maintains each affected record and accepts the change: [fill]
- What the recipient needs to know to act: [fill]
- Version, date, status and review trigger: [fill]