liveBook · Manning

Architectural rigor

As explained in Software Architecture Decision-Making

Architectural rigor is the disciplined use of analysis, safeguards, verification, and operational controls to reduce the consequences of system failure.

Architectural rigor applies deeper analysis, safeguards, verification, and operational controls where failure is expensive, invisible, irreversible, or far-reaching. It rejects both careless compromise and indiscriminate perfectionism: the required standard depends on consequence, reversibility, detectability, and blast radius. section 3.5

Higher-consequence areas demand controls the team can operate and test, including:

  • Security: encryption, secrets management, network exposure review, and periodic access reviews. section 3.5
  • Data integrity: constraints, validation, idempotency, reconciliation, backups, restore testing, and clear correction ownership. section 3.5
  • Financial calculations: audit trails, rounding rules, independent verification, regression tests, reconciliation, and approved change processes. section 3.5
  • Mission-critical resilience: recovery objectives, failover testing, monitoring, alerting, incident runbooks, dependency mapping, and practiced recovery. section 3.5
Table 3.5 Decision rigor rubric
Factor
Lower rigor may be acceptable when...
Higher rigor is justified when...
Reversibility
The decision can be changed, rolled back, or replaced without major disruption.
The decision is hard to reverse once data, users, integrations, or operational processes depend on it.
Detectability
Failure is visible quickly through tests, monitoring, user feedback, or operational signals.
Failure can remain hidden, appear later, or silently corrupt data, calculations, permissions, or business outcomes.
Blast radius
Failure affects a small internal group, a temporary workflow, or a non-critical capability.
Failure affects customers, money, safety, compliance, sensitive data, or core operations.
Cost of failure
The consequence is inconvenience, rework, delay, or local operational pain.
The consequence is legal exposure, financial loss, security breach, regulatory failure, physical harm, or major reputational damage.
Recovery
The team can recover through rollback, retry, correction, or a known manual process.
Recovery requires coordinated incident response, data repair, customer communication, regulatory reporting, or complex restoration.

Use the decision rigor rubric to calibrate safeguards against reversibility, detectability, blast radius, and cost of failure. section 3.5

How Software Architecture Decision-Making covers it

How deep it goes
Details safeguards and testing practices, then calibrates rigor through reversibility, detectability, blast radius, and failure cost.
Examples
Uses encryption, access reviews, reconciliation, backups, restore testing, audit trails, failover tests, runbooks, and dependency mapping.
What you can do after
Evaluate where compromise is safe and operate and test controls where failure carries serious consequences.
How it connects
Connects security, data integrity, financial calculations, resilience, monitoring, incident response, and recovery objectives.

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.