Sciweavers

22 search results - page 1 / 5
» Tracking Concerns in Evolving Source Code: An Empirical Stud...
Sort
View
ICSM
2006
IEEE
13 years 11 months ago
Tracking Concerns in Evolving Source Code: An Empirical Study
The association between the description of a concern (e.g., a feature) and the code that implements it is valuable information that can degrade as the code of a system evolves. We...
Martin P. Robillard
KBSE
2007
IEEE
13 years 11 months ago
Inferring structural patterns for concern traceability in evolving software
As part of the evolution of software systems, effort is often invested to discover in what parts of the source code a feature (or other concern) is implemented. Unfortunately, kn...
Barthélémy Dagenais, Silvia Breu, Fr...
CSMR
2007
IEEE
13 years 11 months ago
How Clones are Maintained: An Empirical Study
Despite the conventional wisdom concerning the risks related to the use of source code cloning as a software development strategy, several studies appeared in literature indicated...
Lerina Aversano, Luigi Cerulo, Massimiliano Di Pen...
ICSE
2010
IEEE-ACM
13 years 2 months ago
Identifying crosscutting concerns using historical code changes
Detailed knowledge about implemented concerns in the source code is crucial for the cost-effective maintenance and successful evolution of large systems. Concern mining techniques...
Bram Adams, Zhen Ming Jiang, Ahmed E. Hassan
WSE
2005
IEEE
13 years 10 months ago
Crosscutting Concerns in J2EE Applications
We explore the evolution benefits of adopting aspects in a J2EE setting by studying crosscutting concerns in a typical J2EE application. To identify these concerns, we take a top...
Ali Mesbah, Arie van Deursen