Upcoming SlideShare
Loading in...5







Total Views
Views on SlideShare
Embed Views



0 Embeds 0

No embeds


Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
Post Comment
Edit your comment

Saam Saam Presentation Transcript

  • DR. HIMANSHU HORA SRMS College of Engg. & Tech., Bareilly (UP) INDIA
  • CONTENTS  What is SAAM  How to perform SAAM  What is a scenario  SAAM Activities
  • SOFTWARE ARCHITECTURE ANALYSIS METHOD  SAAM  Develop scenarios  Describe architectures  Classify scenarios  Direct, indirect  Evaluate indirect scenarios changes  Scenario interaction  Overall evaluation
  • STEPS TO PERFORM SAAM  Structured process for evaluating software architectures.  Before an architecture is finalized  How can this be done  Prepare description of candidate architectures  Evaluate impact of various scenarios  Identify issues with one architecture under study
  • SCENARIO  Definition  Brief description  Of a single interaction  Of a stakeholder  With the system  Stakeholder examples  User performing a desired operation  Maintainer making a system change
  • SAAM ACTIVITIES Scenario Development Architecture Description Scenario Classification Scenario Evaluation Interaction Assessment Overall Evaluation
  • SCENARIO DEVELOPMENT  Illustrate kinds of activities needed  During system usage and modification  Tasks relevant to all stakeholders  Process  Prepare agenda, record all discussion  Brainstorm “proto scenarios”  Remove unimportant ones  Keep “revealing” scenarios, merge others
  • ARCHITECTURE DESCRIPTION  Document candidate architectures  Use well understood notation, etc.  Cover all important aspects  Identify architectural styles  What level of presentation  Suitable for audience  Sufficient to address scenarios
  • SCENARIO CLASSIFICATION  Direct  Scenarios that the candidate architecture can handle without change  Indirect  Scenarios that are not directly supported  Require change to system  Change in component function  Addition of components  Addition of connections between components
  • SCENARIO EVALUATION  Identify needed changes for each scenario  Specific list of changes  Cost estimate  Weight difficulty of changes  Not just the number of changes  Create a table of evaluation results  Scenario  Anticipated changes to support requirements
  • INTERACTION ASSESSMENT  When multiple scenarios require changes to a single component  Scenarios are said to interact  May expose poor allocation of responsibility  If unrelated scenarios affect same component  Ok if related scenarios interact
  • OVERALL EVALUATION  To compare architectures  Assign weights to scenarios  Tabulate with cost estimates  Evaluation is subjective  Depends on all stakeholders
  • THANK YOU DR. HIMANSHU HORA SRMS College of Engg. & Tech., Bareilly (UP) INDIA