# BA-T02 — Business architecture and relationships: completed example

Adrian Sutherland · Version 1.0 · Refreshed September 2026

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

Fictional teaching example. The baseline and proposed revision are illustrative.

## Scope and states

Current situation: responsibility for resolution is unclear between booking
and course teams. Proposed baseline B1 assigns one case owner and uses one
shared cancellation record for provider-run courses. System support is a later
option; partner courses remain outside the first trial.

## Relevant items and relationships

- O1: timely resolution accepted by the learner; owner: service owner.
- P1: the learner agrees to the alternative; maintained by the service owner.
- R1: agreement and ownership survive handovers; accepted by service owner.
- C1: capability to resolve a cancelled booking; supports O1.
- VS1: stages of value: understand options, agree resolution, receive confirmation.
- PR1: open case, assign owner, contact learner, agree alternative, confirm.
- RO1: case owner; remains responsible until resolution or accepted transfer.
- I1: case record with owner, options, agreement, state and confirmation reference.
- A1: RO1 maintains I1 through PR1, with handover constrained by R1.

The completed CSV retains the relationship directions and includes D1, V1 and
L1 from BA-T03. All rows describe the fictional teaching model.

## Methodology configuration

The service brief holds outcome, capability, value stream and responsibility.
The case record holds the operational information. The service review holds
decisions and observations. These three records cover several reference
aspects. In a method that uses an actor model, the case owner could be
represented as a human actor with responsibility for maintaining the case
record; automated actors would need their own responsibilities.

## Change and handover

After hypothetical finding L1, retain O1, P1 and the internal case owner.
Proposed revision B2 adds partner acceptance and confirmation responsibility
to A1 and I1. Keep B1's scope until the service owner accepts those changes.
Extend check V1 to the partner handover before extending the trial.

The case owner maintains I1. Booking/course leads reconcile process changes;
the service owner accepts shared responsibility changes. A recipient must be
able to identify the current owner, agreement and next action. Unknown partner
acceptance remains explicit instead of being assumed.