Volume 2 , Issue 1 , PP: 20-24, 2020 | Cite this article as | XML | Html | PDF | Full Length Article
Ashish Sharma 1 * , Yogesh Sharma 2 , Radhika Bansal 3 , Sushant Verma 4
During the development of the software, Software Requirement Changes (SRC) often occurs. Software estimation helps in maintaining a balance between the increase and decrease of the price, time, etc. Function Point Analysis (FPA) is a software effort estimation technique used for measuring the size and complexity of software by calculating the functionality from a user's point of view. Function count focuses on what functionality is being delivered. It enables programmers to perform function point counting themselves instead of contacting an expert. An empirical study has been conducted to analyze the capability of the FPA technique. The results of the FPA-SDP (Function Point Analysis for Software Development Phase) model can help software project managers in (i) knowing the inconsistent states of software artifacts (ii) estimating the actual size of a change request with its complexity level for the software development phase.
Software Development Phase, Function Point Analysis, Software Requirement Changes, Size Estimation, Line of Code, Effort Estimation
[1] |
N. Kama and M. Halimi, "Extending Change Impact Analysis Approach for Change Effort Estimation in the Software Development Phase," Advanced Informatics School, Universiti Teknologi Malaysia, pp. 1-7, 2013. |
[2] |
J. Shah and N. Kama, "Issues of Using Function Point Analysis Method for Requirement Changes During Software Development Phase," Advanced Informatics School, Universiti Teknologi Malaysia, pp. 156-163, 2018. |
[3] |
A. B. Nassif, D. Ho and L. F. Capretz, "Software Estimation in the Early Stages of the Software Life Cycle," International Conference on Emerging Trends in Computer Science, Communications and Information Technology, pp. 1-13, 2010. |
[4] |
H. Azath and R. Wahidabanu , "Efficient effort estimation system viz. function points and quality assurance coverage," IET Software, vol. 6, no. 4, pp. 335-341, 2016. |
[5] |
J. Shah, N. Kama and S. A. Ismail, "An Empirical Study with Function Point Analysis for Software Development Phase Method," ICSIE'18, pp. 7-11, 2018. |
[6] |
C. R. Symons, "Function Point Analysis: Difficulties and Improvements," IEEE Transactions on Software Engineering, vol. 14, no. 1, pp. 2-11, 1998. |
[7] |
D. Kchaou and N. Bouassida, "UML models change impact analysis using a text similarity technique," IET Digital Library, vol. 11, no. 1, pp. 27-37, 2017. |
[8] |
S. Basri and R. Ibrahim, "A Novel Effort Estimation Approach for Requirement Changes during Software Development Phase," in International Journal of Software Engineering and Its Applications, 2015. |
[9] |
V. Nguyen, S. Deeds, T. Tan and B. Boehm11, "A SLOC Counting Standard," Center for Systems and Software Engineering University of Southern California, vol. 1, no. 1, pp. 1-15, 2007. |
[10] |
S. Bhatia and D. J. Malhotra, "A Survey on Impact of Lines of Code On Software Complexity," IEEE International Conference on Advances in Engineering & Technology Research, pp. 1-4, 2014. |
[11] |
M. Shahid and S. Ibrahim, "Change impact analysis with a software traceability approach to support software maintenance," IEEE, vol. 1, no. 1, pp. 1-6, 2016. |