# Tactic Trade-off Balancing

**In short:** Tactics serve quality goals, and those goals can conflict. Balancing means ranking the goals, finding where they collide, and recording each choice with all its consequences.

## Explanation

Quality goals often pull against each other. A choice that helps one goal can cost another. Tactic trade-off balancing is the work of handling that conflict on purpose. (See Architectural Tactic and Quality Attribute Trade-off for the basics.)

**Rank the goals first.** The ATAM method (Architecture Tradeoff Analysis Method) evaluates an architecture against its quality goals. It also shows how those goals interact and conflict. ATAM uses a utility tree for ranking. This is a tree of the requirements that drive the architecture, and it helps the team prioritize quality goals. With a ranking, a conflict has an answer to start from.

**Find the collision points.** In its analysis step, ATAM names three things: architectural risks, sensitivity points and trade-off points. Sensitivity Point and Trade-off Point have their own articles.

**Expect surprises.** A review of tactics for big data security calls for more research on trade-offs and dependencies among tactics. So these interactions are not well understood. Teams should not assume that tactics combine without friction.

**Write the choice down.** arc42 is a documentation template. Its solution strategy section holds the core decisions, including how the key quality goals are achieved. arc42 asks you to explain why you decided that way. It recommends one consolidated table that ties each quality goal to the decisions that follow from it. Section 9 asks for important decisions with their rationale, so stakeholders can retrace them. It also asks you to list all consequences, not only the positive ones. A trade-off that stays unrecorded is easy to forget.

## Example

A team ranks its quality goals and puts one goal at the top. It picks a tactic for that goal. In review, the team marks a trade-off point where the choice affects a lower-ranked goal. It then adds a row to its quality goal table. The row names the goal, the decision and the cost. It also lists that cost among the consequences in its decision record.

## Trade-offs

Balancing takes effort: ranking goals, running an evaluation and writing down consequences all cost time. Because interactions among tactics are not well understood, some side effects will only show up late. Writing down all consequences, including the negative ones, makes the compromises visible to stakeholders. That is the purpose of the practice.

Balancing tactics: rank goals, choose, analyze, record, and adjust.

```mermaid
flowchart LR
  A[Quality goals] --> B[Rank in utility tree]
  B --> C[Choose tactics]
  C --> D[Analyze risks, sensitivity and trade-off points]
  D --> E[Record decisions and consequences]
  D -.->|adjust| C
```

## Checks

- Quality goals are ranked, for example in a utility tree, so conflicts can be settled by priority.
- Trade-off points and sensitivity points found in the analysis are identified.
- The solution strategy ties each key quality goal to the decisions made for it, ideally in one table.
- Each important decision states its rationale, so stakeholders can retrace it.
- Decision records list all consequences, including the negative ones.

## Related

- [Architectural Tactic](https://arc.fuet.ch/concepts/tactics/architectural-tactic.md)
- [Quality Attribute Trade-off](https://arc.fuet.ch/concepts/quality-attributes/architectural-trade-off-thinking.md)
- [Trade-off Point](https://arc.fuet.ch/concepts/evaluation/trade-off-point.md)
- [Sensitivity Point](https://arc.fuet.ch/concepts/evaluation/sensitivity-point.md)
- [Architecture Tradeoff Analysis Method (ATAM)](https://arc.fuet.ch/concepts/evaluation/architecture-tradeoff-analysis-method-atam.md)
- [Quality Attribute Prioritization](https://arc.fuet.ch/concepts/quality-attributes/quality-attribute-prioritization.md)
- [Solution Strategy](https://arc.fuet.ch/concepts/documentation/arc42-solution-strategy.md)
- [Choosing and Applying Tactics](https://arc.fuet.ch/concepts/tactics/choosing-and-applying-tactics.md)

## Sources

- [Architecture Tradeoff Analysis Method® Collection | CMU Software Engineering Institute](https://www.sei.cmu.edu/library/architecture-tradeoff-analysis-method-collection/) — sei.cmu.edu, accessed 2026-11-09
- [9 - Architecture decisions | arc42 Documentation](https://docs.arc42.org/section-9/) — docs.arc42.org, accessed 2026-11-09
- [4 - Solution strategy | arc42 Documentation](https://docs.arc42.org/section-4/) — docs.arc42.org, accessed 2026-11-09
- [Tip 1-17: Combine quality goals with the action points of the ‘solutions strategy’ section! | arc42 Documentation](https://docs.arc42.org/tips/1-17/) — docs.arc42.org, accessed 2026-11-09
- [[1802.03178] Architectural Tactics for Big Data Cybersecurity Analytic Systems: A Review](https://arxiv.org/abs/1802.03178) — arxiv.org, accessed 2026-11-09