Many of the approaches that analyze software evolution consider a static perspective of a system. Static analysis approaches focus on the evolution of static software entities such as packages, classes and methods. Without knowledge of the roles software entities play in system features, it is difficult to interpret the motivation behind changes and extensions in the code. To tackle this problem, we propose an approach to software evolution analysis that exploits the relationships between features and software entities. Our definition of a feature is a unit of observable behavior of a software system. We define history measurements that summarize the evolution of software entities from a feature perspective. We show how we use our feature p...
The histories of software systems hold useful information when reasoning about the systems at hand o...
Interesting information and Meta-information about software systems can be extracted by analyzing th...
Software change histories are results of incremental updates made by developers. As a byproduct of t...
Features encapsulate the domain knowledge of a software system and thus are valuable sources of info...
Features encapsulate the domain knowledge of a software system and thus are valuable sources of info...
Software developers are often faced with the task of maintaining or extending large and complex appl...
Abstract. The analysis of the evolution of software systems is a useful source of information for a ...
Software analysis and its diachronic sibling, software evolution analysis, rely heavily on data comp...
Previous taxonomies of software evolution have focused on the purpose of the change (i.e., the why) ...
Coping with huge amounts of data is one of the major problems in the context of software evolution. ...
Software developers are constantly required to modify and adapt features of an application in respon...
Understanding the phases and styles of evolution of software systems can provide valuable insight in...
Previous taxonomies of software evolution have focused on the purpose of the change (i.e., the why) ...
Analyzing historical information can show how a software system evolved into its current state, whic...
One of the characteristics of large software systems is that they evolve over time. Evolution patter...
The histories of software systems hold useful information when reasoning about the systems at hand o...
Interesting information and Meta-information about software systems can be extracted by analyzing th...
Software change histories are results of incremental updates made by developers. As a byproduct of t...
Features encapsulate the domain knowledge of a software system and thus are valuable sources of info...
Features encapsulate the domain knowledge of a software system and thus are valuable sources of info...
Software developers are often faced with the task of maintaining or extending large and complex appl...
Abstract. The analysis of the evolution of software systems is a useful source of information for a ...
Software analysis and its diachronic sibling, software evolution analysis, rely heavily on data comp...
Previous taxonomies of software evolution have focused on the purpose of the change (i.e., the why) ...
Coping with huge amounts of data is one of the major problems in the context of software evolution. ...
Software developers are constantly required to modify and adapt features of an application in respon...
Understanding the phases and styles of evolution of software systems can provide valuable insight in...
Previous taxonomies of software evolution have focused on the purpose of the change (i.e., the why) ...
Analyzing historical information can show how a software system evolved into its current state, whic...
One of the characteristics of large software systems is that they evolve over time. Evolution patter...
The histories of software systems hold useful information when reasoning about the systems at hand o...
Interesting information and Meta-information about software systems can be extracted by analyzing th...
Software change histories are results of incremental updates made by developers. As a byproduct of t...