Expert COSYSMO Update Raymond Madachy USC-CSSE Annual Research Review March 17, 2009.

Slides:



Advertisements
Similar presentations
The 20th International Conference on Software Engineering and Knowledge Engineering (SEKE2008) Department of Electrical and Computer Engineering
Advertisements

Guidebook for Risk Analysis Tools and Management Practices to Control Transportation Project Costs Keith R. Molenaar, PhD Stuart D. Anderson, PhD, PE Transportation.
On Representing Uncertainty In Some COCOMO Model Family Parameters October 27, 2004 John Gaffney Fellow, Software & Systems.
Software Cost Estimation Main issues:  What factors determine cost/effort?  How to relate effort to development time?
SBSE Course 3. EA applications to SE Analysis Design Implementation Testing Reference: Evolutionary Computing in Search-Based Software Engineering Leo.
Using the Semantic Web to Construct an Ontology- Based Repository for Software Patterns Scott Henninger Computer Science and Engineering University of.
COCOMO Suite Model Unification Tool Ray Madachy 23rd International Forum on COCOMO and Systems/Software Cost Modeling October 27, 2008.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Ricardo Valerdi USC Center for Systems and Software.
3/14/2006USC-CSE1 Ye Yang, Barry Boehm Center for Software Engineering University of Southern California COCOTS Risk Analyzer and Process Usage Annual.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
University of Southern California Center for Software Engineering CSE USC COSYSMO: Constructive Systems Engineering Cost Model Barry Boehm, USC CSE Annual.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 3/18/08 (Systems and) Software Process Dynamics Ray Madachy USC.
COSYSMO: Constructive Systems Engineering Cost Model Ricardo Valerdi USC CSE Workshop October 25, 2001.
Some Experience With COSYSMOR At Lockheed Martin
1 COSYSMO 3.0: Future Research Directions Jared Fortune University of Southern California 2009 COCOMO Forum Massachusetts Institute of Technology.
Software Metrics II Speaker: Jerry Gao Ph.D. San Jose State University URL: Sept., 2001.
Extensions of COSYSMO to Represent Reuse 21 st International Forum on COCOMO and Software Cost Modeling November 9, 2006 Ricardo ValerdiJohn Gaffney Garry.
Affiliate Feedback and Discussion 1. Future Research: COSYSMO Updated data collection effort Quantifying the effect of schedule Harmonizing across software.
Integrated COCOMO Suite Tool for Education Ray Madachy 24th International Forum on COCOMO and Systems/Software Cost Modeling November.
1 Systems Engineering Reuse Principles Jared Fortune, USC Ricardo Valerdi, MIT COSYSMO COCOMO Forum 2010 Los Angeles, CA.
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.
1 Results of Reuse Survey Jared Fortune, USC Ricardo Valerdi, MIT Gan Wang, BAE COSYSMO COCOMO Forum 2008 Los Angeles, CA.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Barry Boehm USC Center for Systems and Software Engineering.
Risk Analysis and Mitigation with Expert COSYSMO Ray Madachy, Ricardo Valerdi Naval Postgraduate School MIT Lean Aerospace Initiative
(c) Copyright, Lockheed Martin Corporation, Looking At Schedule vs. Effort In Software Engineering, Systems Engineering and Systems John Gaffney.
Copyright USC-CSSE 1 Quality Management – Lessons of COQUALMO (COnstructive QUALity MOdel) A Software Defect Density Prediction Model AWBrown.
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
1 Discussion on Reuse Framework Jared Fortune, USC Ricardo Valerdi, MIT COSYSMO COCOMO Forum 2008 Los Angeles, CA.
SQM - 1DCS - ANULECTURE Software Quality Management Software Quality Management Processes V & V of Critical Software & Systems Ian Hirst.
Systems Engineering Reuse: A Report on the State of the Practice Jared Fortune, USC Ricardo Valerdi, MIT Gan Wang, BAE Systems COCOMO Forum 2008 Los Angeles,
1 COSYSMO 2.0: A Cost Model and Framework for Systems Engineering Reuse Jared Fortune University of Southern California Ricardo Valerdi Massachusetts Institute.
UNCLASSIFIED Schopenhauer's Proof For Software: Pessimistic Bias In the NOSTROMO Tool (U) Dan Strickland Dynetics Program Software Support
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy USC Center for Systems and Software Engineering
©2006 BAE Systems. Practical Implementation of COSYSMO Reuse Extension Gan Wang, Aaron Ankrum, Cort Millar, Alex Shernoff, Ricardo Valerdi.
Towards COSYSMO 2.0: Update on Reuse Jared Fortune, USC Ricardo Valerdi, MIT USC ARR 2009 Los Angeles, CA.
Chapter 10: Architectural Design
COCOMO-SCORM: Cost Estimation for SCORM Course Development
1 Beyond California Water Plan Update 2005 California Water and Environmental Modeling Forum Annual Meeting, March 3 rd, 2005.
UML based dependability modeling, analysis and synthesis Proposers: TU Budapest: A. Pataricza, Gy. Csertán, I. Majzik, D. Varró PDCC Pisa: L. Simoncini,
Deliverable 2.6: Selective Editing Hannah Finselbach 1 and Orietta Luzi 2 1 ONS, UK 2 ISTAT, Italy.
University of Southern California Center for Systems and Software Engineering COSATMO/COSYSMO Workshop Jim Alstad, USC-CSSE Gan Wang, BAE Systems Garry.
1 Chapter 23 Estimation for Software Projects. 2 Software Project Planning The overall goal of project planning is to establish a pragmatic strategy for.
Management & Development of Complex Projects Course Code MS Project Management Perform Qualitative Risk Analysis Lecture # 25.
Lecture 4 Software Metrics
Lecture 7 Risk Analysis CSCI – 3350 Software Engineering II Fall 2014 Bill Pine.
1 Introduction to Software Engineering Lecture 1.
Cost Estimation What is estimated? –resources (humans, components, tools) –cost (person-months) –schedule (months) Why? –Personnel allocation –Contract.
Gan Wang 22 October th International Forum on COCOMO® and Systems/Software Cost Modeling in conjunction with the Practical Software and Systems.
2131 Structured System Analysis and Design By Germaine Cheung Hong Kong Computer Institute Lecture 8 (Chapter 7) MODELING SYSTEM REQUIREMENTS WITH USE.
University of Southern California Center for Systems and Software Engineering COCOMO Suite Toolset Ray Madachy, NPS Winsor Brown, USC.
BSBPMG504A Manage Project Costs 7.1 Estimate Costs Adapted from PMBOK 4 th Edition InitiationPlanning ExecutionClose Monitor Control The process of developing.
SFWR ENG 3KO4 Slide 1 Management of Software Engineering Chapter 8: Fundamentals of Software Engineering C. Ghezzi, M. Jazayeri, D. Mandrioli.
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Rational.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
University of Southern California Center for Systems and Software Engineering Reducing Estimation Uncertainty with Continuous Assessment Framework Pongtip.
University of Southern California Center for Systems and Software Engineering 26 th Annual COCOMO Forum 1 November 2 nd, 2011 Mauricio E. Peña Dr. Ricardo.
Towards a framework for architectural design decision support
Project management assignment, Spring 2017
Component Based Software Engineering
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
A test technique is a recipe these tasks that will reveal something
COSYSMO: Constructive Systems Engineering Cost Model
Towards COSYSMO 2.0: Update on Reuse
Software Engineering: A Practitioner’s Approach, 6/e Chapter 23 Estimation for Software Projects copyright © 1996, 2001, 2005 R.S. Pressman & Associates,
Software Cost Estimation
Chapter 26 Estimation for Software Projects.
Chapter 12 Analyzing Semistructured Decision Support Systems
Presentation transcript:

Expert COSYSMO Update Raymond Madachy USC-CSSE Annual Research Review March 17, 2009

2 Expert COSYSMO Introduction An expert system tool for systems engineering risk management based on the Constructive Systems Engineering Cost Model (COSYSMO) [Valerdi 2005] –Automatically identifies project risks in conjunction with cost estimation similar to Expert COCOMO [Madachy 1997] and provides related advice –Supports project planning by identifying, categorizing and quantifying system-level risks –Supports project execution with automated risk mitigation advice for management consideration Risk situations are characterized by combinations of cost driver values indicating increased effort with a potential for more problems –Includes 98 risk conditions Simultaneously calculates cost to enable tradeoffs with risk

3 Method Analyzes patterns of cost driver ratings submitted for a COSYSMO cost estimate against pre-determined risk rules –Identifies individual risks that an experienced systems engineering manager might recognize but often fails to take into account –Helps users determine and rank sources of project risk. With these risks, mitigation plans are created based on the relative risk severities and provided advice

4 Method (cont.) COSYSMO cost factor combinations used as abstractions for formulating risk heuristics –E.g. if Architecture Understanding = Very Low and Level of Service Requirements = Very High, then there is a high risk Since systems with high service requirements are more difficult to implement especially when the architecture is not well understood Elicitation of knowledge from systems engineering domain experts in CSSE-sponsored workshops –Survey used to identify and quantify risks Devised knowledge representation scheme and risk quantification algorithm All risk rules are fired when the effort multipliers of both cost factors involved are > 1.0 –Can be more granular for gradations of risk Recent extension for risk mitigation advice

5 Risk Conditions

6 Risk Taxonomy and Weighting ProjectRiskrisklevel effort multiplier product,    ij i categoryrisks j categories ij, * ## 11 where risk level =1moderate 2high 4very high effort multiplier product= (driver #1 effort multiplier) * (driver #2 effort multiplier)... * (driver #n effort multiplier). Project Risk Product riskProcess riskPersonnel riskPlatform risk

7 Expert COSYSMO Inputs

8 Expert COSYSMO Outputs

New Risk Mitigation Advice 9 All risks triggered when both related effort multipliers are > 1.0 See handout for review

Size Risk Elaboration Need to establish size range thresholds for risk rules COSYSMO size distribution: Min = 82, Max = 17,763 equivalent requirements Proposed ranges –Small: < 5,000 equivalent requirements –Medium: between 5,000 and 15,000 equivalent requirements –Large: > 15,000 equivalent requirements See handout on size related risks 10

Finer Assignment of Risk Levels Different severity risks would entail contours of different strength Some risk combinations may require re-interpretation of the nominal boundaries

12 Current and Future Work Scaling the risk summary outputs for each category and defining ranges for low, medium and high risks Create more granular risk quantification rules Consider 3-way risk interactions Add rules to detect COSYSMO input anomalies Systems engineering risk data from industrial projects will be analyzed to enhance and refine the technique –Perform statistical testing Domain experts from industry and government will continue to provide feedback and clarification –Supporting surveys and workshops will be continued Integrating alternate risk uncertainty approaches into a more complete risk management framework –Recently added Monte-Carlo analysis

Tasks So Far COSYSMO workshop experts have identified and prioritized risks, and provided advice Researchers devised the risk taxonomy and its weighting scheme Today We invite your comments on all Help us review and complete the advice 13

Assignments Dan/Beth pp. 1-2 Jared/Stan p. 3 Mauricio/Garry p. 4 Miles/Ricardo p. 5 and size risks 14

15 References R. Madachy, Heuristic Risk Assessment Using Cost Factors, IEEE Software, May 1997 Valerdi R., The Constructive Systems Engineering Cost Model (COSYSMO), PhD Dissertation, University of Southern California, Los Angeles, CA, May