Architecture tradeoff analysis method

This is an old revision of this page, as edited by Renny Barrett (talk | contribs) at 09:22, 13 April 2007 (ATAM Benefits). The present address (URL) is a permanent link to this revision, which may differ significantly from the current revision.

In software engineering, Architecture Tradeoff Analysis Method (ATAM) is a risk-mitigation process used early in the software development life cycle.

ATAM was developed by the Software Engineering Institute at the Carnegie Mellon University. Its purpose is to help choose a suitable architecture for a software system by discovering trade-offs and sensitivity points.

ATAM is most beneficial when done early the software development life-cycle when the cost of changing architectures is minimal.

ATAM Benefits

The following are some of the benefits of the ATAM process:

  • Promotes the gathering of precise quality requirements
  • Creates an early start at architecture documentation
  • Creates a documented basis for architectural decisions
  • Promotes identification or risks early in the life-cycle
  • Encourages increased communication among stakeholders

ATAM Process

The ATAM process consists of gathering stakeholders together to analyze business drivers and from these drivers extract quality attributes that are used to create scenarios. These scenarios are then use in conjunction with architectural approaches and architectural decisions to create an analysis of trade-offs, sensitivity points, and risks (or non-risks). This analysis can be converted to risk themes and their impacts whereupon the process can be repeated.

See also