A systematic review of studies on use case points and expert-based estimation of software development effort

Yasir Mahmood, Nazri Kama, Azri Azmi

Research output: Contribution to journalReview articlepeer-review

40 Citations (Scopus)

Abstract

In recent years, due to significant evolution in adopting new technologies and development methodologies in the field of software engineering, the developers and researchers are striving to optimize the accuracy of software effort estimation (SEE). The overestimation and underestimation both are the key challenges for software progress; hence, there is a continuous need for an accurate SEE. This paper highlights a systematic review of studies associated with the best practices of use case point (UCP) and expert judgment–based software development effort estimation techniques. The primary aim and contribution of this paper are to support the researchers through an extensive review to ease to other researcher's search for effort estimation studies. We have performed state-of-the-art review from five viewpoints of reference: (a) review of studies concerning UCPs and expert judgment–based effort estimation, (b) research contribution and future recommendation in different novelties, (c) usage of the dataset, (d) availability of accuracy metrics, and (e) findings of the studies. We have performed a systematic review of studies which are published in the period of 2000 to 2019. We have selected a total of 34 primary studies of UCP and expert judgment–based estimation techniques to report the research questions stated in this review.

Original languageEnglish
Article numbere2245
JournalJournal of software: Evolution and Process
Volume32
Issue number7
DOIs
Publication statusPublished - Jul 1 2020
Externally publishedYes

Keywords

  • effort estimation
  • expert judgment
  • software development
  • systematic literature review
  • use case points

ASJC Scopus subject areas

  • Software

Fingerprint

Dive into the research topics of 'A systematic review of studies on use case points and expert-based estimation of software development effort'. Together they form a unique fingerprint.

Cite this