Architecture Evaluation Cost Benefit Analysis Method (CBAM)

Slides:



Advertisements
Similar presentations
ATAM Architecture Tradeoff Analysis Method
Advertisements

Planning and management of digital projects. Overview Assessing the feasibility to Assessing the feasibility to become digital Building selection criteria.
Point of Sale (POS) Client & Back Office Server. Operational Concept What is our Objective? What is our Objective? What are our Goals? What are our Goals?
Microsoft ® System Center Configuration Manager 2007 R3 and Forefront ® Endpoint Protection Infrastructure Planning and Design Published: October 2008.
Imbalanced data David Kauchak CS 451 – Fall 2013.
Computers in Banking and Retail CEL : C O M P U T E R S I N E V E R Y D A Y L I F E CEL 2 [Sec 2-4] Name: _____________________ Class: ____________ CEL:
Project Selection (Ch 4)
© 2010 Bennett, McRobb and Farmer1 Use Case Description Supplementary material to support Bennett, McRobb and Farmer: Object Oriented Systems Analysis.
Evaluating a Software Architecture By Desalegn Bekele.
Software Architecture – Centric Methods and Agile Development by Craig Castaneda.
Project Management Project Initiation & Selecting
The Profiles Database & Decision Support Tool for Prioritisation of Animal Health and Welfare Issues for Government Intervention SZER Project Team Jane.
Chapter 14 Assessing the Value of IT. Traditional Financial Approaches  ROI – Return on Investments Each area is considered an investment center ROI.
Chapter 4: Project Scope Management
Economic Perspectives in Test Automation: Balancing Automated and Manual Testing with Opportunity Cost Paper By – Rudolf Ramler and Klaus Wolfmaier Presented.
Chapter 10 Ranking and Value Management of Computer System Performance.
Active Review for Intermediate Designs [Clements, 2000]
Assignment of Weights Other methods, besides arbitrary, for weight assignment exist There are both direct and indirect weight elicitation techniques Source:
Business Driven Enterprise Architecture Assessment Methodology Josh Arceneaux August 16, 2011.
ORGANIZATION MANAGEMENT
Software Architecture in Practice Part Two: Creating an Architecture 2nd Ed. Len Bass, Paul Clements, Rick Kazman.
Introduction to Management Science
Trade Study Training Need and Goals Need Consistent methodologies and practices performing trade studies Pros/cons, advantages/disadvantages, customer/management.
The Quality Improvement Model
Software architecture evaluation
Architecture Tradeoff Analysis Method Based on presentations by Kim and Kazman
Performance Management Dan Robbins. Overview Define performance management Describe the process of developing a performance management system Discuss.
Software Performance Engineering Failure Modes and Effects Analysis Presented by Kevin Mobley.
9-1 Copyright © 2010 Pearson Education, Inc. Publishing as Prentice Hall Multicriteria Decision Making Chapter 9.
Multicriteria Decision Making
The Microsoft Office 2007 Enterprise Project Management Solution:
EVALUVATING SOFTWARE ARCHITECTURES FOR REAL-TIME SYSTEMS R.Kazman, M.Klein, P.Clements Software Engineering Institute Carnegie Mellon University.
Chapter 14 Managing Projects.
Evaluating Architectures: ATAM
CPSC 871 John D. McGregor Module 4 Session 3 Architecture Evaluation.
WinCBAM: From Requirements Negotiation to Software Architecture Decisions Hoh In Rick Kazman David Olson Texas A&M SEI/CMU Texas A&M From Software Requirements.
Reporting to Management Using Microsoft Project and EPM Derek Loar, Pcubed.
9-1 Chapter 9 Preevent Evaluation McGraw-Hill/Irwin©2007 The McGraw-Hill Companies, All Rights Reserved.
CoFM: An Environment for Collaborative Feature Modeling Li Yi Institute of Software, School of EECS, Peking University Key Laboratory of High Confidence.
Integrated Risk Management Charles Yoe, PhD Institute for Water Resources 2009.
LOGO Team Assignment 1 Software Architectures. LOGO K15T2- Group21 Contents Introduce to Sale system 1 Architecture Drivers 2 Minimal Acceptable Delivery.
Assessing the influence on processes when evolving the software architecture By Larsson S, Wall A, Wallin P Parul Patel.
Project Portfolio Management Business Priorities Presentation.
Requirements Management with Use Cases Module 10: Requirements Across the Product Lifecycle Requirements Management with Use Cases Module 10: Requirements.
Software Architecture Evaluation Methodologies Presented By: Anthony Register.
1 CHAPTER 4 DEVELOPING A BUSINESS PLAN: BUDGETING.
Copyright 2013 John Wiley & Sons, Inc. Chapter 3 Monitoring and Controlling the Transformation System.
John D. McGregor Architecture Evaluation
Sales Enablement Diagnostic Toolkit June 2014 SBI.
The ATAM method. The ATAM method (1/2) Architecture Tradeoff Analysis Method Requirements for complex software systems Modifiability Performance Security.
Training on Safe Hospitals in Disasters Module 3: Action Planning for “Safe Hospitals”
Analyzing an Architecture. Why analyze an architecture? Decide whether it solves the problem Compare to other architectures Assess what needs to change,
Slide 1 Software Construction Software Construction Lecture 3.
Principals & Self Study Coordinators. School Improvement Concepts Collaboration Data –Collect –Analyze –Use!!! Questions What? So What? Now What?
Requirements capture: Using UML Use Cases David Millard and Yvonne Howard {dem,
Concept Selection and DFMEA Heidi Ploeg Associate Professor Mechanical Engineering and Biomedical Engineering.
Increasing the Success of Business Analytics: Improving Requirements Determination? Ulrike Schultze, Cox School of Business, SMU.
Quality Attribute Workshop. Goal: To identify requirements Held early in development Includes stakeholders Outputs: Business Goals Quality Attribute Scenarios.
Lecture 15 Attribute Driven Design Again Topics ATAM – team expertise and experience needed Chapter 24 Next Time: June 22, 2016 CSCE 742 Software Architecture.
Lecture 15 Attribute Driven Design Again Topics ATAM – team expertise and experience needed Chapter 24 Next Time: June 22, 2016 CSCE 742 Software Architecture.
Part I Project Initiation.
Name: Date: Author: Version:
Lecture 12 Attribute Driven Design Again
Chapter 23: Economic Analysis of Architectures
Lecture 9z Case Study ADD: Garage Door
Project Management – PTM721S
Improvement Selection:
Analyzing an Architecture
Vanilson Burégio The Battlefield Control System – The First Case Study in Applying the ATAM Chapter 4 of: Clements, Paul et al., Evaluating.
Analyzing an Architecture
Presentation transcript:

Architecture Evaluation Cost Benefit Analysis Method (CBAM)

Overview 2

Motivation A set of architectural approaches/decisions/tactics/… can be applied –Add a redundant Web server? –Manage event rate towards Inventory? –Adhere to standard SQL? Resources for implementing decisions are finite –We need to choose? –Criteria? 3

Utility-Reponse Curves Some efforts... –Make little difference –Make a lot difference Key point –Variations of response measure 0: Useless 100:Excellent 4

Cost Benefit Analysis Method (CBAM) Economics-based approach to architecture decision analysis –Benefit of an architectural strategy, Bi Weighted and summed individual utility of strategy –Cost of architectural strategy, Ci –Return On Investment (ROI) for each strategy –Prioritize based on Ri May follow an ATAM evaluation –Uses a number of artefacts produced in an ATAM evaluation Business drivers Scenarios Architectural approaches 5

CBAM Steps 1. Collate Scenarios –Collect a set of scenarios (e.g., from ATAM) –Choose 1/3 based on importance according to business goals 2. Refine Scenarios –Focus on stimulus-response measures –Elicit worst-case, current, desired, and best- case response levels for each scenario 3. Prioritize Scenarios –100 votes for each stakeholder for scenarios –Top scenario is assigned weight 1.0 – the rest a weight relative to that 6

CBAM Steps 4. Assign Utility –Determine utility for each quality attribute response level for scenarios Utility = benefit of achieving the RM for QA 5. Develop Strategies –Develop strategies that address scenarios –Determine expected resulting response level 6. Determine Utility –Determine utility for strategy based on extrapolation 7

CBAM Steps 7. Calculate Benefit –Normalize utility increase with weights of scenarios to get benefit –Sum benefits for each scenario to get total benefit of strategy 8. Choose Strategies –Determine cost and schedule implications of each strategy –Calculate ROI as a ratio between benefit and cost –Choose strategies according to rank 9. Confirm Results –Consider alignment with business goals 8

Example: A POS system 9 Credits: Klaus Marius Hansen

1. Collate Scenarios ScenarioScenario Description 1The barcode scanner fails; continue in degraded mode 2The inventory system fails and the failure is detected 3The POS system should be extended to handle “supermarket” domains as well as “small shop” domains 4The POS systems scans a new item; item is looked up, price updated 10

2. Refine Scenarios 11 Response Goals ScenarioWorstCurrentDesiredBest 10 sec 5 min60 min 2Never 3 sec2,5 sec 32 years1 year6 months2 months 420 sec4 sec2 sec0,5 sec *) time before going from degraded mode to failure *)

3. Prioritize Scenarios 12 Response Goals ScenarioVotesWorstCurrentDesiredBest 1750 sec 5 min60 min 250Never 3 sec2,5 sec years1 year6 months2 months sec4 sec2 sec0,5 sec

4. Assign Utility 13 Utility Scores ScenarioVotesWorstCurrentDesiredBest

5. Develop Strategies 14 StrategyNameScenarios Affected Current Respons e Expected Response 1Heartbeat and cache 10 sec5 min 2Never3 sec 44 sec1 sec 2Virtual machine31 year3 months 44 sec6 sec 3Concurrency44 sec2 sec

6. Determine Utility 15 StrategyNameScenarios Affected Current Utility Expected Utility 1Heartbeat and cache Virtual machine Concurrency42085

7. Calculate Benefits 16 StrategyScenario Affected Scenario Weight BenefitNormalized Benefit Total Benefit

8. Choose Strategies 17 Strategy Cost Total Benefit Strategy ROI Strategy Rank , ,861 Choose top rank, implement, loop until no more funds...

Results A ranking of design decisions with respect to ROI Provides support for structured decision making Side effects –Discussions of costs and benefits –Clarification of scenarios and requirements Discussion –Uncertainties from lot of sources are multiplied quite a lot in this model  18

Summary Economy-based approach to evaluation of architectural strategies –Architectural strategy = set of design decisions Requires –Business drivers –Precise scenarios –Architectural strategies –Cost model Result –Ranking of architectural strategies according to ROI 19