liveBook · Manning

Force assessment framework

As explained in Software Architecture Decision-Making

A force assessment framework is a structured method for evaluating the pressures and conditions that should influence an architectural decision.

A force assessment framework evaluates the pressures surrounding an architectural decision so trade-offs become explicit rather than accidental. It directs attention toward simplifying, strengthening, or documenting the design where pressure is highest. section 2.6

Assess the forces that can constrain or destabilize an architecture:

  • Time: determine whether a deadline dominates the architecture or permits deliberate trade-offs. section 2.6
  • Cost: identify whether budget conditions support resilience and managed services or limit the available options. section 2.6
  • Team capability, risk tolerance, ownership, and the wider project landscape: expose whether the proposed solution can be safely operated, evolved, and supported. section 2.6

Use the assessment to record compromises, their risks, ownership, and revisit conditions. Treat decisions as contracts made under known conditions: changing time, cost, capability, ownership, or governance can make a decision expire. section 2.6

Table 2.3 Project forces and corresponding pressure levels
Force
Low pressure
Medium pressure
High pressure
Time
Flexible time
Delivery date matters but allows trade-offs
Deadline dominates the architecture
Cost
Budget supports managed services and resilience
Cost needs active control
Cost limits architecture options
Team capability
Team has relevant experience
Team can learn with support
Team cannot safely own the proposed solution
Risk tolerance
Experiments are acceptable
Some uncertainty is acceptable
Failure, instability, or compliance exposure is unacceptable
Ownership
Clear long-term owner exists
Ownership is shared but coordinated
Ownership is unclear or externalized
Project landscape
No major related initiatives affect the decision
Related initiatives may change scope, capacity, or integration needs
Competing or upcoming initiatives make the current design temporary, risky, or capacity-constrained

Compare low, medium, and high pressure across the principal project forces before committing to architectural ambition. section 2.6

How Software Architecture Decision-Making covers it

How deep it goes
Defines pressure levels across six forces and connects assessment to documented compromises, ownership, and decision revision.
Examples
Uses a project-forces pressure table and records shortcuts with their rationale, risks, owners, and revisit conditions.
What you can do after
Evaluate architectural ambition against current pressures and identify when an existing decision should be revisited.
How it connects
Connects architectural decisions with technical debt, ownership, governance, team capability, risk tolerance, and project landscape.

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.