Expertise recommender: a flexible recommendation system and architecture
CSCW '00 Proceedings of the 2000 ACM conference on Computer supported cooperative work
Two case studies of open source software development: Apache and Mozilla
ACM Transactions on Software Engineering and Methodology (TOSEM)
Expertise browser: a quantitative approach to identifying expertise
Proceedings of the 24th International Conference on Software Engineering
Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Workspace Awareness in Real-Time Distributed Groupware: Framework, Widgets, and Evaluation
HCI '96 Proceedings of HCI on People and Computers XI
Tutorial on maximum likelihood estimation
Journal of Mathematical Psychology
ICSE '76 Proceedings of the 2nd international conference on Software engineering
Traceability Recovery by Modeling Programmer Behavior
WCRE '00 Proceedings of the Seventh Working Conference on Reverse Engineering (WCRE'00)
Traceability Recovery in RAD Software Systems
IWPC '02 Proceedings of the 10th International Workshop on Program Comprehension
CVS Release History Data for Detecting Logical Couplings
IWPSE '03 Proceedings of the 6th International Workshop on Principles of Software Evolution
Group awareness in distributed software development
CSCW '04 Proceedings of the 2004 ACM conference on Computer supported cooperative work
Proceedings of the 28th international conference on Software engineering
An empirical study of fine-grained software modifications
Empirical Software Engineering
An Industrial Case Study of Program Artifacts Viewed During Maintenance Tasks
WCRE '06 Proceedings of the 13th Working Conference on Reverse Engineering
Experiences from introducing UML-based development in a large safety-critical project
Empirical Software Engineering
MSR '07 Proceedings of the Fourth International Workshop on Mining Software Repositories
Recovering and using use-case-diagram-to-source-code traceability links
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
Does a programmer's activity indicate knowledge of code?
Proceedings of the the 6th joint meeting of the European software engineering conference and the ACM SIGSOFT symposium on The foundations of software engineering
A 3-Dimensional Relevance Model for Collaborative Software Engineering Spaces
ICGSE '07 Proceedings of the International Conference on Global Software Engineering
Focusing knowledge work with task context
Focusing knowledge work with task context
Automated traceability analysis for UML model refinements
Information and Software Technology
Assessing IR-based traceability recovery tools through controlled experiments
Empirical Software Engineering
Introduction to Bayesian Statistics
Introduction to Bayesian Statistics
Exploiting causal independence in Bayesian network inference
Journal of Artificial Intelligence Research
Enabling Automated Traceability Maintenance by Recognizing Development Activities Applied to Models
ASE '08 Proceedings of the 2008 23rd IEEE/ACM International Conference on Automated Software Engineering
Hi-index | 0.00 |
Context: For large software projects it is important to have some traceability between artefacts from different phases (e.g.requirements, designs, code), and between artefacts and the involved developers. However, if the capturing of traceability information during the project is felt as laborious to developers, they will often be sloppy in registering the relevant traceability links so that the information is incomplete. This makes automated tool-based collection of traceability links a tempting alternative, but this has the opposite challenge of generating too many potential trace relationships, not all of which are equally relevant. Objective: This paper evaluates how to rank such auto-generated trace relationships. Method: We present two approaches for such a ranking: a Bayesian technique and a linear inference technique. Both techniques depend on the interaction event trails left behind by collaborating developers while working within a development tool. Results: The outcome of a preliminary study suggest the advantage of the linear approach, we also explore the challenges and potentials of the two techniques. Conclusion: The advantage of the two techniques is that they can be used to provide traceability insights that are contextual and would have been much more difficult to capture manually. We also present some key lessons learnt during this research.