TraceME: Traceability Management in Eclipse

Bavota, Gabriele; Colangelo, Luigi; Lucia, Andrea De; Fusco, Sabato; Oliveto, Rocco; Panichella, Annibale

doi:10.1109/icsm.2012.6405343

Cited by 21 publications

(20 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Many tools use a combination of multiple methods. For example, a static analysis may be used to assign source code artifacts their documentation; then a user must manually confirm or reject the suggested links [9].…”

Section: Persistence Internalmentioning

confidence: 99%

“…Stacksplorer [21] visualizes method's callers in a column on the left of the code editor view, callees in the right one. ConcernMapper [14] eMoose [15] Pollicino [16] SE-Editor [17] Spotlight [18] TagSEA [19] DepDigger [12] RegViz [20] Stacksplorer [21] Traceclipse [22] TraceME [9] GUITA [23] Impromptu HUD [11] in situ profiler [1] Senseo [13] sparklines [24] CnP [25] HeatMaps [26] iTrace [8] Deep Intellisense [27] Miler [28] Rationalizer [29] 101companies [30] Code Bubbles [31] CoderChrome [10] Graphical overlays may be shown to visually connect the current method definition with the left column and method calls in the source code view to items in the right column. Traceclipse [22] and TraceME [9] are traceability management recovery tools.…”

Section: B Codementioning

confidence: 99%

See 1 more Smart Citation

Labeling Source Code with Metadata: A Survey and Taxonomy

Sulír¹,

Porubãn²

2017

Proceedings of the 2017 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

Source code is a primary artifact where programmers are looking when they try to comprehend a program. However, to improve program comprehension efficiency, tools often associate parts of source code with metadata collected from static and dynamic analysis, communication artifacts and many other sources. In this article, we present a systematic mapping study of approaches and tools labeling source code elements with metadata and presenting them to developers in various forms. We selected 25 from more than 2,000 articles and categorized them. A taxonomy with four dimensions-source, target, presentation and persistence-was formed. Based on the survey results, we also identified interesting future research challenges.

show abstract

Section: Persistence Internalmentioning

confidence: 99%

Section: B Codementioning

confidence: 99%

Labeling Source Code with Metadata: A Survey and Taxonomy

Sulír¹,

Porubãn²

2017

Proceedings of the 2017 Federated Conference on Computer Science and Information Systems

View full text Add to dashboard Cite

show abstract

“…When we talk about traceability in software development, we often refer to Requirement Traceability, which is an activity that allows creating links between and within software artefacts [19]. The definition of Requirement Traceability (RT), according to O. C. Z. Gotel and A. C. W. Finkelstein, is the ability to describe and follow the life of a requirement, in both a forward and backward direction [20].…”

Section: Information Technologymentioning

confidence: 99%

“…They have proposed a set of traceability pairs (relation criteria and factors) to define all the variables required in an analysis and hence establish the link between the final result and all the sources used. Moreover, traceability can strengthen the link between the requirements put in place, the specifications and the artefacts throughout the phases of a software development, using Requirements Traceability Matrix [19].…”

Section: Uses Of Traceabilitymentioning

confidence: 99%

“…As detailed in [19], "TraceMe" is an Eclipse module-based plug-in, that can be used to capture and maintain traceability links between different types of artefacts. According to the authors, this plug-in allows the software engineer to define different artefacts categories, capture traceability links between the defined artefacts categories and manage the traceability information through XML files.…”

Section: Graphsmentioning

confidence: 99%

See 1 more Smart Citation

An Overview of Traceability: Towards a general multi-domain model

Souali¹,

Rahmaoui²,

Ouzzif³

2017

Adv. sci. technol. eng. syst. j.

View full text Add to dashboard Cite

Traceability for some people, is merely a tool to keep a history over something important that happened in the past. For others, is has no added value to their actual processes or products. In fact, it is becoming more and more valued. Traceability is still a vast area of research and an undiscovered field that if it is well used and managed, can provide a set of critical information or lead to something bigger. Many researches are still working to enhance its use and its integration by providing solutions to help users better manage and control their different elements (products, source code, documents, requirements, specifications, etc.)

show abstract

CDTC: Automatically establishing the trace links between class diagrams in design phase and source code

Chen,

Zhang,

Lian

2023

Softw Pract Exp

View full text Add to dashboard Cite

ContextThe UML class diagram is commonly used to model functional structures and software code structures in both the preliminary and detailed design stages. And the abstraction level of UML class diagrams is usually higher than that of source code. Usually, there is a lack of trace links between these class diagrams and the source code, which may cause difficulties in understanding the source code, and affect the software evolution and maintenance.ObjectiveThe main goal of this article is to establish the trace links between highly abstracted UML class diagrams in the design phase and source code, and eventually help practitioners better understand source code.MethodWe propose an approach for the automated trace link establishment between UML class diagrams in the design phase and source code. To address the problem of abstraction level gap between them, we extend the UML class diagram by mining the synonymous phrases of class names and deducing the latent missing relationships between classes from multiple design documents. Then we build the trace links with a two‐phase approach including initial construction with fuzzy matching and further optimization by class relationship inference.ResultsExperiments on five open‐source projects show that the recalls of our approach are over 94%, and the F2‐scores are over 88%, with the gains of 30% to 60% than the four baselines.ConclusionOur work can be a reference for establishing the initial trace links between highly‐abstracted UML class diagrams and source code. Towards the higher abstraction of design diagrams, we extend UML class diagrams with the statistical analysis on multiple design documents. To guarantee the quality of trace links, we design a two‐phase approach by obtaining the “full but not good enough” trace links and filtering the “probably wrong” links. Experiments show that the main techniques of our approach behave as important role for tracing between high‐level class diagrams and source code.

show abstract

TraceME: Traceability Management in Eclipse

Cited by 21 publications

References 9 publications

Labeling Source Code with Metadata: A Survey and Taxonomy

Labeling Source Code with Metadata: A Survey and Taxonomy

An Overview of Traceability: Towards a general multi-domain model

CDTC: Automatically establishing the trace links between class diagrams in design phase and source code

Contact Info

Product

Resources

About