Cost estimation in software engineering: Difference between revisions

Content deleted Content added
added citations and rephrased unspecific phrases
Tag: possible conflict of interest
Apolo234 (talk | contribs)
Methods: Changed wikilink to have space instead of underline
 
(12 intermediate revisions by 8 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, debug, and test the software<ref>ProjectCodeMeter [http://www.projectcodemeter.com/cost_estimation/help/FN_budgetsizing.htm "Estimating a Future project schedule and cost for internal budget planning"]</ref>, this can also include peripheralrequirements costsreview, such asmaintenance, training, managing and buying extra equipment, servers and software<ref>Amazon [https://calculator.s3.amazonaws.com/index.html "AWSMany SIMPLEmethods MONTHLYhave CALCULATOR"]</ref>been developed for estimating software costs for a given project.
 
== Methods ==
Methods for estimatingestimation various aspects ofin software engineering include these principles:
*[[Analysis effort method]]
*[[Estimation theory|Parametric Estimating]]
Line 11:
*[[Proxy-based estimating]] (PROBE) (from the [[Personal Software Process]])
*[[Program Evaluation and Review Technique]] (PERT)
*[[Putnam_modelPutnam 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]]
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 29 ⟶ 28:
* [[Comparison of development estimation software]]
 
==References==
 
{{Reflist}}
==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''
Line 40 ⟶ 34:
* 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]
* [https://web.archive.org/web/20111126011102/http://cost.jsc.nasa.gov/COCOMO.html COCOMO™ II]
 
{{Business-term-stub}}