This Article 
 Bibliographic References 
 Add to: 
An Empirical Study Using Task Assignment Patterns to Improve the Accuracy of Software Effort Estimation
March 2001 (vol. 27 no. 3)
pp. 264-271

Abstract—In most software development organizations, there is seldom a one-to-one mapping between software developers and development tasks. It is frequently necessary to concurrently assign individuals to multiple tasks and to assign more than one individual to work cooperatively on a single task. A principal goal in making such assignments should be to minimize the effort required to complete each task. But what impact does the manner in which developers are assigned to tasks have on the effort requirements? This paper identifies four task assignment factors: team size, concurrency, intensity, and fragmentation. These four factors are shown to improve the predictive ability of the well-known Intermediate COCOMO cost estimation model. A parsimonious effort estimation model is also derived that utilizes a subset of the task assignment factors and Unadjusted Function Points. For the data examined, this parsimonious model is shown to have goodness of fit and quality of estimation superior to that of the COCOMO model, while utilizing fewer cost factors.

[1] A. Abran and P. Robillard, “Function Point Analysis: An Empirical Study of Its Measurement Processes,” IEEE Trans. Software Eng., vol. 22, pp. 895-910, Dec. 1996.
[2] A. Albrecht, “Measuring Application Development,” Proc. Symp. IBM Applications Development Joint SHARE/GUIDE, pp. 83-92, 1979.
[3] V. Basili and R. Reiter, “An Investigation of Human Factors in Software Development,” Computer, vol. 12, no. 12, pp. 21-38, 1979.
[4] B. Boehm, Software Engineering Economics, Prentice Hall, Upper Saddle River, N.J., 1981, pp. 533-535.
[5] B. Boehm, B. Clark, E. Horowitz, C. Westland, R. Madachy, and R. Selby, “Cost Models for Future Software Life Cycle Processes: COCOMO 2.0,” Annals of Software Eng., vol. 1, pp. 57-94, 1987.
[6] F.P. Brooks, Jr., The Mythical Man-Month: Essays on Software Engineering, Addison Wesley Longman, Reading, Mass., 1975.
[7] J. Cougar and H. Adelsberger, "Comparing Motivation of Programmers and Analysts in Different Soci/Political Environments: Austria Compared to the United States," Computer Personnel, Vol. 11 No. 4, Apr. 1988, pp. 13-17.
[8] T. DeMarco and T. Lister, Peopleware—Productive Projects and Teams, Dorset House, New York, 1987, p. 30.
[9] S. Devani-Chulani, B. Clark, and B. Boehm, “Calibrating the COCOMO II Post-Architecture Model,” Proc. 22nd Ann. Software Eng. Workshop, Software Engineering Laboratory, pp. 249-268, 1997.
[10] J.B. Dreger, Function Point Analysis.Englewood Cliffs, N.J.: Prentice Hall, 1989.
[11] N. Fenton and L. Pfleeger, Software Metrics–A Rigorous and Practical Approach, second ed. Boston, PWS-Publishing, 1997.
[12] L. Fried, “Team Size and Productivity in Systems Development,” Information Systems Management, vol. 8, no. 3, pp. 27-41, 1991.
[13] R. Grable, J. Jernigan, C. Pogue, and D. Divis, “Metrics for Small Projects: Experiences at the SED,” Software, vol. 16, no. 2, pp. 21-29, 1999.
[14] P.J. Guinan, J.G. Cooprider, and S. Faraj, "Enabling Software Development Team Performance During Requirements Definition: A Behavioral Versus Technical Approach," Information Systems Research, vol. 9, no. 2, 1998, pp. 101-125.
[15] R. Gulezian, “Reformulating and Calibrating COCOMO,” J. Systems Software, vol. 16, pp. 235-242, 1991.
[16] R. Hiltz and M. Turoff, The Network Nation: Human Communication Through Computer. Addison-Wesley, 1978.
[17] Q. Hu, R. Plant, and D. Hertz, “Software Cost Estimation Using Economic Production Models,” J. Management Information Systems, vol. 15, no. 1, pp. 143-163, 1998.
[18] C. Jones, “Backfiring: Converting Lines of Code to Function Points,” Computer, vol. 28, no. 11, pp. 87-88, 1995.
[19] C. Kemerer, "An Empirical Validation of Software Cost Estimation Models," Comm. ACM, vol. 30, pp. 416-429, May 1987.
[20] R. Marouane and A. Mili, "Building Tailor-Made Software Cost Model: Intermediate TUCOMO," Information and Software Technology, vol. 33, no. 3, pp. 232-238, 1991.
[21] Y. Miyazaki and K. Mori, "COCOMO Evaluation and Tailoring," Proc. Eighth Int'l Software. Eng. Conf.London: IEEE CS Press, 1985.
[22] S. Murrel, “Computer Communication Systems Design Affects Group Decision Making,” Proc. CHI '83, pp. 63-67, 1983.
[23] S. Nash and S. Redwine, “People and Organizations in Software Production: A Review of the Literature,” Computer Personnel, vol. 11, no. 3, p. 1021, 1999.
[24] J. Navlakha, “Choosing a Software Cost Estimation Model for Your Organization: A Case Study,” Information and Software Technology, vol. 18, pp. 255-261, 1990.
[25] K. Pillai and S. Nair, "A Model for Software Development Effort and Cost Estimation," IEEE Trans. Software Eng., vol. 23, no. 8, pp. 485-497, 1997.
[26] L. Putnam, “TheImpact of Methodologies on Software Productivity: Case Studies,” Nat'l Conf. Workshop Methodologies and Tools for Real-Time Systems, 1985.
[27] K. Sengupta, T. Abdel-Hamid, and M. Bosley, “Coping with Staffing Delays in Software Project Management: An Experimental Investigation,” Trans. Systems, Man, and Cybernetics, vol. 29, no. 1, pp. 77-91, 1999.
[28] P. Stroh, “Team Building and Systems Development,” Datamation, vol. 27, no. 2, pp. 89-90, 1981.
[29] B. Unger and S. Walker, “Improving Team Productivity in System Software Development,” Proc. 15th Ann. Computer Personnel Research Conf., p. 113, 1977.

Index Terms:
Software effort estimation, COCOMO, project task assignment.
Randy K. Smith, Joanne E. Hale, Allen S. Parrish, "An Empirical Study Using Task Assignment Patterns to Improve the Accuracy of Software Effort Estimation," IEEE Transactions on Software Engineering, vol. 27, no. 3, pp. 264-271, March 2001, doi:10.1109/32.910861
Usage of this product signifies your acceptance of the Terms of Use.