Cost estimation in software engineering: Difference between revisions

Revision as of 19:27, 14 November 2021

Latest revision as of 17:59, 20 February 2023

(One intermediate revision by one other user not shown)

Line 9:

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

*[[ITK method]], also known as Method CETIN

*[https://www.pricesystems.com/cost-engineering-bid-proposal-2/ Model Based Cost Engineering] (MBCE)

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

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

* [https://atomengine.co.uk/instant-app-development-estimator/ Mobile app development estimation tool]

{{Business-term-stub}}