Through industry collaboration we have experienced an increasing interest in software effort estimation based on use cases. We therefore investigated one promising method, the use case points method, which is inspired by function points analysis. Four companies developed equivalent functionality, but their development processes varied, ranging from a light, code-and-fix process with limited emphasis on code quality, to a heavy process with considerable emphasis on analysis, design and code quality. Our effort estimate, which was based on the use case points method, was close to the actual effort of the company with the lightest development process; the estimate was 413 hours while actual effort of the four companies ranged from 431 to 943 hours. These results show, that the use case points method needs modification to better handle effort related to the development process and the quality of the code.
%0 Conference Paper
%1 anda_multiple-case_2005
%A Anda, B.
%A Benestad, H. C
%A Hove, S. E
%B 2005 International Symposium on Empirical Software Engineering, 2005
%D 2005
%I IEEE
%K Case Collaborative Computer Environmental Laboratories; Programming; Project Qualifications; Size Software Use aided analysis; computer cost development effort engineering; estimation; factors; function industry; management; measurement; point points software software;
%R 10.1109/ISESE.2005.1541849
%T A multiple-case study of software effort estimation based on use case points
%X Through industry collaboration we have experienced an increasing interest in software effort estimation based on use cases. We therefore investigated one promising method, the use case points method, which is inspired by function points analysis. Four companies developed equivalent functionality, but their development processes varied, ranging from a light, code-and-fix process with limited emphasis on code quality, to a heavy process with considerable emphasis on analysis, design and code quality. Our effort estimate, which was based on the use case points method, was close to the actual effort of the company with the lightest development process; the estimate was 413 hours while actual effort of the four companies ranged from 431 to 943 hours. These results show, that the use case points method needs modification to better handle effort related to the development process and the quality of the code.
%@ 0-7803-9507-7
@inproceedings{anda_multiple-case_2005,
abstract = {Through industry collaboration we have experienced an increasing interest in software effort estimation based on use cases. We therefore investigated one promising method, the use case points method, which is inspired by function points analysis. Four companies developed equivalent functionality, but their development processes varied, ranging from a light, code-and-fix process with limited emphasis on code quality, to a heavy process with considerable emphasis on analysis, design and code quality. Our effort estimate, which was based on the use case points method, was close to the actual effort of the company with the lightest development process; the estimate was 413 hours while actual effort of the four companies ranged from 431 to 943 hours. These results show, that the use case points method needs modification to better handle effort related to the development process and the quality of the code.},
added-at = {2013-02-28T11:13:35.000+0100},
author = {Anda, B. and Benestad, H. C and Hove, S. E},
biburl = {https://www.bibsonomy.org/bibtex/230b3edf28ea3ba86f7a55db97015426f/fritzsolms},
booktitle = {{2005 International Symposium on Empirical Software Engineering, 2005}},
doi = {10.1109/ISESE.2005.1541849},
interhash = {970a4126b129146841a51807f0dc1608},
intrahash = {30b3edf28ea3ba86f7a55db97015426f},
isbn = {0-7803-9507-7},
keywords = {Case Collaborative Computer Environmental Laboratories; Programming; Project Qualifications; Size Software Use aided analysis; computer cost development effort engineering; estimation; factors; function industry; management; measurement; point points software software;},
lccn = {0024},
month = nov,
publisher = {{IEEE}},
timestamp = {2013-02-28T11:13:39.000+0100},
title = {{A multiple-case study of software effort estimation based on use case points}},
year = 2005
}