# SI-T03: Compatibility and change

Adrian Sutherland · Version 1.0 · Refreshed September 2026

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

Complete or link the relevant existing records. Mark unanswered questions as open.

## Process areas

A Simple Architectural Framework (ASAF) describes four continuing areas of work.

Map the work to your actual stages and reviews. Areas may share a review or
repeat at different scopes. Keep the accepted starting point between cycles.

| ASAF process area | Question | Your activity, owner and retained record |
|---|---|---|
| Visioning | What future outcome and qualities should this change serve? | [fill] |
| Transforming | What changes, checks and handover are required? | [fill] |
| Operating | How will the result be run, supported and observed? | [fill] |
| Governing | Who accepts decisions, exceptions and any wider reconsideration? | [fill] |

## Change and reason

Identify the proposed change, decision, expected benefit and unchanged business obligations.

## Affected participants

List producers, consumers, people, suppliers and the information or actions affected.

## Old and new behaviour

Describe meaning, structure, permissions, errors and versions, including differences that a schema will not reveal.

## Transition and compatibility

Plan migration, mixed versions, source of authority, cutover, consumer readiness and retirement.

## Checks and acceptance

Define compatible examples, failure cases, acceptance owner and actual results.

## Recovery after release

Distinguish reverting software from reversing real actions. Identify corrections and their authority.

## Durability review

Test a replacement of channel, language, supplier or deployment; record which assumptions change.

## Open decisions and measures

Record owners and dates for unresolved questions and how benefits will be observed.