A Framework for Comparing Requirements Tracing Experiments
暂无分享,去创建一个
[1] Mark Neal,et al. Why and how of requirements tracing , 1994, IEEE Software.
[2] Fabio Crestani,et al. “Is this document relevant?…probably”: a survey of probabilistic models in information retrieval , 1998, CSUR.
[3] Giuliano Antoniol,et al. Recovering Traceability Links between Code and Documentation , 2002, IEEE Trans. Software Eng..
[4] T. Landauer,et al. Indexing by Latent Semantic Analysis , 1990 .
[5] Giuliano Antoniol,et al. Design‐code traceability for object‐oriented systems , 2000, Ann. Softw. Eng..
[6] Balasubramaniam Ramesh,et al. Factors influencing requirements traceability practice , 1998, CACM.
[7] Andrea Zisman,et al. Rule-based generation of requirements traceability relations , 2004, J. Syst. Softw..
[8] Stephen E. Robertson. The probabilistic character of relevance , 1977, Inf. Process. Manag..
[9] Christopher M. Lott,et al. Repeatable software engineering experiments for comparing defect-detection techniques , 2004, Empirical Software Engineering.
[10] Victor R. Basili,et al. The TAME Project: Towards Improvement-Oriented Software Environments , 1988, IEEE Trans. Software Eng..
[11] Olly Gotel,et al. Extended requirements traceability: results of an industrial case study , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.
[12] Victor R. Basili,et al. Experimentation in software engineering , 1986, IEEE Transactions on Software Engineering.