The Community for Technology Leaders
RSS Icon
Subscribe
Issue No.04 - July/August (2011 vol.28)
pp: 64-73
Nuno Jardim Nunes , University of Madeira
Larry Constantine , University of Madeira
Rick Kazman , University of Hawaii
ABSTRACT
A proposed approach adapts use-case point (UCP) estimation to agile development of interactive software. To create product cost estimates early during development, developers must agree on the concepts driving the estimations and rely on substantial data from past projects, along with constant feedback and fine-tuning. To enhance the estimations' consistency, interactive UCP (iUCP) uses information extracted according to the concepts of usage-centered design (usageCD). It assigns complexity factors to actors and use cases and uses those factors to calculate unadjusted UCPs reflecting the requirements' complexity. The main basis for weighting complex actors is the user roles. The bases for weighting use cases are essential use-case steps portrayed as user intentions and system responsibilities along with analysis classes extracted from the usageCD architecture. An empirical study shows that estimations based on iUCP are more consistent than those based on the UCP method.
INDEX TERMS
design tools and techniques. distribution; maintenance; enhancement. usability testing
CITATION
Nuno Jardim Nunes, Larry Constantine, Rick Kazman, "iUCP: Estimating Interactive-Software Project Size with Enhanced Use-Case Points", IEEE Software, vol.28, no. 4, pp. 64-73, July/August 2011, doi:10.1109/MS.2010.111
REFERENCES
1. A. Seffah and E. Metzker, "The Obstacles and Myths of Usability and Software Engineering," Comm. ACM, vol. 47, no. 12, 2004, pp. 71–76.
2. L. Constantine, "Beyond User-Centered Design and User Experience," Cutter IT J., vol. 17, no. 2, 2004.
3. A.J. Albrecht, "Measuring Application Development Productivity," Proc. Joint Share, Guide, and IBM Application Development Symp., IBM, 1979, pp. 83–92.
4. B.W. Boehm et al., Software Cost Estimation with COCOMO II, Prentice-Hall, 2000.
5. G. Karner, "Resource Estimation for Objectory Projects," Rational Software, 1993.
6. S. Diev, "Use Cases Modeling and Software Estimation: Applying Use Case Points," ACM Software Eng. Notes, vol. 31, no. 6, 2006, pp. 1–4.
7. E.R. Carroll, "Estimating Software Based on Use Case Points," Proc. 2005 Conf. Object-Oriented Programming, Systems, Languages, and Applications (OOPSLA 05), ACM Press, 2005, pp. 257–265.
8. LL. Constantine and L.A.D. Lockwood, Software for Use: A Practical Guide to the Models and Methods of Usage-Centered Design, Addison-Wesley Longman, 1999.
9. N.J. Nunes and J.F. Cunha, "A Software Engineering Method for Small Software Development Companies," IEEE Software, vol. 17, no. 5, 2000, pp. 113–119.
10. N.J. Nunes and J.F. Cunha, "Wisdom—Whitewater Interactive System Development with Object Models," Object-Oriented User Interface Design, M. van Harmelen, ed., Addison-Wesley, 2001, pp. 197–243.
11. L. Constantine and L. Lockwood, "Structure and Style in Use Cases for User Interface Design," Object-Oriented User Interface Design, M. van Harmelen, ed., Addison-Wesley, 2001, pp. 245–279.
12. N. Nunes, "What Drives Software Development: Bridging the Gap between Software and Usability Engineering," Human-Centered Software Engineering, Springer, 2009, pp. 9–25.
17 ms
(Ver 2.0)

Marketing Automation Platform Marketing Automation Tool