Some Experience With COSYSMOR At Lockheed Martin

Slides:



Advertisements
Similar presentations
1-1 Activity-Based Costing and Activity-Based Management Dr. Hisham Madi.
Advertisements

Introduction CreditMetrics™ was launched by JP Morgan in 1997.
On Representing Uncertainty In Some COCOMO Model Family Parameters October 27, 2004 John Gaffney Fellow, Software & Systems.
Example © 2012 Lockheed Martin Corporation. All Rights Reserved. October 2012 Proxy Estimation Costing for Systems (PECS) Reggie Cole Lockheed Martin Senior.
Cost Estimation Chapter 5 Copyright © 2011 by The McGraw-Hill Companies, Inc. All rights reserved.McGraw-Hill/Irwin
COSYSMO 2.0 Workshop Summary (held Monday, March 17 th 2008) USC CSSE Annual Research Review March 18, 2008 Jared Fortune.
University of Southern California Center for Systems and Software Engineering ©USC-CSSE1 Ray Madachy, Ricardo Valerdi USC Center for Systems and Software.
©2006 BAE Systems. COSYSMO Application At BAE Systems Gan Wang COSYSMO Workshop 23 rd International Forum on COCOMO and Systems/Software Cost Modeling.
University of Southern California Center for Systems and Software Engineering USC CSSE Research Overview Barry Boehm Sue Koolmanojwong Jo Ann Lane Nupul.
Engineering Economics in Canada
Extensions of COSYSMO to Represent Reuse 21 st International Forum on COCOMO and Software Cost Modeling November 9, 2006 Ricardo ValerdiJohn Gaffney Garry.
COSYSMO Reuse Extension 22 nd International Forum on COCOMO and Systems/Software Cost Modeling November 2, 2007 Ricardo ValerdiGan Wang Garry RoedlerJohn.
Affiliate Feedback and Discussion 1. Future Research: COSYSMO Updated data collection effort Quantifying the effect of schedule Harmonizing across software.
1 Systems Engineering Reuse Principles Jared Fortune, USC Ricardo Valerdi, MIT COSYSMO COCOMO Forum 2010 Los Angeles, CA.
(c) Copyright, Lockheed Martin Corporation, Looking At Schedule vs. Effort In Software Engineering, Systems Engineering and Systems John Gaffney.
COSYSMO Reuse Extension 22 nd International Forum on COCOMO and Systems/Software Cost Modeling November 2, 2007 Ricardo ValerdiGan Wang Garry RoedlerJohn.
1 Introduction to System Engineering G. Nacouzi ME 155B.
System-of-Systems Cost Modeling: COSOSIMO July 2005 Workshop Results Jo Ann Lane University of Southern California Center for Software Engineering.
COSYSMO Risk/Confidence Estimation Prototype John Gaffney March 14, 2005.
1 Discussion on Reuse Framework Jared Fortune, USC Ricardo Valerdi, MIT COSYSMO COCOMO Forum 2008 Los Angeles, CA.
Expert COSYSMO Update Raymond Madachy USC-CSSE Annual Research Review March 17, 2009.
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
COSYSMO Reuse Extension COSYSMO Workshop – USC CSSE Annual Research Review March 17, 2008 Ricardo ValerdiGan Wang Garry RoedlerJohn Rieff Jared Fortune.
©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.
Don Cole Risk Assessment and Mitigation Project Management for ARA Engineers and Scientists.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 17 Slide 1 Extreme Programming.
FP OntoGrid: Paving the way for Knowledgeable Grid Services and Systems WP8: Use case 1: Quality Analysis for Satellite Missions.
Risk management in Software Engineering T erm Paper By By Praveenkumar Sammita Praveenkumar Sammita CSC532 CSC532.
Chapter 7: The 30 elements of systems engineering
1SAS 03/ GSFC/SATC- NSWC-DD System and Software Reliability Dolores R. Wallace SRS Technologies Software Assurance Technology Center
Copyright © 2005 by South-Western, a division of Thomson Learning All rights reserved 1 Chapter 7 Planning and Strategy.
1 Quality Center 10.0 NOTE: Uninstall the current version of QC before downloading QC All QC 10.0 documents can be located on the BI Shared Services.
University of Southern California Center for Systems and Software Engineering COSATMO/COSYSMO Workshop Jim Alstad, USC-CSSE Gan Wang, BAE Systems Garry.
9/17/2002 COSYSMO Usage Experience Panel: What is Happening at Lockheed Martin Garry Roedler, Lockheed Martin Engineering Process Improvement Center
SAM Executive Seminar Software Measurement.
1 Some Topics In Measurement/Quantitative Analysis John E. Gaffney, Jr., PE November 3, 2010.
Brian Macpherson Ph.D, Professor of Statistics, University of Manitoba Tom Bingham Statistician, The Boeing Company.
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.
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.
Optimizing NASA IV&V Benefits Using Simulation Grant Number: NAG David M. Raffo, Ph.D College of Engineering and Computer Science School of Business.
 2001 Prentice Hall Business Publishing, Accounting Information Systems, 8/E, Bodnar/Hopwood Systems Implementation, Operation, and Control Chapter.
8-1 Establish Cost/Schedule Performance Impacts Program Requirements Assess Risks Evaluate Risk Handling Options Evaluate Subcontractor Risks Establish.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.
Chapter 3: Software Project Management Metrics
1 3. M ODELING U NCERTAINTY IN C ONSTRUCTION Objective: To develop an understanding of the impact of uncertainty on the performance of a project, and to.
March 2004 At A Glance NASA’s GSFC GMSEC architecture provides a scalable, extensible ground and flight system approach for future missions. Benefits Simplifies.
Project Management Cross lifecycle Activity
Estimating “Size” of Software There are many ways to estimate the volume or size of software. ( understanding requirements is key to this activity ) –We.
Effort Estimation In WBS,one can estimate effort (micro-level) but needed to know: –Size of the deliverable –Productivity of resource in producing that.
The COCOMO model An empirical model based on project experience. Well-documented, ‘independent’ model which is not tied to a specific software vendor.
11/04/091 Some Topics Concerning The COSYSMOR Model/Tool John E. Gaffney, Jr Center For Process Improvement Excellence.
Overview of Addressing Risk with COSYSMO Garry Roedler & John Gaffney Lockheed Martin March 17, 2008.
BV41840 Schedule Risk Analysis of Software Development By: Dr. Joe H. Dean Engineering Chief Risk & System Analysis LFWC And: Mr. David W. Benson, Jr.
11/03/091 Integrating Cost and Schedule Estimation In The COSYSMOR Model/Tool John E. Gaffney, Jr Center For Process Improvement.
CS 577b: Software Engineering II
Estimate Testing Size and Effort Using Test Case Point Analysis
2.2 Graphs of Equations.
PSM 2008 Workshop: Toward Integrating Systems Engineering and Software Engineering Estimation: Harmonizing COSYSMO and COCOMO John Gaffney
LINDSEY BREWER CSSCR (CENTER FOR SOCIAL SCIENCE COMPUTATION AND RESEARCH) UNIVERSITY OF WASHINGTON September 17, 2009 Introduction to SPSS (Version 16)
COSYSMO Delphi Round 2 Results
Towards COSYSMO 2.0: Update on Reuse
COCOMO Models.
COCOMO 2 COCOMO 81 was developed with the assumption that a waterfall process would be used and that all software would be developed from scratch. Since.
Knowing When to Stop: An Examination of Methods to Minimize the False Negative Risk of Automated Abort Triggers RAM XI Training Summit October 2018 Patrick.
Extreme Programming.
Presentation transcript:

Some Experience With COSYSMOR At Lockheed Martin John Gaffney 301-721-5710 j.gaffney@lmco.com Lockheed Martin Systems & Software Resource Center (SSRC) Center for Process Improvement Excellence (CPIE) October 29, 2008 (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 Agenda What Is COSYSMOR ? Some Experience With COSYSMOR (c) Copyright, Lockheed Martin Corporation, 2008

COSYSMOR or COSYSMO Risk and Reuse COSYSMOR evolved from the USC Academic COSYSMO systems engineering estimation model/tool (Dr. Ricardo Valerdi) and LMCO implemented these enhancements in a tool, COSYSMOR, or COSYSMO Risk COSYSMOR is available on request It has been distributed to some organizations outside of Lockheed Martin already A major driver for the development of COSYSMOR was to get away from “single point” cost estimates in order to better recognize the uncertainty associated with effort, schedule, and cost estimates (c) Copyright, Lockheed Martin Corporation, 2008

Additional Functions Provided By COSYSMOR COSYSMOR provides four major additional functions beyond those provided by Academic COSYSMO: Estimation of Cost/Effort and Schedule Uncertainties/Risk and Confidence: Provides quantification of the impacts of uncertainties in the values of key model parameter values. Provides multiple cost and schedule values with associated probabilities. Risk=Prob [Actual Effort Will Be >Estimated Effort] Confidence=100%-Risk Representation of Multiple Types of Size Drivers: Provides for entering counts of: new, modified, reused, and deleted types for each of the four size driver categories. Labor Scheduling: Provides the spread of systems engineering labor for the five systems engineering activities and across four the development phases (time). Labor Allocation: Provides for the user to select the percentage allocations of the twenty activity/phase pairs or effort elements. (c) Copyright, Lockheed Martin Corporation, 2008

What Lockheed Martin Has Been Doing Been calibrating COSYSMOR in various organizations and applying it in several projects Have also developed an analogous model/tool for software resource estimation, COCOMOR We are quite interested in harmonizing the estimation of systems engineering effort and software engineering effort We have also developed a tailored version of COSYMOR, COSYSMOR-A for avionics This illustrates the general utility of this model/tool form (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 COSYSMOR-A COSYSMOR-A stands for COSYSMOR for Avionics COSYSMOR-A is a tailored version of COSYSMOR, to produce resource (effort) estimates for new avionics systems and upgrades produced by Lockheed Martin Aeronautics Company Mission Systems and Avionics The tailoring included changes in two of the size drivers and two of the cost drivers (of COSYSMO/COSYSMOR): Size Drivers: # of Hardware Components and # of Software Functions replace # of Algorithms and # of Operational Scenarios in COSYSMO/R, respectively Cost Drivers: Lab System Integration and Test Complexity and Flight Test Complexity replace Migration Complexity and Multisite Coordination in COSYSMO/R, respectively (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 COSYSMOR Data Entry-1 Three-point data entry for size and cost drivers. (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 COSYSMOR Data Entry-2 You indicate the uncertainty in size driver and cost driver values by entering Low, Likely and High values for each to indicate your assessment of the distribution for the easy, nominal and difficult size driver counts If you don’t believe that there is a range, but rather, there is the value, then you enter the same values for Low, Likely and High (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 COSYSMOR Data Entry-3 A Program User enters the percents of Modified, Reused and Deleted for each of the four size drivers; the tool computes the percent of New These percents are taken to apply to the Easy, Nominal and Difficult values for each of the four types of size drivers A Program User also enters the Relative Cost (relative to New) for the Modified, Reused and Deleted counts Note: If the Program User wants to designate different sets of percents and relative costs for Easy, Nominal and Difficult, then he will have to go the Reuse page of COSYSMOR to enter these values. (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 COSYSMOR Data Entry-4 An Administrative User enters the Low, Likely and High values for A, the Unit Effort Constant, and E, the Exponent, in the COSYSMOR model: K=A*SE* Di (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 Some COSYSMOR Outputs Principal outputs of the COSYSMOR tool are: Equivalent Size Risk Cost Driver Product Risk Systems Engineering Person Hours Risk Systems Engineering Person Hours Overrun Risk Percent of Total Systems Engineering Effort By Process Activity and By Phase Systems Engineering Person Hours Vs. Month Systems Engineering Schedule Risk (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 Systems Engineering Person Hours Risk Use this Graph to help understand labor (and cost) exposure for your choice of labor (say to be bid in a proposal). Example: The risk of exceeding 60000 labor hours is slightly less than 20%. Note: You might choose to present only the smooth curve fit rather than the discrete plot. (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 Systems Engineering Person Hours Overrun Risk This plot shows the overrun risk % for a target of 250000 of Systems Engineering Person Hours values. This plot is the tail of the Systems Engineering Person Hours Risk plot. Some persons might prefer to see this plot in which the “zero” value on the horizontal axis corresponds to the target value and the horizontal axis values are the (potential) overrun values relative to the target. (c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008

(c) Copyright, Lockheed Martin Corporation, 2008 Observations Better management of uncertainty starts with recognizing its existence and in estimating cost/schedule risk Use the risk information to make better management decisions during both business acquisition and program execution Serve as a basis for discussion of alternatives within the project as well as with the customer A key aspect of affordability Relate cost/schedule risk to risk register as part of normal risk management process Relate to potential program failure modes Need to harmonize SE and SW estimation (c) Copyright, Lockheed Martin Corporation, 2008