CocoViz with ambient audio software exploration

Boccuzzo, Sandro; Gall, Harald C.

doi:10.1109/icse.2009.5070558

Cited by 7 publications

(5 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The research in tools for utilizing music to debug programs (Vickers and Alty 2003;Boccuzzo and Gall 2009) and developer environments for non-sighted programmers (Stefik 2008) are based on the concept of sonification (Cohen 1994), i.e., turning non-musical data into musical data to aid its manipulation or understanding.…”

Section: Initial Conceptualizationmentioning

confidence: 99%

Toward a Musical Programming Language

Kirke

2017

Guide to Unconventional Computing for Music

View full text Add to dashboard Cite

This chapter introduces the concept of programming using music, also known as tone-based programming (TBP). There has been much work on using music and sound to debug code, and also as a way of help people with sight problems to use development environments. This chapter, however, focuses on the use of music to actually create program code, or the use of music as program code. The issues and concepts of TBP are introduced by describing the development of the programming language IMUSIC.

show abstract

Section: Initial Conceptualizationmentioning

confidence: 99%

Toward a Musical Programming Language

Kirke

2017

Guide to Unconventional Computing for Music

View full text Add to dashboard Cite

show abstract

“…Besides CodeCity, in the EvoSpaces project, S. Boccuzzo [52]- [54] designed the CocoViz tool, which integrated audio into a 3-D common space metaphor to represent concepts such as code smells or design erosion. CocoViz was focused on supporting the understanding of software structures and evolution, and helping answer common software comprehension questions.…”

Section: B Program Comprehension Tools Using 3-d City Metaphorsmentioning

confidence: 99%

Source Code Revision History Visualization Tools: Do They Work and What Would it Take to Put Them to Work?

Liu

2014

IEEE Access

View full text Add to dashboard Cite

Source code revision history visualization tools have been around for over two decades. Yet, they have not become a mainstream tool in a typical programmer's toolbox and are not typically available in intergraded development environments. So, do they really work? And if they do, what would it take to put them to work? This paper seeks to answer these two questions through experiments, surveys, and interviews. A source code history visualization tool named TeamWATCH was implemented to visualize subversion code repositories. Two comparative controlled experiments were conducted to evaluate the effectiveness of TeamWATCH. The experimental results showed that the subjects using TeamWATCH spent less time than subjects using the command-line subversion client and TortoiseSVN in answering the same set of questions regarding source code revision history. In addition, surveys and interviews were conducted to identify obstacles in adopting source code history visualization tools. Collectively, the results show that source code history visualization tools do bring value to programmers. Key obstacles to wider adoption in practice include nontrivial overhead in using the tools and perceived complexity in visualization.

show abstract

“…Mueller et al [219] use a small multi-touch table to explore software modelling with CRC cards. Boccuzzo and Gall adapted their 3D software exploration tool, CocoViz [40], to multi-touch tables [41]. Soro et al [308] compared observations of user behaviour in pair programming performed at a traditional desktop computer versus a multi-touch table.…”

Section: Collaborative Software Development and Visualizationmentioning

confidence: 99%

Collaborative Software Visualization in Co-located Environments

Anslow¹

View full text Add to dashboard Cite

<p>Most software visualization systems and tools are designed from a single-user perspective and are bound to the desktop and IDEs. These design decisions do not allow users to analyse software collaboratively or to easily interact and navigate visualizations within a co-located environment at the same time. This thesis presents an exploratory study of collaborative software visualization using multi-touch tables in a co-located environment. The thesis contributes a richer understanding of how pairs of developers make use of shared visualizations on large multi-touch tables to gain insight into the design of software systems. We designed a collaborative software visualization application, called Source-Vis, that contained a suite of 13 visualization techniques adapted for multi-touch interaction. We built two large multi-touch tables (28 and 48 inches) following existing hardware designs, to explore and evaluate SourceVis. We then conducted both qualitative and quantitative user studies, culminating in a study of 44 professional software developers working in pairs. We found that pairs preferred joint group work, used a variety of coupling styles, and made many transitions between coupling and arrangement styles. For collaborative group work we recommend designing for joint group work over parallel individual work, supporting a flexible variety of coupling styles, and supporting fluid transitions between coupling and arrangement styles. We found that the preferred style for joint group work was closely coupled and arranged side by side. We found some global functionally was not easily accessible. We found some of the user interactions and visual interface elements were not designed consistently. For the design of collaborative software visualizations we recommend designing visualizations for closely coupled arrangements with rotation features, providing functionality in the appropriate locality, and providing consistent user interactions and visual interface design. We found sometimes visualization windows overlapped each other and text was hard to read in windows. We found when pairs were performing joint group work the size of the table was appropriate but not for parallel individual. We found that because the table could not differentiate between different simultaneous users that some pair interactions were limited. For the design of multi-touch tables we recommend providing a high resolution workspace, providing appropriate table space, and differentiating between simultaneous user interactions.</p>

show abstract

CocoViz with ambient audio software exploration

Cited by 7 publications

References 16 publications

Toward a Musical Programming Language

Toward a Musical Programming Language

Source Code Revision History Visualization Tools: Do They Work and What Would it Take to Put Them to Work?

Collaborative Software Visualization in Co-located Environments

Contact Info

Product

Resources

About