Cost estimation in software engineering
 | This article needs additional citations for verification. (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.
Methods
Methods for estimation in software engineering include these principles:
- Analysis effort method
- GOT[disambiguation needed], the first version known as GOT 81 and the second as GOT™ II
- Vikings[disambiguation needed] Refinement of typical agile estimating techniques using minimal measurement and total time accounting.
- Stranger Things[disambiguation needed]
- Parametric Estimating
- The Planning Game (from Extreme Programming)
- ITK method, also known as Method CETIN
- Proxy-based estimating (PROBE) (from the Personal Software Process)
- Program Evaluation and Review Technique (PERT)
- Putnam_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
- The Use Case Points method (UCP)
- Weighted Micro Function Points (WMFP)
- Wideband Delphi
See also
- Software development effort estimation
- Software metric
- Project management
- Cost overrun
- Risk
- Comparison of development estimation software
External links
- Software Estimation chapter from O'Reilly, Applied Software Project Management
- Estimating With Use Case Points from Methods & Tools
- Definition of Use Case Points method (UCP)
- Roy K. Clemmons, Project Estimation With Use Case Points
- The Dynamics of Software Projects Estimation
- Steve McConnell, Resources on Software Estimation
- Estimating techniques throughout the SDLC
- Top Down, BIM and Parametric Estimating Software
- COCOMO™ II
 | This business term article is a stub. You can help Wikipedia by expanding it. |