Challenge the Estimate Presented by Mort Anvari Steve Loftus 23 June 05.

Slides:



Advertisements
Similar presentations
Using MIS 2e Chapter 10: Managing Development David Kroenke
Advertisements

BENEFITS OF SUCCESSFUL IT MODERNIZATION
ITAuditing Using GAS & CAATs
GCSS-J Best Agile Practices. 2 LTG Gainey, JS/J4 Ops Sponsor: “I want capability delivered in dog-years!” GCSS-J Program Overview Joint Logistics Environment:
Slide 1 Copyright QSMAssociates, Inc. All Rights Reserved “Index Based Productivity Benchmarking” “How Productive Were Our Teams on Our Most Recent Projects?”
University of Southern California Center for Systems and Software Engineering Productivity Data Analysis and Issues Brad Clark, Thomas Tan USC CSSE Annual.
University of Southern California Center for Software Engineering C S E USC Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6, 6.5.
May 11, 2004CS WPI1 CS 562 Advanced SW Engineering Lecture #5 Tuesday, May 11, 2004.
University of Southern California Center for Systems and Software Engineering Building Cost Estimating Relationships for Acquisition Decision Support Brad.
Introduction Wilson Rosa, AFCAA CSSE Annual Research Review March 8, 2010.
1 IS112 – Chapter 1 Notes Computer Organization and Programming Professor Catherine Dwyer Fall 2005.
University of Southern California Center for Systems and Software Engineering Software Cost Estimation Metrics Manual 26 th International Forum on COCOMO.
1 Chapter 6 Systems Development. 2 Learning Objectives  Know the characteristics of systems development.  Understand what professional systems analysts.
Software Verification and Validation (V&V) By Roger U. Fujii Presented by Donovan Faustino.
© 2009 IBM Corporation Developing Successful IT Professionals: Skills Mapping and the 9-14 Model Temeca Simpson- IBM October 29, 2013.
Deputy Assistant Secretary Army (Cost & Economics) Cost Research Army Day DODCAS February 2004.
Agenda Adaptation of existing open-source control systems from compact accelerators to large scale facilities.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
Problems with reuse – Increased maintenance costs; lack of tool support; not-invented- here syndrome; creating, maintaining, and using a component library.
MCS 270 Spring 2014 Object-Oriented Software Development.
Managing the development and purchase of information systems (Part 1)
1 ECE 453 – CS 447 – SE 465 Software Testing & Quality Assurance Lecture 22 Instructor Paulo Alencar.
N A S A G O D D A R D S P A C E F L I G H T C E N T E R I n t e g r a t e d D e s i g n C a p a b i l i t y / I n s t r u m e n t D e s i g n L a b o r.
Data for Costing Data for Parametric Costing Mort Anvari Director, Acquisition Costing (SAFM-CEA) 2008 Cost Research Workshop Acquisition Cost and Earned.
This document is proprietary to Project Consulting Group, Inc. and contains confidential information which is solely the property of Project Consulting.
Project Management Estimation. LOC and FP Estimation –Lines of code and function points were described as basic data from which productivity metrics can.
2 Systems Architecture, Fifth Edition Chapter Goals Describe the activities of information systems professionals Describe the technical knowledge of computer.
SCSC 311 Information Systems: hardware and software.
Maj Richard “Krash” Krasner Directorate of Requirements Headquarters Air Force Space Command Air Force Space Command's Environmental Monitoring Requirements.
Software Estimation How hard can it be? Peter R Hill.
1 BCF-215: Course Admin and Overview Course Administration and Overview 10/12/2010.
1 [insert briefing type here] [insert program name here] for [insert name and organization of person(s) to be briefed here] [insert “month day, year” of.
T. E. Potok - University of Tennessee CS 594 Software Engineering Lecture 3 Dr. Thomas E. Potok
AMERICA’S ARMY: THE STRENGTH OF THE NATION Mort Anvari 1 Cost Risk and Uncertainty Analysis MORS Special Meeting | September.
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
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.
Chapter 5 Technology in the Business Office Copyright © 2011, 2006 Mosby, Inc., an affiliate of Elsevier. All rights reserved.
1 MRL Assist Tool Website Access the MRL Assist Tool at
NASA/Air Force Cost Model presented by Keith Smith Science Applications International Corporation 2002 SCEA National Conference June
Verification and Validation — An OSD Perspective — Fred Myers Deputy Director, Test Infrastructure Test Resource Management Center November 4, 2009.
1 June 18, 2008 Cost Management with Data for Costing Mort Anvari Director, Acquisition Costing (SAFM-CEA) June 18, 2008 Cost Management Panel PRICE Customer.
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.
Markland J. Benson, Computer Systems Manager, White Sands Complex, (575) , Technology Infusion of CodeSonar into the Space.
Project Manager:PATS Project Manager Estimator:Peter Project Manager Start Date:1/1/2010 PATS Software PATS Project Team.
T Project Review Muuntaja I1 Iteration
University of Southern California Center for Systems and Software Engineering Enablers and Inhibitors for Expediting Systems and Software Engineering &
Project Planning Goal 1 - Estimates are documented for use in tracking and planning project. Goal 2 - Project Activities and commitments planned and documented.
1 Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6, 6.5 LiGuo Huang Computer Science and Engineering Southern Methodist University.
Enterprise Library 3.0 Memi Lavi Solution Architect Microsoft Consulting Services Guy Burstein Senior Consultant Advantech – Microsoft Division.
Air Force Institute of Technology
MORS Special Meeting: Risk, Trade Space, & Analytics for Acquisition
Chapter 1 Computer Technology: Your Need to Know
Pragmatics 4 Hours.
Software Configuration Management
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6
Productivity Data Analysis and Issues
Fernando Martinez Irizarry INSCOM G-4 Global Intelligence Logistics
Managing the development of information systems (Part 1)
13 November 2018.
Data for Costing & Cost Uncertainty
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
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.
COCOMO Models.
Cost Estimation Van Vliet, chapter 7 Glenn D. Blank.
Center for Software and Systems Engineering,
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2.6
Using COCOMO for Software Decisions - from COCOMO II Book, Section 2
COCOMO MODEL.
Presentation transcript:

Challenge the Estimate Presented by Mort Anvari Steve Loftus 23 June 05

2  Professional Adversarial Relationship  Determine the Cost  Challenge the Schedule  Conduct Risk Analysis The Cost Review Board History shows again and again how nature points out the folly of men

3 Agenda  Historical Program Growth  Program Schedule  Software Schedule & Productivity  Question the Data Sources Systems  Sources of Data

4 Total CG by Commodity 142 Systems 0% 10% 20% 30% 40% 50% 60% 70% 80% Aircraft 42C4I 24Missile 34Ship 19Space 9Ground Combat 14 Percent Cost Growth

5 RDT&E CG by Commodity

6 Procurement CG by Commodity 138 Systems 0% 10% 20% 30% 40% 50% 60% Aircraft 42C4I 21Missile 34Ship 19Space 9Ground Combat 13 Percent Cost Growth

7 Total CG by Subcommodity

8 Program Schedule

9 The Program Schedule  Backwards Planning FY04FY05FY06FY08FY09FY10FY11 IOC IOTE LRIP MSC Dev Testing HW/SW Dev Full Rate Production MSB

10 Historical Missile Development Effort Durations SOURCE: SAR and JSOW POE

11 Missile Development Effort Durations And Joint Common Missile Estimates So, it can be done in 42 months?

12 Software Development Software estimating parameters  Software Lines of Code (KSLOC)  Effort for Reuse  Effort for Modified  Growth  Productivity (KSLOC per Staff Month)  Labor Rate  Software to Hardware Integration Used to calculate Effective Lines of Code (ESLOC)

13 Software Estimating Rules of Thumb Growth: 40% Reuse Effort: 5% to 30% Modified Effort: 30% – 70% COTS: 5% to 30% Software to Hardware integration: 30% Software Maintenance: 60% to 70% of SW Total Life Cycle Estimate

14 Size Growth

15 Application DomainNumber Projects Size Range (KSLOC) Avg Productivity (SLOC/SM) Range (SLOC/SM) Example Applications Automation5525 to to 440Factory automation Command & Control4335 to 4, to 330Command centers Data Processing3620 to to 500Business systems Environment/Tools7515 to 1, to 610CASE tools, compilers, etc Military-Airborne3820 to 1, to 250Embedded sensors Military-Ground5225 to 2, to 300Combat information center Military-Missile1422 to to 165Guidance, Nav & Control Sys Military-Spaceborne1815 to to 175Attitude control systems Scientific3328 to to 360Seismic processing systems Telecommunications4815 to 1, to 440Digital switches and PABX Trainer/Simulations24200 to to 780Virtual reality simulators Web6410 to to 975Client/server sites SW Productivity (SLOC/SM) by Application Domains Based on 500 projects from a database of 1,500 (Reifer Consultants, Inc) projects. Scope extends from SW requirements review to SW/SW Integration Does not include SW/HW Integration, Quality Assurance, System, or Operational Test, & Beta Test Personnel Different Languages were used (ie Web projects employed Java & Visual C while military projects used Ada & C/C++

16 Software Estimate Given: Labor rate - $145 per hour (fully burdened with fee) 152 hours per staff month Aviation Program Staff Months: 3543 ( / 105) Staff Month Labor Rate: $22,040 ($145 * 152) SW Development: $78M (3543 * $22,040) SW to HW Integration: $23M ($78M * 30%) Total SW Development: $101M ($78M + $23M) SW Maintenance: $168M ($101M/.6) Total SW Life Cycle Cost Estimate: $269M ($101M + $168M)

17 Missile/Seeker Software FY04 FY05 FY06 FY07 FY08 FY09 FY10 FY AH-64D IOC MS B MS C FRP RAH-66 IOC w/JCM PDRCDR F/A-18E/F EOC AH-1Z EOC Phase 1 CA PPT (System Qual) EDT MH-60 R EOC Phase 2INCREMENT 1 DRR Test Support IPR FRP CA Adv Proc LRIP 1 LRIP 2 November, 2003 IOT&E LUT DT DT SHOTS SW Dev before DT ($101M) SW Dev before DT ($74M) Test-Analyze-Fix ($23M) CCA $101M POE $97M

18 Missile Qualification Comparison Missile Test Shots  How does program compare to analogous programs?

19 Comparison of Estimated Resource Requirements

20 Sources of Data

21 Army Tools for Total Ownership Cost Estimating Army Tools for Total Ownership Cost Estimating Life Cycle Cost Management Tools

22 Automated Cost Estimator (ACE) Automated Cost Estimator (Ace)—is a Model-building Tool. Part Spreadsheet, Part Database, It Incorporates Enough Structure to Eliminate Most of the Automation Tasks You Would Have to Perform If You Used a Spreadsheet, Yet It’s Flexible Enough to Perform Nearly Any Kind of Analysis. The Analyst’s Productivity Is Increased Through Built-in Inflation, Learning, Time Phasing, Documentation, Sensitivity/what-if, and Other Analysis Capabilities.

23 Automated Cost Data Base (ACDB) ACDB Is ACEIT’s Automated Cost Database. Just As ACE Is a Model- building Tool, ACDB Is a Database- Building Tool. It Contains Powerful Database Entry and Administration Tools to Enable Any Site/office to Create Its Own Tailored Database. When You Populate It, ACDB Lets You Search and Retrieve Cost, Schedule, Technical, and Programmatic Data.

24 Operating Support (O&S) Costing Operating & Support Management Information System (OSMIS) Force Cost Model(s) Installation Cost (Base Operations / Real Property Maintenance)

25

26 Force Costing / Models FORCES: Unit Operations & Support Force Costing / Models FORCES: Unit Operations & Support Updated Annually Provides Input to 5 Defense Models Supports 9 Separate Study Groups Avg 25 Major Estimates Per Year

27 OSMIS Database OSMIS Operating & Support Management Information System Parts (NSN Level) & Fuel Ammunition Intermediate Maintenance Depot Maintenance Activity Data (miles/Hours) Year of Manufacture

28 Summary  Challenge the schedule through use of historical programs  Software costing and metrics identifies schedule risk Costs Analysis: It’s more than just Cost