Effort Estimation of Software Development: Depth View on IRAN Case

Yaeghoob Yavari¹ and Hassan Bashiri^2,

¹Department of Computer Engineering, Payam Noor University, Hamedan, Iran

²Department of Computer Engineering and Information Technology, Hamedan University of Technology, Hamedan, Iran

Cite this paper:
Yaeghoob Yavari and Hassan Bashiri. Effort Estimation of Software Development: Depth View on IRAN Case. American Journal of Software Engineering. 2013; 1(1):5-11. doi: 10.12691/ajse-1-1-2

Abstract

Although the age of software engineering goes more than a half of a century, successful software projects which meet time and costs based on primary estimation are also in high risk. There are various reasons with different weights for that. Management problem, scheduling and effort estimation are the most important ones. Precise estimation for software development is a very hard and complex task. Because of software special problems in Iran estimation challenges have been doubled between software development companies. Based on our experience at work, many incorrect estimations in software companies urged us research about more accurate statistics and reasons for this problem. More than thirty known companies were selected. We prepared a questionnaire to collect data about companies, as well as, their projects and information about project estimation. The results were analyzed and showed that in most of the cases estimation deviation is more than 40% from primary estimation and in some cases it is up to 60%. These statistics show the necessity of traumatology and more investigation into reasons of these deviations. Our studies have specified the most important reasons of these deviations and suggest some approaches to control them.

Keywords:
software metrics effort estimation use case points analogy agile

This work is licensed under a Creative Commons Attribution 4.0 International License. To view a copy of this license, visit http://creativecommons.org/licenses/by/4.0/

Figures

References:

[1]	Sanjeev D, Software Metrics – A Tool for Measuring Complexity, International Journal of Software and Web Sciences s, 2 (1), pp. 4-7, 2012.
[2]	Ahmad Z, Majeed S, Towards Increase in Quality by Preprocessed Source Code and Measurement Analysis of Software Applications, IST Transactions on Information Technology- Theory and Applications, Vol. 1, No. 1 (2),2010.
[3]	Ahmad Z, Towards performance measurment and Metrics Bassed Analysis of PLA Applications, International Journal of Software Engineering & Applications (IJSEA), Vol.1, No.3, 2010.
[4]	Galorath DD, Evans W. M, Software Sizing, Estimation, and Risk Management, Auerbach Publication (Taylor & Francis Group), 2006.
[5]	Kashyap D, Tripathi A, Misra AK, Software Development Effort and Cost Estimation: Neuro-Fuzzy Model, IOSRJCE, 2012.
[6]	Koteswara RK, Raju G.S.V.P, Madhusudhana RTV, Effort Estimations Based on Lines of Code and Function Points in Software Project Management, IJCSNS, Vol.8 No.6, 2008.
[7]	Attarzadeh I, Hock OS, Improving the Accuracy of Software Cost Estimation Model Based on New Fuzzy Logic Model, World Applied Science Journal Vol.8 No.2, 2010.
[8]	Prabhat KVB, Kumar MS, Complexity Metric for Analogy Based Effort Estimation, Journal of Theoretical and Applied Information Technology, 2009.
[9]	Sharma A, Kushwaha DS, Applying Requirement Based Complexity For The Estimation of Software Development and Testing Effort, ITCS, SIP, JSE, 2012.
[10]	Mohagheghi P, Anda B, Conradi R, Effort Estimation of Use Cases for Incremental Large-Scale Software Development, ICSE, 2005.
[11]	Jorgensen M, Grimstad S, Software Development Effort Estimation Demystifying and Expert Estimation, Simula Research Laboratory, Norway, 2009.
[12]	Reddy CH. S, Raju KVSVN, An Improved Fuzzy Approach for COCOMO’s Effort Estimation Using Gaussian Membership Function, DENSE Research Group, Journal OF Software, Vol.4, No.5, 2009.
[13]	Vijay FJ, Manoharan C, Initial Hybrid Method for Software Effort estimation Benchmarking and Risk Assessment Using Design of Software, Global Journal of Computer Science and Technology, 2009.
[14]	Frohnhoff S, Engels G, Revised Use Case Point Method -Effort Estimation in Development Projects for Business Applications, Germany, 2008.
[15]	Sharifloo Molzam A, Mirakhorli M, Shams Aliee F, Agility in Iran: Position, Motivation, and Adaption, 2008.
[16]	Menzies T, Jalali O, Hihn J, Baker D, Lum K, Software Effort Estimation and Conclusion Stability, Vol.6, No.1, 2007.
[17]	Poscic P, Pavlic M, Vrcek N, Method for Estimating the Complexity of Designing Business Information Systems, JIOS, Vol.32, No.2, 2008.
[18]	Nicholson B, Sahay S, Building Iran’s Software Industry: An Assessment of Plans and Prospects, EJISDDC, 2003.
[19]	Sheppred M, Schofield C, Estimating Software Project Effort Using Analogies. IEEE Transactions on Software Engineering, vol. 23 no. 11, 1997.
[20]	Kim S, Lively W, Simmons D, An Effort Estimation by UML Points in the Early Stage of Software Development, Software Engineering Research and Practice, 2006.
[21]	Pfleeger SL, Felicia W, Lewis R, Software Cost Estimation and Sizing Methods: Issues and Guidelines, RAND Corporation, USA, 2005.
[22]	Sackman H, Erikson WJ, Grant EE, Exploratory Experimental Studies Comparing Online and Offline Programming Performance, ACM Volume 11 Issue 1, 1968.
[23]	Laird LM, Brennan MC, Software Measurement and Estimation a Practical Approach, wiley Interscience Publication & IEEE Computer Society, 2006.
[24]	Karner G, Resource Estimation for Objectory Projects, 1993.
[25]	Anda B, Comparing Effort Estimates Based on Use Case Points with Expert Estimates, 2003.
[26]	ISO/IEC 9126-2, Software Engineering, Product Quality, International Technical Report, Part 2: External Metrics, JAPEN, 2002.
[27]	Humphrey W, Winning with Software: An Executive Strategy, Addison Wesley, 2002.
[28]	Cohn, M, Agile Estimating and Planning, Pearson Education Inc, 2006.
[29]	Yavari Y, Afsharchi M, Karami M, Software Complexity Level Determination Using Software Effort Estimation Use Case Points Metrics, Malaysian Conference in Software Engineering (MySEC), , IEEE Xplore , p 257-262, 2011.