Skip to content
Back to search results

ATAM

Introduced by
Rick Kazman
Year
2000
Type
Architecture analysis method
Family
Architecture Evaluation
Font size

What does it do?

The Architecture Tradeoff Analysis Method (ATAM) is a systematic technique developed by Kazman et al. at CMU/SEI for evaluating software architectures against quality attributes (performance, security, modifiability).

ATAM uncovers architectural risks and tradeoffs early, helping teams assess whether designs meet quality goals before implementation.

The intuition behind the method

Architecture decisions involve tradeoffs: optimizing for performance might hurt maintainability; ensuring security adds complexity. ATAM makes these tradeoffs explicit by analyzing how architectural patterns (layering, caching, replication) impact quality attributes. By identifying sensitive points (critical design decisions) and tradeoff points (decisions affecting multiple attributes), ATAM reveals risks that testing alone cannot catch.

History

Rick Kazman, Mike Klein, and colleagues published ATAM in 2000 at CMU/SEI. It combined ideas from design review, quality modeling, and scenario-based testing. ATAM became standard in architecture reviews across aerospace, financial, and defense industries. Later work extended ATAM to distributed systems and DevOps practices.

When to use it

Use ATAM early in design phase, before implementation commences. Essential for large, complex systems with conflicting quality goals (e.g., real-time + security). Impractical for simple, well-understood systems or when stakeholders are unavailable. Most effective when decision-makers participate.

Limitations and considerations

  • Time-consuming: requires 2–3 days and full stakeholder attendance
  • Subjective: risk identification depends on team knowledge and experience
  • Limited to described scenarios: unexpected workloads not analyzed
  • Doesn't guarantee success: good analysis doesn't fix bad execution

Source conditions do not replace independent scientific review or validation by an analysis engine.

Strengths

  • Identifies architectural risks early, before costly implementation mistakes
  • Makes tradeoffs explicit and negotiable among stakeholders
  • Creates shared understanding of quality goals across team
  • Generates documentation artifact for future architectural decisions

Applications

  • Architecture review: evaluating designs before implementation commitment
  • Risk assessment: identifying architectural weaknesses in mission-critical systems
  • Tradeoff negotiation: aligning stakeholder expectations on performance vs. maintainability
  • Technology selection: comparing architectural options (monolith vs. microservices)
  • Compliance: verifying architecture meets regulatory quality requirements

How it works

How it works

1

Gather stakeholders (architects, developers, domain experts); elicit quality attribute scenarios describing desired system behavior under constraints.

2

Describe architectural approaches (patterns, components, connectors) and their rationale; map each pattern to quality attribute impacts using utility trees and scenarios.

3

Identify architectural patterns that address high-priority scenarios; trace execution paths through architecture for each scenario.

4

Generate list of risks (patterns that don't meet requirements), non-risks (patterns that do), and tradeoffs (patterns that conflict with other attributes).

Common pitfalls

  • Insufficient stakeholder participation; decision-makers must be present
  • Scenarios too vague or generic; specific, measurable scenarios required
  • Ignoring tradeoffs identified; addressing only risks without negotiating conflicts
  • Treating ATAM as one-time activity; revisit and update as architecture evolves

Frequently asked questions

What is a quality attribute scenario in ATAM?

A specific, measurable description of system behavior: 'When a user adds a product to cart, response time < 200ms under normal load.' Combines stimulus (user action), environment (load), response measure (latency), and constraint. Vague goals become testable scenarios.

How long does ATAM take?

Typically 2–3 days on-site: Phase 1 (1 day) = present architecture, elicit scenarios; Phase 2 (1.5 days) = analyze architecture, identify risks; Phase 3 (0.5 days) = consolidate findings. Large systems may need 5+ days.

Who should attend ATAM?

Essential: architect, developers, decision-maker (sponsor), product owner. Recommended: QA, operations, business analyst. Minimum team size = 5–6. Skipping key stakeholders risks missing important scenarios or failing to negotiate tradeoffs.

How do I prioritize which architectures to analyze?

Use utility trees: rank quality attributes by importance and urgency. Analyze architectures addressing high-priority attributes first. Run ATAM on top 2–3 architectural options; compare risks and tradeoffs.

Sources

  1. Kazman, R., Klein, M., Barbacci, M., Longstaff, T., Lipson, H., & Carriere, J. (2000). The Architecture Tradeoff Analysis Method. CMU/SEI Technical Report CMU/SEI-98-TR-008.

    Open publication reference
    Copied.
  2. Bass, L., Klein, M., & Kazman, R. (2003). Attribute-Driven Design (ADD), Version 2. CMU/SEI-2003-TR-002.

    Open publication reference
    Copied.
  3. Kazman, R., Asundi, J., & Klein, M. (2001). Making architecture design decisions: An empirical study. Proceedings of the 23rd International Conference on Software Engineering.

    Open publication reference
    Copied.