This Article 
 Bibliographic References 
 Add to: 
Event-Based Traceability for Managing Evolutionary Change
September 2003 (vol. 29 no. 9)
pp. 796-810
Jane Cleland-Huang, IEEE Computer Society

Abstract—Although the benefits of requirements traceability are widely recognized, the actual practice of maintaining a traceability scheme is not always entirely successful. The traceability infrastructure underlying a software system tends to erode over its lifetime, as time-pressured practitioners fail to consistently maintain links and update impacted artifacts each time a change occurs, even with the support of automated systems. This paper proposes a new method of traceability based upon event-notification and is applicable even in a heterogeneous and globally distributed development environment. Traceable artifacts are no longer tightly coupled but are linked through an event service, which creates an environment in which change is handled more efficiently, and artifacts and their related links are maintained in a restorable state. The method also supports enhanced project management for the process of updating and maintaining the system artifacts.

[1] J.D. Palmer, Traceability Software Requirements Eng., R.H. Thayer and M. Dorfman, eds., 1997.
[2] M. Jarke, Requirements Traceability Comm. ACM, vol. 41, no. 12, pp. 32-36, Dec. 1998.
[3] O. Gotel and A. Finkelstein, An Analysis of the Requirements Traceability Problem Proc. First Int'l Conf. Requirements Eng., pp. 94-101, 1994.
[4] D. Zowghi and R. Offen, A Logical Framework for Modeling and Reasoning about the Evolution of Requirements Proc. Third IEEE Symp. Requirements Eng., Jan. 1997.
[5] R.C. Sugden and M.R. Strens, Strategies, Tactics, and Methods for Handling Change Proc. IEEE Symp. and Workshop Eng. of Computer Based Systems, pp. 457-462, Mar. 1996.
[6] M.R. Strens and R.C. Sugden, Change Analysis: A Step Towards Meeting the Challenge of Changing Requirements Proc. IEEE Symp. and Workshop Eng. of Computer Based Systems, Mar. 1996.
[7] B. Boehm, Software and Its Impact: A Quantitative Assessment Datamation, vol. 19, pp. 48-59, May 1973.
[8] R.K. Fjelstad and W.T. Hamlen, Application Program Maintenance Study Report to Our Respondents technical report, IBM Corporation, DP Marketing Group, 1986.
[9] E. Bersoff, V. Henderson, and S. Siegel, Software Configuration Management. Prentice-Hall, 1980.
[10] P. Devanbu et al., “LaSSIE: A Knowledge‐Based Software Information System,” Comm. ACM, May 1991, pp. 34‐49.
[11] J. Martin and C. McClure, Software Maintenance: The Problem and its Solution.Englewood Cliffs, N.J.: Prentice Hall, 1983.
[12] S. Dart, Concepts in Configuration Management Systems Proc. Third Int'l Software Configuration Management Workshop, pp. 1-18, June 1991.
[13] R. Pressman, Software Engineering, A Practitioner's Approach, fifth ed. McGraw-Hill, 2001.
[14] K. Weidenhaupt, K. Pohl, M. Jarke, and P. Haumer, "Scenarios in System Development: Current Practice," IEEE Software, pp. 34-45, Mar./Apr. 1998.
[15] G. Antoniol, G. Casazza, and A. Cimitile, Traceability Recovery by Modeling Programmer Behavior Proc. Seventh IEEE Working Conf. Reverse Eng., pp. 240-247, Nov. 2000.
[16] L. James, Automatic Requirements Specification Update Processing from a Requirements Management Tool Perspective Proc. IEEE Workshop Eng. of Computer-Based Systems, 1997.
[17] O. Gotel and A. Finkelstein, Contribution Structures Proc. Second IEEE Int'l Symp. Requirements Eng., 1995.
[18] O. Gotel, Contribution Structures for Requirements Engineering PhD dissertation, Imperial College of Science, Technology, and Medicine, London, England, 1996.
[19] D. Leffingwell, Calculating Your Return on Investment from More Effective Requirements Management Rational Software Corporation, 1997. Available online at /productswhitepapers .
[20] R. Domges and K. Pohl, Adapting Traceability Environments to Project Specific Needs Comm. ACM, vol. 41, no. 12, pp. 55-62, 1998.
[21] A. Davis, Software Requirements: Analysis&Specification, Prentice-Hall, Englewood Cliffs, N.J., 1990.
[22] B. Ramesh and M. Jarke, Toward Reference Models for Requirements Traceability IEEE Trans. Software Eng., vol. 27, no. 1, pp. 58-92, Jan. 2001.
[23] H. Kaindle, The Missing Link in Requirements Engineering ACM SIGSOFT Software Eng. Notes, vol. 18, no. 2, pp. 30-39, 1993.
[24] P. Kruchten, The Rational Unified Process: An Introduction, 2nd ed., Addison-Wesley, Reading, Mass., 2000.
[25] M. Glinz, A Lightweight Approach to Consistency of Scenarios and Class Models Proc. Fourth Int'l Conf. Requirements Eng., 2000.
[26] F. Pinhero and J. Goguen, "An Object-Oriented Tool for Tracing Requirements," IEEE Software, Mar. 1996, pp. 52-64.
[27] J. Cooke and R. Stone, A Formal Development Framework and Its Use to Manage Software Production Tools and Techniques for Maintaining Traceability During Design, IEEE Colloquium, Computing and Control Division, Professional Group C1 (Software Eng.), Digest Number: 1991/180, December 2, pp. 10/1 1991.
[28] Draft Recommendation Z.URN: Languages for Telecommunication Applications User Requirement Notation Nov. 2000.
[29] E. Tryggeseth and O. Nytrø, Dynamic Traceability Links Supported by a System Architecture Description Proc. IEEE Int'l Conf. Software Maintenance, Oct. 1997.
[30] B. Azelborn, Building a Better Traceability Matrix with DOORS Telelogic INDOORS US, 2000.
[31] A. Lapeyre, The Four Eras of Requirements Traceability Telelogic INDOORS Europe, 1999.
[32] Rational Software Corporation, Use Case Management with Rational Rose®and Rational RequisitePro® available online at , 2001.
[33] I. Spence and L. Probasco, Traceability Strategies for Managing Requirements with Use Cases Rational Software White Paper, 1999, 022701. jsp.
[34] SE Tools Taxonomy Requirements Traceability Tools Int'l Council Systems Eng., available online athttp://www.incose. org/toolstooltax.html , 2002.
[35] S. Gupta, J. Hartkopf, and S. Ramaswamy, Event Notifier: A Pattern of Event Notification Java Report, vol. 3, no. 7, 1998, available online at notifier .
[36] E. Gamma et al., Design Patterns: Elements of Object-Oriented Software, Addison-Wesley, Reading, Mass., 1994.
[37] D.L. Parnas, On Criteria to Be Used in Decomposing Systems into Modules Comm. ACM, vol. 14, no. 1, pp. 221-227, Apr. 1972.
[38] Niklaus Wirth, "Program Development by Stepwise Refinement," Comm. ACM, vol. 14, p. 221, Apr. 1971.
[39] J. Cleland-Huang, Robust Requirements Traceability for Supporting Evolutionary and Speculative Change PhD dissertation, Univ. of Illinois at Chicago, Mar. 2002.
[40] EvE, an Event-Driven Distributed Workflow Execution Engine available online at: eve.html, 1999.
[41] Geppert and D. Tombros, Event-Based Distributed Workflow Execution with EVE Proc. iFiP Int'l Conf. Distributed Systems Platforms and Open Distributed Processing (MIDDLEWARE '98), Sept. 1998.
[42] TRAMS: Transactions and Active Database Mechanisms for Workflow Management available online athttp://www.ifi. trams.html, 2000.
[43] SEAMAN: Software Engineering with Active Mechanisms available online at SEAMAN/, 1997.
[44] SWORDIES: Swiss Workflow in Distributed Environments available online at SWORDIES index.html, 2000.
[45] C. Green, D. Luckham, R. Balzer, T. Cheatham, and C. Rich, Report on a Knowledge-Based Software Assistant Readings in Artificial Intelligence and Software Eng., C. Rich, and R. Waters, eds., Morgan Kaufmann, 1986.
[46] W.L. Johnson, M.S. Feather, and D.H. Harris, The KBSA Requirements/Specification Facet: ARIES Proc. Sixth Knowledge-Based Software Eng. Conf., pp. 57-66, Sept. 1991.
[47] W.L. Johnson, M.S. Feather, and D.R. Harris, "Representation and Presentation of Requirements Knowledge," IEEE Trans. Software Eng., pp. 853-869, vol. 18, Oct. 1992.
[48] M. DeBellis, K. Miriyala, and W.C. Sasso, Demonstration Description: The KBSA Concept Demonstration System Proc. Seventh Knowledge-Based Software Engineering Conference (KBSE '92), W.L. Johnson, ed., Sept. 1992.
[49] M. DeBellis, K. Miriyala, S. Bhat, W.C. Sasso, and 0. Rambow, Final Report: Knowledge-Based Software Assistant Concept Demonstration System Technical report CDRL AO07, Government Contract F30602-89-C-0160, Oct. 1992.
[50] W.L. Johnson and M. Feather, "Building An Evolution Transformation Library," Proc. 12th Int'l Conf. Software Eng., pp. 238-248, Nice, France, IEEE CS Press, Mar. 1990.
[51] V. Ambriola, R. Conradi, and A. Fuggetta, “Assessing Process-Centered Environments,” ACM Trans. Software Eng. and Methodology, vol. 6, no. 3, July 1997.
[52] K. Pohl, K. Weidenhaupt, R. Domges, P. Haumer, M. Jarke, and R. Klamma, PRIME Toward Process-Integrated Modeling Environments ACM Trans. Software Eng. and Methodology, vol. 8, no. 4, pp. 343-410, Oct. 1999.
[53] M. Dowson, Consistency Maintenance in Process Sensitive Environments Proc. Process Sensitive Software Eng. Architectures Workshop, Sept. 1992.
[54] K. Pohl, Process Centered Requirements Engineering. John Wiley and Sons Ltd., 1996.
[55] K. Pohl and K. Weidenhaupt, A Contextual Approach for Process-Integrated Tools Proc. Sixth European Software Eng. Conf. (ESEC/FSE '97), M. Jazayeri and H. Schauer, eds., 1997.
[56] J. Cleland-Huang, C.K. Chang, and Y. Ge, Supporting Event Based Traceability through High-Level Recognition of Change Events IEEE Proc. Int'l Computer Software and Applications Conf. (COMPSAC), Aug. 2002.
[57] D. Barnard, G. Clarke, and N. Duncan, Tree-to-Tree Correction for Document Trees Technical Report 95-372, Dept. of Computing and Information Science, Queen's Univ., Kingston, Ontario, Canada, 1995, available online at TechReports/ Reports 1995-372.pdf.
[58] S. Selkow, The Tree-to-Tree Editing Problem Information Processing Letters, vol. 6, no. 6, pp. 184-186, Dec. 1977.
[59] J. Cleland-Huang, C.K. Chang, H. Kim, and A. Balakrishnan, Requirements Based Dynamic Metrics in Object-Oriented Systems Proc. Fifth IEEE Int'l Symp. Requirements Eng., pp. 212-219, Aug. 2001.
[60] J. Cleland-Huang, C.K. Chang, H. Hu, J. Kumar, G. Sethi, and J. Xia, Requirements Driven Impact Analysis of System Performance Proc. IEEE Joint Requirements Eng. Conf., pp. 289-296, Sept. 2002.
[61] J. Cleland-Huang, C.K. Chang, and J. Wise, Automating Performance Related Impact Analysis through Event Based Traceability to be published.
[62] J. Conklin and M.L. Begeman, gIBIS: A Tool for All Reasons J. Am. Soc. for Information Science, pp. 200-213, May 1989.
[63] J. Lee, SIBYL: A Qualitative Decision Management System Artificial Intelligence at MIT: Expanding Frontiers, P. Winston and S. Shellard, eds., pp. 105-133, 1990.
[64] J. Lee, SIBYL: A Tool for Managing Group Decision Rationale Proc. Computer Supported Cooperative Work (CSCW '90), 1990.
[65] A. MacLean, R.M. Young, and T.P. Moran, Design Rationale: The Argument Behind the Artifact Proc. Human Factors in Computing Systems (CHI '89), 1989.
[66] A. MacLean, R.M. Young, V. Bellotti, and T. Moran, Questions, Options, and Criteria: Elements of Design Space Analysis Human-Computer Interaction, vol. 6, nos. 3 and 4, pp. 201-250, 1991.
[67] F. Liu, Notification Processing Event Based Traceability Master Project Report, Univ. of Illinois at Chicago, Mar. 2001.
[68] M-Net: Meeting Net Online Demo available athttp:/icse.cs., 2000.
[69] EBT Online Demo available athttp:/, 2003.

Index Terms:
Change management, traceability, requirements management, evolutionary change, software maintenance, impact analysis.
Jane Cleland-Huang, Carl K. Chang, Mark Christensen, "Event-Based Traceability for Managing Evolutionary Change," IEEE Transactions on Software Engineering, vol. 29, no. 9, pp. 796-810, Sept. 2003, doi:10.1109/TSE.2003.1232285
Usage of this product signifies your acceptance of the Terms of Use.