On the importance of understanding the strategies that developers use

Proceedings - International Conference on Software Engineering

Volumn , Issue , 2010, Pages 72-75

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

^a Carnegie Mellon University ^*  (United States)

Author keywords

developer questions; program comprehension; strategies

Indexed keywords

DEVELOPER QUESTIONS; EVALUATION STUDY; PROGRAM COMPREHENSION; PROGRAMMER PRODUCTIVITY; RESEARCH OPPORTUNITIES; STRATEGIES;

COMPUTER PROGRAMMING; SOFTWARE ENGINEERING;

TECHNICAL PRESENTATIONS;

EID: 77955801124     PISSN: 02705257     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1145/1833310.1833322     Document Type: Conference Paper

References (18)

1. Beck, K. (2002). Test-Driven Development. New York: Addison-Wesley.
2. Chase, W. G. & Simon, H. A. (1973). Perception in chess. In Cognitive Psychology.
3. Clarke, S. (2004). Measuring API Usability. In Dr. Dobbs Journal, S6-S9.
4. Détienne, F. (1990). Program understanding and knowledge organization: the influence of acquired schemata. In Cognitive Ergonomics: Understanding, Learning and Designing Human- Computer Interaction, 245-256.
5. Evans, E. (2003). Domain driven design. New York: Addison-Wesley.
6. Hanenberg, S. (2009). What is the impact of static type systems on programming time? In Proc. PLATEAU Workshop at OOPSLA.
7. Hannay, J. E., Sjberg, D.I.K., andDybå, T. (2007). A systematic review of theory use in software engineering experiments. In Transactions on Software Engineering (TSE), 33(2), 87-107. (Pubitemid 46223696)
8. Ko. A. J., Myers, B.A., Coblenz, M. & Aung, H. H. (2006). An exploratory study of how developers seek, relate, and collect relevant information during software maintenance tasks. In Transactions on Software Engineering (TSE), 32(12).
9. Ko., A. J., DeLine, R. & Venolia, G.. (2007). Information needs in collocated software development teams. In Proc. Int'l Conf. Software Eng (ICSE).
10. LaToza, T.D., & Myers, B.A. (2010). Developers ask reach-ability questions. In Proc. Int'l Conf. Software Eng (ICSE).
11. LaToza, T.D., & Myers, B.A. Searching across paths. In Proc. of the Workshop on Search-Driven Development: Users, Infrastructure, Tools, and Evaluation, ICSE.
12. LaToza, T.D., Garlan, D., Herbsleb, J.D., & Myers, B.A. (2007). Program comprehension as fact finding. In Proc. ESEC/FSE.
13. LaToza, T.D., Venolia, G., andDeLine, R. (2006). Maintaining mental models: a study of developer work habits. In Proc. Int'l Conf. Software Eng (ICSE).
14. Llopis, N. (20 February 2005). Stepping through the looking glass: test-driven game development (part 1). In Games from Within. Accessed 1/27/2010. Available at http://gamesfromwithin.com/stepping-through-the-looking-glass- test-driven-game-development-part-1.
15. Luff, M. (2009). Empirically investigating parallel programming paradigms: a null result. In Proc. PLATEAU Workshop at OOPSLA.
16. Sillito, J., Murphy, G.C., & De Volder, K. (2008). Asking and answering questions during a programming change task. In Transactions on Software Engineering (TSE), 34(4).
17. Stylos, J., & Clarke, S. (2007). Usability implications of requiring parameters in objects' constructors. In Proc. Int'l Conf. Software Eng (ICSE).
18. Vans, A.M., von Mayrhauser, A., & Somlo, G. (1999). Program understanding behavior during corrective maintenance of large-scale software. In Int'l J. Human-Computer Studies, 51(1), 31-70.