# Lightweight ATAM

**In short:** A lightweight ATAM is a shortened form of the full Architecture Tradeoff Analysis Method. It uses fewer people and simpler steps to deliver results in about a day, but it finds fewer risks.

## Explanation

A full ATAM review (see Architecture Tradeoff Analysis Method (ATAM)) uses moderated workshops. It takes anywhere from two days to several weeks. One source describes the typical SEI-specified evaluation as two to three days of facilitated workshops.

Lightweight variants, sometimes called mini-ATAM or ATAM-lite, compress the process into a single day. They are common in agile settings, where a formal two-day workshop is hard to schedule.

**How the effort shrinks**

Lightweight methods save effort in three ways:

- Fewer people take part.
- The analysis steps are simpler.
- Results arrive faster.

The main cost drivers of ATAM are the number of stakeholders and the number of scenarios. A scenario is a short story about how the system should respond to a situation. Trimming either one cuts the cost.

**What you still get**

ATAM scenario analysis produces trade-offs, sensitivity points, and risks or non-risks. See ATAM Findings: Risks, Non-Risks, Sensitivity Points and Trade-off Points.

**Who runs it**

Lightweight reviews can be run by one or more external parties, by the team itself, or jointly. This suits intermediate reviews during a project.

## Example

A small team is halfway through building a booking system. They want a quick check of the design before the next phase. They pick a few important scenarios, such as "the system stays responsive during a sales peak". They invite only the architect and a few key people. In one day they walk through the scenarios against the design. They leave with a short list of risks and trade-offs to follow up.

## Trade-offs

Speed comes at a price.

- **Less complete.** Lightweight reviews do not claim to find all risks. They aim to find some of them in a short time.
- **Depends on people.** The result relies heavily on the group's understanding of the system, its context, and its creativity. Full ATAM is more rigorous in this respect.

Choose a lightweight review when speed and low effort matter more than full coverage.



## Checks

- The document states whether the architecture review was a full ATAM or a lightweight variant.
- The document records who ran the lightweight review: external parties, the team, or both.
- The document admits that a lightweight review may not have uncovered all risks.
- The review results list trade-offs, sensitivity points, and risks or non-risks.

## Related

- [Architecture Tradeoff Analysis Method (ATAM)](https://arc.fuet.ch/concepts/evaluation/architecture-tradeoff-analysis-method-atam.md)
- [Advantages and Drawbacks of ATAM](https://arc.fuet.ch/concepts/evaluation/advantages-and-drawbacks-of-atam.md)
- [Lightweight Approach for Software Reviews (LASR)](https://arc.fuet.ch/concepts/evaluation/lightweight-approach-for-software-reviews-lasr.md)
- [ATAM Findings: Risks, Non-Risks, Sensitivity Points and Trade-off Points](https://arc.fuet.ch/concepts/evaluation/atam-findings-risks-non-risks-sensitivity-points-and-trade-offs.md)
- [Software Architecture Evaluation](https://arc.fuet.ch/concepts/evaluation/software-architecture-evaluation.md)
- [Sensitivity Point](https://arc.fuet.ch/concepts/evaluation/sensitivity-point.md)
- [Trade-off Point](https://arc.fuet.ch/concepts/evaluation/trade-off-point.md)
- [ATAM Non-Risk](https://arc.fuet.ch/concepts/evaluation/atam-non-risk.md)

## Sources

- [Risk analysis with lightweight architecture reviews | heise online](https://www.heise.de/en/background/Risk-analysis-with-lightweight-architecture-reviews-10355745.html) — heise.de, accessed 2026-11-09
- [FAQ - Architecture Tradeoff Analysis Method](https://dmccreary.github.io/atam/faq/) — dmccreary.github.io, accessed 2026-11-09
- [Architecture tradeoff analysis method - Wikipedia](https://en.wikipedia.org/wiki/Architecture_tradeoff_analysis_method) — en.wikipedia.org, accessed 2026-11-09