Hierarchical abstraction of execution traces for program comprehension

Feng, Yang; Dreef, Kaj; Jones, James A.; Deursen, Arie van

doi:10.1145/3196321.3196343

Cited by 19 publications

(5 citation statements)

References 40 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Moreover, these tools provide only one level of abstraction, not meeting the expectations of the interviewees (see Section 2.5.3) because the important information might be lost by showing only a certain level of detail. Several studies addressed this limitation (Jerding et al 1997;Beschastnikh et al 2020b;Feng et al 2018) by allowing developers to inspect information at different levels of detail. However, these tools do not guide developers in information navigation, e.g., one needs to manually identify the relevant component interactions when analyzing issues with tools that generate sequence diagrams (Jerding et al 1997;Beschastnikh et al 2020b).…”

Section: Log Comprehensionmentioning

confidence: 99%

An interview study about the use of logs in embedded software engineering

Yang

Cuijpers²,

Hendriks³

et al. 2023

Empir Software Eng

View full text Add to dashboard Cite

published version features the final layout of the paper including the volume, issue and page numbers. Link to publication General rightsCopyright and moral rights for the publications made accessible in the public portal are retained by the authors and/or other copyright owners and it is a condition of accessing publications that users recognise and abide by the legal requirements associated with these rights.• Users may download and print one copy of any publication from the public portal for the purpose of private study or research. • You may not further distribute the material or use it for any profit-making activity or commercial gain • You may freely distribute the URL identifying the publication in the public portal.If the publication is distributed under the terms of Article 25fa of the Dutch Copyright Act, indicated by the "Taverne" license above, please follow below link for the End User

show abstract

Section: Log Comprehensionmentioning

confidence: 99%

An interview study about the use of logs in embedded software engineering

Yang

Cuijpers²,

Hendriks³

et al. 2023

Empir Software Eng

View full text Add to dashboard Cite

show abstract

“…EXTRAVIS uses circular bundling and a massive sequence view, and ExplorViz uses the city metaphors. Scalability in software visualization are commonly addressed by using multiple levels of abstraction [19][41].…”

Section: Related Work 71 Program Behavior Comprehensionmentioning

confidence: 99%

ViBERT: Visual Behavior Regression Testing

Zhao¹,

Chen²,

Zhang³

et al. 2020

JVLC

View full text Add to dashboard Cite

Regression testing is a type of software testing that aims at identifying faults caused by code changes. Regression testing is important especially during software evolution and maintenance. As developers integrate programs or make updates to a software system, they need to make sure the changes do not adversely affect other parts of the system. Using dynamic analysis, behavioral regression testing (BERT) is one of the techniques proposed to solve the problem by re-executing test cases that target the affected area. It compares the behavior of a program before and after the changes upon certain test cases. This paper proposes Visual BEhavioral Regression Testing (ViBERT), a visualization approach to comparing the behavioral differences between the new and old versions of a program in regression testing. We build a prototype called SoftLink, a visual environment that shows correlation/difference between two versions of a program behavior. SoftLink displays call graphs of two executions on angled parallel planes in a 3D space, and constructs correlations between them. It provides developers with an intuitive interpretation of the testing results. A case study is presented.

show abstract

“…A step-by-step log of commands executed by a program is called a program trace (or just a trace or tracing). The importance of the traces has been frequently mentioned earlier to both developing program code (Abualese et al, 2017;Fittkau et al, 2015;Feng et al, 2018;Kashima et al, 2015;Kadar et al, 2016;Khoury et al, 2017;Khoury et al, 2019;Perez & Abreu, 2016) and programming education (Aggarwal et al, 2018;Paaßen et al, 2016;Srinivasan et al, 2016;Terada, 2005).…”

Section: Introductionmentioning

confidence: 99%