Attribute-Driven Design
Updated 2026-08-15
INTRODUCTION
English translation pending.
CORE DEFINITION
Attribute-driven design makes the quality attributes, performance, security, maintainability, and the like, the primary driver of architectural design, so that attribute requirements decide architectural decisions. Its rule reverses the usual habit: it is not that you design first and then check whether the requirements are met, but that the requirements drive the design in the first place, and the tradeoffs between competing attributes are what the architecture actually encodes.
SCAFFOLDING EFFECT
Reduce cognitive load
- Rank the attributes: decide which quality attributes matter most before any structure is drawn. - Map each to a strategy: let every key attribute drive a concrete architectural choice. - Verify against attributes: iterate until the design meets the attribute targets, not the drawing.
Anchor fast decisions
An architecture is a set of committed tradeoffs among quality attributes, and those tradeoffs are fixed at design time whether or not they were chosen deliberately. Letting the attribute requirements drive means the tradeoff is made where it can be reasoned about, which is why retrofitting performance onto a design that never considered it is so expensive.
MINIMUM ACTION
In progress 0/1Practice this model in one real situation:
account_treeGenealogyexpand_more
menu_bookReferencesexpand_more
Source support: Explicit
- en.wikipedia.orghttps://en.wikipedia.org/wiki/Attribute-driven_designverified
PRIVATE NOTES · Only visible to you
SAVED Q&A
ENTRY Q&A · Private saving available
Ask with a clear boundary
thinkingmodels answers from published entry context only.
Your question is sent to thinkingmodels. The answer uses public entry context only.
RELATED MODELS