Understanding interaction differences between newcomer and expert programmers
Proceedings of the 2008 international workshop on Recommendation systems for software engineering
Using Developer Activity Data to Enhance Awareness during Collaborative Software Development
Computer Supported Cooperative Work
Assisting engineers in switching artifacts by using task semantic and interaction history
Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering
Resumption strategies for interrupted programming tasks
Software Quality Control
Exploring a Bayesian and linear approach to requirements traceability
Information and Software Technology
| Hi-index | 0.01 |
Research on maintenance task structure modeling has so far examined only how often program artifacts are modified, and what information can be deduced from modification records. However, developers often access artifacts that they do not change, and this information is not modeled or recorded by current research systems. In this paper, we describe an exploratory industrial case study that we have conducted to investigate this issue; we found that within a given maintenance task, the software artifacts that are viewed but not changed out- number the changed artifacts over 70% of the time. We further found that including information about which artifacts were changed and which were only viewed was key to a mature understanding of the tasks that the developers were performing. Finally, we discuss how creating a repository that captures both the viewed-only and modified artifact accesses can yield further insights into the development process, such as how developers handle interruptions and task switching in their work- °ow.