Development of analogy-based estimation method for software development cost estimation in government agencies

Cost estimation for software development in Government Agencies is still considered as a challenge. Owner Estimate Cost (OEC) should be estimated based on the specifications at the early stage of the procurement. There is no standard used by the government in formulating technical specifications. This affects the OEC value that tends to be highly subjective. Therefore, it is important to develop an estimation method that is able to represent software complexity at the early stage of procurement. The approach that can be considered in the early stages is the Use Case approach. UCP is a method to calculating effort algorithmically using use case complexity. However, UCP has a limitation, which only provides a level of fixed complexity and cannot handle uncertain conditions. In the other hand, Some previous research result shows that the analogy method has better performance than the algorithmic method. In this study, we developed the effort and cost estimation methods based on analogy by building a new dataset using the use case complexity parameters. Datasets are collected from 100 historical software projects data that have been built using the UCP method approach. Cost components for the project follow the current procurement regulations in Indonesia. Dataset evaluation for effort estimation using the proposed analogy method shows the best results of MMRE of 0.36 and PRED(0.25) of 0.57. MMRE shows the average difference of actual effort and estimated effort, whereas PRED (0.25) shows prediction level with error value smaller or equal to 25%. Furthermore, the estimated cost of the three software projects resulted in an average percentage deviation of 7.37%.

[1]  D. Ross Jeffery,et al.  An Empirical Study of Analogy-based Software Effort Estimation , 1999, Empirical Software Engineering.

[2]  Michael J. Prietula,et al.  Software-Effort Estimation: An Exploratory Study of Expert Performance , 1991, Inf. Syst. Res..

[3]  Agnar Aamodt,et al.  Case-Based Reasoning: Foundational Issues, Methodological Variations, and System Approaches , 1994, AI Commun..

[4]  Michael M. Richter,et al.  On the Notion of Similarity in Case Based Reasoning and Fuzzy Theory , 2001, Soft Computing in Case Based Reasoning.

[5]  Alistair Cockburn,et al.  Writing Effective Use Cases , 2000 .

[6]  Ioannis Stamelos,et al.  A Simulation Tool for Efficient Analogy Based Cost Estimation , 2000, Empirical Software Engineering.

[7]  Gustav Karner,et al.  Resource Estimation for Objectory Projects , 2010 .

[8]  Sholiq,et al.  Effort Distribution to Estimate Cost in Small to Medium Software Development Project with Use Case Points , 2015 .

[9]  Zdenka Prokopova,et al.  Algorithmic Optimisation Method for Improving Use Case Points Estimation , 2015, PloS one.

[10]  Shinji Kusumoto,et al.  On a Use Case Points Measurement Tool for Effective Project Management , 2007 .

[11]  Silvia Regina Vergilio,et al.  Software Effort Estimation Based on Use Cases , 2006, 30th Annual International Computer Software and Applications Conference (COMPSAC'06).

[12]  Emilia Mendes,et al.  Do adaptation rules improve web cost estimation? , 2003, HYPERTEXT '03.

[13]  Jonathan Lee,et al.  Fuzzy logic as a basic for use case point estimation , 2011, 2011 IEEE International Conference on Fuzzy Systems (FUZZ-IEEE 2011).

[14]  Martin J. Shepperd,et al.  Estimating Software Project Effort Using Analogies , 1997, IEEE Trans. Software Eng..

[15]  Jacky W. Keung,et al.  Software Development Cost Estimation Using Analogy: A Review , 2009, 2009 Australian Software Engineering Conference.

[16]  Miroslaw Ochodek,et al.  Simplifying effort estimation based on Use Case Points , 2011, Inf. Softw. Technol..

[17]  Shashank Sahu,et al.  Software effort estimation using enhanced use case point model , 2015, International Conference on Computing, Communication & Automation.

[18]  Ivar Jacobson,et al.  Object-oriented software engineering - a use case driven approach , 1993, TOOLS.