ACM Home Page
Please provide us with feedback. Feedback
Using task context to improve programmer productivity
Full text PdfPdf (512 KB)
Source Foundations of Software Engineering archive
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering table of contents
Portland, Oregon, USA
SESSION: Empirical methods and program understanding table of contents
Pages: 1 - 11  
Year of Publication: 2006
ISBN:1-59593-468-5
Authors
Mik Kersten  University of British Columbia, Vancouver, Canada
Gail C. Murphy  University of British Columbia, Vancouver, Canada
Sponsors
SIGSOFT: ACM Special Interest Group on Software Engineering
ACM: Association for Computing Machinery
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 19,   Downloads (12 Months): 193,   Citation Count: 22
Additional Information:

abstract   references   cited by   index terms   collaborative colleagues  

Tools and Actions: Request Permissions Request Permissions    Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1181775.1181777
What is a DOI?

ABSTRACT

When working on a large software system, a programmer typically spends an inordinate amount of time sifting through thousands of artifacts to find just the subset of information needed to complete an assigned task. All too often, before completing the task the programmer must switch to working on a different task. These task switches waste time as the programmer must repeatedly find and identify the information relevant to the task-at-hand. In this paper, we present a mechanism that captures, models, and persists the elements and relations relevant to a task. We show how our task context model reduces information overload and focuses a programmer's work by filtering and ranking the information presented by the development environment. A task context is created by monitoring a programmer's activity and extracting the structural relationships of program artifacts. Operations on task contexts integrate with development environment features, such as structure display, search, and change management. We have validated our approach with a longitudinal field study of Mylar, our implementation of task context for the Eclipse development environment. We report a statistically significant improvement in the productivity of 16 industry programmers who voluntarily used Mylar for their daily work.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Backus, J.W. Automatic programming: properties and performance of FORTRAN systems I and II. Proceedings of the Symposium on the Mechanisation of Thought Processes, The National Physical Laboratory, 1958.
2
 
3
Card, S. K. and D. Nation. Degree-of-Interest Trees: A Component of an Attention-Reactive User Interface. Advanced Visual Interfaces Conference, 2002.
 
4
5
6
7
8
9
 
10
Harrison, W., Ossher, H., Tarr, P., Kruskal, V. and Tip, F. CAT: A Toolkit for Assembling Concerns. Research Report RC22686, IBM, Yorktown Heights, NY, Dec. 2002.
11
12
13
14
 
15
Janzen, D. and de Volder, K. Programming With Crosscutting Effective Views, Proceedings of the European Conference on Object-Oriented Programming. p. 195--218, 2004.
16
17
 
18
Merriam-Webster's collegiate dictionary (11th ed.), Springfield, MA: Merriam-Webster. 2003.
 
19
 
20
Murphy, G., Kersten, M., Robillard, M. and Cubranic, D. The Emergent Structure of Development Tasks. Proceedings of the European Conference on Object-Oriented Programming. p. 33--48, 2005.
21
 
22
23
24
25
 
26
Teitelman, W. and Masinter, L. The Interlisp programming environment. IEEE Computer, vol. 14, 25--34, 1981.

CITED BY  22

Collaborative Colleagues:
Mik Kersten: colleagues
Gail C. Murphy: colleagues