Software Technology Support Center BE AMERICA’S BEST The Problems in Software Estimating Dr. Randall Jensen Software Technology Support Center Hill AFB,

Slides:



Advertisements
Similar presentations
Requirements Engineering Processes – 2
Advertisements

Sequence Diagram Generation & Validation MSE First Presentation Samer Saleh Advisor: Bill Hankley.
Early Effort Estimation of Business Data-processing Enhancements CS 689 November 30, 2000 By Kurt Detamore.
Alternate Software Development Methodologies
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Automated Software Cost Estimation By James Roberts EEL 6883 Spring 2007.
Copyright 2000, Stephan Kelley1 Estimating User Interface Effort Using A Formal Method By Stephan Kelley 16 November 2000.
Cocomo II Constructive Cost Model [Boehm] Sybren Deelstra.
11.1 Lecture 11 CASE tools IMS Systems Design and Implementation.
Integration of Software Cost Estimates Across COCOMO, SEER- SEM, and PRICE-S models Tom Harwick, Engineering Specialist Northrop Grumman Corporation Integrated.
CS351 © 2003 Ray S. Babcock Cost Estimation ● I've got Bad News and Bad News!
Software Process Improvement in Small Organizations A Case Study.
CS 5521 Configuration Management the problem Not a simple task! –Different versions of software usually is in the field during the life cycle –Different.
Swami NatarajanJune 17, 2015 RIT Software Engineering Reliability Engineering.
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
Requirements Engineering Processes
Estimating System of Systems Engineering (SoSE) Effort Jo Ann Lane, USC Symposium on Complex Systems Engineering January 11-12, 2007.
Rick Hefner. Marilee J. Wheaton TRW
COCOMO II Database Brad Clark Center for Software Engineering Annual Research Review March 11, 2002.
April 13, 2004CS WPI1 CS 562 Advanced SW Engineering General Dynamics, Needham Tuesdays, 3 – 7 pm Instructor: Diane Kramer.
Measuring Dollar Savings from Software Process Improvement with COCOMO II Betsy Clark Software Metrics Inc. October 25, 2001 Acknowledgment: This presentation.
UNCLASSIFIED Schopenhauer's Proof For Software: Pessimistic Bias In the NOSTROMO Tool (U) Dan Strickland Dynetics Program Software Support
CS3500 Software Engineering Agile Software Development (1) Agile software development, proposed in 2001 by the non-profit Agile Alliance, has four basic.
© 2005 by Prentice Hall Appendix 2 Automated Tools for Systems Development Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F.
Cost Management Week 6-7 Learning Objectives
Information System Economics Software Project Cost Estimation.
Appendix 2 Automated Tools for Systems Development © 2006 ITT Educational Services Inc. SE350 System Analysis for Software Engineers: Unit 2 Slide 1.
By: Md Rezaul Huda Reza 5Ps for SE Process Project Product People Problem.
Feasibility Study.
Software Engineering Lecture # 1. What is Software? 2 Software is a set of items or objects that includes: programs data documents.
By K Gopal Reddy.  Metrics in software are of two types.direct and indirect.  Function points as indirect metrics.  Function points are used to measure.
1 Software Cost Estimation. Outline  Introduction  Inputs and Outputs  Methods of Estimation  COCOMO  Conclusion 2.
©Ian Sommerville 2000Software Engineering, 6th edition. Chapter 25 Slide 1 Process Improvement l Understanding, Modelling and Improving the Software Process.
Project Planning Copyright, 2002 © Jerzy R. Nawrocki Requirements Engineering.
Capability Maturity Model CS3300 Fall The Problem Contractors over budget and late. Need a way to rank how likely a software company is to deliver.
Cost Estimation What is estimated? –resources (humans, components, tools) –cost (person-months) –schedule (months) Why? –Personnel allocation –Contract.
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.
The Art of Estimating Programming Tasks Adriana Lopez Development Director Dragon Age II.
IND Architecture Modernization, Deep Space Information Services Architecture (DISA), A Business Case for SOA-Based Modernization Mike Kolar, Integrated.
1 540f07cost10 Question of the Day u How important is it to be able to estimate the cost of a software project?
Measurement (II)1 Measurement - Productivity, Estimation, Effort Advanced Software Engineering COM360 University of Sunderland © 1998.
CSE 403, Spring 2008, Alverson Estimation What to say when asked for an estimate “I’ll get back to you” Pragmatic Programmer Deadly sins material adapted.
Overview of COCOMO Reporter:Hui Zhang
“How to Measure the Impact of Specific Development Practices on Fielded Defect Density” by Ann Marie Neufelder Presented by: Feride Padgett.
Empirical Estimation Models Based upon historic data Basic Structure E = A + B * (ev) C where A, B, c are empirical constants ‘ev’ is the effort in terms.
Function Points Synthetic measure of program size used to estimate size early in the project Easier (than lines of code) to calculate from requirements.
CSE 403, Spring 2007, Alverson Estimation What to say when asked for an estimate “I’ll get back to you” Pragmatic Programmer Deadly sins material adapted.
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.
UNCLASSIFIED Approved for Public Release 07-MDA-2965 (26 OCT 07) Load Bearing Walls: Early Sizing Estimation In The NOSTROMO Tool (U) Dan Strickland Dynetics.
Software Engineering Lecture # 1. What is Software? 2 Software is a set of items or objects that includes: programs data documents.
Chapter 4 Automated Tools for Systems Development Modern Systems Analysis and Design Third Edition 4.1.
Chapter One Developments in the Application of Information Technology in Business Presented by James Weimholt.
1 Overview of Maintenance CPRE 416-Software Evolution and Maintenance-Lecture 3.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Smi COCOMO II Calibration Status USC-CSE Annual Research Review March 2004.
Cost12 1 Question of the Day u How important is it to be able to estimate the cost of a software project?
Copyright , Dennis J. Frailey CSE7315 – Software Project Management CSE7315 M15 - Version 9.01 SMU CSE 7315 Planning and Managing a Software Project.
1 Requirements Engineering for Agile Methods Lecture # 41.
1 Agile COCOMO II: A Tool for Software Cost Estimating by Analogy Cyrus Fakharzadeh Barry Boehm Gunjan Sharman SCEA 2002 Presentation University of Southern.
כ"ז/שבט/תשע"ח An Overview of Software Development Effort and Cost Estimation Techniques Professor Ron Kenett Tel Aviv University School of Engineering.
Estimate Testing Size and Effort Using Test Case Point Analysis
Appendix 2 Automated Tools for Systems Development
Requirements Engineering Lecture 13
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
Modern Systems Analysis and Design Third Edition
More on Estimation In general, effort estimation is based on several parameters and the model ( E= a + b*S**c ): Personnel Environment Quality Size or.
Modern Systems Analysis and Design Third Edition
Software Cost Estimation
Presentation transcript:

Software Technology Support Center BE AMERICA’S BEST The Problems in Software Estimating Dr. Randall Jensen Software Technology Support Center Hill AFB, UT

O G D E N A I R L O G I S T I C S C E N T E R Outline Evolution of software estimating models Software problems Management is the issue Data collection concerns New models? BE AMERICA’S BEST It’s all about models – “Existence is elsewhere”

O G D E N A I R L O G I S T I C S C E N T E R Project Uncertainty Principle BE AMERICA’S BEST

O G D E N A I R L O G I S T I C S C E N T E R Software model genealogy Nordon IBM 1970 Putnam/ SLIM US Army/GE/ QSM 1976 Doty RADC 1977 JS1,2,3 CEI 1980 SEER-SEM GAI 1989 Seer II / Sage SEI 1995 COCOMO TRW 1981 COCOMO II USC 1995 Validation Seer HAC 1979 PRICE-S Price 1977 TRUE-S Price 2003 REVIC USAF 1991 Management

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Sage/SEER-SEM - Normal form where K = life cycle cost (person years), T d = development time (years) sloc

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Common estimate dilemma

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Software problems are not new Unreliable Late delivery Modification costs prohibitive Impossible to maintain Inadequate performance Product exceeds budget costs 1968 CS Conference, Munich, Germany KEY

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Historic note: “ More software projects have gone awry for lack of calendar time than for all other causes combined…” F. P. Brooks, Jr., Mythical Man Month

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Common technology claim If you use (new technology), Productivity will improve by an order of magnitude And Defects will reduce to zero Note: None of the history-based estimating models (tools) support this claim, not even close. Neither does history.

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST There is always HOPE Ada OOD Structured Analysis Structured Design Process Maturity PWB Structured Programming 3rd Generation Languages P R O D U C T I V I T Y lppm

O G D E N A I R L O G I S T I C S C E N T E R 3 Dimensions of development BE AMERICA’S BEST

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Impact of management on cost “Poor management can increase software costs more rapidly than any other factor… Despite this variation, COCOMO does not include a factor for management quality, but instead provides estimates which assume that the project will be well managed [ italics mine, RWJ ]” Boehm, B. W., Software Engineering Economics, (Englewood Cliffs, NJ: Prentice-Hall, Inc.), 1981, pg. 486 Note: On a scale of 0 to 10 well managed must rank approximately 3.4?

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Where would you focus effort? TOOLS PEOPLE SYSTEMS MANAGEMENT Source: G. Weinberg, Quality Software Management, Vol. 3

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Biased research? ToolsPeopleSystems Managers SEI Papers Percent Source: G. Weinberg, Quality Software Management, Vol. 3

O G D E N A I R L O G I S T I C S C E N T E R Cost driver relative impact It takes people to implement processes and use technology. April 21 st, 2009

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST BIG productivity drivers Analyst capability Management style Motivation Use of team methods Working environment Problem solving skills Programmer capability Application domain experience Use of modern practices Automated tool support

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Capability shift (environment) Basic Technology Constant (1990)

O G D E N A I R L O G I S T I C S C E N T E R Historic data observations Models are made from historic data More data is better Adequate historic data takes time to collect (Lots of time) Repository vs Database Repository = a place where things may be stored for safekeeping Data stored without concern for a formal definition of the data placed in the repository SRDR is defined as a financial report that happens to contain technical information Database = a collection of data arranged for ease and speed of retrieval Requires consistency of entries Each data field must satisfy common definition DCARC is a repository as was SMC database Data definitions? BE AMERICA’S BEST18

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Problems?

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST Popular estimating solution Let’s create a new software model Models are out of date Models are inaccurate Too difficult to use Oh, really! Are you sure?

O G D E N A I R L O G I S T I C S C E N T E R BE AMERICA’S BEST New estimating models? Lack of confidence in existing tools (current issues) Optimistic estimates Unacceptable estimates Aging tools (?) Culture is constant New models require validation New models -- No silver bullets Quality data (if, where, proprietary) New models require validation New (or better) estimators? Experience Skill Integrity

O G D E N A I R L O G I S T I C S C E N T E R Estimating Prediction is very hard, especially when it’s about the future