The ATAM method (Architecture Tradeoff Analysis Method) is used to evaluate the quality of software architectures by analyzing the trade-offs between different architectural decisions. It helps to understand the impact of design decisions on quality attributes such as performance, security, and maintainability.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Executable approach: can be applied and produces an outcome.
What organizes, connects, or makes decisions possible.
ATAM is a facilitated process for evaluating architecture decisions through quality attributes, scenarios, and risks.
The Software Engineering Institute developed ATAM in the 1990s to expose interactions between architecture decisions and quality requirements systematically. Its name explicitly highlights trade-offs between competing quality goals.
Imagine a structural inspection with several building plans: each plan is tested for stability, cost, and flexibility, revealing where the goals conflict.
The effect of an architecture decision on a quality goal.
A decision whose change strongly affects a quality goal.
A conflict in which improving one property burdens another.
ATAM structures architecture discussions and makes critical decisions traceable. It does not generate an architecture automatically and depends on realistic scenarios and engaged stakeholders.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.