[CSUSB]>> [CNS]>> [CSE]>> [R J Botting]>> biba.php

Bibliographic Item (1.0)


  1. Andrew J Ko & Brad Myers & Micheal J Coblenz & Htet Htet Aung
  2. An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks
  3. ICSE'05 & IEEE Computer Magazine V39n12(Dec 2006)pp971-987
  5. Information_Foraging::=the BIBLIOGRAPHY(authors=>"P Pirolli &S K Card", title=>"Information Foraging", citation=>"Psychological Review V106n4 (1999)pp643-675").
  6. Took video records of developers modifying and correcting bugs in apaint program.
  7. Coded the actions into 9 types: Handling information(15%), reading code(12%), editing code, navigating dependencies, searching for names, testing, reading Java API, switching applications,reading task description(2%).
  8. Early perceptions of bugs can lead to wasted time exploring irrelevant code.
  9. Enhancements: developers had to search for a place to extend the existing framework and for examples to copy and modify.
  10. Developers used "Find" dialog, Eclipse's multiple windows, What is relevant? When interupted developers always complete there current editting task before acknowledging the interuption, but sometimes forgot to save the edited file!
  11. Three states: Search; Relate; Collect.
  12. Need better ways to search for relevant code. Good names are vital! Perhaps use hovering to show header info on methods fro example.
  13. Need less overhead in navigating and viewing code. EG highlight code to show dependencies of nearby code rather than menus.
  14. Show many fragments of code in separate subwindows?
  15. See [KoMyers10]

Search for bibliographic items containing a matching string.

(Search uses POSIX regular expressions and ignores case)

Search for a specific bibliographic item by name.

To see the complete bibliography (1Mb+) select:[Bibliography]