This Article 
 Bibliographic References 
 Add to: 
A Scenario-Driven Approach to Trace Dependency Analysis
February 2003 (vol. 29 no. 2)
pp. 116-132

Abstract—Software development artifacts—such as model descriptions, diagrammatic languages, abstract (formal) specifications, and source code—are highly interrelated where changes in some of them affect others. Trace dependencies characterize such relationships abstractly. This paper presents an automated approach to generating and validating trace dependencies. It addresses the severe problem that the absence of trace information or the uncertainty of its correctness limits the usefulness of software models during software development. It also automates what is normally a time consuming and costly activity due to the quadratic explosion of potential trace dependencies between development artifacts.

[1] M. Abi-Antoun, J. Ho, and J. Kwan, “Inter-Library Loan Management System: Revised Life-Cycle Architecture,” technical report, Center for Software Eng., Univ. of Southern California, 1999.
[2] G. Antoniol, G. Canfora, and A. De Lucia, “Maintaining Traceability During Object-Oriented Software Evolution: A Case Study,” Proc. IEEE Int'l Conf. Software Maintenance, 1998.
[3] B.W. Boehm et al., Software Cost Estimation with COCOMO II, Prentice-Hall, Upper Saddle River, N.J., 2000.
[4] B. Boehm, A. Egyed, J. Kwan, and R. Madachy, “Using the WinWin Spiral Model: A Case Study,” Computer, pp. 33-44, July 1998.
[5] G. Booch, J. Rumbaugh, and I. Jacobson, The Unified Modeling Language User Guide. Addison Wesley, 1999.
[6] S. Clarke, W. Harrison, H. Ossher, and P. Tarr, “Subject-Oriented Design: Towards Improved Alignment of Requirments, Design, and Code,” Proc. 1999 ACM SIGPLAN Conf. Object-Oriented Programming, Systems, Languages, and Applications, pp. 325-339, Oct. 1998.
[7] A. Egyed and P. Gruenbacher, “Automating Requirements Traceability—Beyond the Record and Replay Paradigm,” Proc. 17th Int'l Conf. Automated Software Eng. (ASE), pp. 163-171, Sept. 2002.
[8] A. Egyed, “Heterogeneous View Integration and its Automation 2000,” PhD thesis, Univ. of Southern California, 2000.
[9] O. Gotel and A. Finkelstein, An Analysis of the Requirements Traceability Problem Proc. First Int'l Conf. Requirements Eng., pp. 94-101, 1994.
[10] D. Graham and M. Fewster, Software Test Automation. Addison-Wesley, 1999.
[11] P. Haumer, K. Pohl, K. Weidenhaupt, and M. Jarke, “Improving Reviews by Extending Traceability,” Proc. 32nd Annual Hawaii Int'l Conf. System Sciences (HICSS), 1999.
[12] T. Hughes and C. Martin, “Design Traceability of Complex Systems,” Proc. Fourth Ann. Symp. Human Interaction with Complex Systems, pp. 37-41, 1998.
[13] J. Jackson, “A Keyphrase Based Traceability Scheme,” IEE Colloquium on Tools and Techniques for Maintaining Traceability During Design, pp. 2-1-2/4, 1991.
[14] I. Khriss, M. Elkoutbi, and R. Keller, “Automating the Synthesis of UML Statechart Diagrams from Multiple Collaboration Diagrams,” Proc. Conf. Unified Modeling Language, June 1998.
[15] K. Koskimies, T. Männistö, T. Systä, and J. Tuomi, Automated Support for OO Software IEEE Software, vol. 15, no. 1, pp. 87-94, Jan./Feb. 1998.
[16] D.B. Lange and Y. Nakamura, “Object-Oriented Program Tracing and Visualization,” Computer, vol. 30, no. 5, pp. 63-70, May 1997.
[17] G.C. Murphy, D. Notkin, and K. Sullivan, “Software Reflexion Models: Bridging the Gap Between Source and High-Level Models,” Proc. Third ACM SIGSOFT Symp. Foundations of Software Eng., pp. 18-28, Oct. 1995.
[18] F. Pinhero and J. Goguen, "An Object-Oriented Tool for Tracing Requirements," IEEE Software, Mar. 1996, pp. 52-64.
[19] J. Rumbaugh, I. Jacobson, and G. Booch, The Unified Modeling Language Reference Manual. Addison-Wesley, 1999.
[20] G. Snelting and F. Tip, “Reengineering Class Hierarchies using Concept Analysis,” Proc. Sixth SIGSOFT Symp. Foundations of Software Eng., pp. 99-110, Nov. 1998.
[21] P. Tarr, H. Osher, W. Harrison, and S.M. Sutton Jr., “N Degrees of Separation: Multi-Dimensional Separation of Concerns,” Proc. 21st Int'l Conf. Software Eng. (ICSE 21), pp. 107-119, May 1999.
[22] R. Watkins and M. Neal, “Why and How of Requirements Tracing,” IEEE Software, vol. 11, no. 7, pp. 104-106, July 1994.

Index Terms:
Traceability, test scenarios, software models, Unified Modeling Language (UML).
Alexander Egyed, "A Scenario-Driven Approach to Trace Dependency Analysis," IEEE Transactions on Software Engineering, vol. 29, no. 2, pp. 116-132, Feb. 2003, doi:10.1109/TSE.2003.1178051
Usage of this product signifies your acceptance of the Terms of Use.