liveBook · Manning

Architectural preparation

As explained in Software Architecture Decision-Making

Architectural preparation is the deliberate creation of limited structures, contracts, records, or tests that reduce the cost and risk of responding to plausible future changes.

Architectural preparation deliberately preserves affordable responses to plausible future change without building every imagined capability today. It balances flexibility against the rigidity and cost of speculation. section 4.4

Prepare architecturally when a possible change:

  • Is likely during the system’s lifetime and expensive, risky, or slow to address later. section 4.4
  • Could affect important contracts, data models, security boundaries, integrations, or ownership. section 4.4
  • Would be difficult to reverse, has observable signals, and can be addressed with a small seam, stable contract, ADR, compatibility rule, or test strategy. section 4.4

Last responsible moment

Make consequential architectural decisions late enough to preserve flexibility, but early enough to avoid delivery risk.

How Software Architecture Decision-Making covers it

How deep it goes
Defines preparation criteria and lightweight mechanisms, without prescribing a full implementation process.
Examples
Uses seams, stable contracts, ADRs, compatibility rules, test strategies, and signals such as volume growth or support friction.
What you can do after
Evaluate plausible changes and choose proportionate preparation instead of either speculative building or deferred risk.
How it connects
Connects plausible change with contracts, data models, security boundaries, integrations, ownership, ADRs, and compatibility rules.

Related concepts

This explainer was generated by Manning's knowledge graph from the text of Software Architecture Decision-Making. The section links point to the parts of the book it draws on.