# BP-R01 (Blueprint record set)

Adrian Sutherland · Version 1.0 · September 2026

© 2005–2026 Adrian Sutherland.

Refreshed for the September 2026 website update.

Licensed under [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Keep the [edition note](https://architectureportal.org/downloads/blueprint/1.0/edition.md) with adaptations.

A course is cancelled. The learner needs an alternative they accept and a
clear answer about who will arrange it. This blueprint brings the architecture
of that service into one connected set of views.

The [worked example](/worked-example) follows the decisions and their
consequences. Here the views show the resulting arrangements, their shared
rules and the decisions still needed. The service is fictional; its trial
and software implementation have not been carried out.

## Design states

| State | Arrangement | Scope |
|---|---|---|
| PROC-01 (Process-only proposal) | Shared register, named case owner and explicit acceptance of handovers | Proposed trial for provider-run courses |
| SOFT-01 (Later software option) | A case service with staff access, booking integration and recoverable transfers | Possible later software support |
| PART-01 (Partner extension) | An agreed partner service with its own booking and confirmation responsibilities | Later extension; responsibility and terms remain open |

These states describe different arrangements. Conceptual, Logical and Physical
describe how much detail a view supplies. Visioning, Transforming, Operating
and Governing describe the architectural work around them.

## The views

| View | Question |
|---|---|
| [Service overview](/blueprint/service-overview) | Who keeps the learner's case moving? |
| [Work and responsibility](/blueprint/work-responsibility) | How is agreement reached, ownership transferred and an exception handled? |
| [Information](/blueprint/information) | What does the case mean, and which states and relationships are valid? |
| [Systems and rules](/blueprint/systems) | Which components own decisions, records and exchanges? |
| [Accepted handover](/blueprint/accepted-handover) | What happens when a transfer succeeds but its reply is lost? |
| [Security](/blueprint/security) | Where are identity, permission and information use checked? |
| [Technology and operation](/blueprint/technology-operation) | What must survive release, restart and restoration? |
| [Direction and measures](/blueprint/direction-measures) | Who decides, what would it cost and how would results be judged? |
| [Change and review](/blueprint/change-review) | How do the process areas revisit the design? |

The [object reference](/blueprint/objects) defines identifiers, roles,
information and components used across the views. The
[records and downloads](/blueprint/records) provide the completed blueprint
and an outline to adapt.

## ASAF coverage

A Simple Architectural Framework (ASAF) supplies the aspects below. One view
may address several aspects, and an open choice can be a useful part of the
architecture.

| Aspect | Treatment in this blueprint |
|---|---|
| Customer | [Learner choice, payer and representative authority](/blueprint/work-responsibility#customers-and-channels) |
| Supplier | [Partner confirmation, failure and exit](/blueprint/work-responsibility#partners) |
| Channel | [Messages, assisted contact and offline proposals](/blueprint/work-responsibility#customers-and-channels) |
| Process | [Work, acceptance and escalation](/blueprint/work-responsibility) |
| Structure | [Role responsibilities and delegated decisions](/blueprint/work-responsibility#responsibilities) |
| Information | [Definitions, relationships, state and history](/blueprint/information) |
| Security | [Access, risks, controls and incident response](/blueprint/security) |
| Metrics | [Service results, method effort and recovery quality](/blueprint/direction-measures#measures) |
| Systems | [Applications, integration, software and business rules](/blueprint/systems) |
| Technology | [Runtime, release, persistence and recovery](/blueprint/technology-operation) |
| Management | [Authority, dependencies and exceptions](/blueprint/direction-measures#decisions) |
| Finance | [Comparable option costs and commitments](/blueprint/direction-measures#costs) |
| Purpose | [Accepted resolution, learner agreement and continuous ownership](/blueprint/service-overview) |

## Detail and open choices

The views provide Conceptual and Logical architecture. The
[implementation choices](/blueprint/technology-operation#physical-choices)
record what a Physical description would need: named people, products,
environments, configuration and operating procedures. Those choices remain
open in this fictional service.

## Methodology configuration

Use the views that answer your team's questions and combine them with your
existing records. Retain the meaning, authority and source references when
renaming an object or moving it into another diagram. The
[configuration guidance](/method/configuration) explains this mapping.

The [Systems reference components](/systems/reference-components) offer a
wider catalogue of responsibilities. They can inform a design without becoming
mandatory components of this service.

## View files

| View | Editable source | Static export | View record |
|---|---|---|---|
| BP-V01 (Service overview) | [Mermaid](/downloads/blueprint/1.0/service-overview.mmd) | [SVG](/downloads/blueprint/1.0/service-overview.svg) | [Description](/downloads/blueprint/1.0/view-service-overview-example.md) |
| BP-V02 (Accepted handover) | [Mermaid](/downloads/blueprint/1.0/accepted-handover.mmd) | [SVG](/downloads/blueprint/1.0/accepted-handover.svg) | [Description](/downloads/blueprint/1.0/view-accepted-handover-example.md) |
| BP-V03 (Work and responsibility) | [Mermaid](/downloads/blueprint/1.0/work-responsibility.mmd) | [SVG](/downloads/blueprint/1.0/work-responsibility.svg) | [Description](/downloads/blueprint/1.0/view-work-responsibility-example.md) |
| BP-V04 (Information relationships) | [Mermaid](/downloads/blueprint/1.0/information.mmd) | [SVG](/downloads/blueprint/1.0/information.svg) | [Description](/downloads/blueprint/1.0/view-information-example.md) |
| BP-V05 (Case lifecycle) | [Mermaid](/downloads/blueprint/1.0/case-lifecycle.mmd) | [SVG](/downloads/blueprint/1.0/case-lifecycle.svg) | [Description](/downloads/blueprint/1.0/view-case-lifecycle-example.md) |
| BP-V06 (Systems and rules) | [Mermaid](/downloads/blueprint/1.0/systems.mmd) | [SVG](/downloads/blueprint/1.0/systems.svg) | [Description](/downloads/blueprint/1.0/view-systems-example.md) |
| BP-V07 (Access and authority) | [Mermaid](/downloads/blueprint/1.0/security.mmd) | [SVG](/downloads/blueprint/1.0/security.svg) | [Description](/downloads/blueprint/1.0/view-security-example.md) |
| BP-V08 (Runtime and recovery) | [Mermaid](/downloads/blueprint/1.0/runtime.mmd) | [SVG](/downloads/blueprint/1.0/runtime.svg) | [Description](/downloads/blueprint/1.0/view-runtime-example.md) |