The DOI matches its Crossref record; 11 of the 11 references it cites were found in a registry or an index.
Concern graphs: finding and describing concerns using structural program dependencies
Abstract
Many maintenance tasks address concerns, or features, that are not well modularized in the source code comprising a system. Existing approaches available to help software developers locate and manage scattered concerns use a representation based on lines of source code, complicating the analysis of the concerns. In this paper, we introduce the Concern Graph representation that abstracts the implementation details of a concern and makes explicit the relationships between different parts of the concern. The abstraction used in a Concern Graph has been designed to allow an obvious and inexpensive mapping back to the corresponding source code. To investigate the practical tradeoffs related to this approach, we have built the Feature Exploration and Analysis tool (FEAT) that allows a developer to manipulate a concern representation extracted from a Java system, and to analyze the relationships of that concern to the code base. We have used this tool to find and describe concerns related to software change tasks. We have performed case studies to evaluate the feasibility, usability, and scalability of the approach. Our results indicate that Concern Graphs can be used to document a concern for change, that developers unfamiliar with Concern Graphs can use them effectively, and that the underlying technology scales to industrial-sized programs.
Overview
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Integrity signals
Registry
Cites
Statistics
Verification
Claims the paper makes
The claims and statistics of this paper haven’t been checked yet.
Run the check — free, no account needed. It reads the open-access text and checks the sources it cites.
Self-check
Percentages, sums and reported differences re-computed from the paper’s own numbers.
The self-check needs the paper’s full text.
Citations
Cites
Weiser, M. (1984) · IEEE Transactions on Software Engineering · doi:10.1109/tse.1984.5010248 · Cited by 3,204
SMALLTALK-80: the interactive programming environment
Goldberg, A. (1984) · HAL (Le Centre pour la Communication Scientifique Directe) · Cited by 718
Software Change Impact Analysis
Arnold, R. S. (1996) · Medical Entomology and Zoology · Cited by 665
Seesoft-a tool for visualizing line oriented software statistics
Eick, S. C., Steffen, J. L., & Sumner, E. E. (1992) · IEEE Transactions on Software Engineering · doi:10.1109/32.177365 · Cited by 616
Optimization of Object-Oriented Programs Using Static Class Hierarchy Analysis
Dean, J., Grove, D., & Chambers, C. (2007) · Lecture Notes in Computer Science · doi:10.1007/3-540-49538-x_5 · Cited by 610
On the Criteria To Be Used in Decomposing Systems into Modules
Parnas, D. L. (2002) · Software Pioneers · doi:10.1007/978-3-642-59412-0_26 · Cited by 306
The C information abstraction system
Chen, Y.-F., Nishimoto, M. Y., & Ramamoorthy, C. V. (1990) · IEEE Transactions on Software Engineering · doi:10.1109/32.48940 · Cited by 278
Case study of feature location using dependence graph
Chen, K., & Rajlich, V. (2002) · Proceedings IWPC 2000. 8th International Workshop on Program Comprehension · doi:10.1109/wpc.2000.852498 · Cited by 247
Efficient and precise modeling of exceptions for the analysis of Java programs
Choi, J.-D., Grove, D., Hind, M., et al. (1999) · ACM SIGPLAN-SIGSOFT Workshop on Program Analysis for Software Tools and Engineering (PASTE) · doi:10.1145/316158.316171 · Cited by 134
Exploiting the map metaphor in a tool for software evolution
Griswold, W. G., Yuan, J. J., & Kato, Y. (2001) · doi:10.5555/381473.381501 · Cited by 95
Cited by
Ko, A. J., Myers, B. A., Coblenz, M. J., & Aung, H. H. (2006) · IEEE Transactions on Software Engineering · doi:10.1109/tse.2006.116 · Cited by 685
Feature location in source code: a taxonomy and survey
Dit, B., Revelle, M., Gethers, M., & Poshyvanyk, D. (2013) · Journal of Software: Evolution and Process · doi:10.1002/smr.567 · Cited by 583
Granularity in software product lines
Kästner, C., Apel, S., & Kuhlemann, M. (2008) · Proceedings of the 13th international conference on Software engineering - ICSE '08 · doi:10.1145/1368088.1368131 · Cited by 497
An information retrieval approach to concept location in source code
Marcus, A., Sergeyev, A., Rajlich, V., & Maletic, J. I. (2005) · 11th Working Conference on Reverse Engineering · doi:10.1109/wcre.2004.10 · Cited by 455
Using task context to improve programmer productivity
Kersten, M., & Murphy, G. C. (2006) · Proceedings of the 14th ACM SIGSOFT international symposium on Foundations of software engineering · doi:10.1145/1181775.1181777 · Cited by 452
Self-citation
Metadata
- Authors
- Robillard, M. P., & Murphy, G. C.
- Venue
- Proceedings of the 24th international conference on Software engineering - ICSE '02
- Publisher
- ACM Press
- Published
- 2002
- Pages
- 406
- ISSN
- 0270-5257 (ISSN-L)
- OpenAlex
- W2118944299
- Cited by
- 287
- References
- 11
- Type
- conference abstract
- Language
- en
- Open access
- closed
About these checks
Registry, retraction, Cites and statistics results are computed, not judged, with one exception: a printed reference that no index lists is read once by a model before it counts as a citation error. Claims are extracted by a model and kept only when their quote appears verbatim in the text; each cited source is then checked, with a model’s help, for whether it says what the claim relies on. Those verdicts can be wrong — read the claim’s quote and the cited source before relying on one.
Statistics and arithmetic are recomputed, not judged.
Confidence bands are shown only for fields calibrated on our annotated test set. None is calibrated yet, so no band is shown.
What counts as a claim ›How we measure confidence ›How we check this ›
Are you an author, or do you see a problem with this page? Request a review
How to cite
Cite CoChat for the checks on this page, and the paper for its own findings.
- This page
- CoChat. (2026). Citation check: Concern graphs: finding and describing concerns using structural program dependencies. https://app.cochat.ai/papers/10.1145/581339.581390
- The paper
- Robillard, M. P., & Murphy, G. C. (2002). Concern graphs: finding and describing concerns using structural program dependencies. Proceedings of the 24th international conference on Software engineering - ICSE '02. https://doi.org/10.1145/581339.581390
Data sources
Bibliographic data: Semantic Scholar, OpenAlex, Crossref.
Contains information from the Semantic Scholar Academic Graph Datasets, made available under the ODC Attribution License (ODC-BY 1.0).
Semantic Scholar’s data is described in: Kinney, R., et al. (2023). The Semantic Scholar Open Data Platform. arXiv:2301.10140.