Tracking and Assessing the Evolution of Scattered Concerns

In this position paper, we describe how we document the implementation of scattered concerns by combining intensional descriptions of relations between program elements and their corresponding extensions for a specific version of a program. We show that this strategy allows us to automatically track the source code implementing a concern as it evolves and to assess the stability of a concern’s implementation. We illustrate these benefits with results obtained from ongoing empirical studies of the evolution of scattered concerns.

[1]  William G. Griswold,et al.  Exploiting the map metaphor in a tool for software evolution , 2001, Proceedings of the 23rd International Conference on Software Engineering. ICSE 2001.

[2]  Rick Kazman,et al.  Architecture, design, implementation , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[3]  Eleni Stroulia,et al.  Recognizing Refactoring from Change Tree , 2003 .

[4]  Martin P. Robillard,et al.  FEAT a tool for locating, describing, and analyzing concerns in source code , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[5]  Kim Mens,et al.  Using intentional source-code views to aid software maintenance , 2003, International Conference on Software Maintenance, 2003. ICSM 2003. Proceedings..

[6]  Robert E. Filman,et al.  What Is Aspect-Oriented Programming , 2001 .

[7]  William G. Griswold,et al.  Getting started with ASPECTJ , 2001, CACM.

[8]  Mark Chu-Carroll,et al.  Coven: brewing better collaboration through software configuration management , 2000, SIGSOFT '00/FSE-8.

[9]  Martin P. Robillard,et al.  Evolving Descriptions of Scattered Concerns , 2005 .

[10]  Martin P. Robillard,et al.  Representing concerns in source code , 2007, TSEM.

[11]  Mark Chu-Carroll,et al.  Supporting aggregation in fine grained software configuration management , 2002, SIGSOFT '02/FSE-10.

[12]  H. Ossher,et al.  Concern modeling in the concern manipulation environment , 2005, MACS@ICSE.

[13]  Marvin V. Zelkowitz,et al.  Experimental Models for Validating Technology , 1998, Computer.

[14]  Elliot Soloway,et al.  Designing documentation to compensate for delocalized plans , 1988, CACM.

[15]  Oscar Nierstrasz,et al.  Finding refactorings via change metrics , 2000, OOPSLA '00.

[16]  Tom Mens,et al.  Maintaining software through intentional source-code views , 2002, SEKE '02.

[17]  Gregor Kiczales,et al.  Aspect-oriented programming , 2001, ESEC/FSE-9.

[18]  Martin P. Robillard,et al.  Concern graphs: finding and describing concerns using structural program dependencies , 2002, Proceedings of the 24th International Conference on Software Engineering. ICSE 2002.