Exploring a Bayesian and linear approach to requirements traceability

Context<p></p> 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.<p></p> Objective<p></p> This paper evaluates how to rank such auto-generated trace relationships.<p></p> Method<p></p> We present two approaches for such a ranking: aBayesian technique and alinear inference technique. Both techniques depend on the interaction event trails left behind by collaborating developers while working within a development tool.<p></p> Results<p></p> The outcome of a preliminary study suggest the advantage of the linear approach, we also explore the challenges and potentials of the two techniques.<p></p> Conclusion<p></p> 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