ACM Home Page
Please provide us with feedback. Feedback
An exploration of how comments are used for marking related code fragments
Full text PdfPdf (91 KB)
Source International Conference on Software Engineering archive
Proceedings of the 2005 workshop on Modeling and analysis of concerns in software table of contents
St. Louis, Missouri
SESSION: Modeling and Analysis of Concerns in Software (MACS) table of contents
Pages: 1 - 4  
Year of Publication: 2005
ISBN:1-59593-119-8
Also published in ...
Authors
Annie T. T. Ying  IBM Watson Research Center, Hawthorne, NY
James L. Wright  IBM Watson Research Center, Hawthorne, NY
Steven Abrams  IBM Watson Research Center, Hawthorne, NY
Publisher
ACM  New York, NY, USA
Bibliometrics
Downloads (6 Weeks): 2,   Downloads (12 Months): 17,   Citation Count: 0
Additional Information:

abstract   references   index terms   collaborative colleagues  

Tools and Actions: Review this Article  
DOI Bookmark: Use this link to bookmark this Article: http://doi.acm.org/10.1145/1083125.1083141
What is a DOI?

ABSTRACT

A software developer performing a change task to a system very often has to examine a concern that is scattered across the source code of the system. Although many mechanisms attempt to alleviate the problem of dealing with scattered code, many software developers are still using more ad-hoc approaches to mark related code. In this paper, we explore how developers use comments to mark related code. We found that developers use two basic kinds of conventions to mark related code in comments: by explicitly stating relationships in the comment and by using similar comments in related code elements. These conventions have several major issues. However, we observe that using comments to mark related code fragments offers several benefits. We hope that our observations can give insights into building better tool support for scattered code fragments.


REFERENCES

Note: OCR errors may be found in this Reference List extracted from the full text article. ACM has opted to expose the complete List rather than only correct and linked references.

 
1
Eclipse task tags website. http://127.0.0.1:55317/help/index.jsp?topic=/org.eclipse.jdt.doc.user/reference/refpreferences-task-tags.htm.
 
2
 
3
 
4
G. Kiczales, J. Lamping, A. Menhdhekar, C. Maeda, C. Lopes, J.-M. Loingtier, and J. Irwin. Aspect-oriented programming. In European Conference on Object-Oriented Programming, pages 220--242, 1997.
5
6

Collaborative Colleagues:
Annie T. T. Ying: colleagues
James L. Wright: colleagues
Steven Abrams: colleagues