Cost estimation in software engineering: Difference between revisions

Revision as of 11:10, 4 October 2007

Revision as of 10:15, 1 November 2007

Line 1:

The ability to accurately estimate the time/cost taken for a [[project]] to come to its successful conclusion has been a serious problem for [[software engineering|software engineers]]. The use of repeatable, clearly defined and well understood [[software development process]] has in recent years shown itself to be the most effective method of gaining useful [[historical data]] that can be used for statistical estimation. In particular, the act of sampling more frequently, coupled with the loosening of constraints between parts of a project, has allowed more accurate estimation and more rapid development times.

== Methods ==

Popular methods for estimation in software engineering include:

Line 7 ⟶ 9:

*[[Cocomo]]

*[[Putnam_model|SLIM]]

*[[SEER-SEM]] Parametric Estimation of Effort, Schedule, Cost, Risk. Mimimum time and staffing concepts based on [[Brooks's Law]]

*[[Function point analysis|Function Point Analysis]]

*[[Proxy-based estimating]] (PROBE) (from the [[Personal Software Process]])

Line 13 ⟶ 15:

*[[Program Evaluation and Review Technique]] (PERT)

*[[Analysis Effort method]]

*[[Top Down Estimation]]

*[[Bottom up estimation]]

*[[Converging estimates]]

==See also==