1 / 16

Next-Generation Systems and Software Cost Estimation

Next-Generation Systems and Software Cost Estimation. Wilson Rosa Technical Advisor Air Force Cost Analysis Agency (AFCAA) October 28, 2008. Problem Statement. Emerging technologies such as Systems of Systems (SoS) Model Driven Architecture (MDA) Enterprise Resource Planning (ERP)

jael-newton
Download Presentation

Next-Generation Systems and Software Cost Estimation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Next-Generation Systems and Software Cost Estimation Wilson Rosa Technical Advisor Air Force Cost Analysis Agency (AFCAA) October 28, 2008

  2. Problem Statement • Emerging technologies such as • Systems of Systems (SoS) • Model Driven Architecture (MDA) • Enterprise Resource Planning (ERP) • Service-Oriented Architecture (SOA) • Commercial Off the Shelf (COTS) Services • Reuse-Driven (RUSE) are complicating AFCAA's job of producing accurate software cost estimates

  3. Next-Generation System Challenges • Lines of Code not appropriate for • Model Driven Architecture • COTS-Based Systems (SOA, ERP, etc.) • No guidelines for estimating beyond software design • Infrastructure (servers, LAN, routers, etc.) • Concurrent Users • Enterprise Services (collaboration, discovery, portal, etc.) • Data Migration, External Interfaces • Interoperability and Interdependency • Unfamiliar with total system cost drivers • Lack of Empirical Research – SOA, ERP, SoS, MDA

  4. Data Challenges • AFCAA has multiple software datasets • Unable to combine software datasets because of inconsistencies and lack of standardization • Schedule seems to be reported at program and not CSCI level -- all CSCI’s have same schedule • No reporting of % re-design, % re-coding, % re-test • No common counting method – logical, physical, etc. • No standard application type definitions • No common code counting tool • Product size only reported in lines of code • No reporting of COCOMO, SEER, PRICE parameters • No reporting of quality measures – defects, MTBF, etc.

  5. Parametric Model Challenges • Most AF program offices rely on cost models • Have these models been calibrated with the most recent DoD data? (2002-2008) • Most models only cover a fraction, not total system costs – infrastructure, users, etc. • Model calibration with recent data will help reduce the program office estimating error rate

  6. Consequence: Significant Cost Growth (%) Source : *John McCrillis, 36th DOD Cost Analysis Symposium (2003) **Defense Automated Cost Information System

  7. Software Cost Metrics Manual OVERVIEW

  8. Scope • Cost Agencies in conjunction with University of Southern Californiawill publish a manual to help analysts develop quick software estimates usingreliable metrics from recent programs

  9. Software Cost Manual Content Chapter 1: Basic Software Estimation Chapter 2: Product Size Estimation Chapter 3: Schedule and Cost Growth Chapter 4: Default ESLOC Parameters Chapter 5: Historical Productivity Chapter 6: Default COCOMO/SEER/True-S Parameters Chapter 7: SLIM-ESTIMATE Calibration Chapter 8: Risk and Uncertainty Parameters Chapter 9: Data Normalization Chapter 10: Space Software Cost Guide Chapter 11: Software Maintenance

  10. Data Sources Note: Expecting over 1600 CSCIs by 2010

  11. Data Normalization • USC will interview program offices and developers to obtain additional information… • Cost Model Parameters – True S, SEER, COCOMO • Reuse Type – auto generated, re-hosted, translated, modified • Reuse Source – in-house, third party • Degree-of-Modification – %DM, %CM, %IM • Method – Model Driven Architecture, Object-Oriented, Traditional • Available Data • DoDAF – System Views, Operational Views, etc. • Software Resource Data Report – Software Size, Effort, Schedule • Cost Analysis Requirements Description (CARD) • System Description, Users, Infrastructure, locations, interfaces, etc.

  12. Chapter 4: ESLOC Parameters • Default values from recent programs • Based on Reuse Type and Reuse Source Sample

  13. Chapter 5: Historical Productivity • Overview and Guidelines • Historical Productivity Dataset by Application • Default Productivity Ranges by Application Sample

  14. Significance of Proposed Manual • Collected data can be used for • Systems of Systems cost research • Cost Model improvement initiatives • SEER, True-S, COCOMO, etc. • Understanding relationships between Next-Generation Processes and COCOMO cost drivers can encourage researchers to explore new strategies to improve available cost models…

  15. Way Ahead • Short Term • NCCA/AFCAA Software Cost Handbook (Nov 2008) • Software Cost Metrics Manual (2009) • Long Term • Cost Risk and Uncertainty Handbook Volume II (2011) • ERP Cost Guide (2010) • Impact of MDA on Cost Modeling (2010) • SOA Cost Study (2012) • Data Center Cost Study (2010) Note: Any data you provide will not be attributed to your company or program, but will be combined with like data from other sources and generic zed"

  16. Backup Slides I n t e g r i t y - S e r v i c e - E x c e l l e n c e

More Related