Abstract
Requirement change occurs during the entire software lifecycle, which is not only inevitable but also necessary. However, uncontrolled requirement change will lead to a huge waste of time and effort. Most studies about the change impact analysis assume changes take place in code, which results in the analysis only at the source code level and ignoring the requirement change is the fundamental cause. This paper introduces a Requirement Centric Traceability (RCT) approach to analyze the change impact at the requirement level. The RCT combines with the requirement interdependency graph and dynamic requirement traceability to identify the potential impact of requirement change on the entire system in late phase. This approach has been successfully applied to a real-life project, and the benefits and lessons learned will also be discussed.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Preview
Unable to display preview. Download preview PDF.
Similar content being viewed by others
References
Bohner, S.A., Arnold, R.S.: Software change impact analysis. IEEE Computer Society Press, Los Alamitos (1996)
Weiser, M.: Program slices: formal, psychological, and practical investigations of an automatic program abstraction method. PhD thesis, University of Michigan (1979)
Law, J., Rothermel, G.: Whole Program Path-Based Dynamic Impact Analysis. In: ICSE 2003, Portland, Oregon (2003)
Tip, F.: A Survey of Program Slicing Techniques. J. Programming Languages 3(3), 121–189 (1995)
Hassine, J., Rilling, J., Hewitt, J., Dssouli, R.: Change Impact Analysis for Requirement Evolution using Use Case Maps. In: Proc. of the 8th Int. Workshop on Principles of Software Evolution, pp. 81–90 (2005)
Maryam, S., Jameleddine, H., Juergen, R.: Modification Analysis Support at the Requirements Level. In: IWPSE 2007 (2007)
Baeza-Yates, R., Ribeiro-Neto, B.: Modern Information Retrieval. Pearson Education, London (1999)
Antoniol, G., Canfora, G., Casazza, G., De Lucia, A., Merlo, E.: Recovering Traceability Links between Code and Documentation. IEEE Transaction on Software Engineering, 970–983 (2002)
Pohl, K.: Process-Centered Requirements Engineering. John Wiley & Sons, Chichester (1996)
Ramesh, B., Jarke, M.: Toward Reference Models for Requirements Traceability. IEEE Transactions on Software Engineering 27(1), 58–93 (2001)
Robinson, W.N., Pawlowski, S.D., Volkov, V.: Requirements Interaction Management, GSU CIS Working Paper 99-7, Department of Computer Information Systems, Georgia State of University, Atlanta (1999)
Dahlstedt, A.G., Persson, A.: Requirements Interdependencies - Moulding the State of Research into a Research Agenda. In: Ninth International Workshop on Requirements Engineering: Foundation for Software Quality in conjunction with CAiSE 2003 (2003)
Hayes, J.H., Dekhtyar, A., Sundaram, S.K.: Advancing Candidate Link Generation for Requirements Tracing: The Study of Methods. IEEE Transaction on Software Engineering, 4–19 (2006)
Cleland-Huang, J., Settimi, R., Duan, C., Zou, X.: Utilizing Supporting Evidence to Improve Dynamic Requirements Traceability. In: Proceedings of the 13th IEEE International Requirements Engineering Conference (RE 2005), pp. 135–144 (2005)
Google Translate, http://www.google.com/translate_t
WordNet, http://wordnet.princeton.edu/
Author information
Authors and Affiliations
Editor information
Rights and permissions
Copyright information
© 2008 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Li, Y., Li, J., Yang, Y., Li, M. (2008). Requirement-Centric Traceability for Change Impact Analysis: A Case Study. In: Wang, Q., Pfahl, D., Raffo, D.M. (eds) Making Globally Distributed Software Development a Success Story. ICSP 2008. Lecture Notes in Computer Science, vol 5007. Springer, Berlin, Heidelberg. https://doi.org/10.1007/978-3-540-79588-9_10
Download citation
DOI: https://doi.org/10.1007/978-3-540-79588-9_10
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-79587-2
Online ISBN: 978-3-540-79588-9
eBook Packages: Computer ScienceComputer Science (R0)