0
ATAM
(An Architecture Tradeoff Analysis Method)
1
Dr. Himanshu Hora
SRMS College of Engineering & Technology, Bareilly
An architecture Tradeoff Analysis Method
 ATAM is designed to elicit the business goals for the
system as well as for the...
Participants in ATAM
 The evaluation team.
 Project decision makers.
 Architecture stakeholders.
Evaluation team includes:-
• Team leader
• Evaluation leader
• Scenario scribe
• Proceedings scribe
• Timekeeper
• Process...
Stakeholders include:-
 developers, testers.
 users,
 builders of systems interacting with this one
Outputs of ATAM
 A concise presentation of the architecture.
 Articulation of business goals.
 Quality requirement in t...
Conceptual flow of ATAM
Phases of the ATAM
Steps of the Evaluation Phase
• Present the ATAM
• Present Business drivers
• Present Architecture
• Identify architectura...
ThankYou
Dr. Himanshu Hora
SRMS College of Engineering & Technology, Bareilly
Upcoming SlideShare
Loading in...5
×

ATAM

740

Published on

Published in: Education, Technology
0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
740
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
44
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide

Transcript of "ATAM"

  1. 1. ATAM (An Architecture Tradeoff Analysis Method) 1 Dr. Himanshu Hora SRMS College of Engineering & Technology, Bareilly
  2. 2. An architecture Tradeoff Analysis Method  ATAM is designed to elicit the business goals for the system as well as for the architecture.  ATAM is so named because it reveals how well an architecture satisfies particular quality goals and it provides insight into how quality goals interact-that is, how they tradeoff. ATAM is a comprehensive way to evaluate a software architecture.
  3. 3. Participants in ATAM  The evaluation team.  Project decision makers.  Architecture stakeholders.
  4. 4. Evaluation team includes:- • Team leader • Evaluation leader • Scenario scribe • Proceedings scribe • Timekeeper • Process observer • Process enforcer • Questioner
  5. 5. Stakeholders include:-  developers, testers.  users,  builders of systems interacting with this one
  6. 6. Outputs of ATAM  A concise presentation of the architecture.  Articulation of business goals.  Quality requirement in terms of collection of scenarios.  Mapping of architectural decisions to quality requirements.  A set of identified sensitivity and tradeoff points.  A set of risks and non risks.  A set of risk themes.
  7. 7. Conceptual flow of ATAM
  8. 8. Phases of the ATAM
  9. 9. Steps of the Evaluation Phase • Present the ATAM • Present Business drivers • Present Architecture • Identify architectural approaches • Generate quality attribute utility tree • Analyze architectural approaches • Brainstorm and prioritize scenarios • Analyze architectural approaches • Present results
  10. 10. ThankYou Dr. Himanshu Hora SRMS College of Engineering & Technology, Bareilly
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×