It is common, especially in large software systems, for developers to change code without updating its associated comments due to their unfamiliarity with the code or due to time ...
In the current trend of software engineering, software systems are viewed as clusters of overlapping structures representing various concerns, covering heterogeneous artifacts lik...
Evolutionary annotations are descriptions of how source code evolves over time. Typical source comments, given their static nature, are usually inadequate for describing how a pro...
This report describes some characteristics of the development team of PostgreSQL that were uncovered by analyzing the history of its software artifacts as recorded by the projectâ...
In software evolution research logical coupling has extensively been used to recover the hidden dependencies between source code artifacts. They would otherwise go lost because of...
ArgoUML uses both CVS and Bugzilla to keep track of bugï¬xing activities since 1998. A common practice is to reference source code changes resolving a bug stored in Bugzilla by i...
Versioned and bug-tracked software systems provide a huge amount of historical data regarding source code changes and issues management. In this paper we deal with impact analysis...
Software may contain functionality that does not align with its architecture. Such cross-cutting concerns do not exist from the beginning but emerge over time. By analysing where ...
Open Source Software (OSS) projects provide a unique opportunity to gather and analyze publicly available historical data. The Postgres SQL server, for example, has over seven yea...
Christian Bird, Alex Gourley, Premkumar T. Devanbu...