architecture-tradeoff-analysis
Architecture Tradeoff Analysis
Compare candidate architectures against the quality attributes that actually matter, with every option's costs stated as plainly as its benefits. A comparison where one option has no downsides is advocacy; the downsides exist whether or not they are written down.
When to Use
Use when two or more candidate architectures, designs, or technical approaches need a structured comparison before a decision. Out of scope: recording the decision after it is made (a decision-record activity, not a comparison), single build-vs-adopt dependency decisions judged on maintenance, license, and exit dimensions, inventing candidate options the input does not name beyond the explicit do-nothing baseline rule below, running benchmarks or spikes to produce evidence, and product prioritization between features.
Required Inputs
- Two or more candidate options, named in the input. When only one option is supplied, add
do-nothing(keep the current state) as the baseline second option and say so; if the input explicitly rules the baseline out, emit the BLOCK template asking for a second real option. - The quality attributes that matter for this choice, with weights when supplied.
- Constraints the choice must respect (budget, deadline, compliance, existing stack), when supplied.
If no options are provided at all, emit the BLOCK template; do not invent candidates.
Attribute Set
Score against the attributes the input names. When the input names none, use this default set: performance, consistency-and-correctness, operability, cost, evolvability, team-fit. The Attribute set: header line discloses whether the set was supplied or defaulted and names any dropped default with its one-line reason; add input-specific attributes freely.