Revision as of 15:19, 17 January 2007 edit Dmccreary (talk \| contribs) Extended confirmed users 2,008 edits No edit summary ← Previous edit		Revision as of 15:24, 17 January 2007 edit undo Dmccreary (talk \| contribs) Extended confirmed users 2,008 edits No edit summary Next edit →
Line 5: ATAM is most beneficial when done early the software development life-cycle when the cost of changing architectures is minimal. == ATAM Benefits == 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 tradeoffs, sensitivity points, and risks (or non-risks). This analysis can be converted to risk themes and their impacts whereupon the process can be repeated.▼ The following are some of the benefits of the ATAM process: * A method of gathering precise quality requirements * Early start at architecture documentation * Documented basis for architectural decisions * Identification or risks early in the life-cycle * 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 ~~tradeoffs~~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. ==External links==

Architecture tradeoff analysis method: Difference between revisions