3/14/2006USC-CSE1 Ye Yang, Barry Boehm Center for Software Engineering University of Southern California COCOTS Risk Analyzer and Process Usage Annual.

Slides:



Advertisements
Similar presentations
AASHTO Internal Audit Conference 2012 – Phoenix Daniel Fodera, CMQ/OE Program Management Improvement Team Federal Highway Administration.
Advertisements

PROJECT RISK MANAGEMENT
Empirical Research at USC-CSE Barry Boehm, USC-CSE ISERN Presentation October 8, 2000
University of Southern California Center for Systems and Software Engineering A Look at Software Engineering Risks in a Team Project Course Sue Koolmanojwong.
Project Management Gaafar 2007 / 1 This Presentation is uses information from PMBOK Guide 2000 Project Management Risk Management* Dr. Lotfi Gaafar.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Ricardo Valerdi USC Center for Systems and Software.
University of Southern California Center for Software Engineering C S E USC Barry Boehm, USC USC-CSE Executive Workshop March 15, 2006 Processes for Human.
OTS Integration Analysis using iStudio Jesal Bhuta, USC-CSE March 14, 2006.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
Software in Acquisition Workshop Software Expert Panel Working Groups and Tasks Rick Selby DoD Software In Acquisition.
University of Southern California Center for Software Engineering CSE USC ©USC-CSE 10/23/01 1 COSYSMO Portion The COCOMO II Suite of Software Cost Estimation.
A Model-Driven Framework for Architectural Evaluation of Mobile Software Systems George Edwards Dr. Nenad Medvidovic Center.
10/25/2005USC-CSE1 Ye Yang, Barry Boehm USC-CSE COCOTS Risk Analyzer COCOMO II Forum, Oct. 25 th, 2005 Betsy Clark Software Metrics, Inc.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Barry Boehm USC Center for Systems and Software Engineering.
Computer Engineering 203 R Smith Risk Management 7/ Risk Management The future can never be predicted with 100% accuracy. Failure to plan for risks.
Constructive COTS Model (COCOTS) Status Chris Abts USC Center for Software Engineering Annual Research Review Annual Research Review.
Risk Analysis and Mitigation with Expert COSYSMO Ray Madachy, Ricardo Valerdi Naval Postgraduate School MIT Lean Aerospace Initiative
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
University of Southern California Center for Systems and Software Engineering Assessing the IDPD Factor: Quality Management Platform Project Thomas Tan.
University of Southern California Center for Software Engineering CSE USC USC-CSE Annual Research Review COQUALMO Update John D. Powell March 11, 2002.
Copyright USC-CSSE 1 Quality Management – Lessons of COQUALMO (COnstructive QUALity MOdel) A Software Defect Density Prediction Model AWBrown.
© USC-CSE1 Determine How Much Dependability is Enough: A Value-Based Approach LiGuo Huang, Barry Boehm University of Southern California.
Estimating System of Systems Engineering (SoSE) Effort Jo Ann Lane, USC Symposium on Complex Systems Engineering January 11-12, 2007.
COTS Based System Security Economics - A Stakeholder/Value Centric Approach Related tool demo session: COTS Based System Security Test-bed (Tiramisu) Tuesday.
Expert COSYSMO Update Raymond Madachy USC-CSSE Annual Research Review March 17, 2009.
University of Southern California Center for Software Engineering CSE USC Distributed Assessment of Risk Tool DART Jesal Bhuta
University of Southern California Center for Systems and Software Engineering Decision Support for Value-Based Software Testing Framework Qi Li, Barry.
University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy
1 COSYSMO 2.0: A Cost Model and Framework for Systems Engineering Reuse Jared Fortune University of Southern California Ricardo Valerdi Massachusetts Institute.
University of Southern California Center for Software Engineering CSE USC ©USC-CSE 3/11/2002 Empirical Methods for Benchmarking High Dependability The.
USC CSSE Top 10 Risk Items: People’s Choice Awards Barry Boehm, Jesal Bhuta USC Center for Systems & Software Engineering
Local Bias and its Impacts on the Performance of Parametric Estimation Models Accepted by PROMISE2011 (Best paper award) Ye Yang, Lang Xie, Zhimin He (iTechs)
University of Southern California Center for Software Engineering C S E USC Agile and Plan-Driven Methods Barry Boehm, USC USC-CSE Affiliates’ Workshop.
NCHRP 8-60 Risk Analysis Tools and Management Practices to Control Transportation Project Costs Keith R. Molenaar, PhD Stuart D. Anderson, PhD, PE Transportation.
University of Southern California Center for Systems and Software Engineering Improving Affordability via Value-Based Testing 27th International Forum.
«Enhance of ship safety based on maintenance strategies by applying of Analytic Hierarchy Process» DAGKINIS IOANNIS, Dr. NIKITAKOS NIKITAS University of.
PRM 702 Project Risk Management Lecture #28
COCOMO-SCORM: Cost Estimation for SCORM Course Development
PMI Knowledge Areas Risk Management.
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
HIT241 - RISK MANAGEMENT Introduction
VTT-STUK assessment method for safety evaluation of safety-critical computer based systems - application in BE-SECBS project.
Quick Recap Monitoring and Controlling. Phases of Quality Assurance Acceptance sampling Process control Continuous improvement Inspection before/after.
1 Project Risk Management Project Risk Management Dr. Said Abu Jalala.
© USC-CSE 2001 Oct Constructive Quality Model – Orthogonal Defect Classification (COQUALMO-ODC) Model Keun Lee (
Lecture 7 Risk Analysis CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6 Barry.
Ch 10 - Risk Management Learning Objectives You should be able to: List and describe risk management processes, inputs, outputs, and tools List and describe.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.
Chapter 3 Strategic Information Systems Planning.
BSBPMG504A Manage Project Costs 7.1 Estimate Costs Adapted from PMBOK 4 th Edition InitiationPlanning ExecutionClose Monitor Control The process of developing.
Project Risk Management Planning Stage
University of Southern California Center for Software Engineering CSE USC SCRover Increment 3 and JPL’s DDP Tool USC-CSE Annual Research Review March 16,
Information Technology Project Management Managing IT Project Risk.
University of Southern California Center for Systems and Software Engineering Reducing Estimation Uncertainty with Continuous Assessment: Tracking the.
University of Southern California Center for Systems and Software Engineering NDI/Services Integration Analysis Pongtip Aroonvatanaporn October 16, 2009.
The COCOMO model An empirical model based on project experience. Well-documented, ‘independent’ model which is not tied to a specific software vendor.
University of Southern California Center for Systems and Software Engineering COTS Selection Sergio Romulo Salazar April 28, 2010.
University of Southern California Center for Systems and Software Engineering Reducing Estimation Uncertainty with Continuous Assessment Framework Pongtip.
LECTURE 5 Nangwonvuma M/ Byansi D. Components, interfaces and integration Infrastructure, Middleware and Platforms Techniques – Data warehouses, extending.
ON “SOFTWARE ENGINEERING” SUBJECT TOPIC “RISK ANALYSIS AND MANAGEMENT” MASTER OF COMPUTER APPLICATION (5th Semester) Presented by: ANOOP GANGWAR SRMSCET,
Project Cost Management
A Framework for Integrating Systems and Software Engineering
Build vs. Buy WSATA Panel Discussion
Model-Driven Analysis Frameworks for Embedded Systems
The Extensible Tool-chain for Evaluation of Architectural Models
Phase Distribution of Software Development Effort
Mumtaz Ali Rajput +92 – SOFTWARE PROJECTMANAGMENT Mumtaz Ali Rajput +92 –
Project Risk Management
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6
Presentation transcript:

3/14/2006USC-CSE1 Ye Yang, Barry Boehm Center for Software Engineering University of Southern California COCOTS Risk Analyzer and Process Usage Annual Research Review Mar. 14 th, 2006

3/14/2006USC-CSE2 Outline Motivation COCOTS Model COCOTS Risk Analyzer Evaluation Process Usage: Risk-Based Prioritization Conclusions

3/14/2006USC-CSE3 Motivation Enable COTS integration risk analysis with COCOTS cost estimation inputs Identify relative risk levels of COTS-based development (CBD) Provide recommendations to improve risk management practices

3/14/2006USC-CSE4 COCOTS Model - Calibrated to 20 industry projects

3/14/2006USC-CSE5 COCOTS Glue Code Sub-model

3/14/2006USC-CSE6 COCOTS Risk Analyzer

3/14/2006USC-CSE7 Knowledge Base Contents –Risk Rules (RR) –Risk level scheme –Common risk mitigation strategy Constructing approach –Expert Delphi Survey –Empirical study results –Literature review

3/14/2006USC-CSE8 Risk Rule A CBD risk situation –a combination of two cost attributes at their extreme ratings Risk Rule (RR) –An identified risk situation is formulated as a risk rule. E.g. one example RR: IF ((COTS Product Complexity > Nominal) AND (Integrator’s Experience on COTS Product < Nominal)) THEN there is a project risk.

3/14/2006USC-CSE9 Risk Situation Identification Total # of Delphi responses: 5 # of responses % of responses # of risk situations >=3>50%24 240%26 120%28 24 Risk Rules formulated in the knowledge base >=50%40%20% (Percentage of responses over total)

3/14/2006USC-CSE10 Risk Potential Rating for Cost Factors Mapping between cost factor’s rating to its risk potential rating:

3/14/2006USC-CSE11 Risk Level Scheme Assignment of risk probability levels: Risk levelQuantifier Severe0.4 Significant0.2 General0.1 Quantitative weighting scheme:

3/14/2006USC-CSE12 Productivity Range Reflects the cost consequence of risk occurring Combines both expert judgment and industry data calibration

3/14/2006USC-CSE13 Project Risk Quantification Project Overall Risk: –Riskprob ij corresponds to the nonlinear relative probability of the risk occurring –The product of PR i and PR j represents the cost consequence of the risk occurring Risk interpretation: –Normalized scale: 0 ~ 100 –100 represents the situation where each cost factor is rated at its most expensive extremity –0 ~ 5: low risk; 5 ~ 15: medium risk; 15 ~ 50: high risk; 50 ~ 100: very high risk

3/14/2006USC-CSE14 Risk Mitigation Recommendations Knowledge base built on previous empirical study results, e.g.: Risk RuleRisk SituationMitigation Advice APCPX_ACIPC (High, Very Low) Complex integration with inexperienced personnel Consider more compatible COTS; re-staffing; training; consultant mentoring ACREL_ACPMT (High, Low) High-reliability application dependent on immature COTS Consider more mature COTS; reliability-enhancing COTS wrappers; risk-based testing ACPER_AAREN (High, Very Low) Unvalidated architecture with COTS performance shortfalls Benchmark current and alternative COTS choices; reassess performance requirements vs. achievables

3/14/2006USC-CSE15 Evaluation Results Data: 9 USC e-services projectsData: 7 COCOTS calibration projects

3/14/2006USC-CSE16 Process Usage – An Example COTS A and B are our strongest COTS choices –But there is some chance that they have incompatible HCI’s –Probability of loss P(L) COTS C is almost as good as B, and it is compatible with A

3/14/2006USC-CSE17 Risk-Driven CBD Process Framework

3/14/2006USC-CSE18 Different Risk Strategy Resulting in Different Process

3/14/2006USC-CSE19 Conclusions CBD brings a host of unique risk items Many risk techniques/tools require intensive user inputs COCOTS Risk Analyzer provides a handy way to automate the CBD risk analysis by leveraging on existing knowledge and expertise in both cost estimation and risk mgmt. Case study shows how it supports process decisions following the risk based prioritization strategy

3/14/2006USC-CSE20 Backup Slides

3/14/2006USC-CSE21 Risk Potential Rating Captures the underlying relation between cost attributes and the impact of their specific ratings on project risk –4 Levels OK, Moderate, Risk Prone, and Worst Case Two types of treatments –Transforming continuous Size representation into discrete risk potential ratings –Mapping cost driver ratings into risk potential ratings

3/14/2006USC-CSE22 Risk Potential Rating for Size Delphi Responses for Size Rating (Size in KSLOC):

3/14/2006USC-CSE23 Risk Based Prioritization Strategy