Recovering Traceability Links between Code and Documentation
IEEE Transactions on Software Engineering
Recovering documentation-to-source-code traceability links using latent semantic indexing
Proceedings of the 25th International Conference on Software Engineering
RIPPLES: Tool for Change in Legacy Software
ICSM '01 Proceedings of the IEEE International Conference on Software Maintenance (ICSM'01)
Feed-forward and recurrent neural networks for source code informal information analysis
Journal of Software Maintenance: Research and Practice
Automatically identifying changes that impact code-to-design traceability during evolution
Software Quality Control
| Hi-index | 0.00 |
Software system documentation is usually expressed informally, in natural language and free text. Examples include requirement specifications, design documents, manual pages, system development journals, error logs and related maintenance reports.We propose an approach to establish and maintain traceability links is that programmers use meaningful names for program items, such as functions, variables, types, classes, and methods. We believe that the application-domain knowledge that programmers process when writing the code is often captured by the mnemonics for identifiers; therefore, the analysis of these mnemonics can help to associate high-level concepts with program concepts, and vice-versa. In this paper, the approach is applied to software written in an object-oriented language, namely Java, to trace classes to functional requirements.