Architecture Portal

Information

The case, its history and its valid states.

Adrian Sutherland · Version 1.0 · · © 2005–2026

BP-V04 (Information relationships) · Version 1.0 · September 2026

Information relationships

Records and retained history.

Design state
PROC-01 (Process-only proposal)
Level
Logical
Design
Proposed; checks unrun
Scope
Case meaning shared with the later software option
ASAF aspects
Information, Process

On a small screen, scroll the diagram sideways or read the text description below.

A cancelled booking may have historical cancellation cases, with at most one active case. Each active case has one current owner assignment. Agreement and confirmation histories retain corrections. A resolved case requires confirmation matching its current agreement.
BP-V04 (Information relationships). Fictional process proposal; service checks are unrun.

Key

  • Crow’s-foot ends show how many records may be related. The text states which record is current.
  • History may contain several assignments and agreements; only one of each can be current.

Linked records

Text description

A cancelled booking may have historical cancellation cases, with at most one active case. Each active case has one current owner assignment. Agreement and confirmation histories retain corrections. A resolved case requires confirmation matching its current agreement.

BP-V05 (Case lifecycle) · Version 1.0 · September 2026

Case lifecycle

Agreement and confirmation govern resolution.

Design state
PROC-01 (Process-only proposal)
Level
Logical
Design
Proposed; checks unrun
Scope
Case state across process and software arrangements
ASAF aspects
Information, Process, Systems

On a small screen, scroll the diagram sideways or read the text description below.

Opening assigns an owner. Learner agreement permits awaiting confirmation. Matching confirmation permits resolution. Exceptions retain responsibility while escalated; the appropriate active state resumes after a decision. Corrections can invalidate an agreement or confirmation. Ownership transfer preserves the case state.
BP-V05 (Case lifecycle). Fictional process proposal; service checks are unrun.

Key

  • Arrows name events and conditions for changing state.
  • An accepted transfer changes assignment, not resolution state. Retention and retirement are separate decisions.

Linked records

Text description

Opening assigns an owner. Learner agreement permits awaiting confirmation. Matching confirmation permits resolution. Exceptions retain responsibility while escalated; the appropriate active state resumes after a decision. Corrections can invalidate an agreement or confirmation. Ownership transfer preserves the case state.

Meaning and ownership

I1 (Cancellation case record) records one cancellation case and its cancelled booking. ID-DEF1 (Learner agreement definition) defines learner agreement as acceptance of a specific alternative, including who recorded it, when and the supporting interaction. An offer remains an offer until that acceptance is recorded.

ID-D1 (Shared case register) proposes the shared case register for PROC-01 (Process-only proposal). The case service would hold the same authoritative meaning in SOFT-01 (Later software option). Booking records and booking confirmation retain their separate authority.

Relationship rules

Information Rule
Cancelled booking and case One case refers to one booking. At most one active case is allowed for a cancelled booking; earlier resolved history may remain.
Assignments History can contain several assignments; exactly one is current while the case is active.
Agreements Each agreement names one alternative; corrections preserve history and at most one agreement is current.
Confirmation A resolution needs confirmation of the current agreement and resulting booking.
Acceptance receipt In the software option, identifies the result of one operation; it does not establish the owner after subsequent changes.

The relationship drawing allows historical records. Its cardinalities do not replace the temporal rules for the current assignment and agreement.

State changes

A case opens when cancellation is accepted for handling. Recorded agreement moves it to awaiting confirmation; matching confirmation permits resolution. An exception retains the owner, reason and next action while escalated. The service owner’s decision returns it to the appropriate active state.

A transfer changes the assignment while preserving the case’s resolution state. A correction can invalidate agreement or confirmation; retain its reason and earlier version, then reopen at the appropriate state.

Quality and retention

The service owner approves meaning and retention choices; the steward maintains definitions and helps resolve recurring errors. Access, correction, retirement and treatment of copies need explicit decisions before real learner information is used. The data-governance guide and completed governance record follow a correction into a derived report and its copies. Retention periods and real-data approval remain open.

ID-V1 (Case meaning checks) checks duplicate cancellation, conflicting agreement and confirmation, unaccepted ownership and corrected history. The checks are unrun. See the information records and original case example.

About this edition

Refreshed for the September 2026 website update. This edition develops earlier Architecture Portal and ASAF material; the fictional service example was added in 2026.

Scope, limitations and next checks

Status and accountability

Read this page with its boundaries visible

Status

Proposed

Last reviewed

Intended users

  • Architects describing, comparing and adapting an architecture

Non-goals

  • A prescribed product stack or a claim of measured service outcomes

Limitations

  • The service is a fictional design. Its proposed implementation and operational checks remain unrun.

Next evidence sought

  • Apply the views and linked checks to an actual service.