Towards ensemble-based use case point prediction

Shukla, Suyash; Kumar, Sandeep

doi:10.1007/s11219-022-09612-2

Cited by 1 publication

(1 citation statement)

References 38 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…MMRE, MdMRE, and other evaluation metrics will be used to evaluate the estimation error rate in greater depth. These results will be analyzed to identify patterns in estimation error and the factors that influence it [26]. Furthermore, these results provide insight into the estimated level of complexity of the project.…”

Section: Figure 2 Use Case Diagram Piaud Portalmentioning

confidence: 99%

Activity-based function point complexity of use case diagrams for software effort estimation

Jayadi,

Dewi,

Sussolaikah

2024

J. Soft Comput. Explor.

View full text Add to dashboard Cite

This study proposes a Function Point Analysis (FPA) based software development effort estimation methodology integrated with Use Case Diagrams. These methods include identifying actor activities, classifying those activities into FPA categories, and calculating Unadjusted Function Points (UFP). Followed by the calculation of Technical Complexity Factors (TCF) and Adjusted Function Points (AFP), this study aims to produce more accurate man-hours estimates. Results show a UFP of 162 TCF of 11, AFP of 123.12, and an estimated effort of 1846.8 hours worked, while the actual effort is 1228 hours. Evaluation of estimates using the metrics Mean Magnitude of Relative Error (MMER) 0.34, Mean Magnitude of Relative Error (MMRE) 0.50, Mean Absolute Error (MAE) 618.80, Mean Balanced Relative Error (MBRE) 0.50, Mean Inverse Balanced Relative Error (MIBRE) 0.34, and Root Mean Squared Error (RMSE) 618.80, showed sufficient precision despite the overestimation. The study suggests the need for adjustments in TCF calculations and considering development environment factors in more detail to improve estimation accuracy. These findings are essential in improving the precision of effort estimation methodologies in software development, particularly in projects that use Use Case Diagrams as the primary framework.

show abstract

Section: Figure 2 Use Case Diagram Piaud Portalmentioning

confidence: 99%