Cost estimation in software engineering: Difference between revisions

Revision as of 09:16, 24 February 2019

Latest revision as of 17:59, 20 February 2023

(21 intermediate revisions by 12 users not shown)

Line 1:

{{refimprove|date=November 2011}}

The cost of software development is mainly related to the effort of coding and testing. Many methods have been created for estimating software costs for a given software endeavour (new functionality or code maintenance):

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 ==

Line 9 ⟶ 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 16 ⟶ 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 [[https://en.wikipedia.org/wiki/Burn_down_chartBurn down chart|Agile story points]].

==See also==

* [[Software development effort estimation]]

* [[Software metric]]

Line 28 ⟶ 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]

* [httphttps://wwwmassmediagroup.gem-up.compro/PDF/SK903V1_WP_Estimating.pdf Estimating techniques throughout the SDLC]

* [http://softwaresurvival.blogspot.com/2006/11/dynamics-of-effort-estimation-in-most.html The Dynamics of Software Projects Estimation]

* [[Steve McConnell]], [http://www.construx.com/Page.aspx?nid=297 Resources on Software Estimation]

* [http://www.gem-up.com/PDF/SK903V1_WP_Estimating.pdf Estimating techniques throughout the SDLC]

* [http://www.nomitech.eu Top Down, BIM and Parametric Estimating Software]

* [https://web.archive.org/web/20111126011102/http://cost.jsc.nasa.gov/COCOMO.html COCOMO™ II]

{{Business-term-stub}}