Content deleted Content added
The definition at the beginning was innaccurate. |
→Methods: Changed wikilink to have space instead of underline |
||
| (17 intermediate revisions by 10 users not shown) | |||
Line 1:
{{refimprove|date=November 2011}}
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.
== Methods ==
Line 11:
*[[Proxy-based estimating]] (PROBE) (from the [[Personal Software Process]])
*[[Program Evaluation and Review Technique]] (PERT)
*[[
*[[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]]
Line 18:
*[[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==
* [[Software development effort estimation]]
* [[Software metric]]
Line 30 ⟶ 29:
==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]
* [
{{Business-term-stub}}
| |||