A framework for comparing requirements tracing experiments

International Journal of Software Engineering and Knowledge Engineering

Volumn 15, Issue 5, 2005, Pages 751-781

  Hayes, Jane Huffman ^a   Dekhtyar, Alex ^a  

^a UNIVERSITY OF KENTUCKY   (United States)

Author keywords

Case study; Experiment; Framework; Informar tion retrieval; IV V; Metrics; Requirements tracing; traceability

Indexed keywords

EXPERIMENTS; INFORMATION RETRIEVAL;

CASE STUDY; FRAMEWORK; IV&V; METRICS; REQUIREMENTS TRACING; TRACEABILITY;

REQUIREMENTS ENGINEERING;

EID: 27744500423     PISSN: 02181940     EISSN: None     Source Type: Journal    
DOI: 10.1142/S021819400500252X     Document Type: Article

References (41)

1. M. Abrahams and J. Barkley, Rtl verification strategies, in PIEEE WESCON/98, 1998.
2. D. Anezin, Process and methods for requirements tracing (software development life cycle), 1994.
3. G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, and E. Merlo, Recovering traceability links between code and documentation, IEEE Trans. on Software. Engineering 28(10) (2002) 970-983.
4. G. Antoniol, B. Caprile, A. Potrich, and P. Tonella, Design-code traceability for object oriented systems, Annals of Software Engineering 9 (1999) 35-58.
5. Algorithmic Solutions Software GmbH (AS), Leda research, http://www.mpisb.mpg.de/LEDA/leda.html.
6. R. Baeza-Yates and B. Ribeiro-Neto, Modern Information Retrieval, ACM Press, Addison-Wesley, 1999.
7. V. Basili, R. Selby, and D. Hutchens, Experimentation in software engineering, IEEE Trans. on Software Engineering 12(47) (1986) 733-743.
8. V. Basili, F. Shull, and F. Lanubile, Building knowledge through families of software studies: An experience report, IEEE Trans. on Software Engineering 25(4) (1999) 456-473.
9. V. R. Basili and H. D. Rombach, The tame project: Towards improvement-oriented software environments, IEEE Trans. on Software Engineering 14(6) (1988) 758-773.
10. S. Bohner, A graph traceability approach for software change impact analysis, 1995.
11. P. Bourque and A. Abran, An experimental framework for software engineering research, in Proc. Forum on Software Engineering Standards Issues, 1996.
12. P. Brouse, A process for use of multimedia information in requirements identification and traceability, 1992.
13. A. Casotto, Run-time requirement tracing, in Proc. IEEE/ACM Int. Conf. on Computer-aided Design, 1993.
14. J. Cleland-Huang, C. K. Chang, G. Sethi, K. Javvaji, H. Hu, and J. Xia, Automating speculative queries through event-based requirements traceability, in Proceedings of the IEEE Joint International Requirements Engineering Conference (RE '02), 2002, pp. 289-296.
15. F. Crestani, M. Lalmas, C. J. van Rijsbergen, and I. Campbell, Is this document relevant? ... probably: A survey of probabilistic models in information retrieval, ACM Computing Surveys 30(4) (1998) 528-552.
16. S. Deerwester, S. T. Dumais, T. K. Landauer, G. W. Furnas, and R. A. Harshman, Indexing by latent semantic analysis, J. Society for Information Science 41(6) (1990) 391-407.
17. N. Fenton, S. Pfleeger, and R. Glass, Requirements tracing, IEEE Software, July 1994.
18. O. Gotel and A. Finkelstein, Extended requirements traceability: Results of an industrial case study, in Proc. 3rd IEEE Int. Symposium on Requirements Engineering (RE'97), IEEE Computer Society, 1997, p. 169.
19. GSFC SBRS, Level la and geolocation processing software requirements specification.
20. GSFC SBRS, MODIS science data processing software requirements specification version 2.
21. J. Huffman Hayes, Risk reduction through requirements tracing, in Conf. Proc. of Software Quality Week 1990, 1990.
22. J. Huffman Hayes, Energizing software engineering education through real-world projects as experimental studies, in Proc. Conf. on Software Engineering Education and Training, CSEET, 2002.
23. J. Huffman Hayes, A. Dekhtyar, and J. Osborne, Improving requirements tracing via information retrieval, in Int. Conf. on Requirements Engineering, Monterey, California, 2003, pp. 151-161.
24. J. Huffman Hayes, A. Dekhtyar, S. Sundaram, and S. Howard, Helping analysts trace requirements: An objective look, in Int. Conf. on Requirements Engineering (RE'2004), 2004.
25. J. Hayes, A. Dekhtyar, and S. Sundaram, Measuring the effectiveness of retrieval techniques in software engineering, Technical Report TR 422-04, University of Kentucky, October 2004.
26. N. Juristo and A. Moreno, Basics of Software Engineering Experimentation, Kluwer Academic Publishers, 2001.
27. F. Lanubile, Empirical evaluation of software maintenance technologies, Empirical Software Engineering: An International Journal 2(2) (1997) 95-106.
28. C. M. Lott and H. D. Rombach, Repeatable software engineering experiments for comparing defect-detection techniques, Empirical Software Engineering: An International Journal 1(3) (1996) 241-277.
29. A. Marcus and J. Maletic, Recovering documentation-to-source code traceability links using latent semantic indexing, in Proc. 25th Int. Conf. on Software Engineering 2003, 2003, pp. 125-135.
30. J. Matthias, Requirements tracing, Communications of the ACM 41(12), 1998.
31. T. Mundie and F. Hallsworth, Requirements analysis using SuperTrace PC, in Proc. American Society of Mechanical Engineers (ASME) for the Computers in Engineering Symposium at the Energy & Environmental Expo 1995, 1995.
32. R. Pierce, A requirements tracing tool, in Proceedings of the Software Quality Assurance Workshop on Functional and Performance Issues, 1978.
33. B. Ramesh, Factors influencing requirements traceability practice, Communications of the ACM 41(12) (1998) 37-44.
34. B. Ramesh and M. Jarke, Toward reference models for requirements traceability, IEEE Trans. on Software Engineering 27(1) (2001) 58-93.
35. S. E. Robertson, The probabilistic character of relevance, Information Processing & Management 13(4) (1977) 247-251.
36. J. Rumbaugh, M. Blah, W. Premerlani, F. Eddy, and W. Lorensen, Object-Oriented Modeling and Design, Prentice-Hall, 1991.
37. G. Spanoudakis, A. Zisman, E. Perez-Minana, and P. Krause, Rule-based generation of requirements traceability relations, Journal of Systems and Software 72(2) (2004) 105-127.
38. T. Tsumaki and Y. Morisawa, A framework of requirements tracing using uml, in Proceedings of the Seventh Asia-Pacific Software Engineering Conference 2000, 2000, pp. 206-213.
39. R. Watkins and M. Neal, Why and how of requirements tracing, IEEE Software 11(4) (1994) 104-106.
40. C. Wohlin, P. Runeson, M. Host, M. C. Ohlsson, B. Regnell, and A. Wesslon, Experimentation in Software Engineering - An Introduction, Kluwer Academic Publishers, 2000.
41. A. Zisman, G. Spanoudakis, E. Perez-Minana, and P. Krause, Towards a traceability approach for product family requirements, in Proc. 3rd ICSE Workshop on Software Product Lines: Economics, Architectures and Implications, 2002.