Proceedings of the 28th International Conference on Program Comprehension 2020
DOI: 10.1145/3387904.3389275
|View full text |Cite
|
Sign up to set email alerts
|

Evaluating a Visual Approach for Understanding JavaScript Source Code

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
5
0

Year Published

2020
2020
2024
2024

Publication Types

Select...
3
3
2

Relationship

0
8

Authors

Journals

citations
Cited by 11 publications
(6 citation statements)
references
References 31 publications
0
5
0
Order By: Relevance
“…To facilitate this process, software visualization tools were suggested. Hunter is a visualization tool for JavaScript applications [21]. It visualizes source code through a set of coordinated views that include a node-link diagram that depicts the dependencies among the components of a system and a tree map that helps programmers to orientate when navigating its structure.…”
Section: Program Understanding Toolsmentioning
confidence: 99%
“…To facilitate this process, software visualization tools were suggested. Hunter is a visualization tool for JavaScript applications [21]. It visualizes source code through a set of coordinated views that include a node-link diagram that depicts the dependencies among the components of a system and a tree map that helps programmers to orientate when navigating its structure.…”
Section: Program Understanding Toolsmentioning
confidence: 99%
“…Visualizations facilitate program comprehension because they provide a graphical view of the software rather than an alphabetical sequence of source code text. To this end, researchers propose several visualizations, such as Hunter [29] which focuses on understanding the dependencies between software artefacts. In their article, Dias et al, use colors to distinguish between file branches as well as the size of the node which corresponds to the number of lines of source code in each file.…”
Section: Related Workmentioning
confidence: 99%
“…Many researchers have investigated the modeling and visualization of dependency graphs [21,17,18,22,30,31,15,23,14,20]. For example, Falke et al suggested a hierarchical graph layout for visualizing the functional dependency graph of software applications; by using a hierarchical layout, users can view the top-level nodes as a first overview and step-wise unfold the nodes on demand to look into details [15].…”
Section: Related Workmentioning
confidence: 99%
“…For example, Falke et al suggested a hierarchical graph layout for visualizing the functional dependency graph of software applications; by using a hierarchical layout, users can view the top-level nodes as a first overview and step-wise unfold the nodes on demand to look into details [15]. Dias et al implemented Hunter, a visual tool that includes node-link diagrams as dependency graphs for understanding JavaScript source code [14]. German used package management files to visualize the dependency graph in the hierarchical layout of three popular applications in Fink, one of the software distribution for macOS, and attempted to identify the use of applications in terms of different types of success [18].…”
Section: Related Workmentioning
confidence: 99%