Analysis of signature change patterns

ABSTRACT

Software continually changes due to performance improvements, new requirements, bug fixes, and adaptation to a changing operational environment. Common changes include modifications to data definitions, control flow, method/function signatures, and class/file relationships. Signature changes are notable because they require changes at all sites calling the modified function, and hence as a class they have more impact than other change kinds.We performed signature change analysis over software project histories to reveal multiple properties of signature changes, including their kind, frequency, and evolution patterns. These signature properties can be used to alleviate the impact of signature changes. In this paper we introduce a taxonomy of signature change kinds to categorize observed changes. We report multiple properties of signature changes based on an analysis of eight prominent open source projects including the Apache HTTP server, GCC, and Linux 2.5 kernel.

REFERENCES

• 1: M. M. Lehman, "Rules and Tools for Software Evolution Planning and Management," Proc. Int'l Workshop on Feedback and Evolution in Software and Business Processes (FEAST 2000), Imperial College, London, July 10--12, 2000.
• 2: David Chenho Kung , Jerry Gao , Pei Hsia , F. Wen , Yasufumi Toyoshima , Cris Chen, Change Impact Identification in Object Oriented Software Maintenance, Proceedings of the International Conference on Software Maintenance, p.202-211, September 01, 1994
• 3: Steve Counsell , Youssef Hassoun , Roger Johnson , Keith Mannock , Emilia Mendes, Trends in Java code changes: the key to identification of refactorings?, Proceedings of the 2nd international conference on Principles and practice of programming in Java, June 16-18, 2003, Kilkenny City, Ireland
• 4: J. Bevan, "Kenyon Project Homepage," 2005 http://kenyon.dforge.cse.ucsc.edu
• 5: B. Behlendorf et al., "Subversion Project Homepage," 2005 http://subversion.tigris.org/
• 6: T. Zimmermann and P. Weißgerber, "Preprocessing CVS Data for Fine-Grained Analysis," Proc. MSR 2004, Edinburgh, Scotland, 2004, pp. 2--6.
• 7: Daniel S. Hirschberg, Algorithms for the Longest Common Subsequence Problem, Journal of the ACM (JACM), v.24 n.4, p.664-675, Oct. 1977 [doi>10.1145/322033.322044]
• 8: Qiang Tu , Michael W. Godfrey, An Integrated Approach for Studying Architectural Evolution, Proceedings of the 10th International Workshop on Program Comprehension, p.127, June 27-29, 2002

INDEX TERMS

Primary Classification:
  D. Software
  D.2 SOFTWARE ENGINEERING
      D.2.8 Metrics
          Subjects: Product metrics

Additional Classification:
  K. Computing Milieux
  K.6 MANAGEMENT OF COMPUTING AND INFORMATION SYSTEMS
      K.6.3 Software Management
          Subjects: Software maintenance

General Terms:
Experimentation, Measurement

Keywords:
signature change patterns, software evolution, software evolution path