ATAM-steps | How to do architecture tradeoff analysis
1. Present the ATAM
2. Present business drivers
3. Present architecture
Identify and Analyze.
4. Identify architectural approaches
5. Generate quality attribute utility tree
6. Analyze architectural approaches against import Attribute
Brainstorm and Validate Architecture Decision
7. Brainstorm and prioritize scenarios
8. Validate architectural approaches (continuation from step 6) Conclude
9. Present results
ATAM StepsIf you are using ATAM evaluation - you will go thru these steps
STEP 1Presents an overview of the ATAM including:
Purpose, expectations, utility tree generation, scenarios, risks, “non-risks”, sensitivity points and tradeoffs
The objective of this step is to educate about ATAM Method.
STEP 2Customer representative describes the business drivers including
Business context for the system, High-level functional requirements
High-level quality attribute requirements
Quality attributes most central to the system’s success
Objective of this step is educate everyone about key business drivers.
STEP 3Architect presents an overview of the architecture including: Layering
Important attribute and constraints such as an OS, hardware, tools
Other systems with which the system must interact
Objective of this method is to get familair with architecture decision made.
Many times bussiness owner/Customer does not want to get invove in architecture.  They treat this as "How" and business want to focus on "What".  It is important to realize that Business owner is getting familiar with architecture decision to ensure business requirements will be met.  Any trade off in architecture is taken in favor of those requirement that matter most to business user.
STEP 4Start to identify places in the architecture that are key for realizing quality attribute goals.
Identify any predominant architectural approaches.
Replication or SSIS
Serach or Navigation
Search or Database query
Adhoc Reports or Standard Reports
In this phase you focus on architecture apppraches that have impact on delivering requirement.  Using Search user can enter free form text and get input.  Using navigation user can only select from predefined option.  In Navigation system control the output.  In Search content control the output/
Step 5Identify Quality Attribute
Output: In this phase you produce a output that show prioritization of specific quality attribute requirements.
Step 6Evaluate architecture from Quality Attribute Perspective
In this phase valuation Team probes architectural approaches from the point of view of specific quality attributes to identify risks.
At this point there is - A set of concrete quality requirements + a set of architectural approaches => Size up how well suited they are to each other
Output of this phase
Step 7Brainstorm and Prioritize Scenario
The ATAM evaluation team ask the stakeholders to brainstorm:
Step 8Validate Architecture Decisions
In this Step you validate
If you have done most of things right, very little/no new information will be uncovered
Team should validate that architecture decisions are in favor of utility required by business. If not, then architecture decision need to be corrected.
Step 9Present the Results
The collected information from the ATAM exercise is presented back to the stakeholders
10-Risks 11-Non-Risks 2-why-to-use-atam 3-What-does-ATAM-discover 4-ATAM-Cost-and-benefits 5-ATAM-roles 6-ATAM-Steps-Summary 7-ATAM-Steps 8-Tradeoffs 9-Sensitivity-Points