Analogy based prediction of work item flow in software projects: A case study

Proceedings - 2003 International Symposium on Empirical Software Engineering, ISESE 2003

Volumn , Issue , 2003, Pages 110-119

  Mockus, A ^a  

^a AVAYA LABS RESEARCH   (United States)

Author keywords

Computer aided software engineering; Customer relationship management; Data mining; History; Predictive models; Programming; Project management; Resource management; Software testing; Spatial databases

Indexed keywords

COMPUTER PROGRAMMING; COMPUTER RESOURCE MANAGEMENT; DATA MINING; FORECASTING; HISTORY; INFORMATION MANAGEMENT; MANAGEMENT SCIENCE; MATHEMATICAL PROGRAMMING; PROFESSIONAL ASPECTS; PROJECT MANAGEMENT; PUBLIC RELATIONS; SALES; SOFTWARE DESIGN; SOFTWARE ENGINEERING; SOFTWARE TESTING;

CONFIGURATION MANAGEMENT DATABASE; CUSTOMER RELATIONSHIP MANAGEMENT; PREDICTIVE MODELS; RESOURCE MANAGEMENT; SOFTWARE DEVELOPMENT PROJECTS; SOFTWARE PROJECT PLANNING; SPATIAL DATABASE; WORKFLOW MODELING;

COMPUTER AIDED SOFTWARE ENGINEERING;

EID: 36348963606     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ISESE.2003.1237970     Document Type: Conference Paper

References (19)

1. D. Atkins, T. Ball, T. Graves, and A. Mockus. Using version control data to evaluate the impact of software tools: A case study of the version editor. IEEE Transactions on Software Engineering, 28(7):625-637, July 2002.
2. B. Boehm. Software Engineering Economics. Prentice-Hall, 1981.
3. B. W. Boehm, B. Clark, E. Horowitz, and et al. Cost models for future software life cycle processes: Cocomo 2.0. Annals of Software Engineering, 1(1):1-24, November 1995.
4. P. Cedeqvist and et al. CVS Manual. May be fond on: http://www.cvshome.org/CVS/.
5. S. R. Dalal and C. L. Mallows. When should one stop testing software? Journal of American Statist. Assoc, 83:872-879, 1988.
6. A. L. Goel. Software reliability models: Assumptions, limitations and applicability. IEEE Trans. Software Engineering, SE-11(12), 1985.
7. K. Huff, J. Sroka, and D. Struble. Quantitative models for managing software development processes. Software Engineering Journal, 1(1):17-24, 1986.
8. M. Jørgensen. A review of studies on expert estimation of software development effort. Journal of Systems and Software, 2002. submitted.
9. A. Lefteris and I. Stamelos. A simulation tool for efficient analogy based cost estimation. Empirical Software Engineering, 5(1):35-68, 2000.
10. A. K. Midha. Software configuration management for the 21st century. Bell Labs Technical Journal, 2(1), Winter 1997.
11. A. Mockus and L. G. Votta. Identifying reasons for software change using historic databases. In International Conference on Software Maintenance, pages 120-130, San Jose, California, October 11-14 2000.
12. A. Mockus and D. M. Weiss. Predicting risk of software changes. Bell Labs Technical Journal, 5(2):169-180, April-June 2000.
13. A. Mockus and D. M. Weiss. Globalization by chunking: a quantitative approach. IEEE Software, 18(2):30-37, March 2001.
14. A. Mockus, D. M. Weiss, and P. Zhang. Understanding and predicting effort in software projects. In 2003 International Conference on Software Engineering, pages 274-284, Portland, Oregon, May 3-10 2003. ACM Press.
15. J. Musa, A. Iannino, and K. Okumoto. Software Reliability: Measurement, Prediction, Application. McGrawHill, New York, 1987.
16. T. Pearse, T. Freeman, and P. Oman. Using metrics to manage the end game of a software project. In Software Metrics Symposium, pages 207-215, 1999.
17. M. Rochkind. The source code control system. IEEE Trans. on Software Engineering, 1(4):364-370, 1975.
18. M. Shepperd, C. Schofield, and B. Kitchenham. Effort estimation using analogy. In 18th International Conference on Software Engineering, page 170, Berlin, GERMANY, March 25-29 1996.
19. F. Walkerden and R. Jeffery. An empirical study of analogy-based software effort estimation. Empirical Software Engineering, 4(2):135-158, 1999.