University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 1 Trends in Productivity and COCOMO Cost Drivers over the.

Slides:



Advertisements
Similar presentations
Software Cost Estimation
Advertisements

COST ESTIMATION TECHNIQUES AND COCOMO. Cost Estimation Techniques 1-)Algorithmic cost modelling 2-)Expert judgement 3-)Estimation by analogy 4)-Parkinsons.
SW Economics & COCOMO II November 25, 2005 Jongmoon Baik, Ph.D. School of Engineering Information and Communications University.
Tradespace, Affordability, and COCOMO III Barry Boehm, USC CSSE Annual Research Review 2014 April 30,
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
FAA Information Technology- Information Systems Security R&D Workshop June 2015© USC-CSE Extending COCOMO II to Estimate the Cost of Developing.
LOC, COCOMO I & COCOMO II Subject: Software Engineering Coordinator: Mr Anoj Kumar Presented By: Kamal Kishore (2012ca34) Jyoti Shrivastava (2012ca52)
1 XOMO: understanding Development Options for Autonomy PDX, USA Julian Richardson RIACS,USRA
CSCI COCOMO Tutorial1 CS “Tutorial” Presentation: Software Cost Estimation Tools – COCOMO II and COCOTS A Winsor Brown and Ye.
Applying COCOMO II Effort Multipliers to Simulation Models 16th International Forum on COCOMO and Software Cost Modeling Jongmoon Baik and Nancy Eickelmann.
COCOMO II Calibration Brad Clark Software Metrics Inc. Don Reifer Reifer Consultants Inc. 22nd International Forum on COCOMO and Systems / Software Cost.
University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 1 COCOMO II Maintenance Model Upgrade Vu Nguyen, Barry Boehm.
University of Southern California Center for Systems and Software Engineering 1 © USC-CSSE A Constrained Regression Technique for COCOMO Calibration Presented.
University of Southern California Center for Systems and Software Engineering Assessing the IDPD Factor: Quality Management Platform Project Thomas Tan.
1 CORADMO in 2001: A RAD Odyssey Cyrus Fakharzadeh 16th International Forum on COCOMO and Software Cost Modeling University of Southern.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 Assessing and Estimating Corrective, Enhancive, and Reductive.
COCOMO II Database Brad Clark Center for Software Engineering Annual Research Review March 11, 2002.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 Reuse and Maintenance Estimation Vu Nguyen March 17, 2009.
University of Southern California Center for Software Engineering CSE USC 9/14/05 1 COCOMO II: Airborne Radar System Example Ray Madachy
©2011 Rolls-Royce plc The information in this document is the property of Rolls-Royce plc and may not be copied or communicated to a third party, or used.
April 27, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #3 Tuesday, April 27, 2004.
University of Southern California Center for Systems and Software Engineering © 2009, USC-CSSE 1 An Analysis of Changes in Productivity and COCOMO Cost.
Chapter 23 – Project planning Part 2. Estimation techniques  Organizations need to make software effort and cost estimates. There are two types of technique.
Information System Economics Software Project Cost Estimation.
COCOMO-SCORM: Cost Estimation for SCORM Course Development
ESD web seminar1 ESD Web Seminar February 23, 2007 Ricardo Valerdi, Ph.D. Unification of systems and software engineering cost models.
University of Southern California Center for Systems and Software Engineering Cost Estimation with COCOMO II Barry Boehm CS 510, Fall 2015 v3: Slide 10.
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.
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.
Project Estimation Model By Deepika Chaudhary. Factors for estimation Initial estimates may have to be made on the basis of a high level user requirements.
University of Southern California Center for Systems and Software Engineering Vu Nguyen, Barry Boehm USC-CSSE ARR, May 1, 2014 COCOMO II Cost Driver Trends.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 26 Slide 1 Software cost estimation 2.
University of Southern California Center for Systems and Software Engineering (c) USC CSSECSCI 577a 2010 COCOMO + COCOTS Tutorial1 577a 2010.
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
The COCOMO model An empirical model based on project experience. Well-documented, ‘independent’ model which is not tied to a specific software vendor.
1 COCOMO II Estimation Example: Transaction Processing System (TPS) II Based on Chapter 3 of COCOMO II book Used for new microeconomics examples –Replaces.
Rating Very Very Extra Cost Drivers Low Low Nominal High High High Product Attributes Required software reliability Database size.
Local Calibration: How Many Data Points are Best? Presented by Barry Boehm on behalf of Vu Nguyen, Thuy Huynh University of Science Vietnam National University.
COCOMO Software Cost Estimating Model Lab 4 Demonstrator : Bandar Al Khalil.
1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern.
THE FAMU-CIS ALUMNI SYSTEM
כ"ז/שבט/תשע"ח An Overview of Software Development Effort and Cost Estimation Techniques Professor Ron Kenett Tel Aviv University School of Engineering.
COCOMO III Brad Clark 31tst International Forum on
COCOMO III Workshop Summary
PROJECT LIFE CYCLE AND EFFORT ESTIMATION
Metrics and Terms SLOC (source lines of code)
Cost Estimation with COCOMO II
Tutorial: Software Cost Estimation Tools – COCOMO II and COCOTS
COCOMO II Overview CSCI 510 Fall 2013 (c) USC CSSE.
COCOMO II Overview Barry Boehm CSCI 510 Fall 2011 (c) USC CSSE
COCOMO II Overview Barry Boehm CSCI (c) USC CSSE 2018/9/19.
COCOMO II Overview A Winsor Brown (especially from page 50 on)
Constructive Cost Model
Pongtip Aroonvatanaporn CSCI 577b Spring 2011 March 25, 2011
COCOMO II Overview Ray Madachy CSCI 510
SLOC and Size Reporting
Cost Estimation with COCOMO II
Software Systems Cost Estimation
Cost Estimation with COCOMO II
Cost Estimation with COCOMO II
Cost Estimation with COCOMO II
Based on Chapter 5 of the book [McConnell 2006]
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.
COCOMO II Overview LiGuo Huang Computer Science and Engineering
Chapter 23 Software Cost Estimation
Cost Estimation with COCOMO II
Cost Estimation with COCOMO II
COnstructive COst MOdel
COCOMO II Overview Marilee Wheaton CSCI 510.
Center for Software and Systems Engineering,
Presentation transcript:

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 1 Trends in Productivity and COCOMO Cost Drivers over the Years Vu Nguyen Center for Systems and Software Engineering (CSSE) CSSE Annual Research Review 2010 Mar 9 th, 2010

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 2 Outline Objectives and Background Productivity Trend Discussions and Conclusions Cost Driver Trends

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 3 Objectives Analysis of Productivity –How the productivity of the COCOMO data projects has changed over the years –What caused the changes in productivity Analysis of COCOMO cost drivers –How cost driver ratings have changed over the years –Are there any implications from these changes

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 4 Estimation models need upgrading It has been 10 years since the release of COCOMO II.2000 –Data collected during 1970 – 1999 Software engineering practices and technologies are changing –Process: CMM  CMMI, ICM, agile methods –Tools are more sophisticated –Advanced communication facility Improved storage and processing capability

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 5 COCOMO II Formula Effort estimate (PM) –COCOMO II 2000: A and B constants were calibrated using 161 data points with A = 2.94 and B = 0.91 Productivity = Constant A is considered as the inverse of adjusted productivity

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 6 COCOMO Data Projects Over the Five-year Periods Dataset has 341 projects completed between 1970 and 2009 –161 used for calibrating COCOMO II 2000 –149 completed since 2000

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 7 Outline Objectives and Background Productivity Trend Discussions and Conclusions Cost Driver Trends

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 8 Average productivity is increasing over the periods Two productivity increasing trends exist: 1970 – 1994 and 1995 – Five-year Periods KSLOC per PM productivity trends largely explained by cost drivers and scale factors Post-2000 productivity trends not explained by cost drivers and scale factors

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 9 Effort Multipliers and Scale Factors EM’s and SF’s don’t change sharply as does the productivity over the periods EAF Sum of Scale Factors Effort Adjustment Factor (EAF) or ∏EM Sum of Scale Factors (  SF)

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 10 Constant A generally decreases over the periods Calibrate the constant A while stationing B = 0.91 Constant A is the inverse of adjusted productivity –adjusts the productivity with SF’s and EM’s Constant A decreases over the periods 50% decrease over the post period

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 11 Outline Objectives and Background Productivity Trend Discussions and Conclusions Cost Driver Trends

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 12 Correlation between cost drivers and completion years Trends in cost drivers –Cost drivers unchanged TEAM, FLEX, RESL, RELY, CPLX, ACAP, PCAP, RUSE, DOCU, PCON, SITE, SCED –Increasing trends: increasing effort DATA, APEX –Decreasing trends: decreasing effort PMAT, TOOL, PREC,TIME, STOR, PLEX, LTEX, PVOL

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 13 Application and Platform Experience Platform and language experience has increased while application experience decreased –Programmers might have moved projects more often in more recent years

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 14 Use of Tools and Process Maturity Use of Tools and Process Maturity have increased significantly

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 15 Storage and Time Constraints Storage and Time are less constrained than they were

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 16 Outline Objectives and Background Productivity Trend Discussions and Conclusions Cost Driver Trends

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 17 Discussions Productivity has doubled over the last 40 years –But scale factors and effort multipliers did not fully characterize this increase Hypotheses/questions for explanation –Is standard for rating personnel factors different among the organizations? –Were automatically translated code reported as new code? –Were reused code reported as new code? –Are the ranges of some cost drivers not large enough? Improvement in tools (TOOL) only contributes to 20% reduction in effort –Are more lightweight projects being reported? Documentation relative to life-cycle needs

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 18 Conclusions Productivity is generally increasing over the 40- year period –SF’s and EM’s only partially explain this improvement Advancements in processes and technologies affect some cost drivers –But majority of the cost driver ratings are unchanged Changes in productivity and cost drivers indicate that estimation models should recalibrate regularly

University of Southern California Center for Systems and Software Engineering © 2010, USC-CSSE 19 Thank You