DOCSLIB.ORG

Software Development Cost Estimating Guidebook

Total Page：16

File Type：pdf, Size：1020Kb

Download full-text PDF Read full-text

Load more

Software Development Cost Estimating Guidebook Software Technology Support Center Cost Analysis Group July 2009 Resource manual for education and support in developing credible software development cost estimates Executive Summary The purpose of the Software Development Estimating Guidebook is to provide the cost analyst with a resource manual to use in developing credible software development cost estimates. A realistic estimate is based upon a solid understanding of the software development process and the historical data that forms a framework for the expected values. An estimating methodology that follows a proven process consistent with best practices and Department of Defense (DoD) policies further contributes to estimate validity. The information is presented at two levels. One level will help the experienced analyst immediately focus on the material necessary to develop an estimate. The second level of information is for the novice, or infrequent user, to use as educational information regarding the software development and estimating processes. The estimating process starts with a determination of the purpose of the estimate. Next, the cost (or effort) and schedule for the software development project are determined using three factors: effective size, development environment, and product complexity. The key, and most important, element in the software estimate is the effective size of the software product. Determining size can be approached from several directions depending upon the software size measure (lines of code, function points, use cases, etc.) used by the development organization. A system developed by writing lines of code requires a different estimating approach than a previously developed or off-the- shelf application. The acquisition phase also influences the analyst’s approach because of the amount and type of software development data available from the program or developers. The development environment is the next most important effort and schedule driver. The environment can be factored into five categories: (1) developer capability or efficiency, (2) personnel experience, (3) development system characteristics, (4) management characteristics, and (5) product characteristics. The last four categories are largely driven by the product requirements. These factors take into consideration the development environment itself, the capabilities and experience of the developers, the developing organization’s management style, security requirements, and so on. These factors, along with software size and complexity, combine to determine the productivity or efficiency with which a developer can “build” and test the software. Ultimately, these environment characteristics drive the cost and schedule of the software development and implementation of the system. It is uncertain who first coined the phrase, “A fool with a tool is still a fool.” Plugging numbers into a parametric model without knowing if the results are realistic fits this adage. This guidebook addresses estimate realism using historical data, industry best practices, and authoritative insight. The insight comes from experts in the fields of software development and cost estimating. This information helps the analyst conduct a “sanity check” of their estimate results. A well-understood and validated estimate offers a defensible position for program office analysts, component cost agency analysts, and independent evaluators. A reasonable estimate is useful in budgeting, milestone decision reviews, and determining the life cycle or other costs of the program. The contents of this guide, ten sections and nine appendices, are grouped into four major parts. An introduction and the basics of the software development process lead off the tutorial. The next two major parts cover the estimating process and related details. Finally, concepts and examples presented in the sections are expanded in a set of appendices. The idea behind this structure is to present principles for instruction and reference in the core sections and, then, examine details and related examples. The information herein is not intended to dictate policy or supplant guidance given in official documents. However, the authors hope that everyone within the software cost estimating community in both the public and private sectors will find it useful. The extent of information on software development and cost estimating presented within these pages is not intended to be all-inclusive. Yet, the guidebook is meant to be comprehensive and complete, providing a single-resource document for use in creating estimates. Table of Contents Executive Summary ........................................................................................................... i List of Figures ................................................................................................................... xi List of Tables ................................................................................................................... xii List of Equations ............................................................................................................. xv Acknowledgements ....................................................................................................... xvii Section 1 Introduction ...................................................................................................... 1 1.1 Development constraints ........................................................................................... 4 1.2 Major cost factors ..................................................................................................... 4 1.2.1 Effective size ...................................................................................................... 5 1.2.2 Product complexity ............................................................................................ 5 1.2.3 Development environment ................................................................................. 6 1.2.4 Product characteristics ....................................................................................... 6 1.3 Software support estimation ..................................................................................... 6 1.4 Guidebook overview ................................................................................................. 7 Section 2 Software Development Process ..................................................................... 10 2.1 The Defense Acquisition System ............................................................................ 10 2.1.1 Framework elements ........................................................................................ 10 2.1.2 User needs and technology opportunities ........................................................ 11 2.1.3 Pre-systems acquisition .................................................................................... 11 2.1.3.1 Concept refinement phase ......................................................................... 11 2.1.3.2 Milestone A ............................................................................................... 12 2.1.3.3 Technology development phase ................................................................ 12 2.1.3.4 Milestone B ............................................................................................... 12 2.1.4 Systems acquisition .......................................................................................... 12 2.1.4.1 System development & demonstration ..................................................... 12 2.1.4.2 Milestone C ............................................................................................... 12 2.1.4.3 Production & deployment ......................................................................... 13 ii 2.1.5 Sustainment ...................................................................................................... 13 2.2 Waterfall model ...................................................................................................... 13 2.2.1 Requirements analysis and specification ......................................................... 15 2.2.2 Full-Scale Development ................................................................................... 16 2.2.3 System Integration and Test ............................................................................. 17 2.3 Software development products .............................................................................. 17 2.3.1 Software Development Plan ............................................................................ 17 2.3.1.1 Project organization .................................................................................. 17 2.3.1.2 Schedule .................................................................................................... 18 2.3.1.3 Software Design Document ...................................................................... 18 2.3.1.4 Quality Plan .............................................................................................. 18 2.3.2 Software Requirements Specification .............................................................. 19 2.3.3 Interface Control Document............................................................................. 19 Section 3 Levels of Detail in Software Estimates ......................................................... 20 3.1 Estimate foundation factors ...................................................................................
Recommended publications
  • Systems of Systems Cost Estimation Solutions

    Systems of Systems Cost Estimation Solutions

    Presented at the 2007 ISPA/SCEA Joint Annual International Conference and Workshop - www.iceaaonline.com Systems of Systems Cost Estimation Solutions Josh Wilson Presented at the 2007 ISPA/SCEA Joint Annual International Conference and Workshop - www.iceaaonline.com Content Background – Characteristics of a System of Systems (SoS) – System Engineering (SE) / System of Systems Engineering (SoSE) Cost Estimating solution summary – COSYSMO – COSOSIMO – SECOST – SEER-H with TSV – PES – TruePlanning Systems © 2007 PRICE Systems, LLC. All Rights Reserved. 2 Presented at the 2007 ISPA/SCEA Joint Annual International Conference and Workshop - www.iceaaonline.com Background Maier’s Criteria for defining a System of Systems – Operational Independence of Elements – Managerial Independence of Elements – Evolutionary Development – Emergent Behavior – Geographical Distribution Additional characteristics – Inter-disciplinary – Heterogeneous – Ambiguous changing boundaries – Dynamically changing requirements © 2007 PRICE Systems, LLC. All Rights Reserved. 3 Presented at the 2007 ISPA/SCEA Joint Annual International Conference and Workshop - www.iceaaonline.com Background Traditional SE System of Systems Engineering Purpose Develop to specific Develop to provide broad performance and/or capability and enable requirements interoperability Architecture Defined early and remains Dynamically reconfigured as relatively stable needs change Operability Specific interface Standards permit independent requirements to integrate operation and SoS components interoperability
  • Demarco Article.Indd

    Demarco Article.Indd

    The International Space Station Management and Cost Evaluations Task Force Anthony A. DeMarco President, PRICE Systems, L.L.C. 17000 Commerce Parkway - Suite A Mt. Laurel, NJ 08054 [email protected] 856.608.7214 Introduction The NASA-led International Space Station (ISS) is a technological marvel and a great feat of international cooperation. The ISS is an Earth-orbiting laboratory drawing upon the scientifi c and technological expertise of 16 nations: the United States, Canada, Japan, Russia, Brazil, and the 11 member nations of the European Space Agency (ESA). The ISS is a gateway to new space frontiers, a hallmark to United States space leadership, a unique laboratory, and a virtual space classroom. The ISS also is an out-of-control project, one that needs an immediate managerial overhaul to assure its productivity and retain its promise of being a world-class orbiting laboratory. The project is a victim of inadequate cost-accounting measures, a skyrocketing price tag, and an increasingly suspect research agenda given cost overruns and shrinking crew size. All these issues help frame the program as one steeped in controversy rather than as a cosmic gateway to the universe. ISS Cost Growth Revelations at the start of 2001 pointed to a $4.8 billion growth in NASA’s part of the program. That raised the cost to complete the ISS to a projected $30.1 billion. The escalating number is one that NASA, Congress, and other budget-watchers fear will grow. Furthermore, it was estimated that the outpost would cost on the order of $1.5 billion a year to operate.
  • Parametric World

    Parametric World

    Ask a Parametrician Q&A—p. 7 CER Best Fit study of: LOLS, IRLS and ZMPE—p. 21 PARAMETRIC WORLD Winter 2010 Vol. 29 No. 1 A Newsletter of The International Society of Parametric Analysts 2010 ISPA/SCEA Conference & Training Workshop June 8 – 11 — Sheraton San Diego Hotel & Marina p. 12 Awards Banquet to be held at the San Diego Air and Space Museum pictured here. Inside This Issue Below is an excerpt from Hank Apgar’s ISPA Historian column which features Professional Award Nominations .. P. 9 remembrances of Frank Freiman who ISPA 2010 Board Elections .......... P. 10 recently passed away: Jointness Report ........................ P. 19 “ I learned that Frank’s true genius was that he knew the way things Planning & Governance .............. P. 19 worked — development activities, Parametric World Report ............. P. 19 manufacturing processes, and Chapter News ........................... P. 24 operation and maintenance. And he used that knowledge to build the European Perspectives ............... P. 26 models that launched our industry. Secretary’s Report ..................... P. 28 Frank built models mechanistically, Membership Report .................... P. 29 Tribute to Frank not purely empirically.” Freiman — p. 4 Tony DeMarco, PRICE Systems Calendar of Events .................... P. 30 LeTTer From Your edITor PARAMETRIC WORLD By NiNa Tahir ISSN 1072-3803 ith the severe cold editor weather on the east Nina Tahir coast these days, it’s Email: [email protected] W 310-820-7756 comforting to know that before too long, it will be time to pack Chair, Board of directors shorts, cotton slacks, Hawaiian Jason Dechoretz .....................703-506-4600 shirts or summery dresses, [email protected] and comfy sandals for warm and beautiful San deputy Chair Diego — host city for our June annual conference.
  • SW-13A Wilson Paper Sos Solutions

    SW-13A Wilson Paper Sos Solutions

    Presented at the 2007 ISPA/SCEA Joint Annual International Conference and Workshop - www.iceaaonline.com System of Systems Cost Estimating Solutions Josh Wilson PRICE Systems, LLC Presented at the 2007 ISPA/SCEA Joint Annual International Conference and Workshop - www.iceaaonline.com System of systems is a relatively new term being applied to capability driven projects addressing large, inter-disciplinary problems involving many systems at multiple levels and multiple domains. Being poorly understood overall, it is not surprising that the tools and thought processes needed to address such problems are incomplete. The need to solve system of systems problems is urgent not only because of the growing complexity of modern challenges, but also because system of systems problems involve decisions that commit large amounts of money and resources. Fortunately, an area in which several advocates are attempting to improve industry understanding of system of systems relates to estimating the cost and effort required to deliver capabilities rather than platforms. Currently, the significant offerings in this and closely related realms include COSYSMO, COSOSIMO, SECOST, SEER-H with TSV, PRICE PES, and PRICE TruePlanning Systems. This paper explores the history of each of these models, the origin of their methodologies and cost estimating relationships, the major size and cost drivers, and the extent to which each solution addresses the need for a system of systems estimating capability. But first, what exactly is a system of systems? Maier’s Criteria for defining a system of systems has probably been encountered by anyone spending at least a few minutes looking into the subject. There are a few additional characteristics that often appear, but for the most part a system of systems may be classified as such by exhibiting a majority of the five traits listed by Maier: Operational Independence, Managerial Independence, Evolutionary Development, Emergent Behavior, and Geographical Distribution.