Sciweavers

Share
IWPC
2000
IEEE

Tracing Object-Oriented Code into Functional Requirements

12 years 13 days ago
Tracing Object-Oriented Code into Functional Requirements
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. In this paper, the approach is applied to software written in an object-oriented language, namely Java, to trace classes to functional requirements.
Giuliano Antoniol, Gerardo Canfora, Andrea De Luci
Added 31 Jul 2010
Updated 31 Jul 2010
Type Conference
Year 2000
Where IWPC
Authors Giuliano Antoniol, Gerardo Canfora, Andrea De Lucia, Gerardo Casazza, Ettore Merlo
Comments (0)
books