A multiple-case study of software effort estimation based on use case points

Anda, Bente; Benestad, Hans Christian; Hove, S.E.

doi:10.1109/isese.2005.1541849

Cited by 26 publications

(28 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Nevertheless, the UCP technique has some limitations that (1) it does not consider internal structure of the use cases (2) may reduce accuracy of the estimation process [7,26]. For instance, use case has only 3 categories of complexity, i.e., simple, average, complex, independent of its internal structure.…”

Section: Planning and Estimationmentioning

confidence: 98%

A systematic literature review of use case specifications research

Tiwari

Gupta

2015

Information and Software Technology

View full text Add to dashboard Cite

Section: Planning and Estimationmentioning

confidence: 98%

A systematic literature review of use case specifications research

Tiwari

Gupta

2015

Information and Software Technology

View full text Add to dashboard Cite

“…Anda et al [6] present an experience that measures the estimation of effort in use case points in a specific system. Four different companies were asked to develop an application fulfilling certain requirements.…”

Section: Related Workmentioning

confidence: 99%

“…Among them Karner [5], and Anda et al [6], who work with use case points; Ruhe et al [2], who introduce web objects; Harput et al [7], Fetcke et al [8], and Uemura et al [9], who separately calculate function points from object-oriented models.…”

Section: Related Workmentioning

confidence: 99%

Employing use cases to early estimate effort with simpler metrics

Robiolo

Orosco

2008

Innovations Syst Softw Eng

View full text Add to dashboard Cite

In order to calculate size and to estimate effort in applications, the standard method most usually used is function points, which has been used with good results in the development of industrial software for some time. However, some aspects should be improved, namely: the time at which the estimation of effort is performed and the margin of error in the effort estimation. Consequently, another size metric which could be used to obtain more accurate estimations should be found. This article presents two other size metrics for projects based on use cases: transactions and entity objects. Effort is estimated by using the technique mean productivity value. There is also a description of two case studies, one which involved four academic projects and the other one which involved four industrial projects. They were developed in order to compare the estimations obtained with each method. The result shows that the current way of estimating effort can be improved by using the number of transactions as a size metric and the technique mean productivity value.

show abstract

“…[1], who work with use case points; Ruhe, Jeffery and Wieczorek [19], who introduces web objects; Harput, Kaindl and Kramer [5] and Uemura, Kusumoto and Inoue [22 ], who calculate functional points from object oriented models.…”

Section: Related Workmentioning

confidence: 99%

An Alternative Method Employing Uses Cases for Early Effort Estimation

Robiolo

Orosco²

2007

31st IEEE Software Engineering Workshop (SEW 2007)

View full text Add to dashboard Cite

Function points are a standard method frequently used to calculate size and to estimate effort in applications. Although it has been used with good results in the development of industrial software, it is still necessary to improve some aspects such as: the time at which the estimation of effort is performed and the margin of error in the effort estimation. In this article an alternative method for early effort estimation based on use cases is presented. Two new alternative notions of size are used for effort estimation: Transactions and Entity Objects. A case study developed in order to compare the estimations obtained with the two methods for actual projects is described. The result shows that by using number of transactions as a notion of size and the Technique Mean Productivity Value to perform the estimation, the current way of estimating effort can be improved.

show abstract

A multiple-case study of software effort estimation based on use case points

Cited by 26 publications

References 16 publications

A systematic literature review of use case specifications research

A systematic literature review of use case specifications research

Employing use cases to early estimate effort with simpler metrics

An Alternative Method Employing Uses Cases for Early Effort Estimation

Contact Info

Product

Resources

About