Linking e-mails and source code artifacts
Proceedings of the 32nd ACM/IEEE International Conference on Software Engineering - Volume 1
Towards integrating e-mail communication in the IDE
Proceedings of 2010 ICSE Workshop on Search-driven Development: Users, Infrastructure, Tools and Evaluation
Impact analysis by means of unstructured knowledge in the context of bug repositories
Proceedings of the 2010 ACM-IEEE International Symposium on Empirical Software Engineering and Measurement
Recovering inter-project dependencies in software ecosystems
Proceedings of the IEEE/ACM international conference on Automated software engineering
Miler: a toolset for exploring email data
Proceedings of the 33rd International Conference on Software Engineering
ReLink: recovering links between bugs and changes
Proceedings of the 19th ACM SIGSOFT symposium and the 13th European conference on Foundations of software engineering
Are popular classes more defect prone?
FASE'10 Proceedings of the 13th international conference on Fundamental Approaches to Software Engineering
Improving automated documentation to code traceability by combining retrieval techniques
ASE '11 Proceedings of the 2011 26th IEEE/ACM International Conference on Automated Software Engineering
An empirical study on identifying core developers using network analysis
Proceedings of the 2nd international workshop on Evidential assessment of software technologies
Concept location using formal concept analysis and information retrieval
ACM Transactions on Software Engineering and Methodology (TOSEM)
Multi-layered approach for recovering links between bug reports and fixes
Proceedings of the ACM SIGSOFT 20th International Symposium on the Foundations of Software Engineering
| Hi-index | 0.00 |
During the evolution of a software system, a large amount of information, which is not always directly related to the source code, is produced. Several researchers have provided evidence that the contents of mailing lists represent a valuable source of information: Through e-mails, developers discuss design decisions, ideas, known problems and bugs, etc. which are otherwise not to be found in the system.A technical challenge in this context is how to establish the missing link between free-form e-mails and the system artifacts they refer to. Although the range of approaches is vast, establishing their accuracy remains a problem, as there is no benchmark against which to compare their performance.To overcome this issue, we manually inspected a statistically significant number of e-mails pertaining to the ArgoUML system. Based on this benchmark, we present a variety of lightweight techniques to assign e-mails to software artifacts and measure their effectiveness in terms of precision and recall.