Eliciting design requirements for maintenance-oriented IDEs: a detailed study of corrective and perfective maintenance tasks

ABSTRACT

Recently, several innovative tools have found their way into mainstream use in modern development environments. However, most of these tools have focused on creating and modifying code, despite evidence that most of programmers' time is spent understanding code as part of maintenance tasks. If new tools were designed to directly support these maintenance tasks, what types would be most helpful? To find out, a study of expert Java programmers using Eclipse was performed. The study suggests that maintenance work consists of three activities: (1) forming a working set of task-relevant code fragments; (2) navigating the dependencies within this working set; and (3) repairing or creating the necessary code. The study identified several trends in these activities, as well as many opportunities for new tools that could save programmers up to 35% of the time they currently spend on maintenance tasks.

REFERENCES

• 1: G. Antoniol , R. Fiutem , L. Cristoforetti, Design Pattern Recovery in Object-Oriented Software, Proceedings of the 6th International Workshop on Program Comprehension, p.153, June 24-26, 1998
• 2: Dirk Beyer , Andreas Noack , Claus Lewerentz, Simple and Efficient Relational Querying of Software Structures, Proceedings of the 10th Working Conference on Reverse Engineering, p.216, November 13-17, 2003
• 3: Boehm-Davis, D. A., Fox, J. E., and Philips, B. H., Techniques for Exploring Program Comprehension, Empirical Studies of Programmers, Washington D.C., 3--37, 1996.
• 4: Frederick P. Brooks, Jr., The mythical man-month (anniversary ed.), Addison-Wesley Longman Publishing Co., Inc., Boston, MA, 1995
• 5: Cynthia L. Corritore , Susan Wiedenbeck, An exploratory study of program comprehension strategies of procedural and object-oriented programmers, International Journal of Human-Computer Studies, v.54 n.1, p.1-23, Jan. 2001 [doi>10.1006/ijhc.2000.0423]
• 6: Crosby, M. E., Scholtz, J., and Widenbeck, S., The Roles Beacons Play in Comprehension for Novice and Expert Programmers, 14th Workshop of the Psychology of Programming Interest Group, Brunel University, 58--73, 2002.
• 7: Simon P. Davies, Models and theories of programming strategy, International Journal of Man-Machine Studies, v.39 n.2, p.237-267, Aug. 1993 [doi>10.1006/imms.1993.1061]
• 8: Len Erlikh, Leveraging Legacy System Dollars for E-Business, IT Professional, v.2 n.3, p.17-23, May 2000 [doi>10.1109/6294.846201]
• 9: Christopher Fry, Programming on an already full brain, Communications of the ACM, v.40 n.4, p.55-64, April 1997 [doi>10.1145/248448.248459]
• 10: Victor M. González , Gloria Mark, "Constant, constant, multi-tasking craziness": managing multiple working spheres, Proceedings of the SIGCHI conference on Human factors in computing systems, p.113-120, April 24-29, 2004, Vienna, Austria [doi>10.1145/985692.985707]
• 11: Green, T. R. G., Petre, M., and Bellamy, R. K. E., Comprehensibility of Visual and Textual Programs: A Test of Superlativism against the 'Match-Mismatch' Conjecture, Empirical Studies of Programmers, 4th Workshop, 121--146, 1991.
• 12: Ko, A. J. and Myers, B. A., A Framework and Methodology for Studying the Causes of Software Errors in Programming Systems, To appear in the Journal of Visual Languages and Computing, 2004.
• 13: Andrew J. Ko , Brad A. Myers, Designing the whyline: a debugging interface for asking questions about program behavior, Proceedings of the SIGCHI conference on Human factors in computing systems, p.151-158, April 24-29, 2004, Vienna, Austria [doi>10.1145/985692.985712]
• 14: Müller, H. A., Orgun, M. A., Tilley, S. R., and Uhl, J. S., A Reverse Engineering Approach to Subsystem Structure Identification, Journal of Software Maintenance: Research and Practice, 5, 4, 181--204, 1993.
• 15: Perlow, L., The Time Famine: Toward a Sociology of Work Time, Administrative Science Quarterly, 44, 57--81, 1999.
• 16: Mary Beth Rosson , John M. Carroll, The reuse of uses in Smalltalk programming, ACM Transactions on Computer-Human Interaction (TOCHI), v.3 n.3, p.219-253, Sept. 1996 [doi>10.1145/234526.234530]
• 17: Barbee E. Teasley, The effects of naming style and expertise on program comprehension, International Journal of Human-Computer Studies, v.40 n.5, p.757-770, May 1994 [doi>10.1006/ijhc.1994.1036]
• 18: Xiangyu Zhang , Rajiv Gupta , Youtao Zhang, Precise dynamic slicing algorithms, Proceedings of the 25th International Conference on Software Engineering, May 03-10, 2003, Portland, Oregon

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.6 Programming Environments
          Subjects: Integrated environments

Additional Classification:
  H. Information Systems
  H.5 INFORMATION INTERFACES AND PRESENTATION (I.7)
      H.5.2 User Interfaces (D.2.2, H.1.2, I.3.6)

Keywords:
development environment framework, examples, recommender, software structure