A structured approach to estimate efforts for small sized software projects

Suvarna R. Jagtap


When it comes to estimate the size of the project people always find it difficult to estimate the size of the project that is how ‘big’ or ‘small’ it is. Usually software project sizes are generally categorized as small, medium and big depending on the source lines of codes or function points. For benchmarking and estimating purposes it often is useful to appreciate the relative size of a specific piece of software. It is feasible and practical to relate relative sizes  to a absolute functional sizes expressed on a logarithmic scale.

            The majority of projects (approx.90%) fall in the range ‘small’ to ‘large’; i.e. larger than 30 function points but smaller than 3000 function points. Software cost estimation is a tedious process but it is necessary to keep track of project development progress. Generally  , a more serious approach is used for medium and large projects. This paper throws light on various issues related to the estimation of small sized software projects.


Estimation ,COCOMO II ,SLOC ,FP

Full Text:



Agrawal M., Chari K., (2007) “Software Effort, Quality, and Cycle Time: A Study of CMM Level 5 Projects” IEEE Transactions on Software Engineering, Volume:33, Issue: 3, pp. 145 - 156.

Heemstra, F.J. "Software Cost Estimation". http://core.ac.uk/. N.p., 1992. Web. 21 June 2015.

Khatibi, Vahid, and Dayang Jawawi. "Software Cost Estimation Methods: A Review". http://cisjournal.org/. N.p., 2010. Web. 21 June 2015.

Attarzadeh, I., Hock, O.S.,(2009) “Using Enhancement Method to Improve Earned Value Index to Achieve an Accurate Project Time and Cost Estimation

Ashman R. (2004) “Project Estimation: A Simple Use-Case-Based Model” IT Professional Volume: 6, Issue: 4, pp. 40 – 44.

Boehm, B.W., Software Engineering Economics, Prentice Hall, NJ, 1981.

Boehm, B.W., Improving Software Productivity, Computer , pp 43-57, May 1987.

Azath H., Wahidabanu R. S. D., (2011) “Efficient effort estimation system

viz.function points and quality assurance coverage” IET Software, Volume: 6, Issue :4, pp. 335–341

Beck, K., (2003) “Test driven development: By example”MA: Addison‐Wesley.

Beck, K., Beedle, M., van Bennekum, A., Cockburn, A., Cunningham, W., Martin Fowler, M., Grenning, J., Highsmith, J., Hunt, A., Jeffries, R., Kern, J., Marick, B.,Martin, R.C., Mellor, S., Schwaber,K., Sutherland, J., Thomas, D., (2001). “Manifesto for Agile Software Development” Last accessed from http://agilemanifesto.org/.

Benediktsson O., Dalcher D., (2005) “Estimating size in incremental software development projects” IEE Proceedings online no. 20050019, Volume: 152, Issue:6, pp253-259.

Berger, J., O., (1993) “Statistical Decision Theory and Bayesian Analysis”.Springer; 2nd edition Verlag, New York.

Bo Yang, Huajun Hu, Lixin Jia (2008) “A Study of Uncertainty in Software Cost and Its Impact on Optimal Software Release Time” IEEE Transactions on Software Engineering, Volume: 34, Issue: 6 pp. 813 – 825.

Boehm B, Abts C., Brown W., Chulani S., Clark B.k., Horowitz E , Madachy R.,Reifer D. j. and Steece B., (2000) “Software Cost Estimation with COCOMO

II” Prentice Hall, Edition 1

Davidson, F. and Huot, J-C., Large-Scale Projects: Management Trends for Major Projects, Cost Engineering, 33, 2, pp 15-23, 1991.

DeMarco, T. And Lister, T., Peopleware : productive projects and teams, Dorset House , New York, NY, 1987.

Hihn, J., Habib-agahi, H., Cost Estimation of Software Intensive Projects: A survey of current Practices, IEEE Proceedings…

Jones, T.C., Programming Productivity, McGraw-Hill, NY 1987.

Kansala, K., Integrating Risk Assessment with Cost Estimation, IEEE Software, May/June, 1997, pp. 61-68.


  • There are currently no refbacks.

Creative Commons License
This work is licensed under a Creative Commons Attribution 3.0 License.