Cost estimation in software engineering: Difference between revisions

Revision as of 14:22, 23 February 2019

Revision as of 15:05, 23 February 2019

Line 1:

{{refimprove|date=November 2011}}

<ref name="COSMIC SOFTWARE ESTIMATION APPROACH">{{cite web |last1=Abran |first1=Alain |title=COSMIC software estimation approach|url=http://www.iceaaonline.com/ready/wp-content/uploads/2017/07/ACT13-Cosmic-Software-Estimating.pdf |website=International Cost Estimating and Analysis Association |publisher=ICEAA Online |accessdate=23 February 2019}}</ref>{{refimprove|date=November 2011}}

The cost of software is mainly from developer time, but can also be from training, managing and buying extra equipment, servers and software. Many methods have been developed for estimating software costs for a given project.

The cost of software is mainly from developer time, but can also be from training, managing and buying extra equipment, servers and software. Many methods have been developed for estimating software costs for a given project.

== Methods ==

Line 18 ⟶ 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 [[SLOC]], [[Function Point]] or [[https://en.wikipedia.org/wiki/Burn_down_chart Agile story points]].

==See also==