Eliminating Exception Handling Errors with Dependability Cases: A Comparative, Empirical Study
IEEE Transactions on Software Engineering
Using Visual Momentum to Explain Disorientation in the Eclipse IDE
VLHCC '06 Proceedings of the Visual Languages and Human-Centric Computing
Using task context to improve programmer productivity
Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering
Notation and representation in collaborative object-oriented design: an observational study
Proceedings of the 22nd annual ACM SIGPLAN conference on Object-oriented programming systems and applications
Proceedings of the 30th international conference on Software engineering
Resumption strategies for interrupted programming tasks
Software Quality Control
| Hi-index | 0.00 |
about their activities and the resulting artifacts which helps them remain oriented, avoid omissions, and correctly use artifacts. When stored only in the developer's organic memory, this knowledge may degrade and cannot directly be shared with others. Its consistent externalization, however, is currently limited by production costs, indirect returns, and its limited saliency in contexts where it could be useful. In this work we propose a memory aid which strives to overcome these barriers, and reduce the resulting problems. Developers will provide short and raw subjective notes which will be associated with the code context but stored separately from it, allowing us to increase saliency via two novel presentations. The first, designed after human episodic memory, chronologically interleaves these subjective notes with an automatically-gathered record of the developer's objective activities. It virtually extends shorter-term memory, aiding with orientation and increasing the saliency of recent knowledge and reminders. The second, a contextual view, uses static dependencies and historical records to present notes which may be relevant to the developer's current context.