Understanding where requirements are implemented: The relationship between requirements traces and method calls in code

IEEE International Conference on Software Maintenance, ICSM

Volumn , Issue , 2010, Pages

  Burgstaller, Benedikt ^a   Egyed, Alexander ^a  

^a JOHANNES KEPLER UNIVERSITY LINZ   (Austria)

Author keywords

Call tree; Feature location; Requirements; Traces

Indexed keywords

CALL GRAPHS; CALL TREE; CHANGE MANAGEMENT; CODE UNDERSTANDING; ERROR PRONE TASKS; FEATURE LOCATION; REQUIREMENTS; SOURCE CODES; TRACES;

SOFTWARE ENGINEERING;

COMPUTER SOFTWARE MAINTENANCE;

EID: 78650155928     PISSN: None     EISSN: None     Source Type: Conference Proceeding    
DOI: 10.1109/ICSM.2010.5609699     Document Type: Conference Paper

References (20)

1. B. Ramesh, L. C. Stubbs, and M. Edwards, "Lessons Learned from Implementing Requirements Traceability," Crosstalk - Journal of Defense Software Engineering, vol. 8(4), pp. 11-15, 1995.
2. N. Aizenbud-Reshef, B. T. Nolan, J. Rubin, and Y. Shaham-Gafni, "Model Traceability," IBM Systems Journal, vol. 45(3), pp. 515-526, 2006.
3. M. Deng, R. E. K. Stirewalt, and B. H. C. Cheng, "Retrieval by Construction: a Traceability Technique to Support Verification and Validation of UML Formalizations," Intern. Journal of Software Engineering and Knowledge Eng., vol. 15(5), pp. 837-872, 2005.
4. T. Yue, L. C. Briand, and Y. Labiche, "Automated Traceability Analysis for UML Model Refinements," Journal of Information and Software Technology, vol. 51 pp. 512-527, 2009.
5. M. Lindvall, and K. Sandahl, "Practical Implications of Traceability," Journal on Software - Practice and Experience (SPE), vol. 26(10), pp. 1161-1180, 1996.
6. O. C. Z. Gotel, and A. C. W. Finkelstein, "An Analysis of the Requirements Traceability Problem," in Proc. of the 1st Intern. Conference on Requirements Engineering, 1994, pp. 94-101.
7. J. Cleland-Huang, C. K. Chang, and M. Christensen, "Event-Based Traceability for Managing Evolutionary Change," IEEE Trans. Softw. Eng., vol. 29(9), pp. 796-810, 2003.
8. J. Cleland-Huang, B. Berenbach, S. Clark, R. Settimi, and E. Romanova, "Best Practices for Automated Traceability," Computer, vol. 40(6), pp. 27-35, 2007.
9. G. Antoniol, G. Canfora, G. Casazza, A. De Lucia, and E. Merlo, "Recovering Traceability Links between Code and Documentation," IEEE Transactions on Software Eng. vol. 28(10), pp.970-983, 2002.
10. J. H. Hayes, A. Dekhtyar, S. K. Sundaram, and S. Howard, "Helping Analysts Trace Requirements: An Objective Look," in 12th IEEE International Requirements Engineering Conference, 2004.
11. G. Spanoudakis, A. Zisman, E. Perez-Minana, and P. Krause, "Rulebased generation of requirements traceability relations," Journal of Systems and Software vol. 72(2), pp. 105-127, 2004.
12. M. Marin, A. V. Deursen, and L. Moonen, " Identifying Crosscutting Concerns Using Fan-In Analysis," ACM Transactions on Software Engineering Methodology, vol. 17, pp. 1-37, 2007.
13. M. P. Robillard, and G. Murphy, "Concern Graphs: Finding and Describing Concerns using Structural Program Dependencies," in Proceedings of the 22nd International Conference on Software Engineering (ICSE), Orlando, Florida, 2002, pp. 406-416.
14. P. Tonella, "Using a Concept Lattice of Decomposition Slices for Program Understanding and Impact Analysis," IEEE Transactions on Software Engineering vol. 29(6), pp. 495-509, 2003.
15. C. McMillan, D. Poshyvanyk, and M. Revelle, "Combining Textual and Structural Analysis of Software Artifacts for Traceability Link Recovery," in Proceedings of Workshop on Traceability in Emerging Forms of Software Engineering, Canada, 2009, pp. 41-48.
16. A. V. A. Marc Eaddy, Giuliano Antoniol, Yann-Gaël Guéhéneuc, "CERBERUS: Tracing Requirements to Source Code Using Information Retrieval, Dynamic Analysis, and Program Analysis," in 16th IEEE International Conference on Program Comprehension, Amsterdam, The Netherlands, 2008, pp. 53-62.
17. R. Koschke, and J. Quante, "On dynamic feature location," in Proceedings of the 20th International Conference on Automated software engineering, Long Beach, CA, USA, 2005.
18. A. Egyed, "A Scenario-Driven Approach to Trace Dependency Analysis," IEEE Transactions on Software Engineering vol. 29(2), pp. 116-132, 2003.
19. H. U. Asuncion, F. Francois, and R. N. Taylor, "An end-to-end industrial software traceability tool," in Proceedings of the 6th European Software Engineering Conference and Symposium on the Foundations of Software Engineering, Dubrovnik, Croatia, 2007.
20. O. Gotel, and A. Finkelstein, "Extended Requirements Traceability: Results of an industrial case study," in Proceedings 3rd International Symposium on Requirements Engineering, 1997, pp. 169-178.