Recommendation and decision technologies for requirements engineering
Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering
Assisting engineers in switching artifacts by using task semantic and interaction history
Proceedings of the 2nd International Workshop on Recommendation Systems for Software Engineering
Which traceability visualization is suitable in this context? a comparative study
REFSQ'12 Proceedings of the 18th international conference on Requirements Engineering: foundation for software quality
How do professional developers comprehend software?
Proceedings of the 34th International Conference on Software Engineering
| Hi-index | 0.00 |
If software engineering tools are not "properly integrated", they can reduce engineers' productivity. Associating and retrieving information scattered across the tools become unsystematic and inefficient. Our work provides empirical evidence on what is a "poor" and a "proper" tool integration, focusing on practitioners' perspectives. We interviewed 62 engineers and analyzed the content of their project artifacts. We identified problem situations and practices related to tool integration. Engineers agreed that tool integration approaches must support change, heterogeneity and automatic linking of change to context. To quantify our results, we conducted a field experiment with 27 and a survey with 782 subjects. We found a strong correlation between change frequency and preferred integration approaches. Particularly in projects with short release cycles, tasks should be used to link information handled by different tools. We also found that half of engineers' work is not defined as tasks. Therefore, a context-based tool integration approach is more effective than a task-based one.