liveBook · Manning

Future change

As explained in Software Architecture Decision-Making

Future change is a later alteration in requirements, usage, technology, organization, or operating conditions that an architecture may need to accommodate.

Architecture must preserve room for later changes without turning uncertain possibilities into expensive speculative systems. The central trade-off is between flexibility and present delivery risk. section 4.4

Assess a possible change by asking:

  • How likely and consequential is it, and how difficult would reversal be? section 4.4
  • Can a small seam, stable contract, ADR, compatibility rule, or test strategy preserve useful options? section 4.4
  • What evidence signals rising pressure, such as volume growth, new consumers, cost, support friction, regulation, or workarounds? section 4.4
  • When is the last responsible moment: late enough to retain flexibility, but early enough to avoid delivery, financial, operational, or strategic risk? section 4.4
Figure 4.2 Architectural decisions are most effective when made at the last responsible moment: late enough to preserve flexibility, but early enough to avoid delivery risk.

Use the decision-timing model to distinguish premature commitment from delay that has become risky. section 4.4

How Software Architecture Decision-Making covers it

How deep it goes
Explains risk, reversibility, signals, preparation techniques, and decision timing, but stops short of implementation guidance.
Examples
Uses growth, new consumers, rising cost, support friction, regulatory pressure, workarounds, seams, contracts, ADRs, and test strategies.
What you can do after
Evaluate when to defer, prepare for, or commit to an architectural decision using evidence, impact, likelihood, and reversibility.
How it connects
Connects future change with evolutionary architecture, last responsible moment, ADRs, stable contracts, compatibility rules, and test strategies.

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.