Architecture tradeoff analysis method: Difference between revisions

Revision as of 14:16, 11 September 2024

Latest revision as of 10:50, 25 April 2025

(2 intermediate revisions by 2 users not shown)

Line 1:

{{Short description|Risk-mitigation process in software engineering}}

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

Line 7 ⟶ 8:

== ATAM benefits ==

The following are some of the benefits of the ATAM process:<ref>{{cite web|url=https://resources.sei.cmu.edu/library/asset-view.cfm?assetid=513908|title=Architecture Tradeoff Analysis Method|accessdate=2018-04-20|publisher=Carnegie Mellon Software Engineering Institute}}</ref>

* identified risks early in the life cycle.

* increased communication among stakeholders.

* clarified quality attribute requirements.

* improved architecture documentation.

* documented basis for architectural decisions.

== ATAM process ==

Line 28 ⟶ 29:

#Present results – provide all documentation to the stakeholders.

These steps are separated into two phases: Phase 1 consists of steps 1-6 and after this phase, the state and context of the project, the driving architectural requirements and the state of the architectural documentation are known. Phase 2 consists of steps 7-9 and finishes the evaluation.<ref>{{cite web|url=https://resources.sei.cmu.edu/asset_files/TechnicalReport/2000_005_001_13706.pdf|title=ATAM: Method for Architecture Evaluation|accessdate=2018-04-20|page=39f|author1=Rick Kazman |author2=Mark Klein |author3=Paul Clements |publisher=Carnegie Mellon Software Engineering Institute}}</ref>

== See also ==