anchor.diff:  [[ATAM]]
  -=== [pattern]#ATAM#
  +=== [pattern]#Atam#
   
   Architecture Tradeoff Analysis Method. Systematic approach to find architectural 
   risks, tradeoffs and sensitivity points.
  
positive.code: 
  The ATAM method:
  
  * provides precise quality requirements,
  * discloses the design decisions of the architecture,
  * promotes the communication between the project members.
  
  [IMPORTANT]
  The ATAM method does not develop concrete measures, strategies or 
  tactics against the found risks. 
  
  
  ==== Applicability
  
  
negative.code: 
  . *Preparation*:
    .. 'Identify the relevant stakeholders': 
        The specific goals of the relevant stakeholders define the primary  
        goals of the architecture. Who belongs to these _relevant_ stakeholders
        has to be determined by a <<Stakeholder-Analysis>>.  
     
  . *Kickoff*:
    .. 'Present the ATAM method':
        Convince the relevant stakeholders of the significance of 
        comprehensible and specific architecture and quality goals. 
        ATAM helps identify risks, non-risks, tradeoffs and sensitivity points. 
        Calculation of quantitative attributes is not subject of this method.
      
    .. 'Present the business objectives and architecture goals':
        Present the business context to the relevant stakeholders, especially the
        _business motivation and reasons_ for the development of the system. 
        Clarify specific requirements that the architecture should meet, 
        for instance flexibility, modifiability and performance.
        
    .. 'Present the architecture of the system':
        The architect presents the _architecture_ of the system. This includes:
        
        * All other systems with interactions to the <<SuD>>,
        * building blocks of the top abstraction level,
        * runtime views of some important use cases,
        * change or modification scenarios. 
  
    
  . *Evaluation*:
    .. 'Explain in detail the architecture approaches':
  