ACM Home Page
Please provide us with feedback. Feedback
Digital Library logoTake a look at the new version of this page: [ beta version ]. Tell us what you think.
Estimating software based on use case points
Full text MovMov (29:53),  PdfPdf (268 KB)
Source Conference on Object Oriented Programming Systems Languages and Applications archive
Companion to the 20th annual ACM SIGPLAN conference on Object-oriented programming, systems, languages, and applications table of contents
San Diego, CA, USA
SESSION: Practitioner reports table of contents
Pages: 257 - 265  
Year of Publication: 2005
ISBN:1-59593-193-7
Author
Edward R. Carroll  Agilis Solutions, Beaverton, OR
Sponsors
ACM: Association for Computing Machinery
SIGPLAN: ACM Special Interest Group on Programming Languages
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 16,   Downloads (12 Months): 220,   Citation Count: 1
Additional Information:

abstract   references   cited by   index terms   reviews  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1094855.1094960
What is a DOI?

Warning: The download time has expired please click on the item to try again.


ABSTRACT

It is well documented that software product cost estimates are notoriously inaccurate across the software industry. Creating accurate cost estimates for software product development projects early in the product development lifecycle has always been a challenge for the industry. This article describes how a large multi-team software engineering organization (over 450 engineers) estimates project cost accurately and early in the software development lifecycle using Use Case Points, and the process of evaluating metrics to ensure the accuracy of the model.The engineering teams of Agilis Solutions in partnership with FPT Software, provide our customers with accurate estimates for software product projects early in the product lifecycle. The bases for these estimates are initial definitions of Use Cases, given point factors and modified for technical and environmental factors according to the Use Case Point method defined within the Rational Unified Process. After applying the process across hundreds of sizable (60 man-months average) software projects, we have demonstrated metrics that prove an estimating accuracy of less than 9% deviation from actual to estimated cost on 95% of our projects. Our process and this success factor is documented over a period of five years, and across more than 200 projects.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
 
2
 
3
 
4
 
5
Paulk, M., Curtis, W., Chrissis, M., Weber, C., Capability Maturity Model for Software, Version 1.1, Software Engineering Institute, CMU/SEI-93-TR-24, DTIC Number ADA263403, February 1993.



REVIEWS

"Barrett Hazeltine : Reviewer"

There are two parts to this paper: an example estimating the total man-hours to complete a software development project, and an explanation of using a causal analysis process to drive improvements in the estimating model and the process itself. Th  more...


"James M. Perry : Reviewer"

Accurate estimation is hard to do. This work is a short study of software estimation and analysis, reporting impressive results¿less than nine percent deviation from actual results for 200 projects over five years.

Although the title states   more...