Cost estimation in software engineering: Difference between revisions

Revision as of 05:50, 15 December 2005

Latest revision as of 17:59, 20 February 2023

(168 intermediate revisions by more than 100 users not shown)

Line 1:

{{refimprove|date=November 2011}}

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.

Cost estimation in software engineering is typically concerned with the financial spend on the effort to develop and test the software, this can also include requirements review, maintenance, training, managing and buying extra equipment, servers and software. Many methods have been developed for estimating software costs for a given project.

== Methods ==

One popular methodMethods for estimation in software engineering isinclude [[Widebandthese Delphi]].principles:

*[[Analysis effort method]]

*[[Estimation theory|Parametric Estimating]]

*[[Extreme_Programming_Practices#Planning_game|The Planning Game]] (from [[Extreme Programming]])

*[[ITK method]], also known as Method CETIN

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

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

*[[Putnam model]], also known as SLIM

*[[PRICE Systems]] Founders of Commercial Parametric models that estimates the scope, cost, effort and schedule for software projects.

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

*[[Use Case Points|The Use Case Points method (UCP)]]

*[[Weighted Micro Function Points]] (WMFP)

* [[Wideband Delphi]]

Most cost software development estimation techniques involve estimating or measuring software size first and then applying some knowledge of historical of cost per unit of size. Software size is typically sized in [[Source lines of code|SLOC]], [[Function Point]] or [[Burn down chart|Agile story points]].

==See also==

==See also==

* [[Wideband Delphi]]

* [[Software development effort estimation]]

* [[Software metric]]

* [[Project management]]

* [[Cost overrun]]

* [[Risk]]

* [[Comparison of development estimation software]]

==External links==

* [https://doc.lagout.org/science/0_Computer%20Science/9_Others/9_Misc/Applied%20Software%20Project%20Management.pdf Software Estimation chapter] from O'Reilly, ''Applied Software Project Management''

* [http://www.methodsandtools.com/archive/archive.php?id=25 Estimating With Use Case Points] from ''Methods & Tools''

* [http://www.bfpug.com.br/Artigos/UCP/Banerjee-UCP_An_Estimation_Approach.pdf Definition of Use Case Points method (UCP)]

* Roy K. Clemmons, [http://www.bfpug.com.br/Artigos/UCP/Clemmons-Project_Estimation_with_UCP.pdf Project Estimation With Use Case Points]

* [https://massmediagroup.pro/PDF/SK903V1_WP_Estimating.pdf Estimating techniques throughout the SDLC]

{{Business-term-stub}}

[[Category:Software engineering costs|*]]

* http://www.edwardtufte.com/bboard/q-and-a-fetch-msg?msg_id=0000Vz&topic_id=1&topic=Ask%20E%2eT%2e

* [http://www.stellman-greene.com/ch03 Software Estimation chapter] from [http://www.stellman-greene.com Applied Software Project Management] (O'Reilly)