Developers ask reachability questions

Proceedings - International Conference on Software Engineering

Volumn 1, Issue , 2010, Pages 185-194

  LaToza, Thomas D ^a   Myers, Brad A ^a  

^a Carnegie Mellon University ^*  (United States)

Author keywords

code navigation; developer questions; empirical study; program comprehension; software maintenance

Indexed keywords

CODE NAVIGATION; EMPIRICAL STUDIES; PROFESSIONAL SOFTWARE; PROGRAM COMPREHENSION; REACHABILITY; SEARCH CRITERION; SOFTWARE MAINTENANCE;

COMPUTER PROGRAMMING; COMPUTER SOFTWARE; NAVIGATION;

COMPUTER SOFTWARE MAINTENANCE;

EID: 77954690771     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1806799.1806829     Document Type: Conference Paper

References (22)

1. Bennett, C., Myers, D., Storey, M., German, D. M., Ouellet, D., Salois, M., and Charland, P. (2008). A survey and evaluation of tool features for understanding reverse-engineered sequence diagrams. J. Softw. Maint. Evol., 20 (4), 291-315.
2. Cherubini, M., Venolia, G., and DeLine, R. (2007). Building an Ecologically valid, Large-scale Diagram to Help Developers Stay Oriented in Their Code. In Symposium on Visual Languages and Human-Centric Computing (VL/HCC).
3. Détienne, F. (2002). Software Design - Cognitive Aspects. Springer-Verlag.
4. Dzidek, W. J., Arisholm, E. and Briand, L.C. (2008). A Realistic Empirical Evaluation of the Costs and Benefits of UML in Software Maintenance. In TSE, 34 (3).
5. Edwards, J. (2009). Coherent reaction. In Proc. of Onward! at the Conference on Object Oriented Programming, Systems, Languages, and Applications (OOPSLA), 925-932.
6. Fritz, T., Murphy, G. C., and Hill, E. (2007). Does a programmer's activity indicate knowledge of code? In ESEC/FSE.
7. Harman, M. and Hierons, R. (2001). An overview of program slicing. In Software Focus, 2(3), 85-92.
8. Hill, E., Pollock, L., and Vijay-Shanker, A.K. (2007). Exploring the neighborhood with Dora to expedite software maintenance. In Proc. of Automated Software Engineering (ASE).
9. Ko, A. J., Aung, H., and Myers, B. A. (2005). Eliciting design requirements for maintenance-oriented IDEs: a detailed study of corrective and perfective maintenance tasks. In Proc. Int'l Conf. Software Eng (ICSE), 126-135. (Pubitemid 43283587)
10. Ko., A.J., DeLine, R., and Venolia, G. (2007). Information Needs in Collocated Software Development Teams. In Proc. Int'l Conf. Software Eng (ICSE).
11. Ko, A., Myers, B., Coblenz, M., and Aung, H. An exploratory study of how developers seek, relate, and collect relevant information during software maintenance tasks. In IEEE Trans. Soft. Eng. 32, 12 (2006), 971-987. (Pubitemid 46437704)
12. LaToza, T.D., Garlan, D., Herbsleb, J., and Myers, B.A. Program Comprehension as Fact Finding. In European Software Engineering Conference and Foundations of Software Engineering (ESEC/FSE), 2007.
13. LaToza, T.D., Venolia, G., and DeLine, R. (2006). Maintaining Mental Models: A Study of Developer Work Habits. In Proc. Int'l Conf. Software Eng (ICSE), 492-501. (Pubitemid 46600946)
14. Lawrance, J., Bellamy, R., Burnett, M. and Rector, K. (2008). Using Information Scent to Model the Dynamic Foraging Behavior of Programmers in Maintenance Tasks. In Proc. of CHI, 1323-1332.
15. Parent, S. (2006). A possible future for software development. Keynote talk at the Workshop of Library-Centric Software Design, OOPSLA.
16. Pennington, N. (1987). Stimulus Structures and Mental Representations in Expert Comprehension of Computer Programs. In Cognitive Psychology, Vol. 19, 295-341.
17. Sillito, J., Murphy, G.C., and De Volder, K. (2008). Asking and answering questions during a programming change task. TSE, 34(4).
18. Singer, J., Lethbridge, T., Vinson, N., Anquetil, N. (1997). An examination of software engineering work practices. In Proc. CASCON, 209-223.
19. Sridharan, M., Fink, S. J., and Bodik, R. (2007). Thin slicing. In Programming Language Design and Implementation (PLDI).
20. Tip, F. (1995). A survey of program slicing techniques. In Journal of Programming Languages, 3, 121-189.
21. Weiser, M. (1982). Programmers use slices when debugging. In Communications of the ACM (CACM), 25(7), 446-452.
22. Weiser, M. (1984). Program Slicing. In Transactions on Software Engineering (TSE), 10 (4).