Especially in the field of software engineering, effort estimation plays an essential role. Moreover, the task of defining test scenarios and test cases is often underestimated during the early stages of the software engineering process, due to the fact, that the amount and granularity of required test cases and test steps is not known in advance, for instance, as a result of missing or incomplete requirement specifications. Furthermore, the fact that fix price projects are becoming more and more common makes the process of prior (test) effort estimation even more important, in order to not exceed the budget agreed upon. This paper discusses three important aspects of this development. First, it elaborates on the changing practices in project pricing, followed by a discussion of the general problems involved in the field of effort estimation in software projects. Finally, a distinct selection of today’s commonly used methods for test effort estimation will be presented: Function Point Analysis, Test Point Analysis and Use Case Points.
[1]
Ware Myers,et al.
Five Core Metrics: Intelligence behind Successful Software Management
,
2003
.
[2]
Paulo Borba,et al.
An Estimation Model for Test Execution Effort
,
2007,
ESEM 2007.
[3]
Manfred Bundschuh,et al.
The IT measurement compendium - estimating and benchmarking success with functional size measurement
,
2008
.
[4]
Paul Vickers,et al.
An Introduction to Function Point Analysis By Dr
,
2003
.
[5]
Alistair Cockburn,et al.
Writing Effective Use Cases
,
2000
.
[6]
van Epwm Erik Veenendaal,et al.
Test point analysis : a method for test estimation
,
1999
.
[7]
Suresh Nageswaran,et al.
Test Effort Estimation Using Use Case Points
,
2001
.