ICSE

This keynote highlights areas of significant accomplishments in traceability research and asks the question of "where next?" It describes forward looking projects of the Center of Excellence for Software Traceability (CoEST) and raises some of the ...

Requirements-to-source-code traceability employs information retrieval (IR) methods to automatically link requirements to the source code that implements them. A crucial step in this process is indexing, where partial and important information from the ...

Software development can achieve interesting benefits through the use of requirements traceability, including improved program comprehension, easier maintenance, component reuse, impact analysis, and measure of project progress and completeness. On the ...

The challenges of implementing successful and cost-effective traceability have created a compelling research agenda that has addressed a broad range of traceability related issues, ranging from qualitative studies of traceability users in industry to ...

Traceability link recovery is an active research area in software engineering with a number of open research questions and challenges, due to the substantial costs and challenges associated with software maintenance. We propose Traceclipse, an Eclipse ...

Traceability links can be recovered using data mined from a revision control system, such as CVS, and an issue tracking system, such as Bugzilla. Existing approaches to recover links between a bug and the methods changed to fix the bug rely on the ...

The complexity of environments faced by dynamically adaptive systems (DAS) means that the RE process will often be iterative with analysts revisiting the system specifications based on new environmental understanding product of experiences with ...

Traceability is considered an important activity during the development of software systems. Despite the various classifications that have been proposed for different types of traceability relations, there is still a lack of standard semantic ...

Analyzing candidate traceability links is a difficult, time consuming and error prone task, as it usually requires a detailed study of a long list of software artifacts of various kinds. One option to alleviate this problem is to select the most ...

We present the process and methods applied in undertaking the Traceability Challenge in addressing Grand Challenge C-GC1 - Trace recovery. The Information Retrieval methods implemented in REquirementsTRacing On target .NET (RETRO.NET) were applied to ...

Most log files are of one format - a flat file with the events of execution recorded one after the other. Each line in the file contains at least a timestamp, a combination of one or more event identifiers, and the actual log message with information of ...

This paper posits that a theoretical model of analyst effort in tracing tasks is necessary to assist with study of the analyst. Specifically, it is clear from prior work by numerous research groups that the important factors in such a model are: the ...

In 1993, Goguen published a research note addressing the social issues in Requirements Engineering. He identified in the requirements process three major social groups: the client organization; the requirements team; and the development team. However, ...

The paper advocates for the induction of eye tracking technology in software traceability and takes a position that the use of eye tracking metrics can contribute to several software traceability tasks. The authors posit that the role of eye tracking is ...

Tagging offers a traceability mechanism for software development by connecting artifacts in a meaningful way. Our integrated courseware, SEREBRO, provides a framework of tools that capture conversation and artifact creation and modification throughout ...

Numerous trace retrieval algorithms incorporate the standard tf-idf (term frequency, inverse document frequency) technique to weight various terms. In this paper we address Grand Challenge C-GC1 by comparing the effectiveness of computing idf based only ...