1 / 8

Pragmatic Software Cost Estimation

Pragmatic Software Cost Estimation. By Brian Belonia. Debate: Which Model or Tool?. Which cost estimation model to use Whether to measure software size in source line of code or function points What constitutes a good estimate. Barry Boehm, 1981 Royce, “HUGE BENEFIT”

thai
Download Presentation

Pragmatic 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. Pragmatic Software Cost Estimation By Brian Belonia

  2. Debate: Which Model or Tool? • Which cost estimation model to use • Whether to measure software size in source line of code or function points • What constitutes a good estimate

  3. Barry Boehm, 1981 Royce, “HUGE BENEFIT” Well-documented cost estimation models Three Modes Five Basic Phase Life Cycle Evolution: COCOMO II -“Basic COCOMO is good for rough order of magnitude estimates of software costs, but its accuracy is necessarily limited because of its lack of factors to account for differences in hardware constraints, personnel quality and experience, use of modern tools and techniques, and other project attributes known to have a significant influence on costs." Cost Estimation Models: COCOMO

  4. Cost Estimation Model: Comparison • Algorithmic Model • Expert Judgment • Analogy • Parkinson & Price to Win • Top-Down • Bottom-Up

  5. Source Lines of Code Barry Boehm Easy to Automate and Instrument. More ambiguous measure due to language advances and other components More useful and precise measurement basis of various metrics perspectives Function Points Capers Jones Independent of Technology More accurate estimator in early phases Measuring Software Size: Source lines of code versus function points

  6. A Good Estimate • It is conceived and supported by the project manager, architecture team, development team, and test team accountable for performing the work • It is accepted by all stakeholders as ambitious • It is base on a well-defined software cost model with a credible basis

  7. A Good Estimate (continued) • It is based on a database of relevant project experience that includes similar processes, similar technologies, similar environments, similar quality requirements, and similar people • It is defined in enough detail so that its key risk areas are understood and the probability of success is objectively assessed.

  8. Questions?

More Related