Risk Modeling The Tropos Approach PhD Lunch Meeting 07/07/2005 Yudistira Asnar –

Slides:



Advertisements
Similar presentations
Algorithm Design Techniques
Advertisements

Chapter 7 Managing Risk.
Heuristic Search techniques
ARCHITECTURES FOR ARTIFICIAL INTELLIGENCE SYSTEMS
Group Recommendation: Semantics and Efficiency
Interactive Configuration
1 Fault-Tolerant Computing Systems #6 Network Reliability Pattara Leelaprute Computer Engineering Department Kasetsart University
Imbalanced data David Kauchak CS 451 – Fall 2013.
Greedy Algorithms Greed is good. (Some of the time)
Part 3 Probabilistic Decision Models
Best-First Search: Agendas
4. Project Investment Decision-Making
A Robust Process Model for Calculating Security ROI Ghazy Mahjub DePaul University M.S Software Engineering.
CS 589 Information Risk Management 23 January 2007.
Page 1 Building Reliable Component-based Systems Chapter 10 - Predicting System Trustworthiness Chapter 10 Predicting System Trustworthiness.
Scaling Personalized Web Search Glen Jeh, Jennfier Widom Stanford University Presented by Li-Tal Mashiach Search Engine Technology course (236620) Technion.
Information Retrieval: Human-Computer Interfaces and Information Access Process.
1 Risk evaluation Risk treatment. 2 Risk Management Process Risk Management Process.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Hazards Analysis & Risks Assessment By Sebastien A. Daleyden Vincent M. Goussen.
Annex I: Methods & Tools prepared by some members of the ICH Q9 EWG for example only; not an official policy/guidance July 2006, slide 1 ICH Q9 QUALITY.
Goal Motivation Chapter 11. Chapter 11 Goal Motivation Reinforcers, Incentives, Goals Reinforcers  Have increased the rate or probability of behavior.
Non-functional requirements
Project Risk Management
Classical Planning Chapter 10.
Software Project Management Lecture # 8. Outline Chapter 25 – Risk Management  What is Risk Management  Risk Management Strategies  Software Risks.
Transfer Graph Approach for Multimodal Transport Problems
Software Project Management Lecture # 8. Outline Earned Value Analysis (Chapter 24) Topics from Chapter 25.
Managing Risk. Objectives  To Describe Risk Management concepts and techniques  To calculate and analyze a project using Probability of completion 
Risk Management - the process of identifying and controlling hazards to protect the force.  It’s five steps represent a logical thought process from.
ERT 312 SAFETY & LOSS PREVENTION IN BIOPROCESS RISK ASSESSMENT Prepared by: Miss Hairul Nazirah Abdul Halim.
Verification and Validation Overview References: Shach, Object Oriented and Classical Software Engineering Pressman, Software Engineering: a Practitioner’s.
Theory Revision Chris Murphy. The Problem Sometimes we: – Have theories for existing data that do not match new data – Do not want to repeat learning.
Applying Tropos to Socio-Technical System Design and Runtime Configuration Fabiano Dalpiaz, Raian Ali, Yudistira Asnar, Volha Bryl, Paolo Giorgini Dipartimento.
Querying Structured Text in an XML Database By Xuemei Luo.
程建群 博士 (Dr. Jason Cheng) 年 03 月 Software Engineering Part 05.
FAULT TREE ANALYSIS (FTA). QUANTITATIVE RISK ANALYSIS Some of the commonly used quantitative risk assessment methods are; 1.Fault tree analysis (FTA)
The Connection between Risk Management and Internal Control in Organizations Mag. Norbert Wagner Budapest,
Software Project Management
Integrated Risk Management Charles Yoe, PhD Institute for Water Resources 2009.
Telerik Software Academy Software Quality Assurance.
Chapter McGraw-Hill/Irwin Copyright © 2008 by The McGraw-Hill Companies, Inc. All rights reserved. Risk and Capital Budgeting 13.
RCM Tools Histogram Pareto Chart Cause and Effect Diagram FMEA.
Certified Protection Officer Program. Chapter 1 Unit 1 Concepts and Theories of Asset Protection Pages 3-11.
TUGAS K3 DALAM INDUSTRI KIMIA
Problem Reduction So far we have considered search strategies for OR graph. In OR graph, several arcs indicate a variety of ways in which the original.
R ISK A NALYSIS & M ANAGEMENT. Risk – possibility that an undesirable event (called the risk event) could happen – Involve uncertainty and loss – Events.
©2005 Prentice Hall Business Publishing, Introduction to Management Accounting 13/e, Horngren/Sundem/Stratton Capital Budgeting Chapter 11.
1 Project Management C53PM Session 4 Russell Taylor Staff Work-base – 1 st Floor
Suppose G = (V, E) is a directed network. Each edge (i,j) in E has an associated ‘length’ c ij (cost, time, distance, …). Determine a path of shortest.
1 PowerPointPresentation by PowerPoint Presentation by Gail B. Wright Professor Emeritus of Accounting Bryant University © Copyright 2007 Thomson South-Western,
Dolly Dhamodiwala CEO, Business Beacon Management Consultants
Chapter 13 Risk Management. Chapter Objectives 1.Define risk and risk management 2.Outline key risk issues and types of risk 3.Identify concrete methods.
DARSHANA RAGHU MANAGEMENT. Risk Management Risk management is the identification, assessment, and prioritization of risks followed by coordinated and.
Toward a New ATM Software Safety Assessment Methodology dott. Francesca Matarese.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
October 22, 2005 Parvaiz Ahmed Khand An Overview of Software Safety.
Risk Management in Software Development Projects Roberto Torres Ph.D. 11/6/01.
 System Requirement Specification and System Planning.
Fault Trees.
CSC Modeling with FD Constraints
ESET 419 Engineering Technology Capstone I
Improvement Selection:
Task: It is necessary to choose the most suitable variant from some set of objects by those or other criteria.
Tradeoff Analysis of Strategies for System Qualities
Risk-informed Decision Making under Incomplete Information
Paper by D.L Parnas And D.P.Siewiorek Prepared by Xi Chen May 16,2003
Hazards Analysis & Risks Assessment
Definitions Cumulative time to failure (T): Mean life:
A New Concept for Laboratory Quality Management Systems
Presentation transcript:

Risk Modeling The Tropos Approach PhD Lunch Meeting 07/07/2005 Yudistira Asnar –

Definition Failure: The inability of a system or component to perform its required functions within specified performance Failure mode: The physical or functional manifestation of a failure Model of Risk: Likelihood, but also effect of the failure Risk = Likelihood * Severity –Severity: [0,5] –Likelihood: [0,1]

Every Choice has the own consequences

Risk Modeling

Goal Analysis

Objective of Risk Analysis Traditionally: –Find the most effective and efficient set of mitigation plans such that the risk can be manageable  Strategy of choosing option –Increasing Quality of System (Reliability, Safety, Available, etc) Tropos Approach: The evaluation of the best solution must be based on –Adopt traditional ones –REAL Cost is the cost of achieving main goals and the cost of associated Mitigation Plans This means selecting subgoals taking into account their risks and the associated mitigation plans –We should optimize not only one of them, but both at the same time

Basic Assumption Failure Mode-Risk can be associated with Objective-Asset Tropos: Goal, Task/Plan, Resource Property of Assets (Necessary): –Rank –Threshold (Confidence Level): Denial Likelihood (DL) [0,1] Satisfaction Level (SL) [0,100]

Risk Analysis Scenario Given Threshold of each assets –Find the most efficient set of solutions, that can be acceptable for given threshold (satisfaction level and denial likelihood) Given Budget for accomplishment –Find the set of solutions (Assets and Mitigation) with the highest satisfaction level and the least denial likelihood How much does it cost for achieving the highest satisfaction and confidence level Etc.

Case Study

Computing Impact Top-Level Goals are annotated with their importance ( Imp ), that define by user Leaf-Goal has rank ( R ), value that come form the function. It calculates order among all of them. Failure modes are annotated with likelihood ( L ), a.k.a probability, and severity ( S ) Links between failure modes and goals are annotated with Impact ( I )[-20,20] (e.g. Satisfaction reduction)

Computing Impact The risk of a goal G is computed as Possibility of Loss ( PL ) PL G = R G * Σ G (S * L * |I|) ; I ≤ 0 Mitigation Plans are chosen in order to reduce PL G, until acceptable value PL G is acceptable if PL G ≤ R G * SL * DL If there is no mitigation plan for it, we can de- idealize (Confidence Level) of the least importance goal –How much we can do de-idealize?

Defining Importance Propagation Importance of Top-Level Goal (value: 1, 2, 3, etc., the bigger means more important) Set of Goals with the cheapest cost of satisfaction of top level goal Rules:[??] –And-Decomposition: AND(G1,G2)  G3 Imp G1 =Imp G2 =Imp G3 Cost G3 = Cost G1 + Cost G2 –Or-Decomposition: OR(G1,G2)  G3 Imp G3 =1; Imp G2 =[1,2) and Imp G3 =[1,2)  needs more precise Cost G2 > Cost G1 ↔ Imp G2 < Imp G1 Cost G3 = Min(Cost G1, Cost G2 ) –G3 is sub goal of G1 and G2 Imp G3 = Max(Imp G3-G1,Imp G3-G2 )

Defining Rank

Failure Mode Failure Mode contribute to Intermediate Goal, not just leaf goal Failure modes can contribute not only to goals but to other failure modes Failure Mode is traditionally represented as an isolated event, but in reality, there is interrelation among failure modes Failure Mode property: –Severity and Likelihood

Failure Mode Contribution of FM 1 to FM 2, depends on the intrinsic risk of FM 1 and the weight of edge connecting FM 1 to FM 2 Contribution among FMs can be meant: –Modifying Likelihood –Modifying Severity Weight of edge should represent both Traditional Fault Trees are incomplete and faults should be represented as graphs

Computing Risk In Case Study: –Contribution of Explosive User Added means increasing just likelihood of Limited Key Space R  Original Risk, R’  Contributed Risk, R”  Mitigated Risk –R 2 ”  R 2 * M 1 –R 1 ”  R 1 ’ * M 2 –R 1 ’  R 1 + R 2 ”

Failure Mode Identification Goal has 2 dimension: Satisfy and Maintain Failure Mode of Goal (Negative-Goal) –Undesired thing –Something that not suppose to be maintained Undesired Thing –Set-Theory A’ = U – A –What is the Universe? [??] Context Domain Something that not suppose to be maintained[??]

Mitigation Plan Mitigations are set of actions to reduce (Likelihood and Severity) of Failure Mode –Likelihood ≤ Threshold Denial-Likelihood –Severity * Impact ≤ Threshold Satisfaction-Level One mitigation action can reduce the one risk and can also increase the other risk Choosing plan with considering –Severity Level of Risk –Some mitigation plan give the same effect to one particular failure mode

Mitigation Plan Mitigations are annotated with Costs (C), Category (Transfer, Prevention, Detection, Retention, Alleviation, etc) Link between mitigation and failure mode is annotated as Effect (E) (e.g. reduce/increase the risks) Mitigation Plan Analysis –And-Or Decomposition –Positive-Negative Contribution Mitigation Plan contribute to Goal, instead of Failure Mode Mitigation Plan can fail Introducing concept of time constrain to satisfy goal and to accomplish mitigation

Mitigation Plan Identification Based on experience and repository [??]

Re-Writing Tree Solution to satisfy G1 and G6 –S1: G3,G4,G8 –S2: G3,G5,G8 –S3: G3,G4,G9,G10 –S4: G3,G5,G9,G10

Classic Approach Top-Down

Approach to Solve Classic: Top-Down  Bottom-Up  Adjustment Re-Writing Tree

S1: G3,G4,G8 + M1,M2,M3 S2: G3,G5,G8 + M2,M3 S3: G3,G4,G9,G10 + M1,M2,M3,M4 S4: G3,G5,G9,G10 + M2,M3,M4

Re-Writing Tree Find all possible set goal solutions to satisfy top-level goal Find all Mitigation Plans that is reachable from set goal solution Calculate (Cost, Confidence Level) all possible combination between set goal solutions and all subset of mitigation plans Needs something to reduce the search space

Severity - Mitigation Plan SeverityType of Mitigation Plan 0Ignorable 1Alleviation 2Alleviation, Transfer, Detection, Prevention 3Detection, Transfer, Prevention 4Transfer, Prevention 5Retention