2007 4th IEEE International Workshop on Visualizing Software for Understanding and Analysis 2007
DOI: 10.1109/vissof.2007.4290703
|View full text |Cite
|
Sign up to set email alerts
|

CocoViz: Towards Cognitive Software Visualizations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
22
0

Year Published

2009
2009
2022
2022

Publication Types

Select...
3
1
1

Relationship

3
2

Authors

Journals

citations
Cited by 23 publications
(22 citation statements)
references
References 13 publications
0
22
0
Order By: Relevance
“…The feasibility of the CocoViz audio-visual approach was shown in previous work [3]- [5]. With the presented automated software comprehension tasks we selected an exemplary set of common comprehension tasks solvable with a semi-automated workflow (Table I), and showed that we experience a reduced workload by using automated tasks in the software comprehension and exploration context.…”
Section: Case Studies Summarymentioning
confidence: 85%
See 3 more Smart Citations
“…The feasibility of the CocoViz audio-visual approach was shown in previous work [3]- [5]. With the presented automated software comprehension tasks we selected an exemplary set of common comprehension tasks solvable with a semi-automated workflow (Table I), and showed that we experience a reduced workload by using automated tasks in the software comprehension and exploration context.…”
Section: Case Studies Summarymentioning
confidence: 85%
“…Based on whether the interaction needs to reconfigure a comprehension task and / or reperform an algorithm, dedicated actions are taken. For example, an engineer changes the maximal value visible for a mapped metric Number of Attributes in the SV-Mixer [3]. The comprehension task is notified and checks whether the algorithm affected by this changed metric needs to be updated.…”
Section: B Comprehension Tasks During Software Explorationmentioning
confidence: 99%
See 2 more Smart Citations
“…Another visualization uses a house metaphor to visualize software metrics of all classes in a package, as shown in Figure 5. A three-dimensional variation of this visualization was initially presented by Boccuzzo et al [10]. In this metaphor, well-designed classes are meant to be represented by normal looking houses, while classes that do not follow objectoriented design principles are represented by unnaturallylooking houses that are, for example, too narrow or too wide.…”
Section: B Approachmentioning
confidence: 99%