Cost estimation in software engineering: Difference between revisions

Revision as of 05:52, 17 February 2017

Latest revision as of 17:59, 20 February 2023

(48 intermediate revisions by 29 users not shown)

Line 1:

{{mergeto|Software development effort estimation|date=August 2014}}

{{no lede|date=August 2014}}

{{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. Many methods have been developed for estimating software costs for a given project.

== Methods ==

Methods for estimation in software engineering include thisthese principles:

*[[Analysis effort method]]

*[[COCOMO]], the first version known as COCOMO 81 and the second as COCOMO™ II

*[[COSYSMO]]

*[[Evidence-based Scheduling]] Refinement of typical agile estimating techniques using minimal measurement and total time accounting.

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

*[[Estimation theory|Parametric Estimating]]

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

Line 15 ⟶ 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 21 ⟶ 17:

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

* [[Software development effort estimation]]

* [[Software metric]]

Line 32 ⟶ 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''

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

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

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

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

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

[[Category:Software engineering costs|*]]

* Article [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]

* [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 by Roy Clemmons]

* [COCOMO™ II http://cost.jsc.nasa.gov/COCOMO.html]

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

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

{{Business-term-stub}}

[[Category:Software engineering costs|*]]