Simple software cost analysis: safe or unsafe?
PROMISE '05 Proceedings of the 2005 workshop on Predictor models in software engineering
Specialization and extrapolation of software cost models
Proceedings of the 20th IEEE/ACM international Conference on Automated software engineering
Trade-off Analysis in Web Development
3-WoSQ Proceedings of the third workshop on Software quality
The business case for automated software engineering
Proceedings of the twenty-second IEEE/ACM international conference on Automated software engineering
Can we build software faster and better and cheaper?
PROMISE '09 Proceedings of the 5th International Conference on Predictor Models in Software Engineering
How to avoid drastic software process change (using stochastic stability)
ICSE '09 Proceedings of the 31st International Conference on Software Engineering
On the relative value of cross-company and within-company data for defect prediction
Empirical Software Engineering
Accurate estimates without calibration?
ICSP'08 Proceedings of the Software process, 2008 international conference on Making globally distributed software development a success story
Case-based reasoning vs parametric models for software quality optimization
Proceedings of the 6th International Conference on Predictive Models in Software Engineering
A second look at Faster, Better, Cheaper
Innovations in Systems and Software Engineering
Local vs. global models for effort estimation and defect prediction
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
| Hi-index | 0.00 |
Simple software cost-analysis methods are readily available, but they aren't always safe. The simplest method is to base your cost estimate on the typical costs or productivity rates of your previous projects. That approach will work well if your new project doesn't have any cost-critical differences from those previous projects, but it won't be safe if some critical cost driver has degraded. Simple history-based software cost-analysis methods would be safer if you could identify which cost driver factors were likely to cause critical cost differences and estimate how much cost difference would result if a critical cost driver changed by a given degree. In this article, I provide a safe and simple method for doing both of these by using some cost-estimating relationships. COCOMO II is an updated and re-calibrated version of COCOMO (COnstructive COst MOdel). I also show how the COCOMO II cost drivers let you perform cost sensitivity and tradeoff analyses, and discuss how you can use similar methods with other software cost-estimation models