| Capability Pattern: Architecture Tradeoff Analysis Method (ATAM) |
 |
 |
|
| Description |  | Work Breakdown Structure |  | Team Allocation | | Work Product Usage |  | |
|  | |
|||||||
|
|||||||||
Purpose
| To evaluate the software architecture. |
Relationships
| Context |
|---|
Description
The Architecture Tradeoff Analysis Method (ATAM) is a method for evaluating the architecture to determine whether the architecture is fulfilling its requirements. This is primarily about non-functional requirements. The flow of the evaluation method is shown in the figure below.
The ATAM is explained in detail in the Clements, Kazman, and Klein reference on the references page. It is used in conjunction with the Architecture Evaluation practice area. |
Properties
| Event-Driven |  |
|---|---|
| Multiple Occurrences | |
| Ongoing | |
| Optional | |
| Planned |  |
| Repeatable | |
Key Considerations
| ATAM is a service mark of the Software Engineering Institute. Use of the ATAM requires either an engagement with the SEI or training company people and then licensing the echnology from the SEI. |