Case Study of Feature Location Using Dependence Graph (2000)
| Venue: | In Proceedings of the 8th International Workshop on Program Comprehension |
| Citations: | 71 - 11 self |
BibTeX
@INPROCEEDINGS{Chen00casestudy,
author = {Kunrong Chen and Václav Rajlich},
title = {Case Study of Feature Location Using Dependence Graph},
booktitle = {In Proceedings of the 8th International Workshop on Program Comprehension},
year = {2000},
pages = {241--249},
publisher = {IEEE Computer Society}
}
Years of Citing Articles
Bookmark
 |
 |
 |
 |
 |
 |
OpenURL
Abstract
Software change requests are often formulated as requests to modify or to add a specific feature or concept. To implement these changes, the features or concepts must be located in the code. In this paper, we describe the scenarios of the feature and concept location. The scenarios utilize a computer-assisted search of software dependence graph. Scenarios are demonstrated by a case study of NCSA Mosaic source code. 1. Introduction In software maintenance and evolution, change requirements are often formulated as requests to modify or to add specific program concepts or features [2, 26]. An example of such a request is "Add a new external viewer to Mosaic web browser". Before any actual change can be made to the system, software programmers must locate the implementation of the concepts ("external viewer") in the source code. Concept location is a process that maps domain concepts to the software components. The input is the maintenance request, expressed in natural language and usin...
