@barik @lionel_c_briand @maalejw 2/2 A more elaborate study on the state of reported evidence in a slightly more established but still “fuzzy” area is one by Borg et al. [2]. Note the extensive related work analysis as a foundation for the actual study. [
Mirakhorli gives overview of datasets in traceability research. We had related results in our map (pic 3-4): https://t.co/xZjBlREdWr #re2017 https://t.co/ISrFWRfYrV
Interested in information retrieval for software traceability? Get an overview in new EMSE paper http://t.co/gLtYh4F8vy #springerlink
Interested in information retrieval for software traceability? Get an overview in new EMSE paper http://t.co/gLtYh4F8vy #springerlink
@GregerWikstrand "identified lack of traceability to be a major contributing factor in project overruns and failures" http://t.co/6q3l6aEuBZ
If you want to look back the last decade of traceability, see a systematic mapping of research in http://t.co/XxT9tWMRaQ #icse14
If you want to look back the last decade of traceability, see a systematic mapping of research in http://t.co/XxT9tWMRaQ #icse14
Markus Borg et al summarized a decade of research on traceability using information retrieval methods http://t.co/6q3l6aEuBZ @ieeesoftware
Markus Borg et al summarized a decade of research on traceability using information retrieval methods http://t.co/6q3l6aEuBZ @ieeesoftware
Borg Runeson Ardö, Recovering from a decade: a systematic mapping of IR approaches to SW traceability, EMSE online http://t.co/sZmqEhtIfb