Sufyan Basri
ABSTRACT
In any software development life cycle, requirement and software changes are inevitable. One of the factors that influences the effectiveness of the change acceptance decision is the accuracy of the effort prediction for requirement changes. There are two current models that have been widely used to predict rework effort for requirement changes which are algorithmic and non-algorithmic models. The algorithmic model is known for its formal and structural way of prediction and best suited for Traditional software development methodology. While non-algorithmic model is widely adopted for Agile software development methodology of software projects due to its easiness and requires less work in term of effort predictability. Nevertheless, none of the existing effort prediction models for requirement changes are proven to suit both, Traditional and Agile software development methodology. Thus, this paper proposes an algorithmic-based effort prediction model for requirement changes that uses change impact analysis method which is applicable for both Traditional and Agile software development methodologies. The proposed model uses a current selected change impact analysis method for software development phase. The proposed model is evaluated through an extensive experimental validation using case study of six real Traditional and Agile methodologies software projects. The evaluation results confirmed a significance accuracy improvement of the proposed model over the existing approaches for both Traditional and Agile methodologies.
- Anandhi, V. and R.M. Chezian 2014. Regression Techniques in Software Effort Estimation Using COCOMO Dataset. in 2014 International Conference on Intelligent Computing Applications (ICICA). Google Scholar
Digital Library
- Asl, M.H. and N. Kama 2013. A Change Impact Size Estimation Approach during the Software Development. in 2013 22nd Australian Software Engineering Conference (ASWEC). Australia. Google ScholarDigital Library
- Attarzadeh, I., A. Mehranzadeh, and A. Barati 2012. Proposing an Enhanced Artificial Neural Network Prediction Model to Improve the Accuracy in Software Effort Estimation. in 2012 Fourth International Conference on Computational Intelligence, Communication Systems and Networks (CICSyN). Google ScholarDigital Library
- Awad, M. 2005. A comparison between agile and traditional software development methodologies, in University of Western Australia.Google Scholar
- Bardsiri, V.K., D.N.A. Jawawi, A.K. Bardsiri, and E. Khatibi 2013. LMES: A localized multi-estimator model to estimate software development effort. Engineering Applications of Artificial Intelligence, (0). Google ScholarDigital Library
- Basri, S., N. Kama, S. Adli, and F. Haneem 2016. Using static and dynamic impact analysis for effort estimation. IET Software, 10, 89--95Google ScholarCross Ref
- Bee Bee, C. 2010. Rework Requirement Changes in Software Maintenance. in 2010 Fifth International Conference on Software Engineering Advances (ICSEA). Google ScholarDigital Library
- Bennett, K.H. and T. Rajlich 2000. Software maintenance and evolution: a roadmap, in Proceedings of the Conference on The Future of Software Engineering. ACM: Limerick, Ireland. p. 73--87. Google ScholarDigital Library
- Boehm, B.W. 2000. Software Cost Estimation with Cocomo II. Prentice Hall. Google ScholarDigital Library
- Brooks Jr, F. 1956. No Silver Bullet - Essence and Accident in Software Engineering.Google Scholar
- Chua, B.B. and J. Verner 2010. Examining Requirements Change Rework Effort: A Study. arXiv preprint arXiv:1007.5126.Google Scholar
- Chua, Y.P. 2006. Asas Statistik Penyelidikan. 2 ed.: McGrraw-Hill (Malaysia).Google Scholar
- Faria, P. and E. Miranda 2012. Expert Judgment in Software Estimation During the Bid Phase of a Project - An Exploratory Survey. in 2012 Joint Conference of the 22nd International Workshop on Software Measurement and the 2012 Seventh International Conference on Software Process and Product Measurement (IWSM-MENSURA). Google ScholarDigital Library
- Fedotova, O., L. Teixeira, and H. Alvelos 2013. Software Effort Estimation with Multiple Linear Regression: Review and Practical Application. J. Inf. Sci. Eng., 29(5): p. 925--945.Google Scholar
- Finkelsteiin, A. and J. Kramer 2000. Software engineering: a roadmap. in Proceedings of the conference on The future of Software Engineering. ACM. Google ScholarDigital Library
- Garcia, C.A.L. and C.M. Hirata 2008. Integrating functional metrics, COCOMO II and earned value analysis for software projects using PMBoK, in Proceedings of the 2008 ACM symposium on Applied computing. ACM: Fortaleza, Ceara, Brazil. p. 820--825. Google ScholarDigital Library
- Huang, S.-J., N.-H. Chiu, and L.-W. Chen 2008. Integration of the grey relational analysis with genetic algorithm for software effort estimation. European Journal of Operational Research, 188(3): p. 898--909.Google ScholarCross Ref
- Jorgensen, M. 2005. Practical guidelines for expert-judgment-based software effort estimation. Software, IEEE, 22(3): p. 57--63. Google ScholarDigital Library
- Jorgensen, M. and K. Molokken-Ostvold 2004. Reasons for software effort estimation error: impact of respondent role, information collection approach, and data analysis method. Software Engineering, IEEE Transactions on, 30(12): p. 993--1007. Google ScholarDigital Library
- Jorgensen, M. and M. Shepperd 2007. A Systematic Review of Software Development Cost Estimation Studies. Software Engineering, IEEE Transactions on, 33(1): p. 33--53. Google ScholarDigital Library
- Kama, N. 2013. Change Impact Analysis for the Software Development Phase: State-of-the-art. International Journal of Software Engineering and Its Applications, 7(2): p. 10.Google Scholar
- Kama, N. and F. Azli 2012. A Change Impact Analysis Approach for the Software Development Phase, in Proceedings of the 2012 19th Asia-Pacific Software Engineering Conference - Volume 01. IEEE Computer Society. p. 583--592. Google ScholarDigital Library
- Keaveney, S. and K. Conboy 2006. Cost estimation in agile development projects.Google Scholar
- Kotonya, G. and I. Sommerville 1998. Requirements engineering: processes and techniques. J. Wiley. Google ScholarDigital Library
- Li, J., G. Ruhe, A. Al-Emran, and M. Richter 2007. A flexible method for software effort estimation by analogy. Empirical Software Engineering, 12(1): p. 65--106. Google ScholarDigital Library
- Lubashevsky, A. 1996. Living with function points. in Network Operations and Management Symposium, 1996., IEEE.Google ScholarCross Ref
- Nurmuliani, N., D. Zowghi, and S.P. Williams 2006. Requirements volatility and its impact on change effort: evidence-based research in software development projects. in Proceedings of the Eleventh Australian Workshop on Requirements Engineering.Google Scholar
- Ochodek, M., J. Nawrocki, and K. Kwarciak 2011. Simplifying effort estimation based on Use Case Points. Information and Software Technology, 53(3): p. 200--213. Google ScholarDigital Library
- Pfleeger, S.L. and S.A. Bohner 1990. A framework for software maintenance metrics. in Proceedings., Conference on Software Maintenance, 1990. IEEE.Google ScholarCross Ref
- Popli, R. and N. Chauhan 2014. Cost and effort estimation in agile software development. in 2014 International Conference on Optimization, Reliabilty, and Information Technology (ICROIT).Google ScholarCross Ref
- Seo, Y.-S., D.-H. Bae, and R. Jeffery 2013. AREION: Software effort estimation based on multiple regressions with adaptive recursive data partitioning. Information and Software Technology, 55(10): p. 1710--1725. Google ScholarDigital Library
- Sharif, B., S.A. Khan, and M.W. Bhatti 2012. Measuring the Impact of Changing Requirements on Software Project Cost: An Empirical Investigation. International Journal of Computer Science Issues (IJCSI), 9(3): p. 170--174.Google Scholar
- Shepperd, M., C. Schofield, and B. Kitchenham 1996. Effort estimation using analogy. in Proceedings of the 18th international conference on Software engineering. IEEE Computer Society. Google ScholarDigital Library
- Stålhane, T., V. Katta, and T. Myklebust 2014. Change Impact Analysis in Agile Development. EHPG Røros.Google Scholar
- Suri, P.K. and P. Ranjan 2012. Comparative Analysis of Software Effort Estimation Techniques. International Journal of Computer Applications (0975--8887), 48(21).Google Scholar
- Usman, M., E. Mendes, F. Weidt, and R. Britto 2014. Effort estimation in agile software development: a systematic literature review, in Proceedings of the 10th International Conference on Predictive Models in Software Engineering. ACM: Turin, Italy. p. 82--91. Google ScholarDigital Library
- Yang, Y., M. He, M. Li, Q. Wang, and B. Boehm 2008. Phase distribution of software development effort. in Proceedings of the Second ACM-IEEE international symposium on Empirical software engineering and measurement. ACM. Google ScholarDigital Library
- Yinhuan, Z., W. Beizhan, Z. Yilong, and S. Liang 2009. Estimation of software projects effort based on function point. in 4th International Conference on Computer Science & Education, 2009. ICCSE '09.Google ScholarCross Ref
Index Terms
- Predicting effort for requirement changes during software development
Recommendations
Investigating documented information for accurate effort estimation in agile software development
ESEC/FSE 2021: Proceedings of the 29th ACM Joint Meeting on European Software Engineering Conference and Symposium on the Foundations of Software EngineeringAn Agile development team estimates the effort of a work item to plan a sprint (i.e., an iteration in Scrum). Hence, reliable effort estimation would help the team create a reliable sprint plan. Prior studies proposed automated approaches to help the ...
Effort estimation in software development using story point: a machine learning approach
Agile methodologies are besieged with problems and potential solutions around predictive insights on a project. These problems range from estimation, quality, to effort and duration requirements. Despite of having innumerable predictive models not a ...
Effort estimation in large-scale software development: An industrial case study
AbstractContext: Software projects frequently incur schedule and budget overruns. Planning and estimation are particularly challenging in large and globally distributed agile projects. While software engineering researchers have ...
Comments