1 / 7

Signature Change Analysis

Signature Change Analysis. Sunghun Kim, Jim Whitehead, Jennifer Bevan {hunkim, ejw, jbevan}@cs.ucsc.edu University of California, Santa Cruz. Biological and Software Evolution. v1. v2. v2. Biological and Software Evolution. v1. v2. v2. Biological and Software Evolution.

aubrey-cash
Télécharger la présentation

Signature Change Analysis

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Signature Change Analysis Sunghun Kim, Jim Whitehead, Jennifer Bevan {hunkim, ejw, jbevan}@cs.ucsc.edu University of California, Santa Cruz

  2. Biological and Software Evolution

  3. v1 v2 v2 Biological and Software Evolution

  4. v1 v2 v2 Biological and Software Evolution • Can we shape software evolution path? • LOC • Number of Changes • Structural Changes • Signature Changes

  5. Found Signature Change properties • The most common signature change kinds are complex data type, parameter addition, parameter ordering, and parameter deletion. • More than half of function signatures never change. About 90% of function signatures change less than three times. • A function’s signature changes after every 5-15 function body changes. • A project’s average number of parameters per function remains relatively constant over time. • Functions typically have parameter lists with 1, 2, or 3 parameters. • Weak correlations between signature change and other changes including LOC and function body changes. • Each project has its own signature change patterns, and the pattern can be discovered after analyzing the first 1000 to 1500 revisions. • Probability of a change kind depends on previous changes.

  6. Future Work • Signature change analysis on OOP (Java) • The results presented here are based on a procedural programming language (C) open source projects: Apache HTTP 1.3, Apache HTTP 2.0 , Apache Portable Runtime, APR utility, CVS, GCC, and Subversion • Find OOP signature change properties and compare the with those from a procedural language • Changes inside Struct/Class • Variable addition/deletion • Variable renaming • Method addition/deletion

  7. Signature Change Analysis Sunghun Kim, Jim Whitehead, Jennifer Bevan {hunkim, ejw, jbevan}@cs.ucsc.edu University of California, Santa Cruz

More Related