Research indexJournal article
Tracing object-oriented code into functional requirements
Antoniol, Canfora, Casazza and 2 others
7 Nov 2002
Tracing object-oriented code into functional requirements
Antoniol, Canfora, Casazza and 2 others · 2002 · Subscription
The full text is at the publisher
You can read the abstract here, or open it at the publisher.
Abstract
Software system documentation is almost always 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 between source code and free text documents. A premise of our work 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. The approach is applied to software written in an object oriented language, namely Java, to trace classes to functional requirements.