Concern graphs: finding and describing concerns using structural program dependencies
By Martin P. Robillard, Gail C. Murphy. Proceedings of the 24th International Conference on Software Engineering. ICSE 2002, 2002
386 citations recorded by the source corpus.
Subfields: Information Systems, Software
View Paper: https://www.semanticscholar.org/paper/1770bf20b5b789742603cecb27f00e1aefd4b6dd
How researchers see this paper
The researchers whose trusted networks rank it highest, strongest advocate first. Every researcher gets a different order.
In Information Systems
- Denys Poshyvanyk
- Christian Kästner
- Sven Apel
- Andrian Marcus
- Gunter Saake
- Vaclav Rajlich
- Gail C. Murphy
- Bogdan Dit
In Software
- Christian Kästner
- Sven Apel
- Gail C. Murphy
- Htet Htet Aung
- Denys Poshyvanyk
- Gunter Saake
- Amy J. Ko
- Andrian Marcus
Citations in the corpus
- Feature location in source code: a taxonomy and survey (2013, background): “FEAT allows developers to visualize the Concern Graphs, to explore the Concern Graph and examine the source code associated with the program elements of the graph, and to allow developers to alter the Concern Graph by adding or removing program elements and relations.”
- An Exploratory Study of How Developers Seek, Relate, and Collect Relevant Information during Software Maintenance Tasks (2006, methodology): “…including ways of representing task contexts [41], [43], tools that enable developers to manually build a task context by selecting program elements [42], and methods of automatically inferring the relevant task context based on a developer’s investigations in a development environment [44],…”
- Using task context to improve programmer productivity (2006, background): “For example, a Concern Graph [23] represents the key structure of code contributing to a concern, whereas JQuery [15] and CAT [10] refer to concerns in terms of queries across the code.”
- Granularity in software product lines (2008, background): “The navigation support is in line with prior approaches of concern graphs [41] and the map metaphor [14] that choose tool support over complex modular implementations.”
- An information retrieval approach to concept location in source code (2004, methodology): “Robillard et al [27] [28] built the FEAT tool for feature separation using concern graphs.”
- Feature-Oriented Software Product Lines (2013, background): “For yet other concerns of the system that are currently not configurable, no tracing information may be present in the source code; in such cases, tracing links can be extracted manually or with semi-automatic feature-location tools (Biggerstaff et al. 1993; Robillard and Murphy 2002; Poshyvanyk et ”